CCAMP                                                     F. Le Faucheur
Internet-Draft                                              A. Narayanan
Intended status: Standards Track                             S. Dhesikan
Expires: September 10, 2011 January 26, 2012                                          Cisco
                                                           March 9,
                                                           July 25, 2011

        RSVP Resource Sharing Remote Identification Association
             draft-ietf-ccamp-rsvp-resource-sharing-01.txt
             draft-ietf-ccamp-rsvp-resource-sharing-02.txt

Abstract

   The Resource reSerVation Protocol (RSVP) ASSOCIATION object allows to
   create association across RSVP path states or across Resv states.
   Two association types are currently defined: recovery and resource
   sharing.  This document defines a new association type called
   "Resource Sharing Remote Identification".  It can be used by the
   sender to convey to the receiver the information that can then be
   used by the receiver to identify a downstream initiated resource
   sharing association.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 10, 2011. January 26, 2012.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4  3
     1.1.  Conventions Used in This Document  . . . . . . . . . . . .  5  4
   2.  Resource Sharing Remote Identification Association . . . . . .  6  5
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8  7
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9  8
     4.1.  Resource Sharing Remote Identification Association Type  .  9  8
   5.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 10  9
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     6.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     6.2.  Informative References . . 11 . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 11

1.  Introduction

   The notion of association as well as the corresponding RSVP
   ASSOCIATION object are defined in [RFC4872] and [RFC4873] in the
   context of GMPLS (Generalized Multi-Protocol Label Switching)
   controlled label switched paths (LSPs).  In this GMPLS context, the
   object is used to associate recovery LSPs with the LSP they are protecting.
   protecting ([I-D.ietf-ccamp-assoc-info]).  This object also has
   broader applicability as a mechanism to associate RSVP state, and [I-D.ietf-ccamp-assoc-info]
   [I-D.ietf-ccamp-assoc-ext] defines how the ASSOCIATION object can be
   more generally applied.
   [I-D.ietf-ccamp-assoc-info] also reviews how the association is to be
   provided in the context of GMPLS recovery.

   [RFC4872] defines the IPv4 ASSOCIATION object and the IPv6
   ASSOCIATION object.  In addition, [I-D.ietf-ccamp-assoc-info] [I-D.ietf-ccamp-assoc-ext] defines
   the Extended IPv4 ASSOCIATION object and the Extended IPv6
   ASSOCIATION object.  These four forms of the ASSOCIATION object
   contain an Association Type field that indicates the type of
   association being identified by the ASSOCIATION object.  For example,
   Figure 1 illustrates the format of the IPv4 ASSOCIATION object.

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |            Length             | Class-Num(199)|  C-Type (1)   |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |       Association Type        |       Association ID          |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                  IPv4 Association Source                      |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                 Figure 1: IPv4 ASSOCIATION object format

   [RFC4872] and [RFC4873] define two association types: recovery and
   resource sharing.  Recovery type association is only applicable
   within the context of recovery ( [RFC4872] and [RFC4873]). [RFC4872], [RFC4873],
   [I-D.ietf-ccamp-assoc-info] ).  Resource sharing is useful in
   multiple contexts and its general use is defined in section 4.3.1 2.3.1 of [I-D.ietf-ccamp-assoc-info].
   [I-D.ietf-ccamp-assoc-ext].  For non-recovery usage (for example for
   resource sharing), [I-D.ietf-ccamp-assoc-info] [I-D.ietf-ccamp-assoc-ext] defines, in section 4, 2,
   the notion of upstream initiated association and downstream initiated
   association.  Upstream initiated association is represented in
   ASSOCIATION objects carried in Path messages and can be used to
   associate RSVP Path state across MPLS Tunnels or RSVP sessions.
   Downstream initiated association is represented in ASSOCIATION
   objects carried in Resv messages and can be used to associate RSVP
   Resv state across MPLS Tunnels or RSVP sessions.

   This document defines a new association type called "Resource Sharing
   Remote Identification".

