idnits 2.17.1 draft-ietf-mboned-driad-amt-discovery-04.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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 1 instance of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC7450, updated by this document, for RFC5378 checks: 2001-02-27) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 22, 2019) is 1824 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) -- Obsolete informational reference (is this intentional?): RFC 2845 (Obsoleted by RFC 8945) -- Obsolete informational reference (is this intentional?): RFC 8499 (Obsoleted by RFC 9499) Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Mboned J. Holland 3 Internet-Draft Akamai Technologies, Inc. 4 Updates: 7450 (if approved) April 22, 2019 5 Intended status: Standards Track 6 Expires: October 24, 2019 8 DNS Reverse IP AMT Discovery 9 draft-ietf-mboned-driad-amt-discovery-04 11 Abstract 13 This document updates RFC 7450 (Automatic Multicast Tunneling, or 14 AMT) by extending the relay discovery process to use a new DNS 15 resource record named AMTRELAY when discovering AMT relays for 16 source-specific multicast channels. The reverse IP DNS zone for a 17 multicast sender's IP address is configured to use AMTRELAY resource 18 records to advertise a set of AMT relays that can receive and forward 19 multicast traffic from that sender over an AMT tunnel. 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 https://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 October 24, 2019. 38 Copyright Notice 40 Copyright (c) 2019 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 (https://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 1.1. Background . . . . . . . . . . . . . . . . . . . . . . . 3 57 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 58 1.2.1. Relays and Gateways . . . . . . . . . . . . . . . . . 4 59 1.2.2. Definitions . . . . . . . . . . . . . . . . . . . . . 4 60 2. Relay Discovery Operation . . . . . . . . . . . . . . . . . . 5 61 2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 6 62 2.2. Signaling and Discovery . . . . . . . . . . . . . . . . . 6 63 2.3. Happy Eyeballs . . . . . . . . . . . . . . . . . . . . . 8 64 2.3.1. Overview . . . . . . . . . . . . . . . . . . . . . . 8 65 2.3.2. Connection Definition . . . . . . . . . . . . . . . . 9 66 2.4. Optimal Relay Selection . . . . . . . . . . . . . . . . . 9 67 2.4.1. Overview . . . . . . . . . . . . . . . . . . . . . . 9 68 2.4.2. Preference Ordering . . . . . . . . . . . . . . . . . 10 69 2.4.3. Connecting to Multiple Relays . . . . . . . . . . . . 13 70 2.5. Guidelines for Restarting Discovery . . . . . . . . . . . 13 71 2.5.1. Overview . . . . . . . . . . . . . . . . . . . . . . 13 72 2.5.2. Updates to Restarting Events . . . . . . . . . . . . 14 73 2.5.3. Tunnel Stability . . . . . . . . . . . . . . . . . . 15 74 2.5.4. Traffic Health . . . . . . . . . . . . . . . . . . . 15 75 2.5.5. Relay Loaded or Shutting Down . . . . . . . . . . . . 17 76 2.5.6. Relay Discovery Messages vs. Restarting Discovery . . 17 77 2.5.7. Independent Discovery Per Traffic Source . . . . . . 18 78 2.6. DNS Configuration . . . . . . . . . . . . . . . . . . . . 18 79 2.7. Waiting for DNS resolution . . . . . . . . . . . . . . . 19 80 3. Example Deployments . . . . . . . . . . . . . . . . . . . . . 19 81 3.1. Example Receiving Networks . . . . . . . . . . . . . . . 19 82 3.1.1. Tier 3 ISP . . . . . . . . . . . . . . . . . . . . . 19 83 3.1.2. Small Office . . . . . . . . . . . . . . . . . . . . 20 84 3.2. Example Sending Networks . . . . . . . . . . . . . . . . 22 85 3.2.1. Sender-controlled Relays . . . . . . . . . . . . . . 22 86 3.2.2. Provider-controlled Relays . . . . . . . . . . . . . 23 87 4. AMTRELAY Resource Record Definition . . . . . . . . . . . . . 24 88 4.1. AMTRELAY RRType . . . . . . . . . . . . . . . . . . . . . 24 89 4.2. AMTRELAY RData Format . . . . . . . . . . . . . . . . . . 24 90 4.2.1. RData Format - Precedence . . . . . . . . . . . . . . 25 91 4.2.2. RData Format - Discovery Optional (D-bit) . . . . . . 25 92 4.2.3. RData Format - Type . . . . . . . . . . . . . . . . . 25 93 4.2.4. RData Format - Relay . . . . . . . . . . . . . . . . 26 94 4.3. AMTRELAY Record Presentation Format . . . . . . . . . . . 26 95 4.3.1. Representation of AMTRELAY RRs . . . . . . . . . . . 26 96 4.3.2. Examples . . . . . . . . . . . . . . . . . . . . . . 27 98 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 99 6. Security Considerations . . . . . . . . . . . . . . . . . . . 28 100 6.1. Use of AMT . . . . . . . . . . . . . . . . . . . . . . . 28 101 6.2. Record-spoofing . . . . . . . . . . . . . . . . . . . . . 28 102 6.3. Congestion . . . . . . . . . . . . . . . . . . . . . . . 29 103 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29 104 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 29 105 8.1. Normative References . . . . . . . . . . . . . . . . . . 29 106 8.2. Informative References . . . . . . . . . . . . . . . . . 31 107 Appendix A. Unknown RRType construction . . . . . . . . . . . . 32 108 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 33 110 1. Introduction 112 This document defines DNS Reverse IP AMT Discovery (DRIAD), a 113 mechanism for AMT gateways to discover AMT relays that are capable of 114 forwarding multicast traffic from a known source IP address. 116 AMT (Automatic Multicast Tunneling) is defined in [RFC7450], and 117 provides a method to transport multicast traffic over a unicast 118 tunnel, in order to traverse non-multicast-capable network segments. 120 Section 4.1.5 of [RFC7450] explains that the relay selection process 121 for AMT is intended to be more flexible than the particular discovery 122 method described in that document, and further explains that the 123 selection process might need to depend on the source of the multicast 124 traffic in some deployments, since a relay must be able to receive 125 multicast traffic from the desired source in order to forward it. 127 That section goes on to suggest DNS-based queries as a possible 128 solution. DRIAD is a DNS-based solution, as suggested there. This 129 solution also addresses the relay discovery issues in the 130 "Disadvantages" lists in Section 3.3 of [RFC8313] and Section 3.4 of 131 [RFC8313]. 133 The goal for DRIAD is to enable multicast connectivity between 134 separate multicast-enabled networks when neither the sending nor the 135 receiving network is connected to a multicast-enabled backbone, 136 without pre-configuring any peering arrangement between the networks. 138 This document updates Section 5.2.3.4 of [RFC7450] by adding a new 139 extension to the relay discovery procedure. 141 1.1. Background 143 The reader is assumed to be familiar with the basic DNS concepts 144 described in [RFC1034], [RFC1035], and the subsequent documents that 145 update them, particularly [RFC2181]. 147 The reader is also assumed to be familiar with the concepts and 148 terminology regarding source-specific multicast as described in 149 [RFC4607] and the use of IGMPv3 [RFC3376] and MLDv2 [RFC3810] for 150 group management of source-specific multicast channels, as described 151 in [RFC4604]. 153 The reader should also be familiar with AMT, particularly the 154 terminology listed in Section 3.2 of [RFC7450] and Section 3.3 of 155 [RFC7450]. 157 1.2. Terminology 159 1.2.1. Relays and Gateways 161 When reading this document, it's especially helpful to recall that 162 once an AMT tunnel is established, the relay receives native 163 multicast traffic and sends unicast tunnel-encapsulated traffic to 164 the gateway, and the gateway receives the tunnel-encapsulated 165 packets, decapsulates them, and forwards them as native multicast 166 packets, as illustrated in Figure 1. 168 Multicast +-----------+ Unicast +-------------+ Multicast 169 >---------> | AMT relay | >=======> | AMT gateway | >---------> 170 +-----------+ +-------------+ 172 Figure 1: AMT Tunnel Illustration 174 1.2.2. Definitions 175 +------------+------------------------------------------------------+ 176 | Term | Definition | 177 +------------+------------------------------------------------------+ 178 | (S,G) | A source-specific multicast channel, as described in | 179 | | [RFC4607]. A pair of IP addresses with a source host | 180 | | IP and destination group IP. | 181 | | | 182 | discovery | A broker or load balancer for AMT relay discovery, | 183 | broker | as mentioned in section 4.2.1.1 of [RFC7450]. | 184 | | | 185 | downstream | Further from the source of traffic, as described in | 186 | | [RFC7450]. | 187 | | | 188 | FQDN | Fully Qualified Domain Name, as described in | 189 | | [RFC8499] | 190 | | | 191 | gateway | An AMT gateway, as described in [RFC7450] | 192 | | | 193 | L flag | The "Limit" flag described in Section 5.1.1.4 of | 194 | | [RFC7450] | 195 | | | 196 | relay | An AMT relay, as described in [RFC7450] | 197 | | | 198 | RPF | Reverse Path Forwarding, as described in [RFC5110] | 199 | | | 200 | RR | A DNS Resource Record, as described in [RFC1034] | 201 | | | 202 | RRType | A DNS Resource Record Type, as described in | 203 | | [RFC1034] | 204 | | | 205 | SSM | Source-specific multicast, as described in [RFC4607] | 206 | | | 207 | upstream | Closer to the source of traffic, as described in | 208 | | [RFC7450]. | 209 +------------+------------------------------------------------------+ 211 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 212 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 213 "OPTIONAL" in this document are to be interpreted as described in 214 [RFC2119] and [RFC8174] when, and only when, they appear in all 215 capitals, as shown here. 217 2. Relay Discovery Operation 218 2.1. Overview 220 The AMTRELAY resource record (RR) defined in this document is used to 221 publish the IP address or domain name of a set of AMT relays or 222 discovery brokers that can receive, encapsulate, and forward 223 multicast traffic from a particular sender. 225 The sender is the owner of the RR, and configures the zone so that it 226 contains a set of RRs that provide the addresses or domain names of 227 AMT relays (or discovery brokers that advertise relays) that can 228 receive multicast IP traffic from that sender. 230 This enables AMT gateways in remote networks to discover an AMT relay 231 that is capable of forwarding traffic from the sender. This in turn 232 enables those AMT gateways to receive the multicast traffic tunneled 233 over a unicast AMT tunnel from those relays, and then to pass the 234 multicast packets into networks or applications that are using the 235 gateway to subscribe to traffic from that sender. 237 This mechanism only works for source-specific multicast (SSM) 238 channels. The source address of the (S,G) is reversed and used as an 239 index into one of the reverse mapping trees (in-addr.arpa for IPv4, 240 as described in Section 3.5 of [RFC1035], or ip6.arpa for IPv6, as 241 described in Section 2.5 of [RFC3596]). 243 This mechanism should be treated as an extension of the AMT relay 244 discovery procedure described in Section 5.2.3.4 of [RFC7450]. A 245 gateway that supports this method of AMT relay discovery SHOULD use 246 this method whenever it's performing the relay discovery procedure, 247 and the source IP addresses for desired (S,G)s are known to the 248 gateway, and conditions match the requirements outlined in 249 Section 2.4. 251 Some detailed example use cases are provided in Section 3, and other 252 applicable example topologies appear in Section 3.3 of [RFC8313], 253 Section 3.4 of [RFC8313], and Section 3.5 of [RFC8313]. 255 2.2. Signaling and Discovery 257 This section describes a typical example of the end-to-end process 258 for signaling a receiver's join of a SSM channel that relies on an 259 AMTRELAY RR. 261 The example in Figure 2 contains 2 multicast-enabled networks that 262 are both connected to the internet with non-multicast-capable links, 263 and which have no direct association with each other. 265 A content provider operates a sender, which is a source of multicast 266 traffic inside a multicast-capable network. 268 An end user who is a customer of the content provider has a 269 multicast-capable internet service provider, which operates a 270 receiving network that uses an AMT gateway. The AMT gateway is 271 DRIAD-capable. 273 The content provider provides the user with a receiving application 274 that tries to subscribe to at least one (S,G). This receiving 275 application could for example be a file transfer system using FLUTE 276 [RFC6726] or a live video stream using RTP [RFC3550], or any other 277 application that might subscribe to a SSM channel. 279 +---------------+ 280 | Sender | 281 | | | 198.51.100.15 | 282 | | +---------------+ 283 |Data| | 284 |Flow| Multicast | 285 \| |/ Network | 286 \ / | 5: Propagate RPF for Join(S,G) 287 \ / +---------------+ 288 \/ | AMT Relay | 289 | 203.0.113.15 | 290 +---------------+ 291 | 4: Gateway connects to Relay, 292 sends Join(S,G) over tunnel 293 | 294 Unicast 295 Tunnel | 297 ^ | 3: --> DNS Query: type=AMTRELAY, 298 | / 15.100.51.198.in-addr.arpa. 299 | | / <-- Response: 300 Join/Leave +-------------+ AMTRELAY=203.0.113.15 301 Signals | AMT gateway | 302 | +-------------+ 303 | | 2: Propagate RPF for Join(S,G) 304 | Multicast | 305 Network | 306 | 1: Join(S=198.51.100.15, G) 307 +-------------+ 308 | Receiver | 309 | (end user) | 310 +-------------+ 312 Figure 2: DRIAD Messaging 314 In this simple example, the sender IP is 198.51.100.15, and the relay 315 IP is 203.0.113.15. 317 The content provider has previously configured the DNS zone that 318 contains the domain name "15.100.51.198.in-addr.arpa.", which is the 319 reverse lookup domain name for his sender. The zone file contains an 320 AMTRELAY RR with the Relay's IP address. (See Section 4.3 for 321 details about the AMTRELAY RR format and semantics.) 323 The sequence of events depicted in Figure 2 is as follows: 325 1. The end user starts the app, which issues a join to the (S,G): 326 (198.51.100.15, 232.252.0.2). 328 2. The join propagates with RPF through the multicast-enabled 329 network with PIM [RFC7761] or another multicast routing 330 mechanism, until the AMT gateway receives a signal to join the 331 (S,G). 333 3. The AMT gateway performs a reverse DNS lookup for the AMTRELAY 334 RRType, by sending an AMTRELAY RRType query for the FQDN 335 "15.100.51.198.in-addr.arpa.", using the reverse IP domain name 336 for the sender's source IP address (the S from the (S,G)), as 337 described in Section 3.5 of [RFC1035]. 339 The DNS resolver for the AMT gateway uses ordinary DNS recursive 340 resolution until it has the authoritative result that the content 341 provider configured, which informs the AMT gateway that the relay 342 address is 203.0.113.15. 344 4. The AMT gateway performs AMT handshakes with the AMT relay as 345 described in Section 4 of [RFC7450], then forwards a Membership 346 report to the relay indicating subscription to the (S,G). 348 5. The relay propagates the join through its network toward the 349 sender, then forwards the appropriate AMT-encapsulated traffic to 350 the gateway, which decapsulates and forwards it as native 351 multicast through its downstream network to the end user. 353 2.3. Happy Eyeballs 355 2.3.1. Overview 357 Often, multiple choices of relay will exist for a gateway using DRIAD 358 for relay discovery. It is RECOMMENDED that DRIAD-capable gateways 359 implement a Happy Eyeballs [RFC8305] algorithm to support connecting 360 to multiple relays in parallel. 362 The parallel discovery logic of a Happy Eyeballs algorithm serves to 363 reduce join latency for the initial join of a SSM channel. This 364 section and Section 2.4.2 taken together provide guidance on use of a 365 Happy Eyeballs algorithm for the case of establishing AMT 366 connections. 368 2.3.2. Connection Definition 370 Section 5 of [RFC8305] non-normatively describes success at a 371 connection attempt as "generally when the TCP handshake completes". 373 There is no normative definition of a connection in the AMT 374 specification [RFC7450], and there is no TCP connection involved in 375 an AMT tunnel. 377 However, the concept of an AMT connection in the context of a Happy 378 Eyeballs algorithm is a useful one, and so this section provides the 379 following normative definition: 381 o An AMT connection is completed successfully when the gateway 382 receives from a newly discovered relay a valid Membership Query 383 message (Section 5.1.4 of [RFC7450]) that does not have the L flag 384 set. 386 See Section 2.5.5 of this document for further information about the 387 relevance of the L flag to the establishment of a Happy Eyeballs 388 connection. 390 2.4. Optimal Relay Selection 392 2.4.1. Overview 394 The reverse source IP DNS query of an AMTRELAY RR is a good way for a 395 gateway to discover a relay that is known to the sender. 397 However, it is NOT necessarily a good way to discover the best relay 398 for that gateway to use, because the RR will only provide information 399 about relays known to the source. 401 If there is an upstream relay in a network that is topologically 402 closer to the gateway and able to receive and forward multicast 403 traffic from the sender, that relay is better for the gateway to use, 404 since more of the network path uses native multicast, allowing more 405 chances for packet replication. But since that relay is not known to 406 the sender, it won't be advertised in the sender's reverse IP DNS 407 record. An example network that illustrates this scenario is 408 outlined in Section 3.1.2. 410 It's only appropriate for an AMT gateway to discover an AMT relay by 411 querying an AMTRELAY RR owned by a sender when all of these 412 conditions are met: 414 1. The gateway needs to propagate a join of an (S,G) over AMT, 415 because in the gateway's network, no RPF next hop toward the 416 source can propagate a native multicast join of the (S,G); and 418 2. The gateway is not already connected to a relay that forwards 419 multicast traffic from the source of the (S,G); and 421 3. The gateway is not configured to use a particular IP address for 422 AMT discovery, or a relay discovered with that IP is not able to 423 forward traffic from the source of the (S,G); and 425 4. The gateway is not able to find an upstream AMT relay with DNS-SD 426 [RFC6763], using "_amt._udp" as the Service section of the 427 queries, or a relay discovered this way is not able to forward 428 traffic from the source of the (S,G) (as described in 429 Section 2.5.4.1 or Section 2.5.5); and 431 5. The gateway is not able to find an upstream AMT relay with the 432 well-known anycast addresses from Section 7 of [RFC7450]. 434 When the above conditions are met, the gateway has no path within its 435 local network that can receive multicast traffic from the source IP 436 of the (S,G). 438 In this situation, the best way to find a relay that can forward the 439 required traffic is to use information that comes from the operator 440 of the sender. When the sender has configured an AMTRELAY RR, 441 gateways can use the DRIAD mechanism defined in this document to 442 discover the relay information provided by the sender. 444 2.4.2. Preference Ordering 446 This section defines a preference ordering for relay addresses during 447 the relay discovery process. Gateways are encouraged to implement a 448 Happy Eyeballs algorithm, but even gateways that do not implement a 449 Happy Eyeballs algorithm SHOULD use this ordering, except as noted. 451 When establishing an AMT tunnel to forward multicast data, it's very 452 important for the discovery process to prioritize the network 453 topology considerations ahead of address selection considerations, in 454 order to gain the packet replication benefits from using multicast 455 instead of unicast tunneling in the multicast-capable portions of the 456 network path. 458 The intent of the advice and requirements in this section is to 459 describe how a gateway should make use of the concurrency provided by 460 a Happy Eyeballs algorithm to reduce the join latency, while still 461 prioritizing network efficiency considerations over Address Selection 462 considerations. 464 Section 4 of [RFC8305] requires a Happy Eyeballs algorithm to sort 465 the addresses with the Destination Address Selection defined in 466 Section 6 of [RFC6724], but for the above reasons, that requirement 467 is superseded in the AMT discovery use case by the following 468 considerations: 470 o Prefer Local Relays 472 Figure 5 and Section 3.1.2 provide a motivating example to prefer 473 DNS-SD [RFC6763] for discovery strictly ahead of using the 474 AMTRELAY RR controlled by the sender for AMT discovery. 476 For this reason, it's RECOMMENDED that AMT gateways by default 477 perform service discovery using DNS Service Discovery (DNS-SD) 478 [RFC6763] for _amt._udp. (with chosen as 479 described in Section 11 of [RFC6763]) and use the AMT relays 480 discovered that way in preference to AMT relays discoverable via 481 the mechanism defined in this document (DRIAD). 483 o Prefer Relays Managed by the Containing Network 485 When no local relay is discoverable with DNS-SD, it still may be 486 the case that a relay local to the receiver is operated by the 487 network providing transit services to the receiver. 489 In this case, when the network cannot make the relay discoverable 490 via DNS-SD, the network SHOULD use the well-known anycast 491 addresses from Section 7 of [RFC7450] to route discovery traffic 492 to the relay most appropriate to the receiver's gateway. 494 Accordingly, the gateway SHOULD by default discover a relay with 495 the well-known AMT anycast addresses as the second preference 496 after DNS-SD when searching for a local relay. 498 o Let Sender Manage Relay Provisioning 500 A related motivating example in the sending-side network is 501 provided by considering a sender which needs to instruct the 502 gateways on how to select between connecting to Figure 6 or 503 Figure 7 (from Section 3.2), in order to manage load and failover 504 scenarios in a manner that operates well with the sender's 505 provisioning strategy for horizontal scaling of AMT relays. 507 In this example about the sending-side network, the precedence 508 field described in Section 4.2.1 is a critical method of control 509 so that senders can provide the appropriate guidance to gateways 510 during the discovery process. 512 Therefore, after DNS-SD, the precedence from the RR MUST be used 513 for sorting preference ahead of the Destination Address Selection 514 ordering from Section 6 of [RFC6724], so that only relay IPs with 515 the same precedence are directly compared according to the 516 Destination Address Selection ordering. 518 Accordingly, AMT gateways SHOULD by default prefer relays in this 519 order: 521 1. DNS-SD 522 2. Anycast addresses from Section 7 of [RFC7450] 523 3. DRIAD 525 This default behavior MAY be overridden by administrative 526 configuration where other behavior is more appropriate for the 527 gateway within its network. 529 Among relay addresses that have an equivalent preference as described 530 above, a Happy Eyeballs algorithm for AMT MUST use the Destination 531 Address Selection defined in Section 6 of [RFC6724], as required by 532 [RFC8305]. 534 Among relay addresses that still have an equivalent preference after 535 the above orderings, a gateway MUST make a non-deterministic choice 536 for relay preference ordering, in order to support load balancing by 537 DNS configurations that provide many relay options. 539 The gateway MAY introduce a bias in the non-deterministic choice 540 according to network topology or timing information obtained out of 541 band or from a historical record. The collection of this information 542 is out of scope for this document, but a gateway in possession of 543 such information MAY use it to prefer topologically closer relays. 545 Note also that certain relay addresses may be excluded from 546 consideration by the hold-down timers described in Section 2.5.4.1 or 547 Section 2.5.5. These relays constitute "unusable destinations" under 548 Rule 1 of the Destination Address Selection, and are also not part of 549 the superseding considerations described above. 551 The discovery and connection process for the relay addresses in the 552 above described ordering MAY operate in parallel, subject to delays 553 prescribed by the Happy Eyeballs requirements described in Section 5 554 of [RFC8305] for successively launched concurrent connection 555 attempts. 557 2.4.3. Connecting to Multiple Relays 559 In some deployments, it may be useful for a gateway to connect to 560 multiple upstream relays and subscribe to the same traffic, in order 561 to support an active/active failover model. A gateway SHOULD NOT be 562 configured to do so without guaranteeing that adequate bandwidth is 563 available. 565 A gateway configured to do this SHOULD still use the same preference 566 ordering logic from Section 2.4.2 for each connection. (Note that 567 this ordering allows for overriding by explicit administrative 568 configuration where required.) 570 2.5. Guidelines for Restarting Discovery 572 2.5.1. Overview 574 It's expected that gateways deployed in different environments will 575 use a variety of heuristics to decide when it's appropriate to 576 restart the relay discovery process, in order to meet different 577 performance goals (for example, to fulfill different kinds of service 578 level agreements). 580 In general, restarting the discovery process is always safe for the 581 gateway and relay during any of the events listed in this section, 582 but may cause a disruption in the forwarded traffic if the discovery 583 process results in choosing a different relay, because this changes 584 the RPF forwarding tree for the multicast traffic upstream of the 585 gateway. This is likely to result in some dropped or duplicated 586 packets from channels actively being tunneled from the old relay to 587 the gateway. 589 The degree of impact on the traffic from choosing a different relay 590 may depend on network conditions between the gateway and the new 591 relay, as well as the network conditions and topology between the 592 sender and the new relay, as this may cause the relay to propagate a 593 new RPF join toward the sender. 595 Balancing the expected impact on the tunneled traffic against likely 596 or observed problems with an existing connection to the relay is the 597 goal of the heuristics that gateways use to determine when to restart 598 the discovery process. 600 The non-normative advice in this section should be treated as 601 guidelines to operators and implementors working with AMT systems 602 that can use DRIAD as part of the relay discovery process. 604 2.5.2. Updates to Restarting Events 606 Section 5.2.3.4.1 of [RFC7450] lists several events that may cause a 607 gateway to start or restart the discovery procedure. 609 This document provides some updates and recommendations regarding the 610 handling of these and similar events. The first 5 events are copied 611 here and numbered for easier reference, and the following events are 612 newly added for consideration in this document: 614 1. When a gateway pseudo-interface is started (enabled). 616 2. When the gateway wishes to report a group subscription when none 617 currently exist. 619 3. Before sending the next Request message in a membership update 620 cycle. 622 4. After the gateway fails to receive a response to a Request 623 message. 625 5. After the gateway receives a Membership Query message with the L 626 flag set to 1. 628 6. When the gateway wishes to report a (S,G) subscription with a 629 source address that does not currently have other group 630 subscriptions. 632 7. When there is a network change detected, for example when a 633 gateway is operating inside an end user device or application, 634 and the device joins a different network, or when the domain 635 portion of a DNS-SD domain name changes in response to a DHCP 636 message or administrative configuration. 638 8. When congestion or substantial loss is detected in the stream of 639 AMT packets from a relay. 641 9. When the gateway has reported one or more (S,G) subscriptions, 642 but no traffic is received from the source for some timeout. 643 (See Section 2.5.4.1). 645 This list is not exhaustive, nor are any of the listed events 646 strictly required to always force a restart of the discovery process. 648 Note that during event #1, a gateway may use DNS-SD, but does not 649 have sufficient information to use DRIAD, since no source is known. 651 2.5.3. Tunnel Stability 653 In general, subscribers to active traffic flows that are being 654 forwarded by an AMT gateway are less likely to experience a 655 degradation in service (for example, from missing or duplicated 656 packets) when the gateway continues using the same relay, as long the 657 relay is not overloaded and the network conditions remain stable. 659 Therefore, gateways SHOULD avoid performing a full restart of the 660 discovery process during routine cases of event #3 (sending a new 661 Request message), since it occurs frequently in normal operation. 663 However, see Section 2.5.4, Section 2.5.6, and Section 2.5.4.3 for 664 more information about exceptional cases when it may be appropriate 665 to use event #3. 667 2.5.4. Traffic Health 669 2.5.4.1. Absence of Traffic 671 If a gateway indicates one or more (S,G) subscriptions in a 672 Membership Update message, but no traffic for any of the (S,G)s is 673 received in a reasonable time, it's appropriate for the gateway to 674 restart the discovery process. 676 If the gateway restarts the discovery process multiple times 677 consecutively for this reason, the timeout period SHOULD be adjusted 678 to provide a random exponential back-off. 680 The RECOMMENDED timeout is a random value in the range 681 [initial_timeout, MIN(initial_timeout * 2^retry_count, 682 maximum_timeout)], with a RECOMMENDED initial_timeout of 4 seconds 683 and a RECOMMENDED maximum_timeout of 120 seconds. 685 Note that the recommended initial_timeout is larger than the initial 686 timout recommended in the similar algorithm from Section 5.2.3.4.3 of 687 [RFC7450]. This is to provide time for RPF Join propagation in the 688 sending network. Although the timeout values may be administratively 689 adjusted to support performance requirements, operators are advised 690 to consider the possibility of join propagation delays between the 691 sender and the relay when choosing an appropriate timeout value. 693 Gateways restarting the discovery process because of an absence of 694 traffic MUST use a hold-down timer that removes this relay from 695 consideration during subsequent rounds of discovery while active. 697 The hold-down SHOULD last for no less than 3 minutes and no more than 698 10 minutes. 700 2.5.4.2. Loss and Congestion 702 In some gateway deployments, it is also feasible to monitor the 703 health of traffic flows through the gateway, for example by detecting 704 the rate of packet loss by communicating out of band with receivers, 705 or monitoring the packets of known protocols with sequence numbers. 706 Where feasible, it's encouraged for gateways to use such traffic 707 health information to trigger a restart of the discovery process 708 during event #3 (before sending a new Request message). 710 However, to avoid synchronized rediscovery by many gateways 711 simultaneously after a transient network event upstream of a relay 712 results in many receivers detecting poor flow health at the same 713 time, it's recommended to add a random delay before restarting the 714 discovery process in this case. 716 The span of the random portion of the delay should be no less than 10 717 seconds by default, but may be administratively configured to support 718 different performance requirements. 720 2.5.4.3. Ancient Discovery Information 722 In most cases, a gateway actively receiving healthy traffic from a 723 relay that has not indicated load with the L flag should prefer to 724 remain connected to the same relay, as described in Section 2.5.3. 726 However, a relay that appears healthy but has been forwarding traffic 727 for days or weeks may have an increased chance of becoming unstable. 728 Gateways may benefit from restarting the discovery process during 729 event #3 (before sending a Request message) after the expiration of a 730 long-term timeout, on the order of multiple hours, or even days in 731 some deployments. 733 It may be beneficial for such timers to consider the amount of 734 traffic currently being forwarded, and to give a higher probability 735 of restarting discovery during periods with an unusually low data 736 rate, to reduce the impact on active traffic while still avoiding 737 relying on the results of a very old discovery. 739 Other issues may also be worth considering as part of this heuristic; 740 for example, if the DNS expiry time of the record that was used to 741 discover the current relay has not passed, the long term timer might 742 be restarted without restarting the discovery process. 744 2.5.5. Relay Loaded or Shutting Down 746 The L flag (see Section 5.1.4.4 of [RFC7450]) is the preferred 747 mechanism for a relay to signal overloading or a graceful shutdown to 748 gateways. 750 A gateway that supports handling of the L flag should generally 751 restart the discovery process when it processes a Membership Query 752 packet with the L flag set. If an L flag is received while a 753 concurrent Happy Eyeballs discovery process is under way for multiple 754 candidate relays (Section 2.3), the relay sending the L flag SHOULD 755 NOT be considered for the relay selection. 757 It is also RECOMMENDED that gateways avoid choosing a relay that has 758 recently sent an L flag, with approximately a 10-minute hold-down. 759 Gateways SHOULD treat this hold-down timer in the same way as the 760 hold-down in Section 2.5.4.1, so that the relay is removed from 761 consideration for short-term subsequent rounds of discovery. 763 2.5.6. Relay Discovery Messages vs. Restarting Discovery 765 A gateway should only send DNS queries with the AMTRELAY RRType or 766 the DNS-SD DNS queries for an AMT service as part of starting or 767 restarting the discovery process. 769 However, all AMT relays are required to support handling of Relay 770 Discovery messages (e.g. in Section 5.3.3.2 of [RFC7450]). 772 So a gateway with an existing connection to a relay can send a Relay 773 Discovery message to the unicast address of that AMT relay. Under 774 stable conditions with an unloaded relay, it's expected that the 775 relay will return its own unicast address in the Relay Advertisement, 776 in response to such a Relay Discovery message. Since this will not 777 result in the gateway changing to another relay unless the relay 778 directs the gateway away, this is a reasonable exception to the 779 advice against handling event #3 described in Section 2.5.3. 781 This behavior is discouraged for gateways that do support the L flag, 782 to avoid sending unnecessary packets over the network. 784 However, gateways that do not support the L flag may be able to avoid 785 a disruption in the forwarded traffic by sending such Relay Discovery 786 messages regularly. When a relay is under load or has started a 787 graceful shutdown, it may respond with a different relay address, 788 which the gateway can use to connect to a different relay. This kind 789 of coordinated handoff will likely result in a smaller disruption to 790 the traffic than if the relay simply stops responding to Request 791 messages, and stops forwarding traffic. 793 This style of Relay Discovery message (one sent to the unicast 794 address of a relay that's already forwarding traffic to this gateway) 795 should not be considered a full restart of the relay discovery 796 process. It is recommended for gateways to support the L flag, but 797 for gateways that do not support the L flag, sending this message 798 during event #3 may help mitigate service degradation when relays 799 become unstable. 801 2.5.7. Independent Discovery Per Traffic Source 803 Relays discovered via the AMTRELAY RR are source-specific relay 804 addresses, and may use different pseudo-interfaces from each other 805 and from relays discovered via DNS-SD or a non-source-specific 806 address, as described in Section 4.1.2.1 of [RFC7450]. 808 Restarting the discovery process for one pseudo-interface does not 809 require restarting the discovery process for other pseudo-interfaces. 810 Gateway heuristics about restarting the discovery process should 811 operate independently for different tunnels to relays, when 812 responding to events that are specific to the different tunnels. 814 2.6. DNS Configuration 816 Often an AMT gateway will only have access to the source and group IP 817 addresses of the desired traffic, and will not know any other name 818 for the source of the traffic. Because of this, typically the best 819 way of looking up AMTRELAY RRs will be by using the source IP address 820 as an index into one of the reverse mapping trees (in-addr.arpa for 821 IPv4, as described in Section 3.5 of [RFC1035], or ip6.arpa for IPv6, 822 as described in Section 2.5 of [RFC3596]). 824 Therefore, it is RECOMMENDED that AMTRELAY RRs be added to reverse IP 825 zones as appropriate. AMTRELAY records MAY also appear in other 826 zones, but the primary intended use case requires a reverse IP 827 mapping for the source from an (S,G) in order to be useful to most 828 AMT gateways. 830 When performing the AMTRELAY RR lookup, any CNAMEs or DNAMEs found 831 MUST be followed. This is necessary to support zone delegation. 832 Some examples outlining this need are described in [RFC2317]. 834 See Section 4 and Section 4.3 for a detailed explanation of the 835 contents for a DNS Zone file. 837 2.7. Waiting for DNS resolution 839 The DNS query functionality is expected to follow ordinary standards 840 and best practices for DNS clients. A gateway MAY use an existing 841 DNS client implementation that does so, and MAY rely on that client's 842 retry logic to determine the timeouts between retries. 844 Otherwise, a gateway MAY re-send a DNS query if it does not receive 845 an appropriate DNS response within some timeout period. If the 846 gateway retries multiple times, the timeout period SHOULD be adjusted 847 to provide a random exponential back-off. 849 As with the waiting process for the Relay Advertisement message from 850 Section 5.2.3.4.3 of [RFC7450], the RECOMMENDED timeout is a random 851 value in the range [initial_timeout, MIN(initial_timeout * 852 2^retry_count, maximum_timeout)], with a RECOMMENDED initial_timeout 853 of 1 second and a RECOMMENDED maximum_timeout of 120 seconds. 855 3. Example Deployments 857 3.1. Example Receiving Networks 859 3.1.1. Tier 3 ISP 861 One example of a receiving network is an ISP that offers multicast 862 ingest services to its subscribers, illustrated in Figure 3. 864 In the example network below, subscribers can join (S,G)s with MLDv2 865 or IGMPv3 as described in [RFC4604], and the AMT gateway in this ISP 866 can receive and forward multicast traffic from one of the example 867 sending networks in Section 3.2 by discovering the appropriate AMT 868 relays with a DNS lookup for the AMTRELAY RR with the reverse IP of 869 the source in the (S,G). 871 Internet 872 ^ ^ Multicast-enabled 873 | | Receiving Network 874 +------|------------|-------------------------+ 875 | | | | 876 | +--------+ +--------+ +=========+ | 877 | | Border |---| Border | | AMT | | 878 | | Router | | Router | | gateway | | 879 | +--------+ +--------+ +=========+ | 880 | | | | | 881 | +-----+------+-----------+--+ | 882 | | | | 883 | +-------------+ +-------------+ | 884 | | Agg Routers | .. | Agg Routers | | 885 | +-------------+ +-------------+ | 886 | / \ \ / \ | 887 | +---------------+ +---------------+ | 888 | |Access Systems | ....... |Access Systems | | 889 | |(CMTS/OLT/etc.)| |(CMTS/OLT/etc.)| | 890 | +---------------+ +---------------+ | 891 | | | | 892 +--------|------------------------|-----------+ 893 | | 894 +---+-+-+---+---+ +---+-+-+---+---+ 895 | | | | | | | | | | 896 /-\ /-\ /-\ /-\ /-\ /-\ /-\ /-\ /-\ /-\ 897 |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| 899 Subscribers 901 Figure 3: Receiving ISP Example 903 3.1.2. Small Office 905 Another example receiving network is a small branch office that 906 regularly accesses some multicast content, illustrated in Figure 4. 908 This office has desktop devices that need to receive some multicast 909 traffic, so an AMT gateway runs on a LAN with these devices, to pull 910 traffic in through a non-multicast next-hop. 912 The office also hosts some mobile devices that have AMT gateway 913 instances embedded inside apps, in order to receive multicast traffic 914 over their non-multicast wireless LAN. (Note that the "Legacy 915 Router" is a simplification that's meant to describe a variety of 916 possible conditions; for example it could be a device providing a 917 split-tunnel VPN as described in [RFC7359], deliberately excluding 918 multicast traffic for a VPN tunnel, rather than a device which is 919 incapable of multicast forwarding.) 921 Internet 922 (non-multicast) 923 ^ 924 | Office Network 925 +----------|----------------------------------+ 926 | | | 927 | +---------------+ (Wifi) Mobile apps | 928 | | Modem+ | Wifi | - - - - w/ embedded | 929 | | Router | AP | AMT gateways | 930 | +---------------+ | 931 | | | 932 | | | 933 | +----------------+ | 934 | | Legacy Router | | 935 | | (unicast) | | 936 | +----------------+ | 937 | / | \ | 938 | / | \ | 939 | +--------+ +--------+ +--------+=========+ | 940 | | Phones | | ConfRm | | Desks | AMT | | 941 | | subnet | | subnet | | subnet | gateway | | 942 | +--------+ +--------+ +--------+=========+ | 943 | | 944 +---------------------------------------------+ 946 Figure 4: Small Office (no multicast up) 948 By adding an AMT relay to this office network as in Figure 5, it's 949 possible to make use of multicast services from the example 950 multicast-capable ISP in Section 3.1.1. 952 Multicast-capable ISP 953 ^ 954 | Office Network 955 +----------|----------------------------------+ 956 | | | 957 | +---------------+ (Wifi) Mobile apps | 958 | | Modem+ | Wifi | - - - - w/ embedded | 959 | | Router | AP | AMT gateways | 960 | +---------------+ | 961 | | +=======+ | 962 | +---Wired LAN---| AMT | | 963 | | | relay | | 964 | +----------------+ +=======+ | 965 | | Legacy Router | | 966 | | (unicast) | | 967 | +----------------+ | 968 | / | \ | 969 | / | \ | 970 | +--------+ +--------+ +--------+=========+ | 971 | | Phones | | ConfRm | | Desks | AMT | | 972 | | subnet | | subnet | | subnet | gateway | | 973 | +--------+ +--------+ +--------+=========+ | 974 | | 975 +---------------------------------------------+ 977 Figure 5: Small Office Example 979 When multicast-capable networks are chained like this, with a network 980 like the one in Figure 5 receiving internet services from a 981 multicast-capable network like the one in Figure 3, it's important 982 for AMT gateways to reach the more local AMT relay, in order to avoid 983 accidentally tunneling multicast traffic from a more distant AMT 984 relay with unicast, and failing to utilize the multicast transport 985 capabilities of the network in Figure 3. 987 3.2. Example Sending Networks 989 3.2.1. Sender-controlled Relays 991 When a sender network is also operating AMT relays to distribute 992 multicast traffic, as in Figure 6, each address could appear as an 993 AMTRELAY RR for the reverse IP of the sender, or one or more domain 994 names could appear in AMTRELAY RRs, and the AMT relay addresses can 995 be discovered by finding A or AAAA records from those domain names. 997 Sender Network 998 +-----------------------------------+ 999 | | 1000 | +--------+ +=======+ +=======+ | 1001 | | Sender | | AMT | | AMT | | 1002 | +--------+ | relay | | relay | | 1003 | | +=======+ +=======+ | 1004 | | | | | 1005 | +-----+------+----------+ | 1006 | | | 1007 +-----------|-----------------------+ 1008 v 1009 Internet 1010 (non-multicast) 1012 Figure 6: Small Office Example 1014 3.2.2. Provider-controlled Relays 1016 When an ISP offers a service to transmit outbound multicast traffic 1017 through a forwarding network, it might also offer AMT relays in order 1018 to reach receivers without multicast connectivity to the forwarding 1019 network, as in Figure 7. In this case it's RECOMMENDED that the ISP 1020 also provide at least one domain name for the AMT relays for use with 1021 the AMTRELAY RR. 1023 When the sender wishes to use the relays provided by the ISP for 1024 forwarding multicast traffic, an AMTRELAY RR should be configured to 1025 use the domain name provided by the ISP, to allow for address 1026 reassignment of the relays without forcing the sender to reconfigure 1027 the corresponding AMTRELAY RRs. 1029 +--------+ 1030 | Sender | 1031 +---+----+ Multicast-enabled 1032 | Sending Network 1033 +-----------|-------------------------------+ 1034 | v | 1035 | +------------+ +=======+ +=======+ | 1036 | | Agg Router | | AMT | | AMT | | 1037 | +------------+ | relay | | relay | | 1038 | | +=======+ +=======+ | 1039 | | | | | 1040 | +-----+------+--------+---------+ | 1041 | | | | 1042 | +--------+ +--------+ | 1043 | | Border |---| Border | | 1044 | | Router | | Router | | 1045 | +--------+ +--------+ | 1046 +-----|------------|------------------------+ 1047 | | 1048 v v 1049 Internet 1050 (non-multicast) 1052 Figure 7: Sending ISP Example 1054 4. AMTRELAY Resource Record Definition 1056 4.1. AMTRELAY RRType 1058 The AMTRELAY RRType has the mnemonic AMTRELAY and type code 260 1059 (decimal). 1061 The AMTRELAY RR is class independent. 1063 4.2. AMTRELAY RData Format 1065 The AMTRELAY RData consists of a 8-bit precedence field, a 1-bit 1066 "Discovery Optional" field, a 7-bit type field, and a variable length 1067 relay field. 1069 0 1 2 3 1070 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 1071 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1072 | precedence |D| type | | 1073 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1074 ~ relay ~ 1075 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1077 4.2.1. RData Format - Precedence 1079 This is an 8-bit precedence for this record. It is interpreted in 1080 the same way as the PREFERENCE field described in Section 3.3.9 of 1081 [RFC1035]. 1083 Relays listed in AMTRELAY records with a lower value for precedence 1084 are to be attempted first. 1086 4.2.2. RData Format - Discovery Optional (D-bit) 1088 The D bit is a "Discovery Optional" flag. 1090 If the D bit is set to 0, a gateway using this RR MUST perform AMT 1091 relay discovery as described in Section 4.2.1.1 of [RFC7450], rather 1092 than directly sending an AMT Request message to the relay. 1094 That is, the gateway MUST receive an AMT Relay Advertisement message 1095 (Section 5.1.2 of [RFC7450]) for an address before sending an AMT 1096 Request message (Section 5.1.3 of [RFC7450]) to that address. Before 1097 receiving the Relay Advertisement message, this record has only 1098 indicated that the address can be used for AMT relay discovery, not 1099 for a Request message. This is necessary for devices that are not 1100 fully functional AMT relays, but rather load balancers or brokers, as 1101 mentioned in Section 4.2.1.1 of [RFC7450]. 1103 If the D bit is set to 1, the gateway MAY send an AMT Request message 1104 directly to the discovered relay address without first sending an AMT 1105 Discovery message. 1107 This bit should be set according to advice from the AMT relay 1108 operator. The D bit MUST be set to zero when no information is 1109 available from the AMT relay operator about its suitability. 1111 4.2.3. RData Format - Type 1113 The type field indicates the format of the information that is stored 1114 in the relay field. 1116 The following values are defined: 1118 o type = 0: The relay field is empty (0 bytes). 1120 o type = 1: The relay field contains a 4-octet IPv4 address. 1122 o type = 2: The relay field contains a 16-octet IPv6 address. 1124 o type = 3: The relay field contains a wire-encoded domain name. 1125 The wire-encoded format is self-describing, so the length is 1126 implicit. The domain name MUST NOT be compressed. (See 1127 Section 3.3 of [RFC1035] and Section 4 of [RFC3597].) 1129 4.2.4. RData Format - Relay 1131 The relay field is the address or domain name of the AMT relay. It 1132 is formatted according to the type field. 1134 When the type field is 0, the length of the relay field is 0, and it 1135 indicates that no AMT relay should be used for multicast traffic from 1136 this source. 1138 When the type field is 1, the length of the relay field is 4 octets, 1139 and a 32-bit IPv4 address is present. This is an IPv4 address as 1140 described in Section 3.4.1 of [RFC1035]. This is a 32-bit number in 1141 network byte order. 1143 When the type field is 2, the length of the relay field is 16 octets, 1144 and a 128-bit IPv6 address is present. This is an IPv6 address as 1145 described in Section 2.2 of [RFC3596]. This is a 128-bit number in 1146 network byte order. 1148 When the type field is 3, the relay field is a normal wire-encoded 1149 domain name, as described in Section 3.3 of [RFC1035]. Compression 1150 MUST NOT be used, for the reasons given in Section 4 of [RFC3597]. 1152 For a type 3 record, the D-bit and preference fields carry over to 1153 all A or AAAA records for the domain name. There is no difference in 1154 the result of the discovery process when it's obtained by type 1 or 1155 type 2 AMTRELAY records with identical D-bit and preference fields, 1156 vs. when the result is obtained by a type 3 AMTRELAY record that 1157 resolves to the same set of IPv4 and IPv6 addresses via A and AAAA 1158 lookups. 1160 4.3. AMTRELAY Record Presentation Format 1162 4.3.1. Representation of AMTRELAY RRs 1164 AMTRELAY RRs may appear in a zone data master file. The precedence, 1165 D-bit, relay type, and relay fields are REQUIRED. 1167 If the relay type field is 0, the relay field MUST be ".". 1169 The presentation for the record is as follows: 1171 IN AMTRELAY precedence D-bit type relay 1173 4.3.2. Examples 1175 In a DNS authoritative nameserver that understands the AMTRELAY type, 1176 the zone might contain a set of entries like this: 1178 $ORIGIN 100.51.198.in-addr.arpa. 1179 10 IN AMTRELAY 10 0 1 203.0.113.15 1180 10 IN AMTRELAY 10 0 2 2001:DB8::15 1181 10 IN AMTRELAY 128 1 3 amtrelays.example.com. 1183 This configuration advertises an IPv4 discovery address, an IPv6 1184 discovery address, and a domain name for AMT relays which can receive 1185 traffic from the source 198.51.100.10. The IPv4 and IPv6 addresses 1186 are configured with a D-bit of 0 (meaning discovery is mandatory, as 1187 described in Section 4.2.2), and a precedence 10 (meaning they're 1188 preferred ahead of the last entry, which has precedence 128). 1190 For zone files in name servers that don't support the AMTRELAY RRType 1191 natively, it's possible to use the format for unknown RR types, as 1192 described in [RFC3597]. This approach would replace the AMTRELAY 1193 entries in the example above with the entries below: 1195 10 IN TYPE260 \# ( 1196 6 ; length 1197 0a ; precedence=10 1198 01 ; D=0, relay type=1, an IPv4 address 1199 cb00710f ) ; 203.0.113.15 1200 10 IN TYPE260 \# ( 1201 18 ; length 1202 0a ; precedence=10 1203 02 ; D=0, relay type=2, an IPv6 address 1204 20010db800000000000000000000000f ) ; 2001:db8::15 1205 10 IN TYPE260 \# ( 1206 24 ; length 1207 80 ; precedence=128 1208 83 ; D=1, relay type=3, a wire-encoded domain name 1209 09616d7472656c617973076578616d706c6503636f6d ) ; domain name 1211 See Appendix A for more details. 1213 5. IANA Considerations 1215 This document updates the IANA Registry for DNS Resource Record Types 1216 by assigning type 260 to the AMTRELAY record. 1218 This document creates a new registry named "AMTRELAY Resource Record 1219 Parameters", with a sub-registry for the "Relay Type Field". The 1220 initial values in the sub-registry are: 1222 +-------+---------------------------------------+ 1223 | Value | Description | 1224 +-------+---------------------------------------+ 1225 | 0 | No relay is present. | 1226 | 1 | A 4-byte IPv4 address is present | 1227 | 2 | A 16-byte IPv6 address is present | 1228 | 3 | A wire-encoded domain name is present | 1229 | 4-255 | Unassigned | 1230 +-------+---------------------------------------+ 1232 Values 0, 1, 2, and 3 are further explained in Section 4.2.3 and 1233 Section 4.2.4. Relay type numbers 4 through 255 can be assigned with 1234 a policy of Specification Required (as described in [RFC8126]). 1236 6. Security Considerations 1238 6.1. Use of AMT 1240 This document defines a mechanism that enables a more widespread and 1241 automated use of AMT, even without access to a multicast backbone. 1242 Operators of networks and applications that include a DRIAD-capable 1243 AMT gateway are advised to carefully consider the security 1244 considerations in Section 6 of [RFC7450]. 1246 AMT gateway operators also are encouraged to implement the 1247 opportunistic use of IPSec [RFC4301] when IPSECKEY records [RFC4025] 1248 are available to secure traffic from AMT relays, or when a trust 1249 relationship with the AMT relays can be otherwise secured. 1251 6.2. Record-spoofing 1253 The AMTRELAY resource record contains information that SHOULD be 1254 communicated to the DNS client without being modified. The method 1255 used to ensure the result was unmodified is up to the client. 1257 There must be a trust relationship between the end consumer of this 1258 resource record and the DNS server. This relationship may be end-to- 1259 end DNSSEC validation, a TSIG [RFC2845] or SIG(0) [RFC2931] channel 1260 to another secure source, a secure local channel on the host, DNS 1261 over TLS [RFC7858] or HTTPS [RFC8484], or some other secure 1262 mechanism. 1264 If an AMT gateway accepts a maliciously crafted AMTRELAY record, the 1265 result could be a Denial of Service, or receivers processing 1266 multicast traffic from a source under the attacker's control. 1268 6.3. Congestion 1270 Multicast traffic, particularly interdomain multicast traffic, 1271 carries some congestion risks, as described in Section 4 of 1272 [RFC8085]. 1274 Application implementors and network operators that use DRIAD-capable 1275 AMT gateways are advised to take precautions including monitoring of 1276 application traffic behavior, traffic authentication at ingest, rate- 1277 limiting of multicast traffic, and the use of circuit-breaker 1278 techniques such as those described in Section 3.1.10 of [RFC8085] and 1279 similar protections at the network level, in order to ensure network 1280 health in the event of misconfiguration, poorly written applications 1281 that don't follow UDP congestion control principles, or deliberate 1282 attack. 1284 7. Acknowledgements 1286 This specification was inspired by the previous work of Doug Nortz, 1287 Robert Sayko, David Segelstein, and Percy Tarapore, presented in the 1288 MBONED working group at IETF 93. 1290 Thanks to Jeff Goldsmith, Toerless Eckert, Mikael Abrahamsson, Lenny 1291 Giuliano, Mark Andrews, Sandy Zheng, Kyle Rose, and Ben Kaduk for 1292 their very helpful comments. 1294 8. References 1296 8.1. Normative References 1298 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 1299 STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, 1300 . 1302 [RFC1035] Mockapetris, P., "Domain names - implementation and 1303 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 1304 November 1987, . 1306 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1307 Requirement Levels", BCP 14, RFC 2119, 1308 DOI 10.17487/RFC2119, March 1997, 1309 . 1311 [RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS 1312 Specification", RFC 2181, DOI 10.17487/RFC2181, July 1997, 1313 . 1315 [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 1316 Thyagarajan, "Internet Group Management Protocol, Version 1317 3", RFC 3376, DOI 10.17487/RFC3376, October 2002, 1318 . 1320 [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, 1321 "DNS Extensions to Support IP Version 6", STD 88, 1322 RFC 3596, DOI 10.17487/RFC3596, October 2003, 1323 . 1325 [RFC3597] Gustafsson, A., "Handling of Unknown DNS Resource Record 1326 (RR) Types", RFC 3597, DOI 10.17487/RFC3597, September 1327 2003, . 1329 [RFC3810] Vida, R., Ed. and L. Costa, Ed., "Multicast Listener 1330 Discovery Version 2 (MLDv2) for IPv6", RFC 3810, 1331 DOI 10.17487/RFC3810, June 2004, 1332 . 1334 [RFC4604] Holbrook, H., Cain, B., and B. Haberman, "Using Internet 1335 Group Management Protocol Version 3 (IGMPv3) and Multicast 1336 Listener Discovery Protocol Version 2 (MLDv2) for Source- 1337 Specific Multicast", RFC 4604, DOI 10.17487/RFC4604, 1338 August 2006, . 1340 [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for 1341 IP", RFC 4607, DOI 10.17487/RFC4607, August 2006, 1342 . 1344 [RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown, 1345 "Default Address Selection for Internet Protocol Version 6 1346 (IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012, 1347 . 1349 [RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service 1350 Discovery", RFC 6763, DOI 10.17487/RFC6763, February 2013, 1351 . 1353 [RFC7450] Bumgardner, G., "Automatic Multicast Tunneling", RFC 7450, 1354 DOI 10.17487/RFC7450, February 2015, 1355 . 1357 [RFC8085] Eggert, L., Fairhurst, G., and G. Shepherd, "UDP Usage 1358 Guidelines", BCP 145, RFC 8085, DOI 10.17487/RFC8085, 1359 March 2017, . 1361 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1362 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1363 May 2017, . 1365 [RFC8305] Schinazi, D. and T. Pauly, "Happy Eyeballs Version 2: 1366 Better Connectivity Using Concurrency", RFC 8305, 1367 DOI 10.17487/RFC8305, December 2017, 1368 . 1370 8.2. Informative References 1372 [RFC2317] Eidnes, H., de Groot, G., and P. Vixie, "Classless IN- 1373 ADDR.ARPA delegation", BCP 20, RFC 2317, 1374 DOI 10.17487/RFC2317, March 1998, 1375 . 1377 [RFC2845] Vixie, P., Gudmundsson, O., Eastlake 3rd, D., and B. 1378 Wellington, "Secret Key Transaction Authentication for DNS 1379 (TSIG)", RFC 2845, DOI 10.17487/RFC2845, May 2000, 1380 . 1382 [RFC2931] Eastlake 3rd, D., "DNS Request and Transaction Signatures 1383 ( SIG(0)s )", RFC 2931, DOI 10.17487/RFC2931, September 1384 2000, . 1386 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 1387 Jacobson, "RTP: A Transport Protocol for Real-Time 1388 Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, 1389 July 2003, . 1391 [RFC4025] Richardson, M., "A Method for Storing IPsec Keying 1392 Material in DNS", RFC 4025, DOI 10.17487/RFC4025, March 1393 2005, . 1395 [RFC4301] Kent, S. and K. Seo, "Security Architecture for the 1396 Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, 1397 December 2005, . 1399 [RFC5110] Savola, P., "Overview of the Internet Multicast Routing 1400 Architecture", RFC 5110, DOI 10.17487/RFC5110, January 1401 2008, . 1403 [RFC6726] Paila, T., Walsh, R., Luby, M., Roca, V., and R. Lehtonen, 1404 "FLUTE - File Delivery over Unidirectional Transport", 1405 RFC 6726, DOI 10.17487/RFC6726, November 2012, 1406 . 1408 [RFC7359] Gont, F., "Layer 3 Virtual Private Network (VPN) Tunnel 1409 Traffic Leakages in Dual-Stack Hosts/Networks", RFC 7359, 1410 DOI 10.17487/RFC7359, August 2014, 1411 . 1413 [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 1414 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 1415 Multicast - Sparse Mode (PIM-SM): Protocol Specification 1416 (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 1417 2016, . 1419 [RFC7858] Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D., 1420 and P. Hoffman, "Specification for DNS over Transport 1421 Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May 1422 2016, . 1424 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1425 Writing an IANA Considerations Section in RFCs", BCP 26, 1426 RFC 8126, DOI 10.17487/RFC8126, June 2017, 1427 . 1429 [RFC8313] Tarapore, P., Ed., Sayko, R., Shepherd, G., Eckert, T., 1430 Ed., and R. Krishnan, "Use of Multicast across Inter- 1431 domain Peering Points", BCP 213, RFC 8313, 1432 DOI 10.17487/RFC8313, January 2018, 1433 . 1435 [RFC8484] Hoffman, P. and P. McManus, "DNS Queries over HTTPS 1436 (DoH)", RFC 8484, DOI 10.17487/RFC8484, October 2018, 1437 . 1439 [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS 1440 Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, 1441 January 2019, . 1443 Appendix A. Unknown RRType construction 1445 In a DNS resolver that understands the AMTRELAY type, the zone file 1446 might contain this line: 1448 IN AMTRELAY 128 0 3 amtrelays.example.com. 1450 In order to translate this example to appear as an unknown RRType as 1451 defined in [RFC3597], one could run the following program: 1453 1454 $ cat translate.py 1455 #!/usr/bin/env python3 1456 import sys 1457 name=sys.argv[1] 1458 wire='' 1459 for dn in name.split('.'): 1460 if len(dn) > 0: 1461 wire += ('%02x' % len(dn)) 1462 wire += (''.join('%02x'%ord(x) for x in dn)) 1463 print(len(wire)//2) + 2 1464 print(wire) 1466 $ ./translate.py amtrelays.example.com 1467 24 1468 09616d7472656c617973076578616d706c6503636f6d 1469 1471 The length and the hex string for the domain name 1472 "amtrelays.example.com" are the outputs of this program, yielding a 1473 length of 22 and the above hex string. 1475 22 is the length of the wire-encoded domain name, so to this we add 2 1476 (1 for the precedence field and 1 for the combined D-bit and relay 1477 type fields) to get the full length of the RData, and encode the 1478 precedence, D-bit, and relay type fields as octets, as described in 1479 Section 4. 1481 This results in a zone file entry like this: 1483 IN TYPE260 \# ( 24 ; length 1484 80 ; precedence = 128 1485 03 ; D-bit=0, relay type=3 (wire-encoded domain name) 1486 09616d7472656c617973076578616d706c6503636f6d ) ; domain name 1488 Author's Address 1490 Jake Holland 1491 Akamai Technologies, Inc. 1492 150 Broadway 1493 Cambridge, MA 02144 1494 United States of America 1496 Email: jakeholland.net@gmail.com