Committed to connecting the world

  •  
Submarine cables

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : G.8113.2/Y.1372.2 (2015) Amd.1     
  ITU-T A.5 justification information for referenced document IETF RFC 4446 (2006) in draft G.8113.2/Y.1372.2 (2015) Amd.1
1. Clear description of the referenced document:
Name: IETF RFC 4446 (2006)
Title: IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)
2. Status of approval:
Approved by IESG (Internet Engineering Steering Group).
3. Justification for the specific reference:
G.8113.2 require use of codepoints that are defined in this RFC.
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=4446
5. Other useful information describing the "Quality" of the document:
Best current practice BCP 116
6. The degree of stability or maturity of the document:
Best current practice BCP 116
7. Relationship with other existing or emerging documents:
See item 8.
8. Any explicit references within that referenced document should also be listed:
5.1. Normative References/
/
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998./
/
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and Languages", BCP 18, RFC 2277, January 1998./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
/
5.2. Informative References/
/
[CRTL] Martini, L., Ed., Rosen, E., El-Aawar, N., Smith, T., and G. Heron, "Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)", RFC 4447, April 2006./
/
[VCCV] Nadeau, T. and R. Aggarwal, "Pseudo Wire Virtual Circuit Connectivity Verification (VCCV)", Work in Progress, August 2005./
/
[FRAG] Malis, A. and M. Townsley, "PWE3 Fragmentation and Reassembly", Work in Progress, September 2005./
/
[FCS] Malis, A., Allan, D., and N. Del Regno, "PWE3 Frame Check Sequence Retention", Work in Progress, September 2005./
/
[CEP] Malis, A., Pate, P., Cohen, R., Ed., and D. Zelig, "SONET/SDH Circuit Emulation Service Over Packet (CEP)", Work in Progress./
/
[SAToP] Vainshtein, A. Ed. and Y. Stein, Ed. "Structure-Agnostic TDM over Packet (SAToP)", Work in Progress./
/
[FRAME] Martini, L., Ed. and C. Kawa, "Encapsulation Methods for Transport of Frame Relay Over MPLS Networks", Work in Progress./
/
[ATM] Martini, L., Ed., El-Aawar, N., and M. Bocci, Ed., "Encapsulation Methods for Transport of ATM Over MPLS Networks", Work in Progress./
/
[PPPHDLC] Martini, L., Rosen, E., Heron, G. and A. Malis, "Encapsulation Methods for Transport of PPP/HDLC Frames Over MPLS Networks", Work in Progress./
/
[ETH] Martini, L., Rosen, E., El-Aawar, N., and G. Heron, "Encapsulation Methods for Transport of Ethernet Frames Over MPLS Networks", RFC 4448, April 2006./
/
[CESoPSN] Vainshtein, A., Ed., Sasson, I., Metz, E., Frost, T., and P. Pate, "Structure-aware TDM Circuit Emulation Service over Packet Switched Network (CESoPSN)", Work in Progress./
/
[TDMoIP] Stein, Y., Shashoua, R., Insler, R., and M. Anavi, "TDM over IP", Work in Progress, February 2005./
/
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 2001./
/
[SIG] Rosen, E., Luo, W., Davie, B., and V. Radoaca, "Provisioning, Autodiscovery, and Signaling in L2VPNs", Work in Progress, September 2005./
/
[RFC4385] Bryant, S., Swallow, G., Martini, L., and D. McPherson, "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN", RFC 4385, February 2006.
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):
All RFCs are 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.
Note: This form is based on Recommendation ITU-T A.5