1.1.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Resource Sharing Remote Identification Association

   We define here a new association type called the Resource Sharing
   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].
   [I-D.ietf-ccamp-assoc-ext].

   The Resource Sharing Remote Identification association is only
   defined for use in upstream initiated association.  Thus it can only
   appear in ASSOCIATION objects signaled in Path messages.

   The Resource Sharing Remote Identification association can be used by
   the sender to convey to the receiver (inside the Association Source
   and Association ID fields), information that can then be used by the
   receiver to identify an upstream initiated resource sharing
   association.  This is useful in upstream initiated resource sharing
   applications where the identification of the resource sharing
   association is not known a priori by the receiver, and instead is
   known by the sender (for example because the sender is in a better
   position to assign the association identification necessary to
   implement the desired resource sharing across RSVP sessions).

   [I-D.ietf-ccamp-assoc-info]

   [I-D.ietf-ccamp-assoc-ext] discusses the rules associated with the
   processing of ASSOCIATION objects in RSVP messages.  In addition to
   generic rules applicable to all association types, a given
   association type may define type-specific processing rules.  The
   following type-specific association rule is defined for the Resource
   Sharing Remote Identification association type:

   o  The Resource Sharing Remote Identification association does not
      create any association across Path states.

   This is because the purpose of signaling an Resource Sharing Remote
   Identification association in the downstream direction is purely to
   convey identification information from the sender to the receiver
   that can be used by the receiver to establish an upstream initiated
   resource sharing association.

   Any implementation of the present specification MUST support the
   Resource Sharing Remote Identification association.

   On receipt of an ASSOCIATION object whose association type is
   Resource Sharing Remote Identification, the receiver MAY use the
   association identification information contained in the received
   ASSOCIATION object as the association identification information in
   an upstream initiated resource sharing association.

   On receipt of an ASSOCIATION object whose association type is
   Resource Sharing Remote Identification, an RSVP receiver proxy as
   defined in [I-D.ietf-tsvwg-rsvp-proxy-approaches], [RFC5945], SHOULD initiate an upstream initiated Resource
   Sharing association whose association identification information is
   copied from the received ASSOCIATION object.  This behavior MAY be
   overridden by local policy on the receiver proxy.

3.  Security Considerations

   TBD.

4.  IANA Considerations

   IANA is requested to administer assignment of new values for
   namespaces in accordance with codepoints defined in this document and
   summarized in this section.

4.1.  Resource Sharing Remote Identification Association Type

   This document defines, in Section 2, a new association type.  Thus,
   IANA is requested to allocate the following entry in the Association
   Type registry found at
   http://www.iana.org/assignments/gmpls-sig-parameters/ :

      3 Resource Sharing Remote Identification (I) [this-document]

   There are no other IANA considerations introduced by this document.

5.  Acknowledgments

   We thank Lou Berger for his guidance in this work and in particular
   with respect to aligning it with the related CCAMP work on
   Association .

6.  References

6.1.  Normative References

   [I-D.ietf-ccamp-assoc-info]

   [I-D.ietf-ccamp-assoc-ext]
              Berger, L., Faucheur, F., and A. Narayanan, "RSVP
              Association Object Extensions",
              draft-ietf-ccamp-assoc-ext-00 (work in progress),
              May 2011.

   [I-D.ietf-ccamp-assoc-info]
              Berger, L., "Usage of The RSVP Association Object", draft-ietf-ccamp-assoc-info-00
              draft-ietf-ccamp-assoc-info-02 (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.
              May 2011.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC4872]  Lang, J., Rekhter, Y., and D. Papadimitriou, "RSVP-TE
              Extensions in Support of End-to-End Generalized Multi-
              Protocol Label Switching (GMPLS) Recovery", RFC 4872,
              May 2007.

   [RFC4873]  Berger, L., Bryskin, I., Papadimitriou, D., and A. Farrel,
              "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

   Francois Le Faucheur
   Cisco Systems
   Greenside, 400 Avenue de Roumanille
   Sophia Antipolis  06410
   France

   Phone: +33 4 97 23 26 19
   Email: flefauch@cisco.com

   Ashok Narayanan
   Cisco Systems
   300 Beaver Brook Road
   Boxborough, MAS  01719
   United States

   Email: ashokn@cisco.com

   Subha Dhesikan
   Cisco Systems

   Phone:
   Email: sdhesika@cisco.com