|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
This is an approved IETF Standards Track RFC, published in January 2005.
|
|
3.
|
Justification for the specific reference:
|
|
|
Z.140.10 Recommendation transfers strings of the type @url tag with the "http" URI scheme. RFC 3986 provides the definition of URI syntax which is used in TTCN. Including the entire RFC in the Z.140.10 Recommendation would not be appropriate as only a part of the RFC is relevant to TTCN.
|
|
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=3982
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This document obsoletes [RFC2396], which merged "Uniform Resource Locators" [RFC1738] and "Relative Uniform Resource Locators" [RFC1808] in order to define a single, generic syntax for all URIs. It obsoletes [RFC2732], which introduced syntax for an IPv6 address
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
This document is considered to be stable.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
IETF RFC 1738 "Uniform Resource Locators (URL)", December 1994.
IETF RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1, June 1999
IETF RFC 2818, HTTP Over TLS, May 2000
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[ASCII] American National Standards Institute, "Coded Character/
Set -- 7-bit American Standard Code for Information/
Interchange", ANSI X3.4, 1986./
/
[RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", RFC 2234, November 1997./
/
[STD63] Yergeau, F., "UTF-8, a transformation format of/
ISO 10646", STD 63, RFC 3629, November 2003./
/
[UCS] International Organization for Standardization,/
"Information Technology - Universal Multiple-Octet Coded/
Character Set (UCS)", ISO/IEC 10646:2003, December 2003./
|
|
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
|
