Inter-domain AMT Multicast Use Case Discussion Proposal for AMT Multicast Source-AMT Connectivity Model For Inter-connected Networks (AS’s) 1.

Slides:

Advertisements

Similar presentations

Chapter 16. Windows Internet Name Service(WINS) Network Basic Input/Output System (NetBIOS) N etBIOS over TCP/IP (NetBT) provides commands and support.

Advertisements

AT&T AMT Multicast Update IETF 84 Vancouver, BC. AT&T AMT Landscape Production ready Relays deployed in 12 national sites – Based on v9 – Moving to v14.

EDNS0 Client-Subnet for DNS based CDNs

Chapter 6-7 IPv6 Addressing. IPv6 IP version 6 (IPv6) is the proposed solution for expanding the possible number of users on the Internet. IPv6 is also.

June 2007APTLD Meeting/Dubai ANYCAST Alireza Saleh.ir ccTLD

Multicasting Applications Across Inter-Domain Peering Points Percy S. Tarapore, AT&T Robert Sayko, AT&T Greg Shepherd, Cisco Toerless Eckert, Cisco Ram.

An Engineering Approach to Computer Networking

1 DNS. 2 BIND DNS –Resolve names to IP address –Resolve IP address to names (reverse DNS) BIND –Berkeley Internet Name Domain system Version 4 is still.

Mobile IP Overview: Standard IP Standard IP Evolution of Mobile IP Evolution of Mobile IP How it works How it works Problems Assoc. with it Problems Assoc.

Chapter 29 Structure of Computer Names Domain Names Within an Organization The DNS Client-Server Model The DNS Server Hierarchy Resolving a Name Optimization.

Oct 21, 2004CS573: Network Protocols and Standards1 IP: Addressing, ARP, Routing Network Protocols and Standards Autumn

Anycast Jennifer Rexford Advanced Computer Networks Tuesdays/Thursdays 1:30pm-2:50pm.

Application-Layer Anycasting: A Server Selection Architecture and Use in a Replicated Web Service IEEE/ACM Transactions on Networking Vol.8, No. 4, August.

AT&T AMT Multicast Trials Patricia McCrink 11/09/2009.

DOMAIN NAME SYSTEM. Introduction  There are several applications that follow client server paradigm.  The client/server programs can be divided into.

Multicast DNS Draft-aboba-dnsext-mdns-00.txt. Outline Goals and objectives Scope of the multicast DNS DNS server discovery Non-zeroconf behavior Zeroconf.

Everything. MACIP End-host IP: MAC: 11:11:11:11:11 gateway IP: MAC: 22:22:22:22:22 Google server IP: MACIP MACInterfaceMACInterface.

1 Content Distribution Networks. 2 Replication Issues Request distribution: how to transparently distribute requests for content among replication servers.

1 Study on Adaptation of CDN Request-Routing to Scalable Conference System Toshiyuki KAWASAKI* Koji OKAMURA** * Graduate School of Information Science.

Traffic Engineering for CDNs Matt Jansen Akamai Technologies APRICOT 2015.

資管 Lee Lesson 11 Coexistence and Migration. 資管 Lee Lesson Objectives Coexistence and migration overview Coexistence mechanisms ◦ Dual Stack ◦ Tunneling.

Spring Ch 18 IP Addresses. 2 Internet Protocol  Only protocol at Layer 3  Defines Internet addressing Internet packet format Internet routing.

RSC Part II: Network Layer 3. IP addressing Redes y Servicios de Comunicaciones Universidad Carlos III de Madrid These slides are, mainly, part of the.

Classful IP Addressing

© 2008 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. 1 Video Relay Service and Assignment.

Name Resolution Domain Name System.

Chapter 16 – DNS. DNS Domain Name Service This service allows client machines to resolve computer names (domain names) to IP addresses DNS works at the.

