1 / 29

MHAP

MHAP. IETF-55 ipv6mh http://arneill-py.sacramento.ca.us/ipv6mh/ Michel Py - mpy@ieee.org. MHAP. M ulti H oming A liasing P rotocol Router-based solution. Zero change to hosts. Dual-space protocol. One identifier: PI address (either MHAP or GAPI). Multiple locators: PA addresses. 2.

harry
Download Presentation

MHAP

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. MHAP IETF-55 ipv6mh http://arneill-py.sacramento.ca.us/ipv6mh/ Michel Py - mpy@ieee.org

  2. MHAP Multi Homing Aliasing Protocol • Router-based solution. Zero change to hosts. • Dual-space protocol. • One identifier: PI address (either MHAP or GAPI). • Multiple locators: PA addresses. 2

  3. MHAP • The identifier and the locators are part of the same name space: IPv6 unicast addresses. • The main innovation is that the identifier has limited routability and is used in the identifier-to-locator process. • The scalability comes from the fact that the identifiers are not in the defaultless table. 3

  4. MHAP Similarities with multiaddress host-based solutions: • A host has n PA addresses associated to it. • The address space used for transit is aggregated PA space. 4

  5. MHAP Differences with multiaddress host-based solutions: • The multiple addresses are not bound to the host itself. The host has only one address, the PI identifier. • There is no source address selection. 5

  6. MHAP Differences with multiaddress host-based solutions: • The destination address selection uses BGP. • Binding updates are router-based, not host-based. 6

  7. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R 7

  8. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-a > PI-b Initial packet 8

  9. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-a > PI-b Initial packet 9

  10. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-3 > PI-b MHAP Request 1 PA-4 > PI-b MHAP Request 2 The MHAP requests are triggered by the initial packet. PA-a > PI-b Initial packet 10

  11. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-3 > PI-b MHAP Request 1 PA-4 > PI-b MHAP Request 2 PA-a > PI-b Initial packet 11

  12. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-3 > PA-1 MHAP Request 1 PA-4 > PA-2 MHAP Request 2 The RV point has aliased all the packets on behalf of the client. PA-a > PA-b2 Initial packet 12

  13. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-3 > PA-1 MHAP Request 1 PA-a > PA-2 MHAP Request PA-a > PA-b2 Initial packet 13

  14. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-3 > PA-1 MHAP Request 1 PA-a > PA-2 MHAP Request PA-a > PA-b2 Initial packet 14

  15. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R The endpoint has de-aliased the packet. PA-a > PI-b Initial packet 15

  16. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-a < PI-b Return traffic 16

  17. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-3 < PA1 MHAP Reply1 The MHAP replies are not triggered by the return traffic. PA-4 < PA2 MHAP Reply2 PA-a < PI-b Return traffic 17

  18. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-3 < PA1 MHAP Reply1 PA-4 < PA2 MHAP Reply2 PA-a < PI-b Return traffic 18

  19. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-3 < PA1 MHAP Reply1 PA-4 < PA2 MHAP Reply2 PA-a < PI-b Return traffic 19

  20. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-3 < PA1 MHAP Reply1 The client builds aliasing entry. PA-4 < PA2 MHAP Reply2 PA-a < PI-b Return traffic 20

  21. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-a < PI-b Return traffic 21

  22. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-a < PI-b Return traffic 22

  23. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-a > PI-b Packet #2 23

  24. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-a > PI-b Packet #2 24

  25. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R Packet is now aliased by the client, RV point not needed anymore. PA-a > PA-b2 Packet #2 25

  26. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-a > PA-b2 Packet #2 26

  27. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-a > PA-b2 Packet #2 27

  28. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R PA-a > PA-b2 Packet #2 28

  29. MHAP R R PA-a PA3 R PA1 client PI-b ha R R PI end point hb RV PA4 R R PA2 R The endpoint has de-aliased the packet. PA-a > PI-b Packet #2 29

More Related