Tech-invite3GPPspaceIETF RFCsSIP
in Index   Prev   Next

RFC 3317

Differentiated Services Quality of Service Policy Information Base

Pages: 96
Part 4 of 4 – Pages 90 to 96
First   Prev   None

Top   ToC   RFC3317 - Page 90   prevText

9. Acknowledgments

Early versions of this specification were also co-authored by Michael Fine, John Seligson, Carol Bell, Andrew Smith, and Francis Reichmeyer. This PIB builds on all the work that has gone into the Informal Management Model for DiffServ Routers and Management Information Base for the Differentiated Services Architecture. It has been developed with the active involvement of many people, but most notably Diana Rawlins, Martin Bokaemper, Walter Weiss, and Bert Wijnen.

10. Security Considerations

The information contained in a PIB when transported by the COPS protocol [COPS-PR] may be sensitive, and its function of provisioning a PEP requires that only authorized communication take place. In this PIB, there are no PRCs which are sensitive in their own right, such as passwords or monetary amounts. But there are a number of PRCs in this PIB that may contain information that may be sensitive from a business perspective, in that they may represent a customer's service contract or the filters that the service provider chooses to apply to a customer's traffic. These PRCs have a PIB- ACCESS clause of install:
Top   ToC   RFC3317 - Page 91
   dsDataPathTable, dsClfrTable, dsClfrElementTable, dsMeterTable,
   dsTBParamTable, dsActionTable, dsDscpMarkActTable, dsAlgDropTable,
   dsMQAlgDropTable, dsRandomDropTable, dsQTable, dsSchedulerTable,
   dsMinRateTable, dsMaxRateTable

   Malicious altering of the above PRCs may affect the DiffServ behavior
   of the device being provisioned.

   Malicious access of the above PRCs exposes policy information
   concerning how the device is provisioned.

   This PIB also contain PRCs with PIB-ACCESS clause of notify:

   dsBaseIfCapsTAble, dsIfClassificationCapsTable,
   dsIfMeteringCapsTable, dsIfAlgDropCapsTable, dsIfQueueCapsTable,
   dsIfSchedulerCapsTable, dsIfMaxRateCapsTable, dsIfElmDepthCapsTable,

   Malicious access of the above PRCs exposes information concerning the
   device being provisioned.

   The use of IPSEC between PDP and PEP, as described in [COPS],
   provides the necessary protection.

11. Intellectual Property Considerations

The IETF has been notified of intellectual property rights claimed in regard to some or all of the specification contained in this document. For more information consult the online list of claimed rights.

12. IANA Considerations

