Runtime LMA Assignment Support for Proxy Mobile IPv6

draft-ietf-netext-recirect-03Jouni Korhonen,

Sri Gundavelli,Hidetoshi Yokota,

Xiangsong CuiIETF #78, Netext WG

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.• Solution can fallback to basic RFC5213 operation.

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.

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)

Next Steps

• WGLC started 7th July and ends 27th July.• Complete the WGLC and proceed to IESG.. so

please review!

Questions.. Comments..

RFCs for

dummies

Picture adapted from Flame Warriors