|
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:
|
|
|
Q.CDIV refers to overall specification of IETF RFC 4694 (2006) for CDIV requirements.
|
|
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=4694
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
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:
|
|
|
9.1 Normative References /
/
[E164] ITU-T Recommendation E.164, "The international public /
telecommunication numbering plan," May 1997. /
/
[RFC2119] S. Bradner, RFC2119, "Key words for use in RFCs to /
Indicate Requirement Levels," March 1997. /
/
[RFC3966] H. Schulzrinne, RFC3966, "The tel URI for Telephone /
Numbers," December 2004. /
/
[RFC4234] D. Crocker and P. Overell, RFC4234, "Augmented BNF for /
Syntax Specifications: ABNF," October 2005. /
/
9.2 Informative References /
/
[H323] ITU-T Recommendation H.323, "Packet-Based Multimedia /
Communications Systems," November 2000. /
/
[RFC3261] J. Rosenberg, et al., RFC3261, "SIP: Session Initiation /
Protocol," June 2002. /
/
[RFC3482] M. Foster, T. McGarry and J. Yu, RFC3482, "Number /
Portability in the GSTN: An Overview," February 2003. /
/
[TELREG] C. Jennings and V. Gurbani, "The Internet Assigned Number /
Authority (IANA) tel Uniform Resource Identifier (URI) /
Parameter Registry", draft-ietf-iptel-tel-reg-02.txt (work /
in progress), May 2006./
|
|
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
|
