RFC 2872: Application and Sub Application Identity Policy Element for Use with RSVP
In plain English — editorial summary, not part of the RFC
RSVP 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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2872
- Published
- June 2000
- Authors
- Y. Bernet; R. Pabbati
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2750RSVP Extensions for Policy ControlCurrent
January 2000
- RFC 2749COPS usage for RSVPCurrent
January 2000
- RFC 3181Signaled Preemption Priority Policy ElementCurrent
October 2001
- RFC 3182Identity Representation for RSVPCurrent
October 2001
- RFC 2814SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networksCurrent
May 2000
- RFC 2961RSVP Refresh Overhead Reduction ExtensionsUpdated
April 2001
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 2000
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?