idnits 2.17.1 draft-rosen-l3vpn-spmsi-joins-mldp-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 24, 2011) is 4567 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Yiqun Cai 3 Internet Draft Eric C. Rosen (Editor) 4 Intended Status: Informational IJsbrand Wijnands 5 Expires: April 24, 2012 Cisco Systems, Inc. 7 October 24, 2011 9 MVPN: S-PMSI Join Extensions for mLDP-Created Tunnels 11 draft-rosen-l3vpn-spmsi-joins-mldp-03.txt 13 Abstract 15 The specification for Multicast Virtual Private Networks (MVPN) 16 contains an option that allows UDP-based "S-PMSI Join" messages to be 17 used to bind particular customer multicast flows to particular 18 tunnels through a service provider's network. This document extends 19 the MVPN specification so that these options can be used when the 20 tunnel through the provider's network are Point-to-Multipoint Label 21 Switched Paths. 23 Status of this Memo 25 This Internet-Draft is submitted to IETF in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF), its areas, and its working groups. Note that 30 other groups may also distribute working documents as 31 Internet-Drafts. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 The list of current Internet-Drafts can be accessed at 39 http://www.ietf.org/ietf/1id-abstracts.txt. 41 The list of Internet-Draft Shadow Directories can be accessed at 42 http://www.ietf.org/shadow.html. 44 Copyright and License Notice 46 Copyright (c) 2011 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1 Specification of requirements ......................... 2 62 2 Introduction .......................................... 3 63 3 S-PMSI Join Extensions ................................ 3 64 3.1 mLDP P2MP P-Tunnels ................................... 3 65 3.2 Encapsulation of S-PMSI Joins in UDP Datagrams ........ 4 66 4 IANA Considerations ................................... 5 67 5 Security Considerations ............................... 5 68 6 Acknowledgments ....................................... 5 69 7 Authors' Addresses .................................... 5 70 8 Normative References .................................. 6 72 1. Specification of requirements 74 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 75 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 76 document are to be interpreted as described in [RFC2119]. 78 2. Introduction 80 The Multicast Virtual Private Networks (MVPN) specification [MVPN] 81 specifies "S-PMSI Join" messages, which are optionally used to bind 82 particular customer multicast flows to particular tunnels through a 83 service provider's network (P-tunnels). However, the specification 84 does not cover the case where the P-tunnels are Point-to-multipoint 85 (P2MP) Label Switched Paths (LSPs) created by the Label Distribution 86 Protocol (LDP) [mLDP]. This document extends [MVPN] by providing the 87 specification for that case. This document uses terminology defined 88 in [MVPN]: C-Source, C-Group, C-flow, P-Group, (C-S,C-G) 90 3. S-PMSI Join Extensions 92 The S-PMSI Join message is defined in section 7.4.2.2 of [MVPN]. In 93 this specification, we define the "type 2" and "type 3" S-PMSI Joins, 94 which are used when the S-PMSI tunnel is a P2MP LSP created by mLDP, 95 and the tunnel is to carry C-flows of, respectively, IPv4 or IPv6 96 multicast traffic. 98 3.1. mLDP P2MP P-Tunnels 100 0 1 2 3 101 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 102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 103 | Type | Length | Reserved | 104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 105 | C-Source 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+....... 107 | C-Group 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+....... 109 | FEC Element 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+....... 111 | Padding 112 +-+-+-+-+-+-+-+....... 114 Type (8 bits): 116 - 2 if C-Source and C-Group are IPv4 addresses, 118 - 3 if C-Source and C-Group are IPv6 addresses. 120 Length (16 bits): the total number of octets in the Type, Length, 121 Reserved and Value fields combined, rounded up to the next multiple 122 of 4, encoded as an unsigned binary integer. 124 Reserved (8 bits): This field SHOULD be zero when transmitted, and 125 MUST be ignored when received. 127 C-Source: address of the traffic source in the VPN 129 - for type 2, a 32-bit IPv4 address 131 - for type 3, a 128-bit IPv6 address 133 C-Group: address of the traffic destination in the VPN 135 - for type 2, a 32-bit IPv4 address 137 - for type 3, a 128-bit IPv6 address 139 FEC Element: this variable length field is a P2MP FEC element, 140 encoded as specified in [mLDP]. (Note that this field is itself 141 encoded with a type field and a length field, as specified in 142 [mLDP].) 144 Padding: 0-3 bytes, as needed for 32-bit alignment. The padding 145 bytes SHOULD be zero on transmission and MUST be ignored on 146 reception. 148 In S-PMSI Join messages, the use of an all-zero C-Source or C-Group 149 field is to be interpreted as specifying a wild card value for the 150 respective field. A wild card represents all C-Source or C-group 151 values of a particular address family (IPv4 or IPv6), as specified by 152 the S-PMSI Join message type. 154 3.2. Encapsulation of S-PMSI Joins in UDP Datagrams 156 All S-PMSI Joins are encapsulated in UDP datagrams. 158 If a UDP datagram contains a type 2 S-PMSI Join, it MUST be sent in 159 an IPv4 datagram. 161 If a UDP datagram contains a type 3 S-PMSI Join, it MUST be sent in 162 an IPv6 datagram, following the specification in [SPMSI_JOIN]. 164 4. IANA Considerations 166 [MVPN] creates an IANA registry for the "S-PMSI Join Message Type 167 Field". This document requires two new values: 169 - The value 2 should be registered, and its description should read 170 "mLDP P2MP S-PMSI for IPv4 traffic (unaggregated)". 172 - The value 3 should be registered, and its description should read 173 "mLDP P2MP S-PMSI for IPv6 traffic (unaggregated)". 175 5. Security Considerations 177 There are no additional security considerations beyond those of 178 [MVPN]. 180 6. Acknowledgments 182 The authors wish to thank DP Ayadevara, Arjen Boers, Rayen Mohanty, 183 Rajesh Sharma, and Karthik Subramanian. 185 7. Authors' Addresses 187 Yiqun Cai 188 Cisco Systems, Inc. 189 170 Tasman Drive 190 San Jose, CA, 95134 191 E-mail: ycai@cisco.co 193 Eric C. Rosen 194 Cisco Systems, Inc. 195 1414 Massachusetts Avenue 196 Boxborough, MA, 01719 197 E-mail: erosen@cisco.com 199 IJsbrand Wijnands 200 Cisco Systems, Inc. 201 De kleetlaan 6a Diegem 1831 202 Belgium 203 E-mail: ice@cisco.com 205 8. Normative References 207 [mLDP] "Label Distribution Protocol Extensions for 208 Point-to-Multipoint and Multipoint-to-Multipoint Label Switched 209 Paths", Minei, Kompella, Wijnands, Thomas, 210 draft-ietf-mpls-ldp-p2mp-15.txt, August 2011 212 [MVPN] "Multicast in MPLS/BGP IP VPNs", Rosen, Aggarwal, et. al., 213 draft-ietf-l3vpn-2547bis-mcast-10.txt, January 2010 215 [RFC2119] "Key words for use in RFCs to Indicate Requirement 216 Levels.", Bradner, March 1997 218 [SPMSI_JOIN] "IPv6 MVPN Support Using PIM Control Plane and S-PMSI 219 Join Messages", Cai, Rosen, Wijnands, draft-ietf-l3vpn-mvpn-spmsi- 220 joins-02.txt, November 2010