1 / 5

Route Optimization update

This document discusses the basic features and changes in route optimization, specifically focusing on binding cache messages, binding warning, binding request, binding update, binding acknowledge, smooth handoff, new advertisement bit, and handling mobility-unaware IPv4 nodes. It also covers the use of generalized authentication extension subtypes, smooth handoff authentication subtype, binding warning extension, and more. Additionally, it highlights issues related to the use of binding update and harmonization with new registration messages in 3G documents, and discusses the need for interoperability testing.

clingman
Download Presentation

Route Optimization update

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. Route Optimization update Charles E. Perkins/Nokia David B. Johnson/CMU IETF 47 draft-ietf-mobileip-optim-09.txt

  2. Basic features • Binding Cache messages • Binding Warning • Binding Request • Binding Update • Binding Acknowledge • Smooth Handoff • New advertisement bit • Handling mobility-unaware IPv4 nodes

  3. List of changes • Use Generalized Authentication Extension subtypes instead of separate type numbers • Introduced Smooth Handoff authentication subtype • needed since foreign agent is source address, not mobile node • Introduced Binding Warning extension to Registration Request, with type number

  4. More Changes • Home agent MAY send binding updates when a mobile node reregisters • ‘T’ bit included in diagram • Moved “Master Key” section to appendix

  5. Issues • Binding Update should be used instead of new Registration Messages in 3G document • or, at least their functions should be harmonized • Interoperability testing?

More Related