{ Content Distribution Networks ECE544 Dhananjay Makwana Principal Software Engineer, Semandex Networks 5/2/14ECE544.

23-Support Protocols and Technologies Dr. John P. Abraham Professor UTPA.

SMTP PROTOCOL CONFIGURATION AND MANAGEMENT Chapter 8.

Oasis: Anycast for Any Service Michael J. Freedman Karthik Lakshminarayanan David Mazières in NSDI 2006 Presented by: Sailesh Kumar.

Computer Networks. IP Addresses Before we communicate with a computer on the network we have to be able to identify it. Every computer on a network must.

DNS (Domain Name System) Protocol On the Internet, the DNS associates various sorts of information with domain names. A domain name is a meaningful and.

© MMII JW RyderCS 428 Computer Networking1 Private Network Interconnection  VPN - Virtual Private Networks  NAT - Network Address Translation  Describe.

Cisco 1 - Networking Basics Perrine. J Page 19/17/2015 Chapter 9 What transport layer protocol does TFTP use? 1.TCP 2.IP 3.UDP 4.CFTP.

1 Application Layer Lecture 6 Imran Ahmed University of Management & Technology.

Sistem Jaringan dan Komunikasi Data #9. DNS The Internet Directory Service  the Domain Name Service (DNS) provides mapping between host name & IP address.

Application-Layer Anycasting By Samarat Bhattacharjee et al. Presented by Matt Miller September 30, 2002.

Chapter 13 Microsoft DNS Server n DNS server: A Microsoft service that resolves computer names to IP addresses, such as resolving the computer name Brown.

Microsoft Windows Server 2003 TCP/IP Protocols and Services Technical Reference Slide: 1 Lesson 9 Internet Group Management Protocol (IGMP)

COMT 6251 Network Layers COMT Overview IP and general Internet Operations Address Mapping ATM LANs Other network protocols.

Draft-tarapore-mbone- multicast-cdni-05 Percy S. Tarapore, AT&T Robert Sayko, AT&T Greg Shepherd, Cisco Toerless Eckert, Cisco Ram Krishnan, Brocade.

Chapter 29 Domain Name System (DNS) Allows users to reference computer names via symbolic names translates symbolic host names into associated IP addresses.

Hybrid Overlay Multicast Framework draft-irtf-sam-hybrid-overlay-framework-02.txt John Buford, Avaya Labs Research IETF 71.

CIS 3360: Internet: Network Layer Introduction Cliff Zou Spring 2012.

Draft-engelstad-manet- name-resolution-00.txt IETF 57, Vienna MANET WG meeting Paal Engelstad, Telenor R&D / UniK.

Sharing a single IPv4 address among many broadband customers

Broadcast Federation Untangling the Internet Multicast Landscape Yatin Chawathe Research, Menlo Park Joint work with Mukund Seshadri.

TOMA: A Viable Solution for Large- Scale Multicast Service Support Li Lao, Jun-Hong Cui, and Mario Gerla UCLA and University of Connecticut Networking.

© McLean HIGHER COMPUTER NETWORKING Lesson 4: Domain Name Service Description of domain names and name resolution Domain name servers and domain.

BCP for ARP/ND Scaling for Large Data Centers

Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.

CSI 3125, Preliminaries, page 1 Networking. CSI 3125, Preliminaries, page 2 Networking A network represents interconnection of computers that is capable.

AUTHOR DETAILS: CHANDRASEKHAR NAIDU MUTTINENI Mail: Blog:

1 Lecture, November 20, 2002 Message Delivery to Processes Internet Addressing Address resolution protocol (ARP) Dynamic host reconfiguration protocol.

Enumservice VOID draft-stastny-enum-void-00 Richard Stastny Lawrence Conroy IETF60 San Diego.

A Optimal Load-balance mechanism for NAT64 (OL-NAT) draft-chen-behave-olnat-01 Gang Chen; Hui Deng;

: MobileIP. : r Goal: Allow machines to roam around and maintain IP connectivity r Problem: IP addresses => location m This is important for efficient.

Networking (Cont’d). Congestion Control l Is achieved by informing nodes along a route that congestion has occurred and asking them to reduce their packet.

So DNS is A client-server application that maps domain names into their corresponding IP addresses with the help of name servers. Mapping domain names.

Interdomain Multicast BCP Draft IETF 84 Vancouver, BC Robert Sayko

Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.

CSEN 404 Introduction to Networks Amr El Mougy Lamia AlBadrawy.

NAT : Network Address Translation

Content Distribution Networks

draft-nortz-optimal-amt-relay-discovery-00

Content Distribution Networks

IEEE MEDIA INDEPENDENT HANDOVER

An Engineering Approach to Computer Networking

Presentation transcript:

Inter-domain AMT Multicast Use Case Discussion Proposal for AMT Multicast Source-AMT Connectivity Model For Inter-connected Networks (AS’s) 1

Problem  With the existing model for AMT anycast addressing, when an end-user requests multicast content via AMT, the request will be routed to the nearest AMT Relay, which could be in the requestor’s local network or any other network.  For the connection to be successful, the end-user must reach an AMT Relay that has multicast connectivity to the Multicast Source that originates the content.  If the AMT Relay reached by the end-user does not have multicast connectivity to the source, the result will be a failure to obtain the content via multicast.  If the AMT Relay reached does have multicast connectivity with the source, but is located in a distant network, in many cases the following highly inefficient AMT tunnel will result. Anycast Addressing Issue AMT Relay Internet Multicast Source Multicast-enabled Source Network End-User’s Network AMT Gateway  A way is needed to route an anycast AMT request to the closest AMT Relay that has multicast connectivity to the requested Source. This could be a local (to the end-user) AMT Relay on another provider’s network, or an AMT Relay in the Multicast Source’s network, or an AMT Relay in an intermediate network. 2

11/29/2010 Page 3 © 2011 AT&T Intellectual Property. All rights reserved. Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 Federation A Federation B Network Architecture and Connectivity AMT DNS 2 AMT DNS 1 AMT DNS 3 3 Multicast-enabled interconnection Unicast-only interconnection Federation AFederation B andnetworks are internally multicast-enabled Networks 7 and 8 are not multicast-enabled Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

Requirements for Solution Only three requirements: 1.In a network that hosts a Multicast Source, the Authoritative DNS server has an “in-addr.arpa” address entry for the Source IP. E.g., for S1 of (S1,G1) = 1.x.y.z, there is an entry in Authoritative DNS 1 for “z.y.x.1.in-addr.arpa” that maps to the anycast address described in #2 below. 2.All networks (members of the same “Federation”) that have multicast connectivity to S1 and wish to server content from that Source, must have “AMT DNS” servers reachable by the same anycast address, and the entries in those AMT DNS servers map to the AMT Relays in their own networks. E.g., AMT DNS 1, AMT DNS 2, and AMT DNS 3 in the diagrams are reachable by the same anycast address, and they have entries that map to the address of their own network’s AMT Relays. So, AMT DNS 1 maps queries to AMT Relay(s) 1, AMT DNS 2 maps to AMT Relay(s) 2, AMT DNS 3 maps to AMT Relay(s) 3. 3.AMT Gateways seek to find an AMT Relay by the deterministic construction of an “in-addr.arpa” DNS query* of the form “z.y.x.A.in-addr.arpa” Where “A” is (e.g.) the class A address allocated to the Source’s host network, and “A.x.y.z” is the IP address of the Source specified in the (S,G). 4 * Instead of using the global AMT anycast address

11/29/2010 Page 5 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 AMT Gateway 1 “z.y.x.1.in-addr.arpa” End-user application on Network 8 wants content on S1 (1.x.y.z), the AMT Gateway determines it does not have native multicast access to S1, seeks to connect via AMT Relay, constructs DNS query for “z.y.x.1.in-addr.arpa” AMT DNS 2 AMT DNS 1 AMT DNS 3 5 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 6 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 AMT Gateway 2 “z.y.x.1.in-addr.arpa” Network 8 Local DNS performs recursive queries, eventually finds Authoritative DNS 1 AMT DNS 2 AMT DNS 1 AMT DNS 3 6 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 7 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 AMT Gateway 3 “a.b.c.d” Anycast Network 1 Authoritative DNS redirects query to “a.b.c.d”, the anycast address for all Federation A “AMT DNS” servers (AMT DNS 1, 2, & 3) AMT DNS 2 AMT DNS 1 AMT DNS 3 7 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 8 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 AMT Gateway 4 Send query for “z.y.x.1.in-addr.arpa” to DNS server at “a.b.c.d” Anycast IP Network 8 Local DNS sends a query for “z.y.x.1.in-addr.arpa” to “a.b.c.d”, the anycast address for all Federation A “AMT DNS” servers, which is naturally routed to AMT DNS 3, the closest AMT DNS server in Federation A AMT DNS 2 AMT DNS 1 AMT DNS 3 8 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 9 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 AMT Gateway 5 AMT Relay 3 IP Address Entries in Network 3 AMT DNS map to Network 3’s own AMT Relays because Network 3 has multicast connectivity to S1, thus AMT DNS 3 returns IP address of AMT Relay 3 AMT DNS 2 AMT DNS 1 AMT DNS 3 9 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 10 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 AMT Gateway 6 AMT Relay 3 IP Address End-user receives IP address of optimal AMT Relay for S1 AMT DNS 2 AMT DNS 1 AMT DNS 3 10 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 11 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 AMT Gateway End-user GW establishes optimal tunnel for content at S1 Multicast AMT Tunnel AMT DNS 2 AMT DNS 1 AMT DNS 3 11 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 12 Network 2 AMT Relay 2 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 Network 6 AMT Relay 6 Network 5 AMT Relay 5 AMT DNS 2 AMT DNS 1 AMT DNS 3 AMT DNS 5 AMT DNS 4 AMT DNS 6 Multicast Source 5 Network Architecture and Connectivity – End-user Wants Content at Multicast Source 5 12 Federation A Federation B Network 1 Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 13 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 Network 6 AMT Relay 6 Network 5 AMT Relay 5 AMT Gateway 1 “z.y.x.5.in-addr.arpa” End-user Gateway determines no native multicast access to S5 (IP address = “5.x.y.z”), seeks to connect via AMT Relay, queries DNS to resolve “z.y.x.5.in-addr.arpa” Multicast Source 5 AMT DNS 5 AMT DNS 4 AMT DNS 6 AMT DNS 2 AMT DNS 1 AMT DNS 3 13 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 14 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 Network 6 AMT Relay 6 Network 5 AMT Relay 5 AMT Gateway 2 “z.y.x.5.in-addr.arpa” Network 8 local DNS performs recursive queries, finds Authoritative DNS 5 Multicast Source 5 AMT DNS 5 AMT DNS 4 AMT DNS 6 AMT DNS 2 AMT DNS 1 AMT DNS 3 14 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 15 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 Network 6 AMT Relay 6 Network 5 AMT Relay 5 AMT Gateway 3 “e.f.g.h” Anycast Authoritative DNS 5 redirects query to “e.f.g.h”, the Anycast address for all Federation B “AMT DNS” servers (AMT DNS 4, 5, & 6) Multicast Source 5 AMT DNS 5 AMT DNS 4 AMT DNS 6 AMT DNS 2 AMT DNS 1 AMT DNS 3 15 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 16 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 AMT Gateway 4 Send query for “z.y.x.5.in-addr.arpa” to DNS server at “e.f.g.h” Anycast IP Network 8 Local DNS sends a query for “z.y.x.5.in-addr.arpa” to “e.f.g.h”, the anycast address for Federation B “AMT DNS” servers, which is naturally routed to AMT DNS 6, the closest AMT DNS server in Federation B AMT DNS 2 AMT DNS 1 AMT DNS 3 16 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 17 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 AMT Gateway 5 AMT Relay 6 IP Address Entries in Network 6 AMT DNS map to Network 6’s own AMT Relays because Network 6 has multicast connectivity to S5, thus AMT DNS 6 returns IP address of AMT Relay 6 AMT DNS 2 AMT DNS 1 AMT DNS 3 17 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 18 Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 AMT DNS 4 Network 6 AMT Relay 6 AMT DNS 6 Network 5 AMT Relay 5 AMT DNS 5 AMT Gateway 6 AMT Relay 6 IP Address End-user receives IP address of optimal AMT Relay for S5 AMT DNS 2 AMT DNS 1 AMT DNS 3 18 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6

11/29/2010 Page 19 © 2011 AT&T Intellectual Property. All rights reserved. Network 2 AMT Relay 2 Network 1 AMT Relay 1 Multicast Source 1 Network 7 Local DNS 7 Network 8 Local DNS 8 Network 3 AMT Relay 3 Network 4 AMT Relay 4 Network 6 AMT Relay 6 Network 5 AMT Relay 5 AMT Gateway End-user GW establishes optimal tunnel for content at S5 Multicast AMT Tunnel AMT DNS 2 AMT DNS 1 AMT DNS 3 Multicast Source 5 AMT DNS 5 AMT DNS 4 AMT DNS 6 19 Federation A Federation B Author. DNS 1 Author. DNS 2 Author. DNS 3 Author. DNS 4 Author. DNS 5 Author. DNS 6