Revising RFC 3775 MEXT WG, IETF 70 Vijay Devarapalli

Updates to RFC 3775 A number of minor issues have been identified with RFC 3775 –Needs to be revised to fix the bugs Scope restricted to only minor changes –No major changes to the actual protocol –Restricted scope necessary in order to not scare away SDOs who are interested in MIPv6 Quick update – shouldn’t take more than two IETF meetings

Bootstrapping RFC 3775 makes a number of assumptions regarding configuration on the MN and HA –MN is configured with a home prefix –MN and HA are configured with a pre-shared key or certificates for IKEv1 authentication –HA is configured with information which lets it determine which MN is authorized for which home address Bootstrapping work done so far eliminates the need for this kind of pre-configuration –Pre-configuration would still be allowed of course Need to clean up the spec to take into account dynamic configuration of various parameters

Returning Home RFC 3775 is not clear whether the MN should send a de-registration BU when it returns home –SHOULD is used –This caused quite a bit of confusion in the PMIPv6 – MIPv6 interactions document RFC 3775 treats a BU with home address set to CoA as a de-registration BU –Assumes BU sent with home address as source address is sent from the home link –In DS-MIPv6, BU is sent with home address as the source address IPv4 CoA option or the outer IPv4 header carries the actual CoA

MH Checksum Calculation RFC 3775 says use the value “2” for the Next Header field in the pseudo-header while calculating the checksum –It’s a bug, should have been 135 (Mobility Header) This is an interop issue that needs to be fixed

Other Minor Issues Can the HA send a Binding Error message with status ‘1’ ever, or is it the CN only? Can the HA send a Binding Refresh Request message ever? Clarify text in section that describes MN behavior in response to binding ack with status 135 Sending ICMP error to the MN in response to a BU sent from the home link What is the HA response for a malformed or invalid mobility option? –ICMP parameter problem error needs to be sent – this is not specified Relax the requirement to use a unicast address as the source address in DHAAD reply –Anycast address can also be used as the source address