Browse Prior Art Database

RSVP Extensions for Policy Control (RFC2750)

IP.com Disclosure Number: IPCOM000003347D
Original Publication Date: 2000-Jan-01
Included in the Prior Art Database: 2019-Feb-10
Document File: 13 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Herzog: AUTHOR

Related Documents

10.17487/RFC2750: DOI

Abstract

This memo presents a set of extensions for supporting generic policy based admission control in RSVP. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 13% of the total text.

Network Working Group S. Herzog Request for Comments: 2750 IPHighway Updates: 2205 January 2000 Category: Standards Track

RSVP Extensions for Policy Control

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

This memo presents a set of extensions for supporting generic policy based admission control in RSVP. It should be perceived as an extension to the RSVP functional specifications [RSVP]

These extensions include the standard format of POLICY_DATA objects, and a description of RSVP’s handling of policy events.

This document does not advocate particular policy control mechanisms; however, a Router/Server Policy Protocol description for these extensions can be found in [RAP, COPS, COPS-RSVP].

Herzog Standards Track [Page 1]

RFC 2750 RSVP Extensions for Policy Control January 2000

Table of Contents

1 Introduction.......................................................2 2 A Simple Scenario..................................................3 3 Policy Data Objects................................................3 3.1 Base Format.....................................................4 3.2 Options.........................................................4 3.3 Policy Elements.................................................7 3.4 Purging Policy State............................................7 4 Processing Rules...................................................8 4.1 Basic Signaling.................................................8 4.2 Default Handling for PIN nodes..................................8 4.3 Error Signaling.................................................9 5 IANA Considerations................................................9 6 Security Considerations............................................9 7 References........................................................10 8 Acknowledgments...................................................10 9 Author Information................................................10 Appendix A: Policy Error Codes......................................11 Appendix B: INTEGRITY computation for POLICY_DATA objects...........12 Full Copyright Statement ...........................................13

1 Introduction

RSVP, by definition, discriminates between users, by providing some users with better service at the expense of others. Therefore, it is reasonable to expect that RSVP be accompanied by mechanisms for controlling and enforcing access and usage policies. Version 1 of the RSVP Functional Specifications [RSVP] left a placeholder for policy support in the form of POLICY_DATA object.

The current RSVP Functional Specification describes t...

Processing...
Loading...