1 / 6

Enhancements and Requirements in RFC 2002bis for Mobile Node Mobility Management

RFC 2002bis outlines significant updates aimed at improving mobile node management in networking. Key changes include the support for reverse tunneling by foreign agents, enabling more frequent advertisement issuance, and strict authentication requirements. Noteworthy appendices introduce number assignments and packet format examples. Furthermore, essential considerations on ARP limitations ensure mobile nodes adhere to best practices when not connected to their home network. These revisions enhance registration processes and clarify responsibilities of mobility agents.

leslie-estes
Download Presentation

Enhancements and Requirements in RFC 2002bis for Mobile Node Mobility Management

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. RFC 2002bis Charles E. Perkins http://www.iprg.nokia.com/~charliep

  2. Changes from RFC 2002 • Foreign agents SHOULD support Reverse Tunneling • Advertisements MAY be issued more often than once per second • SPI number MUST be included as part of authentication calculation

  3. New appendices • Added new appendix with existing and proposed number assignments • Added new appendix with change information • Added new appendix with overall packet format examples for advertisement and registration messages

  4. ARP limitations • Mobile node MUST NOT use ARP when away from home • Mobility agents SHOULD NOT advertise other default routers • Foreign agent MUST NOT broadcast ARP for mobile node’s IP address

  5. Bits • Home agent MUST ignore ‘V’ bit • Home agent MUST ignore ‘B’ bit if it does not support broadcast (instead of rejecting the registration) • Registrations with unknown care-of address and ‘D’ bit zero MUST be rejected • Mobile node MUST ignore reserved bits in advertisements

  6. More changes • Mobile node MAY use care-of address with multicast • Mobile node MAY use source IP address of advertisement as default router • Foreign agent MAY limit number of pending registrations (typically 5?)

More Related