|
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:
|
|
|
G.9961 includes the hooks to authenticate G.hn interfaces by upper layers by encapsulating EAP frames into G.hn frames.
|
|
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=3748
|
|
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:
|
|
|
[RFC1661] Simpson, W., "The Point-to-Point Protocol (PPP)",/
STD 51, RFC 1661, July 1994./
/
[RFC1994] Simpson, W., "PPP Challenge Handshake/
Authentication Protocol (CHAP)", RFC 1994, August/
1996./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to/
Indicate Requirement Levels", BCP 14, RFC 2119,/
March 1997./
/
[RFC2243] Metz, C., "OTP Extended Responses", RFC 2243,/
November 1997./
/
[RFC2279] Yergeau, F., "UTF-8, a transformation format of/
ISO 10646", RFC 2279, January 1998./
/
[RFC2289] Haller, N., Metz, C., Nesser, P. and M. Straw, "A/
One-Time Password System", RFC 2289, February/
1998./
/
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for/
Writing an IANA Considerations Section in RFCs",/
BCP 26, RFC 2434, October 1998./
/
[RFC2988] Paxson, V. and M. Allman, "Computing TCP's/
Retransmission Timer", RFC 2988, November 2000./
/
[IEEE-802] Institute of Electrical and Electronics Engineers,/
"Local and Metropolitan Area Networks: Overview/
and Architecture", IEEE Standard 802, 1990./
/
[IEEE-802.1X] Institute of Electrical and Electronics Engineers,/
"Local and Metropolitan Area Networks: Port-Based/
Network Access Control", IEEE Standard 802.1X,/
September 2001./
Informative References/
/
[RFC793] Postel, J., "Transmission Control Protocol", STD/
7, RFC 793, September 1981./
/
[RFC1510] Kohl, J. and B. Neuman, "The Kerberos Network/
Authentication Service (V5)", RFC 1510, September/
1993./
/
[RFC1750] Eastlake, D., Crocker, S. and J. Schiller,/
"Randomness Recommendations for Security", RFC/
1750, December 1994./
/
[RFC2246] Dierks, T., Allen, C., Treese, W., Karlton, P.,/
Freier, A. and P. Kocher, "The TLS Protocol/
Version 1.0", RFC 2246, January 1999./
/
[RFC2284] Blunk, L. and J. Vollbrecht, "PPP Extensible/
Authentication Protocol (EAP)", RFC 2284, March/
1998./
/
[RFC2486] Aboba, B. and M. Beadles, "The Network Access/
Identifier", RFC 2486, January 1999./
/
[RFC2408] Maughan, D., Schneider, M. and M. Schertler,/
"Internet Security Association and Key Management/
Protocol (ISAKMP)", RFC 2408, November 1998./
/
[RFC2409] Harkins, D. and D. Carrel, "The Internet Key/
Exchange (IKE)", RFC 2409, November 1998./
/
[RFC2433] Zorn, G. and S. Cobb, "Microsoft PPP CHAP/
Extensions", RFC 2433, October 1998./
/
[RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and/
Policy Implementation in Roaming", RFC 2607, June/
1999./
/
[RFC2661] Townsley, W., Valencia, A., Rubens, A., Pall, G.,/
Zorn, G. and B. Palter, "Layer Two Tunneling/
Protocol "L2TP"", RFC 2661, August 1999./
/
[RFC2716] Aboba, B. and D. Simon, "PPP EAP TLS/
Authentication Protocol", RFC 2716, October 1999./
/
[RFC2865] Rigney, C., Willens, S., Rubens, A. and W./
Simpson, "Remote Authentication Dial In User/
Service (RADIUS)", RFC 2865, June 2000./
[RFC2960] Stewart, R., Xie, Q., Morneault, K., Sharp, C.,/
Schwarzbauer, H., Taylor, T., Rytina, I., Kalla,/
M., Zhang, L. and V. Paxson, "Stream Control/
Transmission Protocol", RFC 2960, October 2000./
/
[RFC3162] Aboba, B., Zorn, G. and D. Mitton, "RADIUS and/
IPv6", RFC 3162, August 2001./
/
[RFC3454] Hoffman, P. and M. Blanchet, "Preparation of/
Internationalized Strings ("stringprep")", RFC/
3454, December 2002./
/
[RFC3579] Aboba, B. and P. Calhoun, "RADIUS (Remote/
Authentication Dial In User Service) Support For/
Extensible Authentication Protocol (EAP)", RFC/
3579, September 2003./
/
[RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G. and J./
Roese, "IEEE 802.1X Remote Authentication Dial In/
User Service (RADIUS) Usage Guidelines", RFC 3580,/
September 2003./
/
[RFC3692] Narten, T., "Assigning Experimental and Testing/
Numbers Considered Useful", BCP 82, RFC 3692,/
January 2004./
/
[DECEPTION] Slatalla, M. and J. Quittner, "Masters of/
Deception", Harper-Collins, New York, 1995./
/
[KRBATTACK] Wu, T., "A Real-World Analysis of Kerberos/
Password Security", Proceedings of the 1999 ISOC/
Network and Distributed System Security Symposium,/
http://www.isoc.org/isoc/conferences/ndss/99//
proceedings/papers/wu.pdf./
/
[KRBLIM] Bellovin, S. and M. Merrit, "Limitations of the/
Kerberos authentication system", Proceedings of/
the 1991 Winter USENIX Conference, pp. 253-267,/
1991./
/
[KERB4WEAK] Dole, B., Lodin, S. and E. Spafford, "Misplaced/
trust: Kerberos 4 session keys", Proceedings of/
the Internet Society Network and Distributed/
System Security Symposium, pp. 60-70, March 1997./
/
[PIC] Aboba, B., Krawczyk, H. and Y. Sheffer, "PIC, A/
Pre-IKE Credential Provisioning Protocol", Work in/
Progress, October 2002./
/
[IKEv2] Kaufman, C., "Internet Key Exchange (IKEv2)/
Protocol", Work in Progress, January 2004./
/
[PPTPv1] Schneier, B. and Mudge, "Cryptanalysis of/
Microsoft's Point-to- Point Tunneling Protocol",/
Proceedings of the 5th ACM Conference on/
Communications and Computer Security, ACM Press,/
November 1998./
/
[IEEE-802.11] Institute of Electrical and Electronics Engineers,/
"Wireless LAN Medium Access Control (MAC) and/
Physical Layer (PHY) Specifications", IEEE/
Standard 802.11, 1999./
/
[SILVERMAN] Silverman, Robert D., "A Cost-Based Security/
Analysis of Symmetric and Asymmetric Key Lengths",/
RSA Laboratories Bulletin 13, April 2000 (Revised/
November 2001),/
http://www.rsasecurity.com/rsalabs/bulletins//
bulletin13.html./
/
[KEYFRAME] Aboba, B., "EAP Key Management Framework", Work in/
Progress, October 2003./
/
[SASLPREP] Zeilenga, K., "SASLprep: Stringprep profile for/
user names and passwords", Work in Progress, March/
2004./
/
[IEEE-802.11i] Institute of Electrical and Electronics Engineers,/
"Unapproved Draft Supplement to Standard for/
Telecommunications and Information Exchange/
Between Systems - LAN/MAN Specific Requirements -/
Part 11: Wireless LAN Medium Access Control (MAC)/
and Physical Layer (PHY) Specifications:/
Specification for Enhanced Security", IEEE Draft/
802.11i (work in progress), 2003./
/
[DIAM-EAP] Eronen, P., Hiller, T. and G. Zorn, "Diameter/
Extensible Authentication Protocol (EAP)/
Application", Work in Progress, February 2004./
/
[EAP-EVAL] Zorn, G., "Specifying Security Claims for EAP/
Authentication Types", Work in Progress, October/
2002./
[BINDING] Puthenkulam, J., "The Compound Authentication/
Binding Problem", Work in Progress, October 2003./
/
[MITM] Asokan, N., Niemi, V. and K. Nyberg, "Man-in-the-/
Middle in Tunneled Authentication Protocols", IACR/
ePrint Archive Report 2002/163, October 2002,/
http://eprint.iacr.org/2002/163./
/
[IEEE-802.11i-req] Stanley, D., "EAP Method Requirements for Wireless/
LANs", Work in Progress, February 2004./
/
[PPTPv2] Schneier, B. and Mudge, "Cryptanalysis of/
Microsoft's PPTP Authentication Extensions (MS-/
CHAPv2)", CQRE 99, Springer-Verlag, 1999, pp./
192-203./
|
|
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
|
|