This document describes the dsPolicyPib Policy Information Base (PIB) modules for standardization under the "pib" branch registered with IANA. The IANA has assigned a PIB number (4) under the "pib" branch. [SPPI] PIB SUBJECT-CATEGORIES are mapped to COPS Client Types. IANA Considerations for SUBJECT-CATEGORIES follow the same requirements as specified in [COPS] IANA Considerations for COPS Client Types. The DiffServ QoS PIB defines a new COPS Client Type in the Standards space. The IANA has assigned a COPS client type diffServ (2) as described in [COPS] IANA Considerations. IANA has updated the registry ( for COPS Client Types as a result.
Top   ToC   RFC3317 - Page 92

13. Normative References

[COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and A. Sastry, "The COPS (Common Open Policy Service) Protocol", RFC 2748, January 2000. [COPS-PR] Chan, K., Durham, D., Gai, S., Herzog, S., McCloghrie, K., Reichmeyer, F., Seligson, J., Smith, A. and R. Yavatkar, "COPS Usage for Policy Provisioning", RFC 3084, March 2001. [SPPI] McCloghrie, K., Fine, M., Seligson, J., Chan, K., Hahn, S., Sahita, R., Smith, A. and F. Reichmeyer, "Structure of Policy Provisioning Information", RFC 3159, August 2001. [DSARCH] Carlson, M., Weiss, W., Blake, S., Wang, Z., Black, D. and E. Davies, "An Architecture for Differentiated Services", RFC 2475, December 1998. [DSFIELD] Nichols, K., Blake, S., Baker, F. and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998. [FR-PIB] Fine, M., McCloghrie, K., Seligson, J., Chan, K., Hahn, S., Sahita, R., Smith, A. and F. Reichmeyer, "Framework Policy Information Base", RFC 3318, March 2003. [RAP-FRAMEWORK] Yavatkar, R. and D. Pendarakis, "A Framework for Policy-based Admission Control", RFC 2753, January 2000. [SNMP-SMI] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [MODEL] Bernet, Y., Blake, S., Grossman, D. and A. Smith "An Informal Management Model for Diffserv Routers", RFC 3290, May 2002. [IFMIB] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
Top   ToC   RFC3317 - Page 93
   [DS-MIB]        Baker, F., Chan, K. and A. Smith, "Management
                   Information Base for the Differentiated Services
                   Architecture", RFC 3289, May 2002.

   [ACTQMGMT]      Firoiu, V. and M. Borden, "A Study of Active Queue
                   Management for Congestion Control", March 2000, In
                   IEEE Infocom 2000,

   [AQMROUTER]     Misra, V., Gong, W. and D. Towsley, "Fluid-based
                   analysis of a network of AQM routers supporting TCP
                   flows with an application to RED", In SIGCOMM 2000,

   [AF-PHB]        Heinanen, J., Baker, F., Weiss, W. and J. Wroclawski,
                   "Assured Forwarding PHB Group", RFC 2597, June 1999.

   [EF-PHB]        Jacobson, V., Nichols, K. and K. Poduri, "An
                   Expedited Forwarding PHB", RFC 2598, June 1999.

   [INTSERVMIB]    Baker, F., Krawczyk, J. and A. Sastry, "Integrated
                   Services Management Information Base using SMIv2",
                   RFC 2213, September 1997.

   [QUEUEMGMT]     Braden, B., Clark, D., Crowcroft, J., Davie, B.,
                   Deering, S., Estrin, D., Floyd, S., Jacobson, V.,
                   Minshall, G., Partridge, C., Peterson, L.,
                   Ramakrishnan, K., Shenker, S., Wroclawski, J.
                   and L. Zhang, "Recommendations on Queue Management
                   and Congestion Avoidance in the Internet", RFC 2309,
                   April 1998.

   [SRTCM]         Heinanen, J. and R. Guerin, "A Single Rate Three
                   Color Marker", RFC 2697, September 1999.

   [TRTCM]         Heinanen, J. and R. Guerin, "A Two Rate Three Color
                   Marker", RFC 2698, September 1999.

   [TSWTCM]        Fang, W., Seddigh, N. and B. Nandy, "A Time Sliding
                   Window Three Colour Marker", RFC 2859, June 2000.

   [RFC2026]       Bradner, S., "The Internet Standards Process --
                   Revision 3", BCP 9, RFC 2026, October 1996.

   [RFC2119]       Bradner, S., "Key words for use in RFCs to Indicate
                   Requirement Levels", BCP 14, RFC 2119, March 1997.
Top   ToC   RFC3317 - Page 94
   [RFC2579]       McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
                   J., Rose, M. and S. Waldbusser, "Textual Conventions
                   for SMIv2", STD 58, RFC 2579, April 1999.

   [SHAPER]        Bonaventure, O. and S. De Cnodder, "A Rate Adaptive
                   Shaper for Differentiated Services", RFC 2963,
                   October 2000.

   [POLTERM]       Westerinen, A., Schnizlein, J., Strassner, J.,
                   Scherling, M., Quinn, B., Herzog, S., Huynh, A.,
                   Carlson, M., Perry, J. and S. Waldbusser,
                   "Terminology for Policy-Based Management",
                   RFC 3198, November 2001.
Top   ToC   RFC3317 - Page 95

14. Authors' Addresses

Kwok Ho Chan Nortel Networks, Inc. 600 Technology Park Drive Billerica, MA 01821 USA Phone: +1 978 288 8175 EMail: Ravi Sahita Intel Labs. 2111 NE 25th Avenue Hillsboro, OR 97124 USA Phone: +1 503 712 1554 EMail: Scott Hahn Intel 2111 NE 25th Avenue Hillsboro, OR 97124 USA Phone: +1 503 264 8231 EMail: Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA Phone: +1 408 526 5260 EMail:
Top   ToC   RFC3317 - Page 96

15. Full Copyright Statement

Copyright (C) The Internet Society (2003). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.