Application and Sub Application Identity Policy Element for Use with RSVP
RFC 2872

Document Type RFC - Proposed Standard (June 2000; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2872 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
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.

Bernet & Pabbati            Standards Track                     [Page 1]
RFC 2872            Application Identifiers for RSVP           June 2000

   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 application vendor
      2. identifier of the application
      3. version number of the application
      4. sub-application identifier

   An arbitrary number of sub-application identifiers may be included in
   the policy locator. An example of such an identifier is 'print
   transaction'.

   This memo specifies the structure of the application policy element
   and proposes keywords for the sub-elements at each level of the
   hierarchy. It does not enumerate specific values for the sub-
   elements: such an enumeration is beyond the scope of this memo.

2. Simple Application Identity Policy Element Structure

   General application identity policy elements are defined in
   [RFC2752]. These are policy elements with a P-type of AUTH_APP.
   Following the policy element header is a list of authentication
   attributes.

   The first authentication attribute is of the A-type POLICY_LOCATOR.
   The sub-type of the POLICY_LOCATOR attribute is of type ASCII_DN
   [RFC1779] or UNICODE_DN. The actual attribute data is formatted as an
   X.500 distinguished name (DN), representing a globally unique
   identifier, the application, version number and sub-application in a
   hierarchical structure. The POLICY_LOCATOR attribute contains
   keywords as described in section 2. For further details on the format
   of the POLICY_LOCATOR attribute, see [RFC2752].

   The second authentication attribute is of the A-type CREDENTIAL. The
   sub-type of the CREDENTIAL attribute is of type ASCII_ID or
   UNICODE_ID. The actual attribute data is an ASCII or Unicode string
   representing the application name. This structure is illustrated in
   the following diagram:

Bernet & Pabbati            Standards Track                     [Page 2]
RFC 2872            Application Identifiers for RSVP           June 2000

               0              1               2               3
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    PE Length (8)              |   P-type = AUTH_APP           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    Attribute Length           |   A-type =    |  Sub-type =   |
Show full document text