|
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:
|
|
|
Rec. Q.OIP/OIR refers to IETF defined "The tel URI for Telephone Numbers" specified in (1).
|
|
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=3966
|
|
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:
|
|
|
13.1. Normative References/
/
[E.123] International Telecommunications Union, "Notation for/
national and international telephone numbers, e-mail/
addresses and web addresses", Recommendation E.123,/
February 2001./
/
[E.161] International Telecommunications Union, "Arrangement of/
digits, letters and symbols on telephones and other/
devices that can be used for gaining access to a telephone/
network", Recommendation E.161, May 1995./
/
[E.164] International Telecommunications Union, "The international/
public telecommunication numbering plan", Recommendation/
E.164, May 1997./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", RFC 2234, November 1997./
/
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,/
A., Peterson, J., Sparks, R., Handley, M., and E./
Schooler, "SIP: Session Initiation Protocol", RFC 3261,/
June 2002./
/
[T1.703] ANSI, "Allocation of Letters to the Keys of Numeric/
Keypads for Telecommunications", Standard T1.703-1995/
(R1999), 1999./
/
13.2. Informative References/
/
[RFC2368] Hoffman, P., Masinter, L., and J. Zawinski, "The mailto/
URL scheme", RFC 2368, July 1998./
/
[RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifiers (URI): Generic Syntax", RFC 2396,/
August 1998./
/
[RFC2806] Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806,/
April 2000./
/
[RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform/
Resource Identifiers (URI) Dynamic Delegation Discovery/
System (DDDS) Application (ENUM)", RFC 3761, April 2004./
/
[RFC3187] Hakala, J. and H. Walravens, "Using International Standard/
Book Numbers as Uniform Resource Names", RFC 3187, October/
2001./
/
[RFC3191] Allocchio, C., "Minimal GSTN address format in Internet/
Mail", RFC 3191, October 2001./
/
[RFC3192] Allocchio, C., "Minimal FAX address format in Internet/
Mail", RFC 3192, October 2001./
/
[RFC3219] Rosenberg, J., Salama, H., and M. Squire, "Telephony/
Routing over IP (TRIP)", RFC 3219, January 2002./
/
[T.50] International Telecommunications Union, "International/
Reference Alphabet (IRA) (Formerly International Alphabet/
No. 5 or IA5) - Information technology - 7-bit coded/
character set for information interchange", Recommendation/
T.50, 1992./
|
|
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
|
|
