|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2206 (1997)
|
|
Title:
|
RSVP Management Information Base using SMIv2, Category: standard track, September 1997
|
|
|
2.
|
Status of approval:
|
|
|
Approved by the IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Z.140.10 Recommendation transfers strings of the type @url tag with the "http" URI scheme. RFC 2660 provides the definition of Secure Hyper Text Transfer Protocol for secure transfer 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=2206
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of this referred RFC is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of this referred RFC is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFC are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Rose, M., Editor, "Management Information Base for/
Network Management of TCP/IP-based internets", STD 17,/
RFC 1213, May 1990./
/
[2] Information processing systems - Open Systems/
Interconnection - Specification of Abstract Syntax/
Notation One (ASN.1), International Organization for/
Standardization. International Standard 8824, (December, 1987)./
/
[3] Information processing systems - Open Systems/
Interconnection - Specification of Basic Encoding Rules/
for Abstract Notation One (ASN.1), International/
Organization for Standardization. International Standard/
8825, (December, 1987).
|
|
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):
|
|
|
All RFCs are 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.
|
