홈 > 표준화 개요 > TTA의 표준현황
| 표준번호 | TTAE.IF-RFC5462 | 구표준번호 | |
|---|---|---|---|
| 제개정일 | 2010-12-23 | 총페이지 | 20 |
| 한글표준명 | MPLS 레이블 스택: TC필드 정의 | ||
| 영문표준명 | Multiprotocol Label Switching (MPLS) Label Stack Entry: EXP Field Renamed to Traffic Class Field | ||
| 한글내용요약 | MPLS 프로토콜 스택에는 3비트의 EXP 필드가 있는데, EXP 필드는 “서비스 클래스” 정보를 전달하기 위해 만들어졌으나, 실제 정확한 사용에 대해서는 정의되지 않고, “실험적 사용”을 위해서로만 정의되어 있다. 본 표준은 이 필드의 이름을 트래픽 클래스 필드로 바꾸고, 국내 표준 TTAS.IF-RFC3032, TTAS.IF-RFC3270와 국외 표준 RFC5129의 내용에서 일부를 갱신하여 트래픽 클래스 필드의 사용법을 정의하며, 국내 표준 TTAS.IF-RFC3469, TTAS.IF-RFC4364와 국외 표준 RFC3272, RFC3443, RFC3564, RFC3985, RFC4182, RFC4379, RFC4448, RFC4761의 내용에서 “EXP field”, “Exp bits”, “EXP bits” 혹은 “EXP”로 지칭한 용어를 “TC field”로 변경한다. | ||
| 영문내용요약 | The format of an MPLS label stack entry is defined by RFC 3032 [RFC3032] to include a three-bit field called the "EXP field". The exact use of this field is not defined by RFC 3032, except to state that it is to be "reserved for experimental use".
The EXP field, from the start, was intended to carry "Class of Service" (CoS) information. The field was actually called the "Class of Service field" in early versions of the working group document that was published as RFC 3032. However, at the time that RFC 3032 was published, the exact usage of this "Class of Service" field was not agreed upon and the field was designated as "experimental use"; hence, the name has since been the "EXP field". The designation "for experimental use" has led other Standards Development Organizations (SDOs) and implementors to assume that it is possible to use the field for other purposes. This document changes the name of the field to clearly indicate its use as a traffic classification field. At first, we discussed using the original "CoS field" as the name for the field, but it has been pointed out that this name does not cover the following changes that have occurred with respect to its usage since RFC 3032 was published. This document, hence, uses the name "Traffic Class field (TC field)", which better covers the potential use. The MPLS TC field relates to an MPLS encapsulated packet the same way as the IPv6 TC field relates to an IPv6 encapsulated packet or the IPv4 Precedence field relates to an IPv4 encapsulated packet. The definitions of how the EXP field is used are perfectly clear in RFC 3270 and RFC 5129. However, these RFCs do not explicitly state they update RFC 3032, and this fact was not captured in the RFC repository until after work on this document was started. This document updates RFC 3032, RFC 3270, and RFC 5129 to clarify the intended usage of the TC field. The changes to these RFCs requires some changes to the actual text in those documents; Section 2 explains the changes. This document also updates several other RFCs; see Section 2.4. For these documents, the change is limited to changing the name of the Label Stack entry field. |
||
| 국제표준 | |||
| 관련파일 |
 TTAE.IT-RFC5462_2009-1185.pdf
| ||
