Mobile IPv6 Fast Handovers for 802.11 Networks
RFC 4260

Note: This ballot was opened for revision 04 and is now closed.

(Margaret Cullen) (was No Objection) Yes

(Thomas Narten) Yes

Comment (2005-01-25 for -)
No email
send info
>    otherwise be possible.  By tunneling data between the old and new 
>    access routers, it is possible to provide IP connectivity in advance 
>    of actual Mobile IP registration with the home agent or correspondent 
>    node.  This removes such Mobile IP registration, which may require 
>    time-consuming Internet round-trips, from the critical path before 
>    real-time service is re-established. 

Could be made more clear. Last sentence in particular is hard to
follow. (remember, orient this towards general reader).

>    The RtSolPr message is used to request information about the 
>    router(s) connected to one or more APs.  The APs are specified by 
>    link layer address in the RtSolPr and associated IP-layer information 
>    is returned in the PrRtAdv.  In the case of an 802.11 link, the link 
>    layer address is the BSSID of some AP. 

Might be good here (and elsewhere in this section) to be more clear
about which fields are used to carry the info. E.g.,

      The APs are specified in the New Access Point Link-Layer Address
      option [rfcxx ] in the RtSolPr ...

and in paragraph 2:

>     This list would supply the necessary BSSIDs to fill into the
>     RtSolPr messages.

Actually, what field is used for this?

>    from Section 4 and the lettered events are from Section 5.  For 
>    example, "1abcde234567fg" is the sequence where the MN performs a 

where do these gobbledigook "1abcde234567fg" strings come from and why
do you use them?

Oh, I see. Another sentence or two explanation would be good. E.g.,
add something like:

 For example, "1" denotes step 1, "abcde" denotes steps a-e), etc.

>    changing radio conditions may cause nAR to be suddenly unreachable.  


(Ted Hardie) No Objection

(Scott Hollenbeck) No Objection

(Russ Housley) (was Discuss) No Objection

Comment (2005-01-31)
No email
send info
  In section 6: s/IEEE 802.11k subgroup/IEEE 802.11k task group/

(David Kessens) No Objection

(Bert Wijnen) No Objection