1 / 6

Runtime LMA Assignment Support for Proxy Mobile IPv6

Runtime LMA Assignment Support for Proxy Mobile IPv6. draft-ietf-netext-recirect-03 Jouni Korhonen , Sri Gundavelli , Hidetoshi Yokota, Xiangsong Cui IETF #78, Netext WG. Recap: An enhancement to RFC5213.

marlie
Télécharger la présentation

Runtime LMA Assignment Support for Proxy Mobile IPv6

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. Runtime LMA Assignment Support for Proxy Mobile IPv6 draft-ietf-netext-recirect-03 JouniKorhonen, Sri Gundavelli, Hidetoshi Yokota, Xiangsong Cui IETF #78, Netext WG

  2. Recap: An enhancement to RFC5213 • The I-D defines two LMA behaviors to enable a runtime LMA assignment (i.e. redirection): • “Soft” – BCE created on a target LMA during the redirection procedure. • “Hard” – BCE created on a target LMA using an additional PBU/PBA exchange after the redirection. • LMA indicates to a MAG which one took place and the MAG supports both approaches. • Solutioncanfallback to basic RFC5213 operation.

  3. Status – Changes from 01 -> 02 • Clarifications in Introduction (review Qin Wu) • Independence from DNS bullet: added a reference to draft-ietf-netlmm-lma-discovery. • Independence from AAA bullet: added a reference to RFC5777 (Diameter stuff for PMIPv6). • Anycast bullet: clarified how anycast could fit into the picture.. • Section 4.2 (review Qin Wu) • Redirect mobility option has two new flags: ‘K’ & ‘N’ for indicating whether IPv6 or IPv4 r2LMA addresses are included in the option. • Clarified the use/role of ‘F’ flag when making a decision to add IPv4 r2LMA address.

  4. Status – Changes from 02 -> 03 • Introduction revisited • Anycast bullet: more text massaging how anycast could fit into the picture.. • Section 4.2 • Fixed erroneous message length.. • Btw - known nits in -03 (== comments): • Still using old boilerplate • At least one outdated reference • Some weird spacing (that need manual fixing)

  5. Next Steps • WGLC started 7th July and ends 27th July. • Complete the WGLC and proceed to IESG.. so please review!

  6. Questions.. Comments.. RFCs for dummies Picture adapted from Flame Warriors

More Related