Multicast VPN Using BIER
draft-ietf-bier-mvpn-08
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8556.
|
|
---|---|---|---|
Authors | Eric C. Rosen , Mahesh Sivakumar , Sam Aldrin , Andrew Dolganow , Tony Przygienda | ||
Last updated | 2017-10-16 (Latest revision 2017-07-26) | ||
Replaces | draft-rosen-l3vpn-mvpn-bier | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Consensus: Waiting for Write-Up | |
Document shepherd | Nabeel Cocker | ||
IESG | IESG state | Became RFC 8556 (Proposed Standard) | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | Nabeel Cocker <nabeel.cocker@nokia.com> |
draft-ietf-bier-mvpn-08
IPSECME WG A. Noble Internet-Draft S. Gundavelli Intended status: Standards Track Cisco Expires: August 22, 2013 J. Korhonen Nokia Siemens Networks F. Baboescu Broadcom Corporation February 18, 2013 3GPP IMS Option for IKEv2 draft-gundavelli-ipsecme-3gpp-ims-options-00.txt Abstract This document defines two new configuration attributes for Internet Key Exchange Protocol version 2 (IKEv2). These attributes can be used for carrying the IPv4 and IPv6 address of the Proxy-Call Control and Service function (P-CSCF). This is one of the few methods that an IPsec client can obtain the IP address of the P-CSCF function located in the home network. 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 August 22, 2013. Copyright Notice Copyright (c) 2013 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 Noble, et al. Expires August 22, 2013 [Page 1] Internet-Draft 3GPP IMS Option for IKEv2 February 2013 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions and Terminology . . . . . . . . . . . . . . . . . . 3 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 3. P-CSCF_IP4_ADDRESS Configuration Attribute . . . . . . . . . . 4 4. P-CSCF_IP6_ADDRESS Configuration Attribute . . . . . . . . . . 5 5. Example Scenario . . . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . . 7 9.2. Informative References . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 Noble, et al. Expires August 22, 2013 [Page 2] Internet-Draft 3GPP IMS Option for IKEv2 February 2013 1. Introduction The 3GPP S2b reference point [TS23402], specified by the 3GPP system architecture defines a mechanism for allowing a mobile node attached in an untrusted non-3GPP IP Access Network to securely connect to the 3GPP home network and access IP services. In this scenario, the mobile node establishes an IPsec tunnel to the security gateway called ePDG and which in turn establishes a PMIPv6/GTP tunnel to the PDN gateway where the mobile node's session is anchored. The below figure shows the interworking option for Untrusted Non-3GPP access. +------------+ | ePDG | | +--------+ | +------+ _----_ | | IPsec | | _----_ +-----+ | MN | _( )_ | | Module | | _( )_ | LMA | | |<====( Internet )=====| +--------+ |===( Operator )===|(PGW)| +------+ (_ _) | : | (_Network_) +-----+ '----' | +--------+ | '----' IPsec Tunnel | | PMIPv6 | | PMIPv6/GTP Tunnel | | MAG | | | +--------+ | +------------+ |<------------ IKEv2/IPsec ------> | <-------------PMIPv6/GTP-->| Figure 1: Exchange of IPv4 Traffic Offload Selectors A mobile node in this scenario may potentially need to access the IMS services in the home network. Currently, there are no attributes in IKEv2 that can be used for carrying these information elements. In the absence of these Attributes the mobile node needs to be statically configured with this information and this is proving to be an operational challenge. This specification therefore defines two new IKEv2 attributes [RFC5996] that allows an IPsec gateway to provide the IPv4 and/or IPv6 address of the P-CSCF function. These attributes can be exchanged by IKEv2 peers as part of the configuration payload exchange. 2. Conventions and Terminology Noble, et al. Expires August 22, 2013 [Page 3] Internet-Draft 3GPP IMS Option for IKEv2 February 2013 2.1. Conventions 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 RFC 2119 [RFC2119]. 2.2. Terminology All the IKEv2 related terms used in this document are to be interpreted as defined in [RFC5996] and [RFC5739]. All the mobility related terms are to interpreted as defined in [RFC5213] and [RFC5844]. Additionally, this document uses the following terms: Proxy-Call Session Control Function (P-CSCF) The P-CSCF is the entry point to the 3GPP IMS (IP Multimedia Subsystem) domain and serves as the outbound proxy server for the mobile node. The mobile node attaches to the P-CSCF prior to performing IMS registrations and initiating SIP sessions. 3. P-CSCF_IP4_ADDRESS Configuration Attribute The P-CSCF_IP4_ADDRESS configuration attribute is formatted 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |R| Attribute Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | IPv4 Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2: IPv4 Address of P-CSCF Reserved (1 bit) Refer to IKEv2 specification Attribute Type (15 bits) <IANA-1> Length (2 octets) Length of the value field in octets. In this case, its 4. Noble, et al. Expires August 22, 2013 [Page 4] Internet-Draft 3GPP IMS Option for IKEv2 February 2013 IPv4 Address (4 octets) An IPv4 address of the P-CSCF function. Multiple instances of this Attribute with different values can be present in the configuration payload and there is no implied preferrential order. 4. P-CSCF_IP6_ADDRESS Configuration Attribute The P-CSCF_IP4_ADDRESS configuration attribute is formatted 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |R| Attribute Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | | | IPv6 Address | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 3: IPv6 Address of P-CSCF Reserved (1 bit) Refer to IKEv2 specification Attribute Type (15 bits) <IANA-1> Length (2 octets) Length of the value field in octets. In this case, its 16. IPv6 Address (16 octets) An IPv4 address of the P-CSCF function. Multiple instances of this Attribute with different values can be present in the configuration payload and there is no implied preferrential order. 5. Example Scenario The mobile node MAY request the IP address of an P-CSCF function as Noble, et al. Expires August 22, 2013 [Page 5] Rosen, et al. Expires April 19, 2018 [Page 14] Internet-Draft MVPN with BIER October 2017 8. Security Considerations The security considerations of [BIER_ARCH], [BIER_ENCAPS], [RFC6513] and [RFC6514] are applicable. 9. References 9.1. Normative References [BIER_ARCH] Wijnands, IJ., Rosen, E., Dolganow, A., Przygienda, T., and S. Aldrin, "Multicast using Bit Index Explicit Replication", internet-draft draft-ietf-bier-architecture- 07, June 2017. [BIER_ENCAPS] Wijnands, IJ., Rosen, E., Dolganow, A., Tantsura, J., and S. Aldrin, "Encapsulation for Bit Index Explicit Replication in MPLS Networks", internet-draft draft-ietf- bier-mpls-encapsulation-07.txt, June 2017. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>. [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2006, <https://www.rfc-editor.org/info/rfc4364>. [RFC5331] Aggarwal, R., Rekhter, Y., and E. Rosen, "MPLS Upstream Label Assignment and Context-Specific Label Space", RFC 5331, DOI 10.17487/RFC5331, August 2008, <https://www.rfc-editor.org/info/rfc5331>. [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 2012, <https://www.rfc-editor.org/info/rfc6513>. [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, <https://www.rfc-editor.org/info/rfc6514>. [RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R. Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes", RFC 6625, DOI 10.17487/RFC6625, May 2012, <https://www.rfc-editor.org/info/rfc6625>. Rosen, et al. Expires April 19, 2018 [Page 15] Internet-Draft MVPN with BIER October 2017 9.2. Informative References [EXPLICIT_TRACKING] Dolganow, A., Kotalwar, J., Rosen, E., and Z. Zhang, "Explicit Tracking with Wild Card Routes in Multicast VPN", internet-draft draft-ietf-bess-mvpn-expl-track-02, June 2017. [RFC7524] Rekhter, Y., Rosen, E., Aggarwal, R., Morin, T., Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area Point-to-Multipoint (P2MP) Segmented Label Switched Paths (LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015, <https://www.rfc-editor.org/info/rfc7524>. [RFC7900] Rekhter, Y., Ed., Rosen, E., Ed., Aggarwal, R., Cai, Y., and T. Morin, "Extranet Multicast in BGP/IP MPLS VPNs", RFC 7900, DOI 10.17487/RFC7900, June 2016, <https://www.rfc-editor.org/info/rfc7900>. Authors' Addresses Eric C. Rosen (editor) Juniper Networks, Inc. 10 Technology Park Drive Westford, Massachusetts 01886 United States Email: erosen@juniper.net Mahesh Sivakumar Cisco Systems, Inc. 510 McCarthy Blvd Milpitas, California 95035 United States Email: masivaku@cisco.com Sam K Aldrin Google, Inc. 1600 Amphitheatre Parkway Mountain View, California United States Email: aldrin.ietf@gmail.com Rosen, et al. Expires April 19, 2018 [Page 16] Internet-Draft MVPN with BIER October 2017 Andrew Dolganow Nokia 438B Alexandra Rd #08-07/10 Alexandra Technopark Singapore 119968 Email: andrew.dolganow@nokia.com Tony Przygienda Juniper Networks, Inc. 1137 Innovation Way San Jose, California 94089 United States Email: prz@juniper.net Rosen, et al. Expires April 19, 2018 [Page 17]