@techreport{hamid-issll-rsvp-cap-dsmark-00,
    number =    {draft-hamid-issll-rsvp-cap-dsmark-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hamid-issll-rsvp-cap-dsmark/00/},
    author =    {Syed Hamid},
    title =     {{The DS marking Capability Negotiation: A Usage Case for the RSVP CAP Object
}},
    pagetotal = 7,
    year =      2001,
    month =     feb,
    day =       20,
    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.},
}