|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2712 (1999)
|
|
Title:
|
Addition of Kerberos Cipher Suites to Transport Layer Security (TLS)
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track - Proposed Standard (December 1999)
|
|
3.
|
Justification for the specific reference:
|
|
|
H.248.91 defines requirements and profile guidelines for TLS bearer traffic, which includes Cipher Suites used for TLS.
|
|
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=2726
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Standards Track
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards Track RFC, used since more than 10 years in the real world.
|
|
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:
|
|
|
[1] Dierks, T. and C. Allen, "The TLS Protocol, Version 1.0", RFC/
2246, January 1999./
/
[2] Kohl J. and C. Neuman, "The Kerberos Network Authentication/
Service (V5)", RFC 1510, September 1993./
|
|
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
|
