L3VPN Working Group Y. Peng Internet-Draft X. Wu Intended status: Standards Track D. Wang Expires: July 20, 2010 UESTC January 16, 2010 Dynamic hose model for Virtual Private Network draft-peng-l3vpn-dynamic-hose-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 20, 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents Peng, et al. Expires July 20, 2010 [Page 1] Internet-Draft Dynamic hose model for VPN January 2010 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 presents a method that allowing a Customer Edge (CE) to automatically control the up-and-down bandwidth of the hose interface in the Hose VPN Model. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Hose Mode Overview . . . . . . . . . . . . . . . . . . . . . . 4 4. CE Control Unit . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Sending Control Unit . . . . . . . . . . . . . . . . . . . 4 4.2. Receiving Control Unit . . . . . . . . . . . . . . . . . . 5 5. PE Control Unit . . . . . . . . . . . . . . . . . . . . . . . 5 6. Message Format . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1. Bandwidth Query or Control Message . . . . . . . . . . . . 6 6.2. Bandwidth Adjust Application Message . . . . . . . . . . . 8 7. Client Control Mode . . . . . . . . . . . . . . . . . . . . . 9 7.1. Timer Mode . . . . . . . . . . . . . . . . . . . . . . . . 10 7.2. Increase Send Bandwidth Control Mode . . . . . . . . . . . 10 7.3. Decrease Send Bandwidth control Mode . . . . . . . . . . . 10 7.4. Increase Receive Bandwidth control Mode . . . . . . . . . 10 7.5. Decrease Receive Bandwidth control Mode . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 9. Security Considerations . . . . . . . . . . . . . . . . . . . 11 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 10.1. Normative References . . . . . . . . . . . . . . . . . . . 11 10.2. Informative References . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Peng, et al. Expires July 20, 2010 [Page 2] Internet-Draft Dynamic hose model for VPN January 2010 1. Introduction This document presents a method that allowing a Customer Edge (CE) to automatically control the up-and-down bandwidth of the hose interface in the Hose VPN Model. For instance, in the hose VPN method, when a CE transmits great deal of data to other client /clients of the same hose VPN, it could send message automatically to the provider edge and other client (or clients) for applying to increase the bandwidth. When the transmittal is finished, the sending and the receiving CE will automatically decrease the send and the receive bandwidth of the hose interface to their normal states. The mechanism can satisfy the demand that the client adjust bandwidth of hose interface dynamically to level up the network utility and to support bandwidth on demand (BoD) services Via L3 VPN. 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]. This document uses terminologies defined in RFC4031 [RFC4031], RFC2205 [RFC2205], RFC3209 [RFC3209], RFC4461 [RFC4461], and RFC4110 [RFC4110]. The reader is assumed to be familiar with the terminology in [Extensions to P2MP RSVP-TE for Hose Model Provisioning in L3 PPVPN]. The NHSB, the Needed Hose Send Bandwidth, is needed bandwidth for CE to send data in the send buffer. The HSB, the Hose Send Bandwidth, is the biggest bandwidth for CE to send data. The IHSB, the Initiating Hose Send Bandwidth, is the smallest HSB of CE, and is fixed when the Hose VPN is established. The CHRB, the Current Hose Receive Bandwidth, is current speed of receive data stream for CE. The HRB, the Hose Receive Bandwidth, is the biggest bandwidth for CE to receive data. The IHRB, the Initiating Hose Receive Bandwidth, is the smallest HSB of CE, and is fixed when the Hose VPN is established. The threshold Bth, is the threshold of bandwidth adjusting. If the value of difference is bigger than Bth, the state will increase or Peng, et al. Expires July 20, 2010 [Page 3] Internet-Draft Dynamic hose model for VPN January 2010 decrease the Hose Interface bandwidth. 3. Hose Mode Overview In Hose VPN, a hose is used to connect the customers and its VPN network. The customer does not have to specify the traffic matrix or the spread of this traffic to other customers like traditional VPN network, and it only needs to specify the performance characteristics of Hose Interface bandwidth. The provider can ensure the hose interface performance in Hose VPN. 4. CE Control Unit CE Control Unit is with CE, consisting of Sending Control Unit and Receiving Control Unit.CE Control Unit is used to control the up-and- down bandwidth of hose interface; send and receive message to adjust hose interface bandwidth; and detect data stream in the sending or receiving buffer.The architecture of CE Control Unit is illustrated in Figure 1.It includes one Sending Control Unit, one Receiving Control Unit and two buffers for data sending and data reception. ___________________________________ | User-controlled Unit | | __________________________ | |--|->| Transmitter control Unit|<-| | | | -------------------------- | | ___________ | | ________________________ | | |Hose model|<----|->| Transmitter buffer |<---| | |interface | | ========================= | ------------<----|->| Receiver buffer |<---| | | | ------------------------ | | | | __________________________ | | |--|->| Receiver control Unit |<-| | | -------------------------- | |_________________________________| Figure 1.CE Control Unit 4.1. Sending Control Unit The functions of Sending Control Unit are as follows. Peng, et al. Expires July 20, 2010 [Page 4] Internet-Draft Dynamic hose model for VPN January 2010 o Detect the number of data stream in sending buffer and compute the NHSB with the number. o According to relation of the NHSB, the HSB and the IHSB, decide to go into which model, Timer Model, Increasing Send Bandwidth Model or Decrease Send Bandwidth Model. o Charges of sending Bandwidth Adjust Application Message to the Receive CE via Hose VPN for getting the negotiated receive bandwidth for Receive CE, and receiving ACK message. o Charge of sending Bandwidth Control Message to PE via Link Control channel to increase or decrease Hose Sending Bandwidth, and receiving ACK message. 4.2. Receiving Control Unit The functions of Receiving Control Unit are as follows. o Detect the number of data stream in receiving buffer and compute the CHRB with the number. o According to relation of the CHRB, the HRB and the IHRB, decide to go into which model, Timer Model, Increase Receive Bandwidth Model or Decrease Receive Bandwidth Model. o Charges of receiving Bandwidth Adjust Application Message, ensure the appropriate receive bandwidth according to the applied receive bandwidth and the receive ability of local machine, return ACK message, and make Receive Data Control Unit go into the Increase Receive Bandwidth Model. o Charge of sending Bandwidth Control Message to PE via Link Control channel to increase or decrease Hose Sending Bandwidth, and receiving ACK message. 5. PE Control Unit PE Control Unit is with PE. It is used to receive Bandwidth Adjust Application Message; compute the appropriate bandwidth according to the the applied bandwidth increased in Bandwidth Adjust Application Message; and send the ACK message of the Bandwidth Adjust Application Message.In addition, the PE Control Unit can increase or decrease the Hose Receive or Send Bandwidth according to the Bandwidth Control Message received. 6. Message Format Some new message formats are created to transfer information. Peng, et al. Expires July 20, 2010 [Page 5] Internet-Draft Dynamic hose model for VPN January 2010 6.1. Bandwidth Query or Control Message The general message format of Bandwidth Query or Adjust Application Message has the following format. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Message Attribute | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of hose interface | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | CE Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Bandwidth | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ....... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ....... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Destination Address: 32 bits The Destination Address is the final destination for the message. It may be CE address or PE address. Source Address: 32 bits The Source Address is the object's address who creates this message, and only CE can do this. Message Attribute: 32 bits Indicates the style of message. The following table shows the permitted values and their meaning. Peng, et al. Expires July 20, 2010 [Page 6] Internet-Draft Dynamic hose model for VPN January 2010 +-------+---------------------------------------------------+ | Value | Meaning | +-------+---------------------------------------------------+ | 0 | Bandwidth Query Message | | 1 | ACK of Bandwidth Query Message | | 2 | Bandwidth Increase Control Message | | 3 | ACK of Bandwidth Increase Control Message | | 4 | Send Bandwidth Decrease Control Message | | 5 | ACK of Send Bandwidth Decrease Control Message | | 6 | Receive Bandwidth Decrease Control Message | | 7 | ACK of Receive Bandwidth Decrease Control Message | +-------+---------------------------------------------------+ Table 1: The meaning of Message Attribute for Bandwidth Query or Control Message According to the difference of message attribute, the meaning of CE address and Bandwidth are different. Number of hose interface: 32 bits Indicates the number of CE needed to adjust hose bandwidth. CE Address and Bandwidth: Indicates the reference CE needed to adjust the corresponding hose bandwidth.For different Message Attribute, it has different meaning. o On receiving the Bandwidth Query Message, a PE will look out the associated receiving PEs and receiving CEs, as well as Bandwidth to be increased. o The PE will then compute the appropriated bandwidth network can provide. The appropriated bandwidth is send to each CE in ACK of Bandwidth Query Message. o On receiving the Bandwidth Increase Control Message, the PE will recompute the path bandwidth from the source PE to the destination PE according to the Bandwidth and CE Address in the message, so that the source PE will increase HSB and the destination PE will increase HRB. o In ACK of Bandwidth Increase Control Message, the value of Bandwidth is the real bandwidth increased for each CE Address. o When the message PE received is the Send Bandwidth Decrease Control Message, PE will decrease HSB. After that, it will recompute the path bandwidth and adjust link to improve utility of network. o In ACK of Send Bandwidth Decrease Control Message, the value of Bandwidth is the real bandwidth decreased. Peng, et al. Expires July 20, 2010 [Page 7] Internet-Draft Dynamic hose model for VPN January 2010 o On receiving the Receive Bandwidth Decrease Control Message, the PE will decrease HRB, and then recompute the path bandwidth. o In ACK of Receive Bandwidth Decrease Control Message, the value of Bandwidth is the real bandwidth decreased. 6.2. Bandwidth Adjust Application Message The format of Bandwidth Adjust Application Message is as follows. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Message Attribute | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Bandwidth | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Destination Address: 32 bits The Destination Address is the final destination for the message and it is CE address. Source Address: 32 bits The Source Address is the object's address who creates this message and it is a CE address. Message Attribute: 32 bits Indicates the style of message. The following table shows the permitted values. +-------+---------------------------------------------+ | Value | Meaning | +-------+---------------------------------------------+ | 0 | Bandwidth Adjust Application Message | | 1 | ACK of Bandwidth Adjust Application Message | +-------+---------------------------------------------+ Table 2: The meaning of Message Attribute for Bandwidth Adjust Application Message Peng, et al. Expires July 20, 2010 [Page 8] Internet-Draft Dynamic hose model for VPN January 2010 Bandwidth: 32 bits For different Message Attribute, it has different meaning. o For Bandwidth Adjust Application Message, the destination CE is required to adjust the Bandwidth demanded by the source CE. o The destination CE will compute the appropriate HRB, and return ACK of Bandwidth Adjust Application Message with the value of Bandwidth. 7. Client Control Mode Hose VPN is configured with default configuration when established. With default state, HSB is equal to IHSB in Sending Control Unit and HRB is equal to IHRB in Receiving Control Unit. When Hose VPN began to run, HSB may equal to or bigger than IHSB, and HRB may equal to or smaller than IHRB. In Sending Control Unit: 1. If the IHSB is smaller than or equal to HSB, the state will go into Send Timer Mode, or the state will continue judging conditions from step 2. 2. If the absolute value of NHSB subtracting HRB is smaller than threshold value Bth, the state will go into Send Timer Mode, or the state will continue judging conditions from step 3. 3. If NHSB is bigger than HSB, the state will go into Increase Send Bandwidth Control Mode, or the state will go into Decrease Send Bandwidth control Mode. 4. When the Send Timer Mode is end, the state will restart to judge conditions from step 1. In Receiving Control Unit: 1. If the state receives Bandwidth Adjust Application Message, it will go into Increase Receive Bandwidth control Mode, or it will go into Receive Timer Mode. 2. When the Receive Timer Mode is end, the state will continue judging conditions as follows. If the value of HRB subtracting CHRB is smaller than Bth, the state will continue judge condition from step I, or it will continue judge conditions from step 3. 3. If HRB is bigger than IHRB, the state will go into Decrease Receive Bandwidth control Mode, or it will go into Receive Timer Mode. Peng, et al. Expires July 20, 2010 [Page 9] Internet-Draft Dynamic hose model for VPN January 2010 7.1. Timer Mode In Timer Mode, the state will compute time through a time counter. After a fixed interval of time, the Timer Mode will end automatically. 7.2. Increase Send Bandwidth Control Mode In Increase Send Bandwidth Control Mode, the state will send Bandwidth Query Message to PE and then wait for ACK of Bandwidth Query Message. If there is no bandwidth available in ACK of Bandwidth Query Message, the state will go into Send Timer Mode, or it will continue send Bandwidth Adjust Application Message and then wait for the ACK of Bandwidth Adjust Application Message. At the same method, it there is no bandwidth available in ACK of Bandwidth Adjust Application Message, the state will go into Send Timer Mode, or it will send Bandwidth Increase Control Message, and then wait for ACK of Bandwidth Increase Control Message. If it is failed in ACK of Bandwidth Increase Control Message, the state will go into Send Timer Mode, or it will increase local Hose Interface Send bandwidth and then go into Send Timer Mode. 7.3. Decrease Send Bandwidth control Mode In Decrease Send Bandwidth control Mode, the state will decrease local Hose Interface Send bandwidth firstly, and then send Send Bandwidth Decrease Control Message and wait for ACK of Send Bandwidth Decrease Control Message. After receive the ACK message, the state will go into the Send Timer Mode. 7.4. Increase Receive Bandwidth control Mode After receive Bandwidth Adjust Application Message in Increase Receive Bandwidth control Mode, the state will judge whether the local machine can full the demand of source CE. If Yes, the state will increase local Hose Interface Receive bandwidth and then reply ACK of Bandwidth Adjust Application Message; or No, the state will reply ACK message indirectly. After replying ACK message, the state will go into Receive Timer Mode. 7.5. Decrease Receive Bandwidth control Mode In Decrease Receive Bandwidth control Mode, the state will send Receive Bandwidth Decrease Control Message to PE and then wait for the ACK message. After receive ACK of Receive Bandwidth Decrease Control Message, the state will decrease local Hose Interface Receive bandwidth and then the state will go into Receive Timer Mode. Peng, et al. Expires July 20, 2010 [Page 10] Internet-Draft Dynamic hose model for VPN January 2010 8. IANA Considerations This memo includes no request to IANA. 9. Security Considerations Since association of a particular port with a Hose VPN is done by the service provider as part of the service provisioning process, and since signaling between CE and PE is assumed to be over a private network, the solution described in this document doesn't require authentication in signaling. 10. References 10.1. Normative References [RFC2205] Braden, B., Zhang, L., Berson, S., Herzog, S., and S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification", RFC 2205, September 1997. [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001. [RFC4031] Carugi, M. and D. McDysan, "Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs)", RFC 4031, April 2005. [RFC4110] Callon, R. and M. Suzuki, "A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)", RFC 4110, July 2005. [RFC4461] Yasukawa, S., "Signaling Requirements for Point-to- Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)", RFC 4461, April 2006. 10.2. Informative References [I-D.byun-vpn-provision-rsvp-te] Byun, H. and M. Lee, "Extensions to P2MP RSVP-TE for Hose Model Provisioning in L3 PPVPN", draft-byun-vpn-provision-rsvp-te-00 (work in progress), June 2006. [I-D.ietf-mpls-rsvp-te-p2mp] Aggarwal, R., "Extensions to RSVP-TE for Point to Peng, et al. Expires July 20, 2010 [Page 11] Internet-Draft Dynamic hose model for VPN January 2010 Multipoint TE LSPs", draft-ietf-mpls-rsvp-te-p2mp-05 (work in progress), May 2006. Authors' Addresses Yunfeng Peng University of Electronic Science and Technology of China 2006 Xiyuan Road Gaoxinxiqu Chengdu 200240 CN Phone: +86 13880719187 Email: yfpeng@uestc.edu.cn Xufeng Wu University of Electronic Science and Technology of China 2006 Xiyuan Road Gaoxinxiqu Chengdu, 200240 CN Email: wuxiufeng@uestc.edu.cn Dong Wang University of Electronic Science and Technology of China 2006 Xiyuan Road Gaoxinxiqu Chengdu 200240 CN Phone: +86 13880432704 Email: wangdongflower@163.com Peng, et al. Expires July 20, 2010 [Page 12]