|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.cso refers to Layer Two Tunneling Protocol "L2TP", IETF RFC, August 1999.
|
|
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=2661
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[DSS1] ITU-T Recommendation, "Digital subscriber Signaling System/
No. 1 (DSS 1) - ISDN user-network interface layer 3/
specification for basic call control", Rec. Q.931(I.451),/
May 1998/
/
[KPS] Kaufman, C., Perlman, R., and Speciner, M., "Network/
Security: Private Communications in a Public World",/
Prentice Hall, March 1995, ISBN 0-13-061466-1/
/
[RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791, September/
1981./
/
[RFC1034] Mockapetris, P., "Domain Names - Concepts and Facilities",/
STD 13, RFC 1034, November 1987./
/
[RFC1144] Jacobson, V., "Compressing TCP/IP Headers for Low-Speed/
Serial Links", RFC 1144, February 1990./
/
[RFC1661] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51,/
RFC 1661, July 1994./
/
[RFC1662] Simpson, W., "PPP in HDLC-like Framing", STD 51, RFC 1662,/
July 1994./
/
[RFC1663] Rand, D., "PPP Reliable Transmission", RFC 1663, July 1994./
/
[RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC/
1700, October 1994. See also:/
http://www.iana.org/numbers.html/
[RFC1990] Sklower, K., Lloyd, B., McGregor, G., Carr, D. and T./
Coradetti, "The PPP Multilink Protocol (MP)", RFC 1990,/
August 1996./
/
[RFC1994] Simpson, W., "PPP Challenge Handshake Authentication/
Protocol (CHAP)", RFC 1994, August 1996./
/
[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G./
and E. Lear, "Address Allocation for Private Internets",/
BCP 5, RFC 1918, February 1996./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2138] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote/
Authentication Dial In User Service (RADIUS)", RFC 2138,/
April 1997./
/
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and/
Languages", BCP 18, RFC 2277, January 1998./
/
[RFC2341] Valencia, A., Littlewood, M. and T. Kolar, "Cisco Layer Two/
Forwarding (Protocol) L2F", RFC 2341, May 1998./
/
[RFC2401] Kent, S. and R. Atkinson, "Security Architecture for the/
Internet Protocol", RFC 2401, November 1998./
/
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations Section in RFCs", BCP 26, RFC 2434,/
October 1998./
/
[RFC2637] Hamzeh, K., Pall, G., Verthein, W., Taarud, J., Little, W./
and G. Zorn, "Point-to-Point Tunneling Protocol (PPTP)",/
RFC 2637, July 1999./
/
[STEVENS] Stevens, W. Richard, "TCP/IP Illustrated, Volume I The/
Protocols", Addison-Wesley Publishing Company, Inc., March/
1996, ISBN 0-201-63346-9/
|
|
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):
|
|
|
None
|
|
