|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3289 (2002)
|
|
Title:
|
Management Information Base for the Differentiated Services Architecture
|
|
|
2.
|
Status of approval:
|
|
|
Published as IETF Proposed Standard
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. Q.3303.1v2 refers to RFC 3289 for inheriting part of the data definitions in PIB.
|
|
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=3289
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
IETF Proposed Standard. No IETF activity likely to modify it.
|
|
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:
|
|
|
[1] RFC 2571 An Architecture for Describing SNMP Management Frameworks, April 1999/
[2] RFC 1155 Structure and Identification of Management Information for TCP/IP-based Internets, May 1990/
[3] RFC 1212 Concise MIB Definitions, March 1991/
[4] RFC 1215 A Convention for Defining Traps for use with the SNMP, March 1991/
[5] RFC 2578 Structure of Management Information Version 2 (SMIv2), April 1999/
[6] RFC 2579 Textual Conventions for SMIv2, April 1999/
[7] RFC 2580 Conformance Statements for SMIv2, April 1999/
[8] RFC 1157 Simple Network Management Protocol, May 1990/
[9] RFC 1901 Introduction to Community-based SNMPv2, January 1996/
[10] RFC 1906 Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2), January 1996/
[11] RFC 2572 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP), April 1999/
[12] RFC 2574 User-based Security Model (USM) for version 3 of the Simple Network/
Management Protocol (SNMPv3), April 1999/
[13] RFC 1905 Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2) , January 1996/
[14] RFC 2573 SNMP Applications, April 1999/
[15] RFC 2575 View-based Access Control Model (VACM) for the Simple Network/
Management Protocol (SNMP), April 1999/
[16] RFC 2570 Introduction to Version 3 of the Internet-standard Network Management Framework, April 1999/
/
[17] RFC 2119 Key words to use in the RFCs, March 1997/
[18] In IEEE Infocom 2000, A Study of Active Queue Management for Congestion Control, http://www.ieee- infocom.org/2000/papers/405.pdf/
[19] In SIGCOMM 2000, Fluid-based analysis of a network of AQM routers supporting TCP flows with an application to RED ,http://www.acm.org/sigcomm/sigcomm2000/conf/ paper/sigcomm2000-4-3.ps.gz/
[20] RFC 2597 Assured Forwarding PHB Group, June 1999/
[21] RFC 2475 An Architecture for Differentiated Service, December 1998/
[22] RFC 2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers, December 1998/
[23] Differentiated Services Quality of Service Policy Information Base, Work in Progress/
[24] RFC 3260 New Terminology for Differentiated, April 2002/
[25] RFC 3246 An Expedited Forwarding PHB, March 2002/
[26] RFC 2863 The Interfaces Group MIB using SMIv2, June 2000/
[27] RFC 3291 Textual Conventions for Internet Network Addresses , May 2002/
[28] RFC 2213 Integrated Services Management Information Base using SMIv2, September 1997/
[29] An Informal Management Model for Differentiated Services Routers, Work in Progress/
[30] "Random Early Detection", 1993/
[31] RFC 2697 A Single Rate Three Color Marker, September 1999/
[32] RFC 2698 A Two Rate Three Color Marker, September 1999/
[33] RFC 2859 A Time Sliding Window Three Color Marker (TSWTCM), June 2000/
[34] RFC 2963 A Rate Adaptive Shaper for Differentiated Services, October 2000/
|
|
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):
|
|
|
ftp://ftp.rfc-editor.org/in-notes/rfc3289.txt
|
