|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3665 (2003)
|
|
Title:
|
Definitions of Managed Objects for the Ethernet-like Interface Types
|
|
|
2.
|
Status of approval:
|
|
|
All are approved IETF documents
|
|
3.
|
Justification for the specific reference:
|
|
|
The data model for provisioning the E-UE defined in this recommendation uses the Structure of Management information Framework and existing MIBs in IETF. The protocol used to interact with the data elements implemented according to these MIB definitions is also defined by IETF. The referenced IETF documents are essential to provision the E-UE.
|
|
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=3665
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[1] 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./
/
[2] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with/
SDP", RFC 3264, April 2002./
/
[3] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach,/
P., Luotonen, A. and L. Stewart, "HTTP authentication: Basic and/
Digest Access Authentication", RFC 2617, June 1999./
/
[4] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
/
|
|
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):
|
|
|
If the study group decides to make the reference to the RFC, the reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs
|
|
