Committed to connecting the world

  •  
wtisd

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : Y.2771     
  ITU-T A.5 justification information for referenced document IETF RFC 4011 (2005) in draft Y.2771
1. Clear description of the referenced document:
Name: IETF RFC 4011 (2005)
Title: Policy Based Management MIB
2. Status of approval:
The referred RFC was approved by IESG (Internet Engineering Steering Group).
3. Justification for the specific reference:
DPI policy rule data modeling may serve [IETF RFC 4011] as baseline. See clause 7.
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=4016
5. Other useful information describing the "Quality" of the document:
Standards Track
6. The degree of stability or maturity of the document:
Standards Track
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:
Normative References/
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for/
Describing Simple Network Management Protocol (SNMP) Management/
Frameworks", STD 62, RFC 3411, December 2002./
/
[2] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of/
Management Information Version 2 (SMIv2)", STD 58, RFC 2578,/
April 1999./
/
[3] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual/
Conventions for SMIv2", STD 58, RFC 2579, April 1999./
/
[4] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance/
Statements for SMIv2", STD 58, RFC 2580, April 1999./
/
[5] Presuhn, R., "Transport Mappings for the Simple Network/
Management Protocol (SNMP)", STD 62, RFC 3417, December 2002./
/
[6] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)/
for version 3 of the Simple Network Management Protocol/
(SNMPv3)", STD 62, RFC 3414, December 2002./
/
[7] Presuhn, R., "Version 2 of the Protocol Operations for the/
Simple Network Management Protocol (SNMP)", STD 62, RFC 3416,/
December 2002./
/
[8] Frye, R., Levi, D., Routhier, S., and B. Wijnen, "Coexistence/
between Version 1, Version 2, and Version 3 of the Internet-/
standard Network Management Framework", BCP 74, RFC 3584, August/
2003./
[9] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access/
Control Model (VACM) for the Simple Network Management Protocol/
(SNMP)", STD 62, RFC 3415, December 2002./
/
[10] International Standards Organization, "Information Technology -/
Programming Languages - C++", ISO/IEC 14882-1998/
/
[11] Daniele, M. and J. Schoenwaelder, "Textual Conventions for/
Transport Addresses", RFC 3419, December 2002./
/
[12] Levi, D. and J. Schoenwaelder, "Definitions of Managed Objects/
for Scheduling Management Operations", RFC 3231, January 2002./
/
[13] Hoffman, P. and M. Blanchet, "Preparation of Internationalized/
Strings ("stringprep")", RFC 3454, December 2002./
/
[14] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD/
63, RFC 3629, November 2003./
/
[15] Dawson, F. and D. Stenerson, "Internet Calendaring and/
Scheduling Core Object Specification (iCalendar)", RFC 2445,/
November 1998./
Informative References/
/
[16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction/
and Applicability Statements for Internet-Standard Management/
Framework", RFC 3410, December 2002./
/
[17] ECMA, "ECMAScript Language Specification", ECMA-262, December/
1999/
/
[18] Moore, B., Ellesson, E., Strassner, J., and A. Westerinen,/
"Policy Core Information Model -- Version 1 Specification", RFC/
3060, February 2001./
/
[19] MacFaden, M., Partain, D., Saperia, J., and W. Tackabury,/
"Configuring Networks and Devices with Simple Network Management/
Protocol (SNMP)", RFC 3512, April 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
Note: This form is based on Recommendation ITU-T A.5