Browse Prior Art Database

Application and Sub Application Identity Policy Element for Use with RSVP (RFC2872)

IP.com Disclosure Number: IPCOM000003473D
Original Publication Date: 2000-Jun-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 4 page(s) / 10K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Y. Bernet: AUTHOR [+2]

Abstract

RSVP [RFC 2205] signaling messages typically include policy data objects, which in turn contain policy elements. Policy elements may describe user and/or application information, which may be used by RSVP aware network elements to apply appropriate policy decisions to a traffic flow. This memo details the usage of policy elements that provide application information.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 27% of the total text.

Network Working Group Y. Bernet

Request for Comments: 2872 R. Pabbati

Category: Standards Track Microsoft

June 2000

Application and Sub Application Identity Policy Element for

Use with 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.

Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

document are to be interpreted as described in [RFC2119].

Abstract

RSVP [RFC 2205] signaling messages typically include policy data

objects, which in turn contain policy elements. Policy elements may

describe user and/or application information, which may be used by

RSVP aware network elements to apply appropriate policy decisions to

a traffic flow. This memo details the usage of policy elements that

provide application information.

1. Overview

RSVP aware network elements may act as policy enforcement points

(PEPs). These work together with policy decision points (PDPs) to

enforce QoS policy. Briefly, PEPs extract policy information from

RSVP signaling requests and compare the information against

information stored by a PDP in a (possibly remotely located) policy

database or directory. A policy decision is made based on the results

of the comparison.

One type of policy information describes the application on behalf of

which an RSVP signaling request is generated. When application policy

information is available, network administrators are able to manage

QoS based on application type. So, for example, a network

administrator may establish a policy that prioritizes known mission-

critical applications over games.

This memo describes a structure for a policy element that can be used

to identify application traffic flows. The policy element includes a

number of attributes, one of which is a policy locator. This policy

locator includes the following hierarchically ordered sub-elements

(in descending levels of hierarchy):

1. identifier that uniquely identifies the ...