60 likes | 196 Views
RFC 4068bis draft-ietf-mipshop-fmipv6-rfc4068bis-02.txt. Rajeev Koodli. Changes. Added a New Prefix Management Section Resolved the remaining issues. Prefix Management. NAR advertises a prefix valid on the interface to which the target AP is attached
E N D
RFC 4068bisdraft-ietf-mipshop-fmipv6-rfc4068bis-02.txt Rajeev Koodli
Changes • Added a New Prefix Management Section • Resolved the remaining issues
Prefix Management • NAR advertises a prefix valid on the interface to which the target AP is attached • Some deployments may provide per-MN prefix (which must also be valid on the interface to which the AP is attached) • 4068bis cannot specify prefix management • Base protocol works • Provide aggregate prefix in PrRtAdv • Provide the per-MN prefix in HAck, NAACK • Other scenarios possible
IANA Section • ICMP messages use Experimental Mobility Protocol registry • Need to move them over to an appropriate registry (assignments/mobility-parameters ?) • BADF MH option needs assignment • LLA, MH-LLA, Prefix-Info, IPv6 Address, NAACK already have assignments
Other Issues • Merge Prefix Information Option and IPv6 Address Option • Include text about Proxy Router messages, and HI/HAck in Section 8 (Security Considerations) • Define additional terms (predictive, reactive, neighborhood discovery) • Lifetime of handover key should be the same as tunnel lifetime • Using NAACK to provide an alternate address • Should we make this an option?
Other Issues (done) • Added code for unsolicited HAck • UNA could be unicast to NAR • Include MH-LLA option in FBU