End to End Multihoming
-
Upload
poli-markova -
Category
Documents
-
view
226 -
download
0
description
Transcript of End to End Multihoming
![Page 2: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/2.jpg)
2
THE PROBLEM
• Full Routing Table Too Large– because of random IPv4 address allocation
• to be solved with IPv6
– because of Multihoming
• # of TLAs should be controlled– below what?– below 1,000 seems to be easy– below 100 is not difficult, hopefully
![Page 3: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/3.jpg)
3
TLI
SLI
Subscribers
Typical Scenario of IPv6 Multihoming
![Page 4: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/4.jpg)
4
TLI
SLI
Subscribers 3 8 2 4
3 3 2 2
1 1 1 1
5
2
1
Number of Prefixes with E2E Multihoming
![Page 5: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/5.jpg)
5
Multihoming
• Typical IPv4 multihoming– Advertise an address range through multiple
(not necessarily 2) routes– Explosion of
• # of routing table entries
• # of ASes
![Page 6: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/6.jpg)
6
MultihomedSite
H
ISP A ISP B
Rest of the Internet
Singly HomedSite
![Page 7: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/7.jpg)
7Multihoming by (Intelligent) Routing
131.112.0.0/16131.112.0.0/16
131.112.0.0/16 131.112.0.0/16、131.113.0.0/16
131.113.0.0/16
MultihomedSite
H
ISP A ISP B
Rest of the Internet
Singly HomedSite
![Page 8: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/8.jpg)
8Multihoming by (Intelligent) Routing
131.112.0.0/16131.112.0.0/16
131.112.0.0/16 131.112.0.0/1 5
131.113.0.0/16
MultihomedSite
H
ISP A ISP B
Rest of the Internet
Singly HomedSite
![Page 9: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/9.jpg)
9
End to EndMultihoming (1)
• A host has multiple addresses
• Application or transport tries all the destination addresses– Each address range can be aggregated
• No routing table entry explosion
• No AS number explosion
![Page 10: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/10.jpg)
10
End to EndMultihoming (2)
– When to Try Alternative Addresses?• Application/Transport dependent
– Controlled by the intelligence of end systems
• TCP will have a default timeout period
– Which Address Should be Tried Next?• Routing table can give hints
– Lack of a routing table entry means lack of reachability to a host
» Existence of an aggregated routing table entry does not mean reachability to the host
– Metric information in routing table can help too
![Page 11: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/11.jpg)
11End to End Multihoming
133.112.0.0/16131.112.0.0/16
133.0.0.0/8 131.0.0.0/8
131.113.0.0/16
133.112.32.132,131.112.32.132
MultihomedSite
H
ISP A ISP B
Rest of the Internet
Singly HomedSite
![Page 12: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/12.jpg)
12
Because It IS End to End
• No change to router functionality
• MUST change API on hosts– Or the hosts are singly homed
• Wrong to assume– Intelligent routers help dumb nodes– A host can and is recommended to have a
default free global (but now small) routing table– A real dumb host is dumb and singly homed
![Page 13: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/13.jpg)
13
Do Intelligent End SystemsRequire Standard IGP?
• No.
• Standard protocol to distribute (but not compute) routing table to hosts is required
• RIPv2 (with metric >15) seems to be good enough. Or RA?
• BGP routers generate metric from policy based preference
![Page 14: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/14.jpg)
14
Source Address Selection?
• Wrong topic for multihoming
• Both sources select destination addresses– At the destination, reverse & forward DNS
lookup of source address gives all the address of the source
• The destination selects an appropriate destination address for reply
• No source address selection by source meaningful
– Or, protocols may be modified to carry them
![Page 15: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/15.jpg)
15
TCP API/Protocol Changes
• Source have no reachability information of SYNACK reply addresses at the destination– Destination should select the address
• Multiple PCB entries for a connection• How to give the multiple addresses of the
source to the destination?– DNS?– Let SYN carry all the addresses?
![Page 16: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/16.jpg)
16
DNS Changes
• DNS can not give addresses for DNS reply• Clients should choose source address
reachable from the name server– First, choose randomly– Should (re)try with other source addresses– A lot of delay
• Or, change protocol?– Query carries all the addresses of the source
![Page 17: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/17.jpg)
17
End to End Multihomingand DNS/SMTP
• DNS and SMTP servers already deploy E2E multihoming– NS/MX servers may have multiple A records– If a server has multiple addresses
• All the addresses are tried
• It is of course as the most important, required-to-be-rubust applications of the Internet
![Page 18: End to End Multihoming](https://reader036.fdocuments.in/reader036/viewer/2022082403/5695d3e61a28ab9b029f92d4/html5/thumbnails/18.jpg)
18
8+8
• DNS reverse lookup by lower 8 bytes only
• Hosts are identified by lower 8 bytes (IID)– A compact DNS name carried by all the packets
of all the protocols– Makes modification to application/transport
protocols for E2E multihoming easier
• Not Mike O’dell’s GSE one (violate E2E)
• Teraoka san will present his version (8+5)