draft-ietf-issll-rsvp-cap-00.txt   draft-ietf-issll-rsvp-cap-01.txt 
draft-ietf-issll-rsvp-cap-00.txt draft-ietf-issll-rsvp-cap-01.txt
Internet Draft Syed, Hamid, Internet Draft Syed, Hamid,
draft-ietf-issll-rsvp-cap-00.txt Nortel Networks draft-ietf-issll-rsvp-cap-01.txt Nortel Networks
September, 2000 November, 2000
Capability Negotiation: The RSVP CAP Object Capability Negotiation: The RSVP CAP Object
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
skipping to change at page 1, line 48 skipping to change at page 1, line 48
The DCLASS object is proposed in [DCLASS] to represent and carry The DCLASS object is proposed in [DCLASS] to represent and carry
Differentiated Services Code Points (DSCPs) within RSVP messages. The Differentiated Services Code Points (DSCPs) within RSVP messages. The
principle use of the DCLASS object is to carry DSCP information principle use of the DCLASS object is to carry DSCP information
between a DS network and upstream nodes that may wish to mark packets 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 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 value for DSCP which is further carried as a DCLASS object in RSVP
RESV message to the sender host. RESV message to the sender host.
There may be situations where the sender host is not capable or may There may be situations where the sender host is not capable or may
not wish to mark the packets. Currently, there is no way for the not wish to mark the packets. Currently, there is no way for the
host or network devices to specify their capabilities to the upstream host or network devices to specify their capabilities to the downstream
nodes. nodes.
This draft proposes a capability object (CAP object) in the RSVP PATH This draft proposes a capability object (CAP object) in the RSVP PATH
message that can be used to convey end host/downstream node message that can be used to convey end host/upstream node
capabilities to the upstream network. It also defines one bit in the capabilities to the downstream network. It also defines one bit in the
CAP field of the CAP object to convey the host/downstream node's CAP field of the CAP object to convey the host/upstream node's
draft-ietf-issll-rsvp-cap-00.txt September, 2000 draft-ietf-issll-rsvp-cap-01.txt November, 2000
marking capability/willingness for accepting a DCLASS object from the marking capability/willingness for accepting a DCLASS object from the
upstream network and marking the upstream packets. downstream network and marking the downstream packets.
2. Introduction 2. Introduction
The mechanics of using RSVP [RSVP] signalling and the DCLASS object The mechanics of using RSVP [RSVP] signalling and the DCLASS object
for requesting and applying the QoS in a differentiated services [DS] for requesting and applying the QoS in a differentiated services [DS]
network is described fully in [INTDIFF]. It assumes an architecture network is described fully in [INTDIFF]. It assumes an architecture
with RSVP senders and receivers and a differentiated services network with RSVP senders and receivers and a differentiated services network
somewhere between the sender and the receiver. At least one RSVP aware somewhere between the sender and the receiver. At least one RSVP aware
network element resides in the diff-serv network. This network element network element resides in the diff-serv network. This network element
interacts with RSVP messages arriving from outside the DS network. interacts with RSVP messages arriving from outside the DS network.
skipping to change at page 2, line 42 skipping to change at page 2, line 42
specified in [DCLASS]. specified in [DCLASS].
There may be situations where the sender host is not capable or may There may be situations where the sender host is not capable or may
not wish to mark the packets. In the current definition of DCLASS not wish to mark the packets. In the current definition of DCLASS
object, the network edge device inserts the DCLASS object in the RSVP object, the network edge device inserts the DCLASS object in the RSVP
RESV message without having any prior knowledge of the host capability RESV message without having any prior knowledge of the host capability
whether or not the host can make use of this object. This is one whether or not the host can make use of this object. This is one
example where the network element needs to know the host capabilities example where the network element needs to know the host capabilities
before making a policy decision. Moreover, the definition of DCLASS before making a policy decision. Moreover, the definition of DCLASS
object allows any DS domain to supply DCLASS object on a flow to the object allows any DS domain to supply DCLASS object on a flow to the
downstream DS domains. A prior knowledge of the downstream DS domain's upstream DS domains. A prior knowledge of the upstream DS domain's
marking capability could be useful for the upstream DS domain. There marking capability could be useful for the downstream DS domain. There
could be other scenerios where an advance knowledge of the host or a could be other scenerios where an advance knowledge of the host or a
downstream node's capability may help the network to provide better upstream node's capability may help the network to provide better
policy decisions to the end host. Currently, there is no way for the policy decisions to the end host. Currently, there is no way for the
host or network devices to specify their capabilities. host or network devices to specify their capabilities.
The decision where the data packets should be marked can be made at the The decision where the data packets should be marked can be made at the
DS network nodes assuming that the network edge devices have a prior DS network nodes assuming that the network edge devices have a prior
knowledge of the marking capability of the downstream domains. knowledge of the marking capability of the upstream domains.
Section 3 of this draft describes two scenarios to explain the use of Section 3 of this draft describes two scenarios to explain the use of
CAP object in RSVP PATH message. CAP object in RSVP PATH message.
3. Capability Negotiation 3. Capability Negotiation
The capability object called 'CAP' object can be used as a mechanism The capability object called 'CAP' object can be used as a mechanism
for conveying node capabilities or willingness in RSVP messages. As an for conveying node capabilities or willingness in RSVP messages. As an
example, we will focus on the marking capability of nodes throughout example, we will focus on the marking capability of nodes throughout
this document and define a single bit for host marking information to this document and define a single bit for host marking information to
be carried in the CAP field inside the CAP object of RSVP PATH message. be carried in the CAP field inside the CAP object of RSVP PATH message.
draft-ietf-issll-rsvp-cap-00.txt September, 2000 draft-ietf-issll-rsvp-cap-01.txt November, 2000
However, the CAP is a generic object that can be used to carry any other However, the CAP is a generic object that can be used to carry any other
meaningful capability information in the RSVP PATH message. To explain meaningful capability information in the RSVP PATH message. To explain
the use of CAP object in RSVP PATH message, we will describe two the use of CAP object in RSVP PATH message, we will describe two
scenarios scenarios
- Host-Edge router interaction - Host-Edge router interaction
- Border Router-Border Router interaction - Border Router-Border Router interaction
It should be noted that how and when the packets will be marked is a It should be noted that how and when the packets will be marked is a
decision governed by the network policies. The network policy domain decision governed by the network policies. The network policy domain
may or may not trust the end host marking. Hence, even though the network may or may not trust the end host marking. Hence, even though the network
may have supplied the DCLASS object to the end host on request (via CAP) may have supplied the DCLASS object to the end host on request (via CAP)
it may overwrite the marking based on the domain policy. it may overwrite the marking based on the domain policy.
3.1 Host-Edge Router Capbility Negotiation 3.1 Host-Edge Router Capbility Negotiation
The advance knowledge of the end host's capabilities may help the The advance knowledge of the end host's capabilities may help the
network edge devices to make policy decisions on end host's requests. network edge devices to make policy decisions on end host's requests.
These capabilities can be indicated in the RSVP PATH message to the These capabilities can be indicated in the RSVP PATH message to the
upstream edge devices. downstream edge devices.
The end hosts can be classiffied in two categories: Those capable of The end hosts can be classiffied in two categories: Those capable of
marking upstream packets and decide to do so. The other category of marking downstream packets and decide to do so. The other category of
hosts either do not have the capability to mark packets or they decide hosts either do not have the capability to mark packets or they decide
not to mark packets. In either case, the network element needs to know not to mark packets. In either case, the network element needs to know
the host packet marking capability/willingness. This information can the host packet marking capability/willingness. This information can
help the network element to decide whether or not a DCLASS object must help the network element to decide whether or not a DCLASS object must
be added in a RSVP message for the flow. One way to convey the host be added in a RSVP message for the flow. One way to convey the host
capability/willingness to the network is to use the RSVP PATH message. capability/willingness to the network is to use the RSVP PATH message.
We give examples here to explain the scenarios. We give examples here to explain the scenarios.
If the sender host is ready to mark the upstream traffic (based on the If the sender host is ready to mark the downstream traffic (based on the
DCLASS provided by the network element), it sets the marking bit of the DCLASS provided by the network element), it sets the marking bit of the
CAP field inside the CAP object of the RSVP PATH message. On receiving CAP field inside the CAP object of the RSVP PATH message. On receiving
the RSVP message, the network element at the DS edge records the host the RSVP message, the network element at the DS edge records the host
marking capability as the PATH state. It then resets the marking bit and marking capability as the PATH state. It then resets the marking bit and
sends the RSVP message to the upstream nodes. The treatment of the CAP sends the RSVP message to the downstream nodes. The treatment of the CAP
object at the upstream nodes will be explained in next section. For now, object at the downstream nodes will be explained in next section. For now,
consider the RESV message comes back to the edge device, it performs the consider the RESV message comes back to the edge device, it performs the
necessary admission control. If the network element determines that the necessary admission control. If the network element determines that the
request represented by the PATH and RESV messages is admissible to the request represented by the PATH and RESV messages is admissible to the
diff-serv network, it adds a DCLASS object after consulting the recorded diff-serv network, it adds a DCLASS object after consulting the recorded
state. It may decide to overwrite any DCLASS object inserted by the state. It may decide to overwrite any DCLASS object inserted by the
an upstream node/domain based on its own domain policies. This is exactly an downstream node/domain based on its own domain policies. This is
how the DCLASS object is defined. exactly how the DCLASS object is defined.
Another example could be the end host that is not capable of upstream Another example could be the end host that is not capable of downstream
packet marking. This either will not include a CAP object or the host packet marking. This either will not include a CAP object or the host
will reset the marking bit of the CAP object as an indication of his will reset the marking bit of the CAP object as an indication of his
unwillingness of packet marking. The network edge router will then know unwillingness of packet marking. The network edge router will then know
that the downstream node/end host does not require a DCLASS object. The that the upstream node/end host does not require a DCLASS object. The
edge router, in this case, would be responsible for marking the upstream edge router, in this case, would be responsible for marking the downstream
packets from the end host. packets from the end host.
draft-ietf-issll-rsvp-cap-00.txt September, 2000 draft-ietf-issll-rsvp-cap-01.txt November, 2000
3.2 Boundry router-Boundry Router Interaction 3.2 Boundry router-Boundry Router Interaction
The CAP object could be carried in the PATH message end-to-end. The RSVP The CAP object could be carried in the PATH message end-to-end. The RSVP
PATH message is generated by the end host. The network edge router 'A' PATH message is generated by the end host. The network edge router 'A'
of the DS domain processes the message, resets the marking bit of the of the DS domain processes the message, resets the marking bit of the
CAP object (if it comes as set from the host) and passes the PATH message CAP object (if it comes as set from the host) and passes the PATH message
to the next RSVP Hop. For a DS domain, the boundray router 'B' of the to the next RSVP Hop. For a DS domain, the boundray router 'B' of the
access/stub network receives the RSVP PATH message as next RSVP enabled access/stub network receives the RSVP PATH message as next RSVP enabled
node (Figure 1). It may set the marking bit again to advertise the marking node (Figure 1). It may set the marking bit again to advertise the marking
capability of its own domain. The decision must be governed by the domain capability of its own domain. The decision must be governed by the domain
policy. The ingress boundary router 'C' of the upstream domain receives policy. The ingress boundary router 'C' of the downstream domain receives
the CAP object with the marking bit set providing an indication of the the CAP object with the marking bit set providing an indication of the
marking capability of the downstream node/domain. It again stores this marking capability of the upstream node/domain. It again stores this
information as the PATH state, resets the marking bit and passes it to information as the PATH state, resets the marking bit and passes it to
the upstream RSVP enabled network element. The boundary router 'D' of the downstream RSVP enabled network element. The boundary router 'D' of
this domain may decide to set the marking bit again based on the domain this domain may decide to set the marking bit again based on the domain
policy. The PATH message may pass through more domains like this until policy. The PATH message may pass through more domains like this until
it is received by the host. The RSVP RESV message is then generated and it is received by the host. The RSVP RESV message is then generated and
passed through the same route. The RSVP message arrives at the the passed through the same route. The RSVP message arrives at the the
router 'C' and it may contain a DCLASS object provided by an upstream router 'C' and it may contain a DCLASS object provided by an downstream
node/domain. The PATH state of router 'C' indicates that the downstream node/domain. The PATH state of router 'C' indicates that the upstream
node/domain is capable of packet marking and a DCLASS object is to be node/domain is capable of packet marking and a DCLASS object is to be
passed back. The domain policy/admission control decisions of router 'C' passed back. The domain policy/admission control decisions of router 'C'
may not allow the router to use the same DCLASS value as it received may not allow the router to use the same DCLASS value as it received
from the upstream. So it may decide to overwrite the DCLASS value. The from the downstream. So it may decide to overwrite the DCLASS value. The
edge router 'A' may also decide to remark the DCLASS value in the RESV edge router 'A' may also decide to remark the DCLASS value in the RESV
message following its admission control outcome and knowing the end message following its admission control outcome and knowing the end
host's willingness for packet marking. Finally, the end host receives host's willingness for packet marking. Finally, the end host receives
the DCLASS value in RESV message and it may start marking the upstream the DCLASS value in RESV message and it may start marking the downstream
packets with the appropriate DSCP. packets with the appropriate DSCP.
Once again, It should be noted that how and when the packets will be Once again, It should be noted that how and when the packets will be
marked is a decision governed by the network policies. The network marked is a decision governed by the network policies. The network
policy domain may or may not trust the end host marking. Hence, even policy domain may or may not trust the end host marking. Hence, even
though the network may have supplied the DCLASS object to the end host though the network may have supplied the DCLASS object to the end host
on request (via CAP) it may overwrite the marking based on the domain on request (via CAP) it may overwrite the marking based on the domain
policy. policy.
+----------+ +-----------+ +----------+ +-----------+
skipping to change at page 5, line 5 skipping to change at page 5, line 5
The CAP object has the following format: The CAP object has the following format:
0 | 1 | 2 | 3 0 | 1 | 2 | 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | C-Num (226) | C-Type=1 | | Length | C-Num (226) | C-Type=1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CAP field | | CAP field |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
draft-ietf-issll-rsvp-cap-00.txt September, 2000 draft-ietf-issll-rsvp-cap-01.txt November, 2000
CAP field: CAP field:
0x01: D_MARK 0x01: D_MARK
The host marking capability/willingness identifier. The host marking capability/willingness identifier.
If D_MARK bit is reset, the sender host/downstream node If D_MARK bit is reset, the sender host/upstream node
is not able to mark packets is not able to mark packets
If D_MARK bit is set, the sender host/Downstream node is If D_MARK bit is set, the sender host/upstream node is
able/willing to mark packets able/willing to mark packets
Note: D_MARK is a bit in the CAP (capbility) field. Note: D_MARK is a bit in the CAP (capbility) field.
5. Deployment Scenarios 5. Deployment Scenarios
There are a number of hosts today which do have the marking capability There are a number of hosts today which do have the marking capability
and they even do not depend on a DCLASS object from the network. The and they even do not depend on a DCLASS object from the network. The
marking is based on a default mapping from requested service type to marking is based on a default mapping from requested service type to
the DSCP. In this section, we will briefly address the deployment the DSCP. In this section, we will briefly address the deployment
scenarios for such hosts which do mark without signaling network scenarios for such hosts which do mark without signaling network
about their marking capability. about their marking capability.
If a host does not provide an CAP object, then the network edge must If a host does not provide a CAP object, then the network edge must
be provisioned (or be given policies) as to how it should react. This be provisioned (or be given policies) as to how it should react. This
may be one of: may be one of:
- send a DCLASS object. - send a DCLASS object.
- install a filter to mark the appropriate flow at the edge. - install a filter to mark the appropriate flow at the edge.
- do both. - do both.
The problem here is ensuring that the mapping configured in the host The problem here is ensuring that the mapping configured in the host
matches the allowed mappings configured in the edge router. If there matches the allowed mappings configured in the edge router. If there
is a mismatch, the edge router will, at best, remark the packets to is a mismatch, the edge router will, at best, remark the packets to
match its policies (possibly resulting in a treatment different from match its policies (possibly resulting in a treatment different from
that expected by the host) or, at worst, mark packets as non-conforming that expected by the host) or, at worst, mark packets as non-conforming
and discard them. The policy may be for a specific host address, for and discard them. The policy may be for a specific host address, for
a specific interface, for a specific edge router or for the entire a specific interface, for a specific edge router or for the entire
domain. The bottom line is that manual provisioning would be required domain. The bottom line is that manual provisioning would be required
in the interim until hosts support the CAP option. Once hosts support in the interim until hosts support the CAP option. Once hosts support
the CAP option, manual provisioning would no longer be required. the CAP option, manual provisioning would no longer be required.
In a multi-domain scenario, the boundary router 'B' could be the first In a multi-domain scenario, the boundary router 'B' could be the first
and the only router in the first DS domain who is dealing with the and the only router in the first DS domain who is dealing with the
CAP/DCLASS objects (maintaining the state information and deciding for CAP/DCLASS objects (maintaining the state information and deciding for
a DSCP for the downstream end host). This will allow only one router a DSCP for the upstream end host). This will allow only one router
in a domain with the knowledge of the host's capability and will be in a domain with the knowledge of the host's capability and will be
the one responsible for deciding/providing a DCLASS object in a RSVP the one responsible for deciding/providing a DCLASS object in a RSVP
RESV message. In this scenario, the boundary router 'B' becomes the DS RESV message. In this scenario, the boundary router 'B' becomes the DS
edge for the end host. edge for the end host.
6. References 6. References
[INTDIFF], Bernet, Y., Yavatkar, R., Ford, P., Baker, F., Zhang, L., [INTDIFF], Bernet, Y., Yavatkar, R., Ford, P., Baker, F., Zhang, L.,
Speer, M., Braden, R., Davie, B., Wroclawski, J., "Integrated Services Speer, M., Braden, R., Davie, B., Wroclawski, J., "Integrated Services
[DS] An Architecture for Differentiated Services. S. Blake, D. Black, [DS] An Architecture for Differentiated Services. S. Blake, D. Black,
M. Carlson, E. Davies, Z. Wang, W. Weiss, RFC 2475, December 1998. M. Carlson, E. Davies, Z. Wang, W. Weiss, RFC 2475, December 1998.
draft-ietf-issll-rsvp-cap-00.txt September, 2000 draft-ietf-issll-rsvp-cap-01.txt November, 2000
[RSVP] Braden, R. ed., "Resource ReSerVation Protocol (RSVP) - [RSVP] Braden, R. ed., "Resource ReSerVation Protocol (RSVP) -
Functional Specification.", IETF RFC 2205, Sep. 1997. Functional Specification.", IETF RFC 2205, Sep. 1997.
[DCLASS] Bernet, Y., "Format of the RSVP DCLASS Object", [DCLASS] Bernet, Y., "Format of the RSVP DCLASS Object",
IETF <draft-ietf-isll-dclass-01.txt>, Oct., 1999. IETF <draft-ietf-isll-dclass-01.txt>, Oct., 1999.
6. Acknowledgments 7. Acknowledgments
Thanks to Bill Gage, Yoram Bernet, Goran Janevski, Gary Kenward, Thanks to Bill Gage, Yoram Bernet, Goran Janevski, Gary Kenward,
kwok Ho chan, Muhammad Jaseemuddin and Louis-Nicolas Hamer for kwok Ho chan, Muhammad Jaseemuddin and Louis-Nicolas Hamer for
reviewing this draft and providing useful input. reviewing this draft and providing useful input.
7. Author's Address 8. Author's Address
Syed, Hamid Syed, Hamid
Nortel Networks Nortel Networks
100 - Constellation Crescent, 100 - Constellation Crescent,
Nepean, ON K2G 6J8 Nepean, ON K2G 6J8
Phone: (613) 763-6553 Phone: (613) 763-6553
Email: hmsyed@nortelnetworks.com Email: hmsyed@nortelnetworks.com
8. Full Copyright Statement 9. Full Copyright Statement
"Copyright (C) The Internet Society (date). All Rights Reserved. "Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
skipping to change at line 337 skipping to change at line 337
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
draft-ietf-issll-rsvp-cap-00.txt September, 2000 draft-ietf-issll-rsvp-cap-01.txt November, 2000
 End of changes. 35 change blocks. 
41 lines changed or deleted 41 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/