Browse Prior Art Database

COPS usage for RSVP (RFC2749)

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

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Herzog: AUTHOR [+5]

Related Documents

10.17487/RFC2749: DOI

Abstract

This document describes usage directives for supporting COPS policy services in RSVP environments. [STANDARDS-TRACK]

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

Network Working Group S . Herzog, Ed. Request for Comments: 2749 IPHighway Category: Standards Track J. Boyle Level3 R. Cohen Cisco D. Durham Intel R. Rajan AT&T A. Sastry Cisco January 2000

COPS usage for RSVP

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 document describes usage directives for supporting COPS policy services in RSVP environments.

Table of Contents

1 Introduction....................................................2 2 RSVP values for COPS objects....................................2 2.1 Common Header, client-type...................................2 2.2 Context Object (Context).....................................3 2.3 Client Specific Information (ClientSI).......................4 2.4 Decision Object (Decision)...................................4 3 Operation of COPS for RSVP PEPs.................................6 3.1 RSVP flows...................................................6 3.2 Expected Associations for RSVP Requests......................6 3.3 RSVP’s Capacity Admission Control: Commit and Delete.........7 3.4 Policy Control Over PathTear and ResvTear....................7

Herzog, et al. Standards Track [Page 1]

RFC 2749 COPS usage for RSVP January 2000

3.5 PEP Caching COPS Decisions...................................7 3.6 Using Multiple Context Flags in a single query...............8 3.7 RSVP Error Reporting.........................................9 4 Security Considerations.........................................9 5 Illustrative Examples, Using COPS for RSVP......................9 5.1 Unicast Flow Example.........................................9 5.2 Shared Multicast Flows......................................11 6 References.....................................................14 7 Author Information and Acknowledgments.........................15 8 Full Copyright Statement.......................................17

1 Introduction

The Common Open Policy Service (COPS) protocol is a query response protocol used to exchange policy information between a network policy server and a set of clients [COPS]. COPS is being developed within the RSVP Admission Policy Working Group (RAP WG) of the IETF, primarily for use as a mechanism for providing policy-based admission control over requests for network resources [RAP].

This document is based on and assumes prior knowledge of the RAP framework [RAP] and the basic COPS [COPS] protocol. It provides specific usage directives for using COPS in outsourcing policy control decisions by RSVP clients (PEPs) to policy servers (PDPs).

Given the COPS protocol design, RSVP directives are mainly limit...

Processing...
Loading...