idnits 2.17.1 draft-ietf-idr-mdrs-00.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 (February 4, 2014) is 3706 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) 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 Internet Engineering Task Force H. Jeng 3 Internet-Draft AT&T 4 Intended status: Standards Track J. Haas 5 Expires: August 8, 2014 Y. Rekhter 6 J. Zhang 7 Juniper Networks 8 February 4, 2014 10 Multicast Distribution Reachability Signaling 11 draft-ietf-idr-mdrs-00 13 Abstract 15 This document describes a mechanism whereby a subscriber's Internet 16 service provider may signal in BGP the ability of the subscriber 17 network to receive content using multicast connectivity. This 18 mechanism is called Multicast Distribution Reachability Signaling 19 (MDRS). 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on August 8, 2014. 38 Copyright Notice 40 Copyright (c) 2014 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Specification of Requirements . . . . . . . . . . . . . . . . . 3 57 2.1. Multicast Distribution Reachability Signaling . . . . . . . 4 58 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 59 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 60 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 61 6. Normative References . . . . . . . . . . . . . . . . . . . . . 5 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 64 1. Introduction 66 Consider a content provider that wants to deliver a particular 67 content to a set of customers/subscribers, where the provider and the 68 subscribers are connected by an IP service provider. This content 69 provider can deliver its content via unicast connectivity or, if 70 supported by the subscriber network, multicast connectivity. A 71 mechanism is required to determine if the subscriber network supports 72 delivery of content to subscribers via multicast connectivity. 74 This document describes a mechanism whereby the subscriber's Internet 75 service provider may signal in BGP the ability of the subscriber 76 network to receive the content using multicast connectivity. This 77 mechanism is called Multicast Distribution Reachability Signaling 78 (MDRS). 80 For the purpose of this document we assume that a content provider 81 consists of one or more Content Servers, and one or more Content 82 Distribution Controllers. While this document assumes communication 83 between Content Servers and Content Distribution Controllers, the 84 procedures for implementing such communication is outside the scope 85 of this document. 87 Content Servers are connected to one or more IP service providers 88 (ISPs) that can offer both multicast and unicast connectivity service 89 to the subscribers of the content provider. Content providers use 90 these ISPs to deliver content to their subscribers. 92 Subscribers are connected to the Egress Routers (ERs) of the ISP. 93 Note that the multicast connectivity service provided by the ISP 94 extends all the way to the ERs. Such service could be provided by 95 either deploying IP multicast natively, or with some tunneling 96 mechanism like AMT, or by a combination of both within the ISP. 97 However, between the ERs and the subscribers there may, or may not be 98 multicast connectivity. 100 In the case where a particular subscriber of a given content provider 101 does not have multicast connectivity to its ER, the content provider 102 would use IP unicast service provided by the ISP to transmit the 103 particular content to that subscriber. 105 2. Specification of Requirements 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 109 document are to be interpreted as described in RFC 2119 [RFC2119]. 111 2.1. Multicast Distribution Reachability Signaling 113 Multicast distribution reachability signaling is responsible for 114 giving a content provider, and specifically Content Distribution 115 Controller(s) of the content provider the information of whether a 116 particular subscriber of that content provider has multicast 117 connectivity to an ER of an ISP that the content provider uses for 118 distributing its content. 120 This document assumes that each ER can determine the multicast 121 reachability status for each of the subscriber connected to that ER. 122 Procedures by which an ER accomplishes this are outside the scope of 123 this document. 125 To indicate whether a given ER has multicast reachability to a 126 subscriber (be that either a native multicast or AMT) this document 127 uses BGP as follows. An ER originates into IBGP routes for the 128 subscribers connected to that ER for which the ER has multicast 129 reachability. These routes are carried using BGP multi-protocol 130 capabilities [RFC4760] with AFI 1 or 2, and the MCAST-REACH SAFI. 131 The NLRI field in the MP_REACH_NLRI/MP_UNREACH_NLRI attribute of 132 these routes contains subscribers' IP addresses encoded as IP address 133 prefixes. The value of the AFI field in the MP_REACH_NLRI/ 134 MP_UNREACH_NLRI attribute of these routes determines whether 135 subscribers' addresses are IPv4 or IPv6 (AFI 1 indicates IPv4 136 addresses, AFI 2 indicates IPv6 addresses). 138 A Content Distribution Controller, when it receives such routes, uses 139 them to determine whether the content could be delivered to the 140 subscribers via the ISP who owns the ERs using the multicast 141 connectivity service provided by the ISP. 143 To constrain the flow of BGP routes that carry multicast distribution 144 reachability information such routes carry a particular Route Target 145 (RT) Extended Community [RFC4360], and Content Distribution 146 Controller(s) are provisioned to import routes with such a RT. 148 RTs carried by routes with AFI 1 and MCAST-REACH SAFI SHOULD NOT be 149 re-used by routes with any other AFI and/or SAFI. Likewise, RTs 150 carried by routes with AFI 2 and MCAST-REACH SAFI SHOULD NOT be re- 151 used by routes with any other AFI and/or SAFI. 153 To facilitate such constrained distribution of multicast distribution 154 reachability information one MAY use Constrained Route Distribution 155 [RFC4684]. 157 3. IANA Considerations 159 This document defines a new BGP Subsequent Address Family Identifier 160 (SAFI) value, MCAST-REACH. The authors request assignment of a value 161 from the First Come, First Served portion of this registry. 163 4. Security Considerations 165 TBD 167 5. Acknowledgements 169 The authors would like to thank Han Nguyen for his contributions to 170 this document. 172 6. Normative References 174 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 175 Requirement Levels", BCP 14, RFC 2119, March 1997. 177 [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended 178 Communities Attribute", RFC 4360, February 2006. 180 [RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk, 181 R., Patel, K., and J. Guichard, "Constrained Route 182 Distribution for Border Gateway Protocol/MultiProtocol 183 Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual 184 Private Networks (VPNs)", RFC 4684, November 2006. 186 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 187 "Multiprotocol Extensions for BGP-4", RFC 4760, 188 January 2007. 190 Authors' Addresses 192 Huajin Jeng 193 AT&T 195 Phone: 196 Email: hj2387@att.com 197 Jeffrey Haas 198 Juniper Networks 199 1194 N. Mathida Ave. 200 Sunnyvale, CA 94089 201 US 203 Email: jhaas@juniper.net 205 Yakov Rekhter 206 Juniper Networks 207 1194 N. Mathida Ave. 208 Sunnyvale, CA 94089 209 US 211 Email: yakov@juniper.net 213 Jeffrey (Zhaohui) Zhang 214 Juniper Networks 215 1194 N. Mathida Ave. 216 Sunnyvale, CA 94089 217 US 219 Email: zzhang@juniper.net