Network Working Group D. Wang, Ed. Internet-Draft Y. Peng, Ed. Intended status: Standards Track UESTC Expires: July 13, 2010 January 9, 2010 Extension to RSVP-TE for signaling control of dynamic Hose-based VPN draft-wang-mpls-rsvp-te-00.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on July 13, 2010. Copyright Notice Copyright (c) 2010 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 Wang & Peng Expires July 13, 2010 [Page 1] Internet-Draft Extension to RSVP-TE for Hose VPN January 2010 (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 BSD License. Abstract This document describes the extension to resource reservation protocol-traffic engineering for signaling control of dynamic Hose- based VPN. The signaling procedure is used to achieve dynamic revision of hose interface. This document proposes a new Hose-Notify message and a series of signaling procedure for extension of RSVP-TE to achieve this function. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Hose-Notify message . . . . . . . . . . . . . . . . . . . . . 5 4.1. Introduction of Hose-Notify message . . . . . . . . . . . 6 4.2. VPN_Request Object . . . . . . . . . . . . . . . . . . . . 6 4.3. VPN_Response Object . . . . . . . . . . . . . . . . . . . 8 4.3.1. VPN_ACK Object . . . . . . . . . . . . . . . . . . . . 8 4.3.2. VPN_NACK Object . . . . . . . . . . . . . . . . . . . 9 4.3.3. Rerouting_ACK Object . . . . . . . . . . . . . . . . . 11 4.4. Hose_Resizing Object . . . . . . . . . . . . . . . . . . . 12 4.5. Net_Inf_Notify Object . . . . . . . . . . . . . . . . . . 13 4.6. Hose state block (HSB) . . . . . . . . . . . . . . . . . . 14 4.7. Network state block (NSB) . . . . . . . . . . . . . . . . 15 5. Signaling Procedures . . . . . . . . . . . . . . . . . . . . . 15 5.1. VPN Connection Establishment . . . . . . . . . . . . . . . 15 5.2. Hose Resizing and Routing update procedure . . . . . . . . 16 5.3. Notification of Network Information . . . . . . . . . . . 17 5.4. Resv message Failure for insufficient network resources . 18 6. Update Message object of RSVP-TE . . . . . . . . . . . . . . . 19 6.1. Extension of sender template . . . . . . . . . . . . . . . 19 6.2. Extension for Filter Specification Object . . . . . . . . 20 6.3. Extension for Explicit Route Object . . . . . . . . . . . 21 6.4. Extension for Error Code . . . . . . . . . . . . . . . . . 22 7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 8.1. New message Type . . . . . . . . . . . . . . . . . . . . . 22 8.2. New Class Numbers . . . . . . . . . . . . . . . . . . . . 23 8.3. New Object Types . . . . . . . . . . . . . . . . . . . . . 23 8.4. New Error Code . . . . . . . . . . . . . . . . . . . . . . 24 Wang & Peng Expires July 13, 2010 [Page 2] Internet-Draft Extension to RSVP-TE for Hose VPN January 2010 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 24 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 10.1. Normative References . . . . . . . . . . . . . . . . . . . 25 10.2. Informative References . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 Wang & Peng Expires July 13, 2010 [Page 3] Internet-Draft Extension to RSVP-TE for Hose VPN January 2010 1. Introduction To solve the resource provisioning in virtual private networks (VPNs), two interface models are defined. One is the pipe model, and the other is the hose model [Duf1999]. Compared with pipe model, hose model provides important advantages to a VPN. It is easy to specify QoS requests from customer since only one inward and outward rate per hose endpoint needs to be specified. It also provides flexibility by allowing packets to and from a given hose endpoint to be distributed arbitrarily over other endpoints. Statistical multiplexing gains can also be achieved on hose rate aggregation. And the requirements are easier to be characterized because the statistical variability of each pipe is smoothed by aggregating into hoses. Section 3 of [Duf1999] describes a Dynamically Resized VPNs, in which online measurements are used to determine the capacity requirements of hoses and then the amount of resources are reserved dynamically adapting to such measurements. To accommodate the above requirements, methods for traffic measuring and signaling protocols for dynamically reserving resources are required. [Duf1999] only gave the method for prediction of traffic rates, and no signaling protocol was mentioned. The new features described in this document are focusing on signaling protocol scenario for dynamically resized VPNs. RSVP-TE is a protocol used to establish label-switched paths (LSPs) with traffic engineering in MPLS (Multi-Protocol Label Switching). The capability of RSVP-TE on supporting explicit routing facilitates constructing a dynamically resizable VPN. The optimal VPN tunnels can be renewed just through simply changing the explicit route object. The signaling protocol discussed in this document is used to achieve the dynamically resizable VPN, including the resizable hose interface at customer side and the changeable explicit routing. To complete these function, some additional objects and a new message are proposed in the document. And some related RSVP-TE objects are also redefined. The purpose of this document is to describe extensions of RSVP-TE to realize dynamically resizable VPN. All the associated objects, package format, and signaling procedures for interoperation between customer edge (CE) and provider edge (PE), are described in detail. All objects and messages described in this document are optional, i.e., RSVP-TE can still work on its basic functions without these objects and messages. Wang & Peng Expires July 13, 2010 [Page 4] Internet-Draft Extension to RSVP-TE for Hose VPN January 2010 All the CEs and PEs participate in a multicast group via IGMP [RFC2236], and all the messages are transmitted and received by group package. 2. Terminology 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 [RFC2119] This document uses terminologies defined in RFC2205 [RFC2205],RFC3209 [RFC3209],RFC2236 [RFC2236] The reader is assumed to be familiar with the terminology in RFC3209 [RFC3209] 3. Overview This document defines extensions to RSVP-TE protocol as signaling to establish a user-controlled dynamic hose-based VPN. This document relies on the semantics of RSVP-TE for building hose LSPs and explicit routing. This document describes a new message which contains four new objects. The new message, termed as Hose-Notify message, has several functions including VPN connection request, Notification of hose model resizing, and notification of network information changed. To perform the signaling procedure of dynamic hose-based VPN, some of the RSVP-TE message objects, such as sender template object, filter specification object, explicit routing object, and extension of Error Code, are revised. In this document, Custom Edges (CEs) resize the hose interface via prediction on local traffic, and Provider Edges (PEs) renew the optimal routing by calculating the explicit routing. Nevertheless, explicit routing calculation aspects for optimal routing and local traffic prediction are outside of scope of this document. Specifically, the extensions described in this draft include the message formats and the signaling flow chart. The constructions for hose LSPs and resource reservation are completed by original RSVP-TE. 4. Hose-Notify message Wang & Peng Expires July 13, 2010 [Page 5] Internet-Draft Extension to RSVP-TE for Hose VPN January 2010 4.1. Introduction of Hose-Notify message Hose-Notify message is a new message as an additional component of RSVP-TE for hose-based VPN. The effect of Hose-Notify message is divided into two parts; one is used to complete the VPN connection request through hose interface, the other is used to send notification message whether hose interface size is changed or network information is changed. The format of Hose-Notify message is as follows: Hose-Notify message Type =TBD ::= [ ]