|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4261 (2005)
|
|
Title:
|
Common Open Policy Service (COPS) Over Transport Layer Security (TLS)
|
|
|
2.
|
Status of approval:
|
|
|
Published as IETF Proposed Standard.
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. Q.3303.1v2 refers to RFC 4261 as the basic protocol on Rw interface
|
|
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=4261
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
|
|
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:
|
|
|
Normative References/
/
[1] RFC 2119 Key words to use in the RFCs, March 1997/
[2] RFC 2748 The COPS (Common Open Policy Service) Protocol, January 2000/
[3] RFC 2753 A Framework for Policy-based Admission Control, January 2000/
[4] RFC 3280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile, April 2002/
[5] RFC 2246 The TLS Protocol Version 1.0, January 1999/
/
Informative References/
/
[1] RFC 2818 HTTP Over TLS, May 2000/
[2] RFC 2595 Using TLS with IMAP, POP3 and ACAP, June 1999/
[3] RFC 2434 Guidelines for Writing an IANA Considerations Section in RFCs, October 1998/
|
|
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):
|
|
|
ftp://ftp.rfc-editor.org/in-notes/rfc4261.txt
|
