1 / 7

Multiaddressing with MAST

Multiaddressing with MAST. SAINT 2004, Tokyo D. Crocker Brandenburg InternetWorking http://brandenburg.com/current. IP Independent datagrams Infrastructure works fine Long time to get that way Leave it alone ! Multiaddressing Multiple IP Addresses Association of datagrams

marc
Download Presentation

Multiaddressing with MAST

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Multiaddressing with MAST SAINT 2004, Tokyo D. Crocker Brandenburg InternetWorking http://brandenburg.com/current

  2. IP Independent datagrams Infrastructure works fine Long time to get that way Leave it alone! Multiaddressing Multiple IP Addresses Association of datagrams Like transport: context Like IP: routing choice Simultaneous Changing Mobile Multiaddressing Multihomed Renumber D. Crocker SAINT 2004 2

  3. MAST • Multiple Address Service for Transport • Pools of locators, for pairs of endpoints • Protected control channel, for maintenance of pools • Identify association with TCP-like “Association ID” • Peer-to-Peer — No infrastructure needed for core service! • Add third-party components when essential Mobile client:Standard transport rendezvous Mobile target: Dynamic “presence” service Endpoint surrogate: Forwarding agent (NAT-like) D. Crocker SAINT 2004 3

  4. Association(EIDl, Port l, EIDr, Port r) DNS Presence EIDl EIDr IP-EP IP-EP MAST IPa IPy MAST Architecture EP = Endpoint TR = Transit EID = Ephemeral IDentifier Transport Transport IPf IPq IP-TR IP-TR IP-TR IPa IPf IPq IPy D. Crocker SAINT 2004 4

  5. MAST Protocol • Pool maintenance • Send complete locator list, to avoid synchronization problems • Send PROBE to peer, to discover your own NAT public address • Security – only equal to current IP • Domain Name, as registered, global identifier • Nonce, internal to association for context reference, anti-hijacking • Design the nonce and channel scheme for desired protection • Efficiencies • MAST is not in critical path of transport startup(!) • Can even defer MAST until association is persistent • However separate MAST channel adds to packet overhead D. Crocker SAINT 2004 5

  6. SLAP:Shared Locator Address Pool • Multiple transports • Cooperative • Reduce packet overhead • Share on sets of attributes • Issue • Synchronizing changes between different control paths Assoc-ID = [ EIDl, EIDr,(IPl1, IPr1), (IPl2, IPr2), …A1, A2, … ] SLAP TCP mTCP SCTP MAST IP-TR D. Crocker SAINT 2004 6

  7. Features Multiaddressing Multihoming, mobility, both Infrastructure None, sometimes, always IP version(s) Identifier Registered vs. ephemeral Rendezvous Creating the association After service interruption Overhead Per payload packet Control protocol Transport startup delay Scaling impact Constant per association, vs. deferred Administration Evaluating Design Choices D. Crocker SAINT 2004 7

More Related