|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 6371 (2011)
|
|
Title:
|
Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks
|
|
|
2.
|
Status of approval:
|
|
|
Approved and published by IETF
|
|
3.
|
Justification for the specific reference:
|
|
|
ITU-T G.8152.1 refers to types of ME as defined in IETF RFC 6371.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=6371
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The category of this RFC is "Informational" with IETF consensus.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
This document was approved and published by IETF
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced draft are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[1] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label/
Switching Architecture", RFC 3031, January 2001./
/
[2] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire Emulation Edge-/
to-Edge (PWE3) Architecture", RFC 3985, March 2005./
/
[3] Nadeau, T., Ed., and C. Pignataro, Ed., "Pseudowire Virtual/
Circuit Connectivity Verification (VCCV): A Control Channel for/
Pseudowires", RFC 5085, December 2007./
/
[4] Bocci, M. and S. Bryant, "An Architecture for Multi-Segment/
Pseudowire Emulation Edge-to-Edge", RFC 5659, October 2009./
/
[5] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed.,/
Sprecher, N., and S. Ueno, "Requirements of an MPLS Transport/
Profile", RFC 5654, September 2009./
/
[6] Agarwal, P. and B. Akyol, "Time To Live (TTL) Processing in/
Multi-Protocol Label Switching (MPLS) Networks", RFC 3443,/
January 2003./
/
[7] Bocci, M., Ed., Vigoureux, M., Ed., and S. Bryant, Ed., "MPLS/
Generic Associated Channel", RFC 5586, June 2009./
/
[8] Bocci, M., Ed., Bryant, S., Ed., Frost, D., Ed., Levrau, L., and/
L. Berger, "A Framework for MPLS in Transport Networks", RFC/
5921, July 2010./
/
[9] Bocci, M., Levrau, L., and D. Frost, "MPLS Transport Profile/
User-to-Network and Network-to-Network Interfaces", RFC 6215,/
April 2011./
/
[10] Frost, D., Ed., Bryant, S., Ed., and M. Bocci, Ed., "MPLS/
Transport Profile Data Plane Architecture", RFC 5960, August/
2010./
/
[11] Vigoureux, M., Ed., Ward, D., Ed., and M. Betts, Ed.,/
"Requirements for Operations, Administration, and Maintenance/
(OAM) in MPLS Transport Networks", RFC 5860, May 2010./
/
[12] Bradner, S. and J. McQuaid, "Benchmarking Methodology for/
Network Interconnect Devices", RFC 2544, March 1999./
/
[13] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., and W./
Weiss, "An Architecture for Differentiated Service", RFC 2475,/
December 1998./
/
[14] ITU-T Recommendation G.806 (01/09), "Characteristics of/
transport equipment - Description methodology and generic/
functionality", January 2009./
/
Informative References/
/
[15] Sprecher, N. and L. Fang, "An Overview of the OAM Tool Set for/
MPLS based Transport Networks", Work in Progress, June 2011./
/
[16] Nichols, K., Blake, S., Baker, F., and D. Black, "Definition of/
the Differentiated Services Field (DS Field) in the IPv4 and/
IPv6 Headers", RFC 2474, December 1998./
/
[17] Grossman, D., "New Terminology and Clarifications for Diffserv",/
RFC 3260, April 2002./
/
[18] Kompella, K., Rekhter, Y., and L. Berger, "Link Bundling in MPLS/
Traffic Engineering (TE)", RFC 4201, October 2005./
/
[19] ITU-T Recommendation G.707/Y.1322 (01/07), "Network node/
interface for the synchronous digital hierarchy (SDH)", January/
2007./
/
[20] ITU-T Recommendation G.805 (03/00), "Generic functional/
architecture of transport networks", March 2000./
/
[21] ITU-T Recommendation Y.1731 (02/08), "OAM functions and/
mechanisms for Ethernet based networks", February 2008./
/
[22] IEEE Standard 802.1AX-2008, "IEEE Standard for Local and/
Metropolitan Area Networks - Link Aggregation", November 2008./
/
[23] Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen, P.,/
Krishnan, R., Cheval, P., and J. Heinanen, "Multi-Protocol Label/
Switching (MPLS) Support of Differentiated Services", RFC 3270,/
May 2002./
/
[24] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport Profile/
(MPLS-TP) Identifiers", RFC 6370, September 2011./
/
[25] Winter, R., Ed., van Helvoort, H., and M. Betts, "MPLS-TP/
Identifiers Following ITU-T Conventions", Work in Progress, July/
2011./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
Reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or to IETF RFCs categorized as Historic or Experimental. Normative references must only be made to IETF RFCs that are Standards Track or to Informational RFCs that have IETF consensus.
|
|
