RFC 2749: COPS usage for RSVP
In plain English — editorial summary, not part of the RFC
This document describes usage directives for supporting COPS policy services in RSVP environments. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2749
- Published
- January 2000
- Authors
- S. Herzog; J. Boyle; R. Cohen; D. Durham; R. Rajan; A. Sastry
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3181Signaled Preemption Priority Policy ElementCurrent
October 2001
- RFC 2748The COPS (Common Open Policy Service) ProtocolUpdated
January 2000
- RFC 2750RSVP Extensions for Policy ControlCurrent
January 2000
- RFC 2751Signaled Preemption Priority Policy ElementObsoleted
January 2000
- RFC 2872Application and Sub Application Identity Policy Element for Use with RSVPCurrent
June 2000
- RFC 2940Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol ClientsCurrent
October 2000
- RFC 3182Identity Representation for RSVPCurrent
October 2001
- RFC 2747RSVP Cryptographic AuthenticationUpdated
January 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?