|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3931 (2004)
|
|
Title:
|
J. Lau, et. al., Layer Two Tunneling Protocol - Version 3 (L2TPv3), March 2005.
|
|
|
2.
|
Status of approval:
|
|
|
Proposed Standard
|
|
3.
|
Justification for the specific reference:
|
|
|
Technical specifications that use the Internet Protocol will need to reference RFCs.
|
|
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=3931
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
generally stable and well-understood; real implementation desirable but not necessary; no known technical flaws; considered immature; may be changed if problems are found or better solutions are identified; deploying implementation of such standards into a disruption-sensitive environment is not recommended
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
generally stable and well-understood; real implementation desirable but not necessary; no known technical flaws; considered immature; may be changed if problems are found or better solutions are identified; deploying implementation of such standards into a disruption-sensitive environment is not recommended.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and/
Languages", BCP 18, RFC 2277, January 1998./
/
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations section in RFCs", BCP 26, RFC 2434,/
October 1998./
/
[RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6/
Specification", RFC 2473, December 1998./
/
[RFC2661] Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn, G.,/
and Palter, B., "Layer Two Tunneling Layer Two Tunneling/
Protocol (L2TP)", RFC 2661, August 1999./
/
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,/
"Remote Authentication Dial In User Service (RADIUS)", RFC/
2865, June 2000./
/
[RFC3066] Alvestrand, H., "Tags for the Identification of Languages",/
BCP 47, RFC 3066, January 2001./
/
[RFC3193] Patel, B., Aboba, B., Dixon, W., Zorn, G., and Booth, S.,/
"Securing L2TP using IPsec", RFC 3193, November 2001./
/
[RFC3438] Townsley, W., "Layer Two Tunneling Protocol (L2TP) Internet/
Assigned Numbers Authority (IANA) Considerations Update",/
BCP 68, RFC 3438, December 2002./
/
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646",/
STD 63, RFC 3629, November 2003.
|
|
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
|
|
