1 / 16

Overview of draft–16 for MIPv6

Overview of draft–16 for MIPv6. MIPv6 Design Team March 19 th , 2002. Basics. Submitted yesterday, not in I-D directories yet For the moment can be accessed at: http://www.piuha.net/~jarkko/publications/mipv6/ draft-ietf-mobileip-ipv6-pre16.txt (I-D format)

aure
Télécharger la présentation

Overview of draft–16 for MIPv6

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. Overview of draft–16 for MIPv6 MIPv6 Design Team March 19th, 2002

  2. Basics • Submitted yesterday, not in I-D directories yet • For the moment can be accessed at: http://www.piuha.net/~jarkko/publications/mipv6/ draft-ietf-mobileip-ipv6-pre16.txt (I-D format) mipv6-modified-parts-pre16.pdf (modified parts) • Modifications based on the security discussions and decisions • The document is in debt to various Internet Drafts that have been issued around this subject • Still needs some work (expect draft–17 soon)

  3. What’s new • Now securely usable on a global scale • Routing topology has changed • Due to HAO restrictions • Message sequences have changed • Due to RR, the new security mechanism • Signalling formats have changed • Due to desire to allow IPsec usage on MN-HA and tunneled RR signaling • Terminology has changed • Mainly due to formatting modifications, options => messages, sub-options => parameters, … • Many changed sections

  4. Still, it looks kind of familiar… • New messages added but old ones intact • Messages carried by new protocol instead of DO, but format still largely the same • Route Optimization and Bidirectional tunneling functionally intact

  5. Document modifications • 4.1. Overview • 4.x. New protocols • 4.4. Security Design (was authentication) • 5.1. Mobility Header (was BU, BA, BR) • 5.4. HAO • 5.x. Routing Header Type 2 • 7.2. Requirements for all IPv6 Nodes • 8. CN Behaviour • 9.x. Protecting RR packets • 10. MN Behaviour • X. Future Enhancements • 11. IANA Considerations • 13. Security Considerations • A.1. Modifications

  6. Overview of functionality • Return Routability procedure • Home Address Option processing • New role for Binding Request • Message Formats

  7. 2a. Home Test 1b. Care-of Test Init 1a. Home Test Init 2b. Care-of Test 3. Binding Update 4. Binding Ack RR messaging HA CN MN

  8. RR details and math 1a. HOTI: MN(HoA) -> CN: HoA 1b. COTI: MN(CoA) -> CN: CoA 2a. HOT: CN -> MN(HoA): K0, j 2b. COT: CN -> MN(CoA): K1, i 3. BU: MN(CoA) -> CN: HoA, CoA, MAC, j, i 4. BA: CN -> MN(CoA): MAC • CN is stateless until a good BU is received • K0 and K1 are cookies derived from a key known by CN • BU and BA MACs are based the cookies • The MACs are calculated over the messages • CN is assured that BU is from someone on path

  9. Bidir tunneling: no HAO Regular answer BCE exists: HAO Regular answer BCE expired: HAO Binding Missing Usage of HAO- and related messaging HA CN MN

  10. New role for Binding Request • Detection of mobile nodes may not be possible anymore for the CN! • Bidirectional tunneling hides the fact that the node is mobile • Binding Request in draft-16 has become a kind of a “Binding Refresh Request” • Responsibility for starting Route Optimisation on the MN side

  11. Mobility Header format . . . IPv6 header . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Payload Proto | Header Len | MH Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Checksum | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | . . . Message Data . . . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Messages carried in this format: • Binding Request • Home Test Init, Home Test, Care-of Test Init, Care-of Test • Binding Update, Binding Ack • Binding Missing

  12. Home Test message data +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Home Nonce Index | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + + | Home Cookie (128 bits) | + + | | + + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | . . . Parameters . . . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  13. Binding Update message data +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|H|S|D| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sequence # | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Lifetime | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + + | | + Home Address (?) + | | + + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | . Parameters . . . . (Mandatory carried parameters for CN Bus: Nonce Indices, . | Authentication Data) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  14. Nonce Indices parameter +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type = 4 | Len = 6 | Home Nonce Index | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Care-of Nonce Index | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  15. Authentication Data parameter +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 5 | 18 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SPI, always zero in draft-16 (?) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Authenticator + | | + (calculated from RR specific rules, different from draft–15) + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  16. Summary • Main new things: RR, HAO, formats • Questions, comments? • Some open issues remain and will be discussed later

More Related