draft-ietf-ccamp-rsvp-resource-sharing-00.txt   draft-ietf-ccamp-rsvp-resource-sharing-01.txt 
CCAMP F. Le Faucheur CCAMP F. Le Faucheur
Internet-Draft A. Narayanan Internet-Draft A. Narayanan
Intended status: Standards Track S. Dhesikan Intended status: Standards Track S. Dhesikan
Expires: April 21, 2011 Cisco Expires: September 10, 2011 Cisco
October 18, 2010 March 9, 2011
RSVP Resource Sharing Remote Identification Association RSVP Resource Sharing Remote Identification Association
draft-ietf-ccamp-rsvp-resource-sharing-00.txt draft-ietf-ccamp-rsvp-resource-sharing-01.txt
Abstract Abstract
The RSVP ASSOCIATION object allows to create association across RSVP The Resource reSerVation Protocol (RSVP) ASSOCIATION object allows to
path states or across Resv states. Two association types are create association across RSVP path states or across Resv states.
currently defined: recovery and resource sharing. This document Two association types are currently defined: recovery and resource
defines a new association type called "Resource Sharing Remote sharing. This document defines a new association type called
Identification". It can be used by the sender to convey to the "Resource Sharing Remote Identification". It can be used by the
receiver the information that can then be used by the receiver to sender to convey to the receiver the information that can then be
identify a downstream initiated resource sharing association. used by the receiver to identify a downstream initiated resource
sharing association.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 21, 2011. This Internet-Draft will expire on September 10, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 22 skipping to change at page 3, line 7
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Conventions Used in This Document . . . . . . . . . . . . 4 1.1. Conventions Used in This Document . . . . . . . . . . . . 5
2. Resource Sharing Remote Identification Association . . . . . . 5 2. Resource Sharing Remote Identification Association . . . . . . 6
3. Security Considerations . . . . . . . . . . . . . . . . . . . 7 3. Security Considerations . . . . . . . . . . . . . . . . . . . 8
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
4.1. Resource Sharing Remote Identification Association Type . 8 4.1. Resource Sharing Remote Identification Association Type . 9
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 6. Normative References . . . . . . . . . . . . . . . . . . . . . 11
6.1. Normative References . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
6.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
The notion of association as well as the corresponding RSVP The notion of association as well as the corresponding RSVP
ASSOCIATION object are defined in [RFC4872] and [RFC4873] in the ASSOCIATION object are defined in [RFC4872] and [RFC4873] in the
context of GMPLS (Generalized Multi-Protocol Label Switching) context of GMPLS (Generalized Multi-Protocol Label Switching)
controlled label switched paths (LSPs). In this context, the object controlled label switched paths (LSPs). In this context, the object
is used to associate recovery LSPs with the LSP they are protecting. is used to associate recovery LSPs with the LSP they are protecting.
This object also has broader applicability as a mechanism to This object also has broader applicability as a mechanism to
associate RSVP state, and [I-D.ietf-ccamp-assoc-info] defines how the associate RSVP state, and [I-D.ietf-ccamp-assoc-info] defines how the
ASSOCIATION object can be more generally applied. [I-D.ietf-ccamp- ASSOCIATION object can be more generally applied.
assoc-info] also reviews how the association is to be provided in the [I-D.ietf-ccamp-assoc-info] also reviews how the association is to be
context of GMPLS recovery. provided in the context of GMPLS recovery.
[RFC4872] defines the IPv4 ASSOCIATION object and the IPv6 [RFC4872] defines the IPv4 ASSOCIATION object and the IPv6
ASSOCIATION object. In addition, [I-D.ietf-ccamp-assoc-info] defines ASSOCIATION object. In addition, [I-D.ietf-ccamp-assoc-info] defines
the Extended IPv4 ASSOCIATION object and the Extended IPv6 the Extended IPv4 ASSOCIATION object and the Extended IPv6
ASSOCIATION object. These four forms of the ASSOCIATION object ASSOCIATION object. These four forms of the ASSOCIATION object
contain an Association Type field that indicates the type of contain an Association Type field that indicates the type of
association being identified by the ASSOCIATION object. For example, association being identified by the ASSOCIATION object. For example,
Figure 1 illustrates the format of the IPv4 ASSOCIATION object. Figure 1 illustrates the format of the IPv4 ASSOCIATION object.
0 1 2 3 0 1 2 3
skipping to change at page 3, line 41 skipping to change at page 4, line 41
| Association Type | Association ID | | Association Type | Association ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Association Source | | IPv4 Association Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: IPv4 ASSOCIATION object format Figure 1: IPv4 ASSOCIATION object format
[RFC4872] and [RFC4873] define two association types: recovery and [RFC4872] and [RFC4873] define two association types: recovery and
resource sharing. Recovery type association is only applicable resource sharing. Recovery type association is only applicable
within the context of recovery ( [RFC4872] and [RFC4873]). Resource within the context of recovery ( [RFC4872] and [RFC4873]). Resource
sharing is generally useful and its general use is defined in section sharing is useful in multiple contexts and its general use is defined
4.3.1 of [I-D.ietf-ccamp-assoc-info]. For non-recovery Usage (for in section 4.3.1 of [I-D.ietf-ccamp-assoc-info]. For non-recovery
example for resource sharing), [I-D.ietf-ccamp-assoc-info] defines, usage (for example for resource sharing), [I-D.ietf-ccamp-assoc-info]
in section 4, the notion of upstream initiated association and defines, in section 4, the notion of upstream initiated association
downstream initiated association. Upstream initiated association is and downstream initiated association. Upstream initiated association
represented in ASSOCIATION objects carried in Path messages and can is represented in ASSOCIATION objects carried in Path messages and
be used to associate RSVP Path state across MPLS Tunnels / RSVP can be used to associate RSVP Path state across MPLS Tunnels or RSVP
sessions. Downstream initiated association is represented in sessions. Downstream initiated association is represented in
ASSOCIATION objects carried in Resv messages and can be used to ASSOCIATION objects carried in Resv messages and can be used to
associate RSVP Resv state across MPLS Tunnels / RSVP sessions. associate RSVP Resv state across MPLS Tunnels or RSVP sessions.
This document defines a new association type called "Resource Sharing This document defines a new association type called "Resource Sharing
Remote Identification". Remote Identification".
1.1. Conventions Used in This Document 1.1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Resource Sharing Remote Identification Association 2. Resource Sharing Remote Identification Association
We define here a new association type called the Resource Sharing We define here a new association type called the Resource Sharing
Remote Identification. Remote Identification.
The Resource Sharing Remote Identification association type can be
used with the IPv4 ASSOCIATION object and the IPv6 ASSOCIATION object
defined in [RFC4872] as well as with the Extended IPv4 ASSOCIATION
object and the Extended IPv6 ASSOCIATION object defined in
[I-D.ietf-ccamp-assoc-info].
The Resource Sharing Remote Identification association is only The Resource Sharing Remote Identification association is only
defined for use in upstream initiated association. Thus it can only defined for use in upstream initiated association. Thus it can only
appear in ASSOCIATION objects signaled in Path messages. appear in ASSOCIATION objects signaled in Path messages.
The Resource Sharing Remote Identification association can be used by The Resource Sharing Remote Identification association can be used by
the sender to convey to the receiver (inside the Association Source the sender to convey to the receiver (inside the Association Source
and Association ID fields), information that can then be used by the and Association ID fields), information that can then be used by the
receiver to identify an upstream initiated resource sharing receiver to identify an upstream initiated resource sharing
association. This is useful in upstream initiated resource sharing association. This is useful in upstream initiated resource sharing
applications where the identification of the resource sharing applications where the identification of the resource sharing
skipping to change at page 5, line 52 skipping to change at page 7, line 9
Resource Sharing Remote Identification association. Resource Sharing Remote Identification association.
On receipt of an ASSOCIATION object whose association type is On receipt of an ASSOCIATION object whose association type is
Resource Sharing Remote Identification, the receiver MAY use the Resource Sharing Remote Identification, the receiver MAY use the
association identification information contained in the received association identification information contained in the received
ASSOCIATION object as the association identification information in ASSOCIATION object as the association identification information in
an upstream initiated resource sharing association. an upstream initiated resource sharing association.
On receipt of an ASSOCIATION object whose association type is On receipt of an ASSOCIATION object whose association type is
Resource Sharing Remote Identification, an RSVP receiver proxy as Resource Sharing Remote Identification, an RSVP receiver proxy as
defined in [RFC5945], SHOULD initiate an upstream initiated Resource defined in [I-D.ietf-tsvwg-rsvp-proxy-approaches], SHOULD initiate an
Sharing association whose association identification information is upstream initiated Resource Sharing association whose association
copied from the received ASSOCIATION object. This behavior MAY be identification information is copied from the received ASSOCIATION
overridden by local policy on the receiver proxy. object. This behavior MAY be overridden by local policy on the
receiver proxy.
3. Security Considerations 3. Security Considerations
TBD. TBD.
4. IANA Considerations 4. IANA Considerations
IANA is requested to administer assignment of new values for IANA is requested to administer assignment of new values for
namespaces in accordance with codepoints defined in this document and namespaces in accordance with codepoints defined in this document and
summarized in this section. summarized in this section.
skipping to change at page 10, line 5 skipping to change at page 11, line 5
3 Resource Sharing Remote Identification (I) [this-document] 3 Resource Sharing Remote Identification (I) [this-document]
There are no other IANA considerations introduced by this document. There are no other IANA considerations introduced by this document.
5. Acknowledgments 5. Acknowledgments
We thank Lou Berger for his guidance in this work and in particular We thank Lou Berger for his guidance in this work and in particular
with respect to aligning it with the related CCAMP work on with respect to aligning it with the related CCAMP work on
Association . Association .
6. References 6. Normative References
6.1. Normative References [I-D.ietf-ccamp-assoc-info]
Berger, L., Faucheur, F., and A. Narayanan, "Usage of The
RSVP Association Object", draft-ietf-ccamp-assoc-info-00
(work in progress), October 2010.
[I-D.ietf-tsvwg-rsvp-proxy-approaches]
Faucheur, F., Manner, J., Wing, D., and L. Faucheur, "RSVP
Proxy Approaches",
draft-ietf-tsvwg-rsvp-proxy-approaches-09 (work in
progress), March 2010.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4872] Lang, J., Rekhter, Y., and D. Papadimitriou, "RSVP-TE [RFC4872] Lang, J., Rekhter, Y., and D. Papadimitriou, "RSVP-TE
Extensions in Support of End-to-End Generalized Multi- Extensions in Support of End-to-End Generalized Multi-
Protocol Label Switching (GMPLS) Recovery", RFC 4872, Protocol Label Switching (GMPLS) Recovery", RFC 4872,
May 2007. May 2007.
[RFC4873] Berger, L., Bryskin, I., Papadimitriou, D., and A. Farrel, [RFC4873] Berger, L., Bryskin, I., Papadimitriou, D., and A. Farrel,
"GMPLS Segment Recovery", RFC 4873, May 2007. "GMPLS Segment Recovery", RFC 4873, May 2007.
6.2. Informative References
[RFC5945] Le Faucheur, F., Manner, J., Wing, D., and A. Guillou,
"Resource Reservation Protocol (RSVP) Proxy Approaches",
RFC 5945, October 2010.
Authors' Addresses Authors' Addresses
Francois Le Faucheur Francois Le Faucheur
Cisco Systems Cisco Systems
Greenside, 400 Avenue de Roumanille Greenside, 400 Avenue de Roumanille
Sophia Antipolis 06410 Sophia Antipolis 06410
France France
Phone: +33 4 97 23 26 19 Phone: +33 4 97 23 26 19
Email: flefauch@cisco.com Email: flefauch@cisco.com
 End of changes. 14 change blocks. 
46 lines changed or deleted 55 lines changed or added

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