The DS marking Capability Negotiation: A Usage Case for the RSVP CAP Object
draft-hamid-issll-rsvp-cap-dsmark-00

Document Type Expired Internet-Draft (individual)
Last updated 2001-02-20
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hamid-issll-rsvp-cap-dsmark-00.txt

Abstract

The DCLASS object is proposed in [DCLASS] to represent and carry Differentiated Services Code Points (DSCPs) within RSVP messages. The principle use of the DCLASS object is to carry DSCP information between a DS network and upstream nodes that may wish to mark packets with DSCP values. A network element in the DS network determines the value for DSCP which is further carried as a DCLASS object in RSVP RESV message to the sender host. The RSVP capability negotiation CAP Object [RSVP_CAP] is proposed to convey end host/upstream node Capabilities to the downstream network.

Authors

Syed Hamid (hmsyed@nortelnetworks.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)