Internet Engineering Task Force (IETF) Y. Cai
Request for Comments: 6516 E. Rosen, Ed.
Category: Standards Track IJ. Wijnands
ISSN: 2070-1721 Cisco Systems
February 2012
Internet Engineering Task Force (IETF) Y. Cai
Request for Comments: 6516 E. Rosen, Ed.
Category: Standards Track IJ. Wijnands
ISSN: 2070-1721 Cisco Systems
February 2012
IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane and Selective Provider Multicast Service Interface (S-PMSI) Join Messages
IPv6多播VPN（MVPN）支持使用PIM控制平面和选择性提供商多播服务接口（S-PMSI）加入消息
Abstract
摘要
The specification for Multicast Virtual Private Networks (MVPNs) contains an option that allows the use of PIM as the control protocol between provider edge routers. It also contains an option that allows UDP-based messages, known as Selective Provider Multicast Service Interface (S-PMSI) Join messages, to be used to bind particular customer multicast flows to particular tunnels through a service provider's network. This document extends the MVPN specification (RFC 6513) so that these options can be used when the customer multicast flows are IPv6 flows.
多播虚拟专用网络（MVPN）规范包含一个选项，允许使用PIM作为提供商边缘路由器之间的控制协议。它还包含一个选项，允许使用基于UDP的消息（称为选择性提供商多播服务接口（S-PMSI）连接消息）通过服务提供商的网络将特定的客户多播流绑定到特定的隧道。本文档扩展了MVPN规范（RFC 6513），以便在客户多播流为IPv6流时可以使用这些选项。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6516.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6516.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 IETF信托基金和确定为文件作者的人员。版权所有。
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
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您在以下方面的权利和限制：
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.
请参阅本文件。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
2. Specification of Requirements ...................................3
3. S-PMSI Joins Binding IPv6 Flows to GRE/IPv4 P-Tunnels ...........3
3.1. Encoding ...................................................3
3.2. Encapsulation of S-PMSI Joins in UDP Datagrams .............4
4. PE-PE PIM/IPv6 over an IPv4 P-Tunnel ............................4
5. IANA Considerations .............................................5
6. Security Considerations .........................................5
7. Acknowledgments .................................................5
8. Normative References ............................................5
1. Introduction ....................................................2
2. Specification of Requirements ...................................3
3. S-PMSI Joins Binding IPv6 Flows to GRE/IPv4 P-Tunnels ...........3
3.1. Encoding ...................................................3
3.2. Encapsulation of S-PMSI Joins in UDP Datagrams .............4
4. PE-PE PIM/IPv6 over an IPv4 P-Tunnel ............................4
5. IANA Considerations .............................................5
6. Security Considerations .........................................5
7. Acknowledgments .................................................5
8. Normative References ............................................5
The Multicast Virtual Private Network (MVPN) specification [RFC6513] defines the notion of a "PMSI" (Provider Multicast Service Interface) and specifies how a PMSI can be instantiated by various kinds of tunnels through a service provider's network ("P-tunnels"). It also specifies the procedures for using PIM (Protocol Independent Multicast [RFC4601]) as the control protocol between Provider Edge (PE) routers. When PIM is used as the control protocol, PIM messages are sent through a P-tunnel from one PE in an MVPN to others in the same MVPN. These PIM messages carry customer multicast routing information. However, [RFC6513] does not cover the case where the customer is using IPv6, but the service provider is using P-tunnels created by PIM over an IPv4 infrastructure.
多播虚拟专用网（MVPN）规范[RFC6513]定义了“PMSI”（提供商多播服务接口）的概念，并规定了如何通过服务提供商的网络（“P隧道”）通过各种隧道实例化PMSI。它还规定了使用PIM（协议独立多播[RFC4601]）作为提供商边缘（PE）路由器之间的控制协议的过程。当PIM用作控制协议时，PIM消息通过P隧道从MVPN中的一个PE发送到同一MVPN中的其他PE。这些PIM消息携带客户多播路由信息。但是，[RFC6513]不包括客户使用IPv6的情况，但服务提供商使用PIM通过IPv4基础设施创建的P隧道。
The MVPN specification [RFC6513] also specifies "S-PMSI (Selective PMSI) Join" messages, which are optionally used to bind particular customer multicast flows to particular P-tunnels. However, the specification does not cover the case where the customer flows are IPv6 flows.
MVPN规范[RFC6513]还指定了“S-PMSI（选择性PMSI）连接”消息，这些消息可选地用于将特定客户多播流绑定到特定的P隧道。但是，该规范不包括客户流为IPv6流的情况。
This document extends [RFC6513] by adding the specification for handling customer IPv6 multicast flows when a service provider is using PE-PE PIM and/or S-PMSI Join messages over an IPv4 infrastructure. This document also specifies how to send multiple S-PMSI Join messages in a single UDP datagram.
本文档扩展了[RFC6513]，添加了当服务提供商在IPv4基础设施上使用PE-PE PIM和/或S-PMSI连接消息时处理客户IPv6多播流的规范。本文档还指定了如何在单个UDP数据报中发送多个S-PMSI连接消息。
This document uses terminology defined in [RFC6513]: C-source, C-group, C-flow, P-group, and (C-S,C-G).
本文件使用[RFC6513]中定义的术语：C源、C组、C流、P组和（C-S、C-G）。
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]中所述进行解释。
The S-PMSI Join message is defined in Section 7.4.2.2 of [RFC6513]. These messages contain a type field, and [RFC6513] defines only Type 1 S-PMSI Joins. A Type 1 S-PMSI Join may be used to assign a customer IPv4 (C-S,C-G) flow to a P-tunnel that is created by PIM/IPv4. To transmit data or control packets over such a P-tunnel, the packets are encapsulated in GRE (Generic Routing Encapsulation) within IPv4, as specified in Section 12 of [RFC6513].
[RFC6513]第7.4.2.2节定义了S-PMSI连接消息。这些消息包含类型字段，[RFC6513]仅定义类型1 S-PMSI联接。类型1 S-PMSI联接可用于将客户IPv4（C-S，C-G）流分配给由PIM/IPv4创建的P隧道。如[RFC6513]第12节所述，为了通过这样的P隧道传输数据或控制数据包，数据包被封装在IPv4内的GRE（通用路由封装）中。
In this document, we define the Type 4 S-PMSI Join. A Type 4 S-PMSI Join may be used to assign a customer IPv6 (C-S,C-G) flow to a P-tunnel that is created by PIM/IPv4. GRE/IPv4 encapsulation is used to send data or control packets on the P-tunnel.
在本文档中，我们定义了类型4 S-PMSI联接。类型4 S-PMSI联接可用于将客户IPv6（C-S、C-G）流分配给由PIM/IPv4创建的P隧道。GRE/IPv4封装用于在P隧道上发送数据或控制数据包。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| C-source |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| C-group |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| P-group |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| C-source |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| C-group |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| P-group |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (8 bits): 4
类型（8位）：4
Length (16 bits): 40, the length in octets of the entire S-PMSI Join message, including the Type, Length, Reserved, C-source, C-group, and P-group fields.
长度（16位）：40，整个S-PMSI连接消息的长度（以八位字节为单位），包括类型、长度、保留、C源、C组和P组字段。
Reserved (8 bits): this field SHOULD be zero when transmitted and MUST be ignored when received.
保留（8位）：此字段在传输时应为零，在接收时必须忽略。
C-source (128 bits): the IPv6 address of the traffic source in the VPN.
C源（128位）：VPN中流量源的IPv6地址。
C-group (128 bits): the IPv6 group address of the multicast traffic.
C组（128位）：多播流量的IPv6组地址。
P-group (32 bits): the IPv4 group address identifying the P-tunnel. Data packets sent on this tunnel are encapsulated in IPv4 GRE packets with this group address in the IP destination address field of the outer header.
P组（32位）：标识P隧道的IPv4组地址。在此隧道上发送的数据包封装在IPv4 GRE数据包中，该组地址位于外部报头的IP目标地址字段中。
All S-PMSI Joins are encapsulated in UDP datagrams [RFC768]. A Type 4 S-PMSI Join MUST be encapsulated in an IPv6 UDP datagram. The IPv6 source address field of these datagrams SHOULD be the IPv4-mapped IPv6 address [RFC4291] corresponding to the IPv4 address that the originating PE router uses as its source address in the instance of PIM that is used to create the specified P-tunnel.
所有S-PMSI联接都封装在UDP数据报[RFC768]中。类型4 S-PMSI联接必须封装在IPv6 UDP数据报中。这些数据报的IPv6源地址字段应为IPv4映射IPv6地址[RFC4291]，对应于发起PE路由器在用于创建指定P隧道的PIM实例中用作其源地址的IPv4地址。
A single UDP datagram MAY carry multiple S-PMSI Join messages, as many as can fit entirely within it. If there are multiple S-PMSI Joins in a UDP datagram, they MUST be of the same S-PMSI Join type. The end of the last S-PMSI Join (as determined by the S-PMSI Join length field) MUST coincide with the end of the UDP datagram, as determined by the UDP length field. When processing a received UDP datagram that contains one or more S-PMSI Joins, a router MUST process all the S-PMSI Joins that fit into the datagram.
一个UDP数据报可以携带多个S-PMSI连接消息，尽可能多的消息可以完全包含在其中。如果UDP数据报中存在多个S-PMSI联接，则它们必须具有相同的S-PMSI联接类型。最后一个S-PMSI联接的结束（由S-PMSI联接长度字段确定）必须与UDP数据报的结束（由UDP长度字段确定）一致。当处理接收到的包含一个或多个S-PMSI联接的UDP数据报时，路由器必须处理适合该数据报的所有S-PMSI联接。
If a VPN customer is using PIM over IPv6, but the SP (service provider) is using an IPv4 infrastructure (i.e., is using an IPv4-based control protocol to construct its P-tunnels), then the PE routers will need to originate IPv6 PIM control messages. The IPv6 Source Address field of any such IPv6 PIM control message SHOULD be the IPv4-mapped IPv6 address [RFC4291] corresponding to the IPv4 address that the originating PE router uses as its source address in the instance of PIM that is used to create the specified P-tunnel. If the IPv6 Destination Address field is the multicast address ALL-PIM-ROUTERS, the IPv6 form of the address (ff02::d) is used. These IPv6 PIM control messages are, of course, not transmitted natively over the service provider's network but rather are encapsulated in GRE/IPv4.
如果VPN客户正在使用IPv6上的PIM，但SP（服务提供商）正在使用IPv4基础设施（即，正在使用基于IPv4的控制协议来构建其P隧道），则PE路由器将需要发起IPv6 PIM控制消息。任何此类IPv6 PIM控制消息的IPv6源地址字段应为IPv4映射IPv6地址[RFC4291]，对应于原始PE路由器在用于创建指定P隧道的PIM实例中用作其源地址的IPv4地址。如果IPv6目标地址字段是多播地址ALL-PIM-ROUTERS，则使用地址的IPv6形式（ff02:：d）。当然，这些IPv6 PIM控制消息不是通过服务提供商的网络本地传输的，而是封装在GRE/IPv4中。
[RFC6513] created an IANA registry for the "S-PMSI Join Message Type Field". This document registers a new value in that registry:
[RFC6513]为“S-PMSI连接消息类型字段”创建了IANA注册表。此文档在该注册表中注册一个新值：
Value: 4 Description: GRE S-PMSI for IPv6 traffic (unaggregated)
值：4说明：IPv6流量的GRE S-PMSI（未汇总）
There are no additional security considerations beyond those of [RFC6513].
除了[RFC6513]的安全注意事项外，没有其他安全注意事项。
The authors wish to thank DP Ayyadevara, Arjen Boers, Rayen Mohanty, Rajesh Sharma, and Karthik Subramanian.
作者希望感谢DP Ayyadevara、Arjen Boers、Rayen Mohanty、Rajesh Sharma和Karthik Subramanian。
[RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980.
[RFC768]Postel，J.，“用户数据报协议”，STD 6，RFC 768，1980年8月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006.
[RFC4291]Hinden，R.和S.Deering，“IP版本6寻址体系结构”，RFC 42912006年2月。
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", RFC 4601, August 2006.
[RFC4601]Fenner，B.，Handley，M.，Holbrook，H.，和I.Kouvelas，“协议独立多播-稀疏模式（PIM-SM）：协议规范（修订版）”，RFC 46012006年8月。
[RFC6513] Rosen, E., Ed., and R. Aggarwal, Ed., "Multicast in MPLS/BGP IP VPNs", RFC 6513, February 2012.
[RFC6513]Rosen，E.，Ed.，和R.Aggarwal，Ed.，“MPLS/BGP IP VPN中的多播”，RFC 6513，2012年2月。
Authors' Addresses
作者地址
Yiqun Cai Cisco Systems, Inc. 170 Tasman Drive San Jose, CA 95134 EMail: ycai@cisco.com
蔡益群思科系统有限公司，地址：加利福尼亚州圣何塞塔斯曼大道170号，邮编：95134电子邮件：ycai@cisco.com
Eric C. Rosen (editor) Cisco Systems, Inc. 1414 Massachusetts Avenue Boxborough, MA 01719 EMail: erosen@cisco.com
Eric C.Rosen（编辑）Cisco Systems，Inc.马萨诸塞州伯斯堡马萨诸塞大道1414号邮编01719电子邮件：erosen@cisco.com
IJsbrand Wijnands Cisco Systems, Inc. De kleetlaan 6a Diegem 1831 Belgium EMail: ice@cisco.com
IJsbrand Wijlands Cisco Systems，Inc.De kleetlaan 6a Diegem 1831比利时电子邮件：ice@cisco.com