|
1.
|
Clear description of the referenced document:
|
|
|
|
|
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=4293
|
|
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:
|
|
|
Obsoletes: 2011, 2465, 2466
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[1] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of/
Management Information Version 2 (SMIv2)", STD 58, RFC 2578,/
April 1999./
/
[2] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual/
Conventions for SMIv2", STD 58, RFC 2579, April 1999./
/
[3] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance/
Statements for SMIv2", STD 58, RFC 2580, April 1999./
/
[4] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery/
for IP Version 6 (IPv6)", RFC 2461, December 1998./
/
[5] Thomson, S. and T. Narten, "IPv6 Stateless Address/
Autoconfiguration", RFC 2462, December 1998./
/
[6] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB",/
RFC 2863, June 2000./
/
[7] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder,/
"Textual Conventions for Internet Network Addresses", RFC 4001,/
February 2005./
/
[8] Draves, R. and D. Thaler, "Default Router Preferences and More-/
Specific Routes", RFC 4191, November 2005./
/
|
|
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
|
|
