1. Multiple Care-of Address Registration draft-ietf-monami6-multiplecoa-02.txt

2. Status draft-ietf-monami6-multiplecoa-02.txt The draft is updated based on comments after the last IETF meeting.

3. Comments on ML Lack of failure detection scheme removing the failure detection capability from the MCoA Allow to use BID when single binding is active? Yes The Priority field of BID option is not clearly defined. Flow filtering needs default binding MN can use the priority value to pick one binding if no filtering scheme is available Verification whether CN supports MCoA or not Returning Home issue (MN returns home while it attaches to another foreign link) RR timing issue Blank security section Is Sequence Number assigned per HoA? The spec. itself is too long… Packet format is odd…

4. Updates Updating the text of BID definition. Removing R flag according to complexity. Introducing O (Overwrite) flag. Removing the Binding Error Clearing up the Status code of Binding Unique Identifier sub-option and Binding Acknowledgment. Renewing the texts in Section 6.3. Adding new section "Sending Packets to HA" and "Receiving Packets from MN". adding how to handle correspondent nodes which do not support MCoA extension in Section 5.2. Return routability is now extended to carry and use BID to generate Authenticator. Section 6.2 and Section 5.2 are added. Adding a new section: IPsec and IKEv2 interaction. Shortening Introduction. We also remove several useless texts in this doc.

5. Message Format Care-of address (C) flag for bulk registration When this flag is set, a mobile node can store a Care-of Address corresponding to the BID in the Binding Unique Identifier sub-option. This flag must be used whenever a mobile node sends multiple bindings in a single Binding Update, i.e. bulk registration. Overwrite (O) flag for both bulk and separate registration When this flag is set, a mobile node requests a home agent to replace all the bindings to binding entries stored in a Binding Update. This flag is valid for Home Registration and Deregistration.

6. Overwrite (O) flag When this flag is set, a mobile node requests a home agent to replace all the bindings to binding entries stored in a Binding Update. This flag is valid for Home Registration and Deregistration. It is useful when a MN bootstraps and sends a BID-sub-option(s) by a single Binding Update. Old bindings registered before rebooting may be left on HA and CNs. when a MN wants to de-register some bindings from HA. R flag is obsolete This may be useful for binding registration to CNs, but the bulk registration is not supported for binding registration to CN

7. Return Routability When MCoA extension is used for binding registration to CN, it MUST use BID to calculate its care-of keygen token. care-of keygen token := First (64, HMAC_SHA1 (Kcn, (care-of address | nonce | BID | 1))) This extension is useful for MN to verify whether CN supports MCoA or not.

8. Sequence Number Handling In the bulk registration, MN carefully pick a Seq # for its BU. Otherwise, HA may reply a BA with the sequence number out of window code. Single Sequence Number field for all the bindings in a single BU Sequence number is assigned per HoA. Thus, MN should share one value for BUs for all the available MCoA. (Adopted) MN HA Registered binding HoA:CoA1:Seq05 HoA:CoA2:Seq512 HoA:CoA3:Seq2054 BULK Binding Update Sequence number must be greater than 2054 Registered binding HoA:CoA1:Seq2055 HoA:CoA2:Seq2055 HoA:CoA3:Seq2055

9. Next Step Please send your comments on the list. We receive only few comments so far… If we have few issues left, go for WGLC? please continue to review!