1 / 8

Multiple Care-of Address Registration

Multiple Care-of Address Registration. WGLC completed. WGLC for -05.txt. After WGLC, we published -06.txt and –pre07.txt(ML) We did several editorial updates and applied received comments Binding Unique Identifier is renamed to Binding Identifier

aolani
Download Presentation

Multiple Care-of Address Registration

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. Multiple Care-of Address Registration

  2. WGLC completed • WGLC for -05.txt. • After WGLC, we published -06.txt and –pre07.txt(ML) • We did several editorial updates and applied received comments • Binding Unique Identifier is renamed to Binding Identifier • New Status Code [MCOA NOTCOMPLETE], the home agent uses this status code in BA when not all the bindings are accepted in the bulk registration. • [MCOA FLAG CONFLICTS] are now merged with [MCOA MALFORMED] • Add care-of address verification issue in the Security Consideration, the text is proposed by Benjamin Lim. • Support DSMIPv6 • Support simultaneous foreign and home location. (Section 5.5)

  3. Remaining Issues • Sequence number for the bindings. Should we maintain the sequence number for each binding separately or not? • In the simultaneous home and visited link operation, how does the HA delete the state about forwarding packets to the mobile node's home address on the home link? When the does the state expire? • We added some text, but might require further discussion • On whether we should consider enhanced RO for this draft. Not sure if there are any issues

  4. Sequence Number issue • MN manages an individual sequence value per binding. The problem is when MN changes the registration mode from individual to bulk. Which sequence number should be picked for BU? • MN should manage the single sequence value for all bindings.

  5. Enhanced RO • MN can register its binding to CN with Return Routability procedure (RFC3775). • We need to investigate whether MCoA is compliant with the enhanced RO (RFC4886) or not. • We will get additional review

  6. Simultaneous Home and Foreign attachment • HA intercepts all packets meant for MN and decides to send the traffic directly to HoA on the link or tunnel to CoA. • For the scenario on the left, MN learns L2 address of default router and constructs outgoing packets w/out NDP. Likewise HA learns MN’s L2 address and delivers packets to MN w/out NDP. INTERNET INTERNET R HA HA PROXY NDP NDP MN MN

  7. Simultaneous Home and Foreign Attachments • MN sets the ‘H’ flag in the BID option of the deregistration BU for the interface attached to the home link. • MN will know whether it can operate NDP or not by the status value in BA • “MCOA RETURNHOME WO/NDP” status code • While MN is attached to both home and foreign links, MN sends BU with H flag set in BID option for CoA. • When H flag is explicitly unset, the HA stops delivering packets to the HoA on the home link. • If all the bindings have expired for HoA, HA delivers all the packets to the HoA on the home link. (Returning home) • H flag is required to keep the state of MN’s attachment to both home and foreign links at the home agent

  8. Next Step • Will publish the updated version • draft-ietf-monami6-multiplecoa-07.txt • second WGLC right after this IETF.

More Related