Skip to main content

Mobile IPv6 Fast Handovers for 802.11 Networks
RFC 4260

Revision differences

Document history

Date Rev. By Action
2015-10-14
04 (System) Notify list changed from gab@sun.com, mccap@lucent.com to gab@sun.com
2012-08-22
04 (System) post-migration administrative database adjustment to the No Objection position for Russ Housley
2006-01-10
04 Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2006-01-10
04 Amy Vezza [Note]: 'RFC 4260' added by Amy Vezza
2005-11-22
04 (System) RFC published
2005-05-16
04 Amy Vezza State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza
2005-05-13
04 Amy Vezza IESG state changed to Approved-announcement sent
2005-05-13
04 Amy Vezza IESG has approved the document
2005-05-13
04 Amy Vezza Closed "Approve" ballot
2005-05-13
04 Margaret Cullen State Changes to Approved-announcement to be sent from IESG Evaluation::AD Followup by Margaret Wasserman
2005-05-13
04 Margaret Cullen [Ballot Position Update] Position for Margaret Wasserman has been changed to Yes from No Objection by Margaret Wasserman
2005-04-14
04 Russ Housley [Ballot Position Update] Position for Russ Housley has been changed to No Objection from Discuss by Russ Housley
2005-04-14
04 (System) Sub state has been changed to AD Follow up from New Id Needed
2005-04-14
04 (System) New version available: draft-ietf-mipshop-80211fh-04.txt
2005-03-11
04 Mark Townsley Shepherding AD has been changed to Margaret Wasserman from Thomas Narten
2005-02-04
04 (System) Removed from agenda for telechat - 2005-02-03
2005-02-03
04 Amy Vezza State Changes to IESG Evaluation::Revised ID Needed from IESG Evaluation by Amy Vezza
2005-02-03
04 Michelle Cotton IANA Comments:
We understand this document to have NO IANA Actions.
2005-02-03
04 Bert Wijnen [Ballot Position Update] New position, No Objection, has been recorded for Bert Wijnen by Bert Wijnen
2005-02-03
04 Margaret Cullen [Ballot Position Update] New position, No Objection, has been recorded for Margaret Wasserman by Margaret Wasserman
2005-02-02
04 David Kessens [Ballot Position Update] New position, No Objection, has been recorded for David Kessens by David Kessens
2005-01-31
04 Ted Hardie [Ballot Position Update] New position, No Objection, has been recorded for Ted Hardie by Ted Hardie
2005-01-31
04 Russ Housley
[Ballot discuss]
In my view, deployment of IAPP could be harmful.  I strongly
  encourage the removal of all references to IAPP.  Task Group r …
[Ballot discuss]
In my view, deployment of IAPP could be harmful.  I strongly
  encourage the removal of all references to IAPP.  Task Group r
  (which is working on 802.11r) is working on better layer 2 support
  for fast roaming.  Further, IAPP is not really needed to make the
  central points.  I suggest the following changes:

    (a) Remove the discussion of IAPP in section 2.

    (b) In section 4, remove step 6.  Likewise, please delete the
        reference to "step 6" elsewhere.  I found two references in
        the security considerations.

    (c) Remove reference [8].

  In section 4, the document says:
  >
  > Note that in some existing 802.11 implementations, steps 1-4 are
  > performed by firmware in rapid succession (note that even in these
  > implementations step 3 is sometimes performed in a host driver,
  > especially for newer WPA implementations). ...
  >
  Earlier, there is a discussion of 802.11i.  Here, WPA is discussed.
  The relationship of the two is going to be lost on most readers.  I
  think it is best to refer to IEEE 802 standards, and avoid the WiFi
  Alliance marketing terms.
2005-01-31
04 Russ Housley
[Ballot discuss]
In my view, deployment of IAPP could be harmful.  I strongly
  encourage the removal of all references to IAPP.  Task Group r …
[Ballot discuss]
In my view, deployment of IAPP could be harmful.  I strongly
  encourage the removal of all references to IAPP.  Task Group r
  (which is working on 802.11r) is working on better layer 2 support
  for fast roaming.  Further, IAPP is not really needed to make the
  central points.  I suggest the following changes:

    (a) Remove the discussion of IAPP in section 2.

    (b) In section 4, remove step 6.  Likewise, please delete the
        reference to "step 6" elsewhere.  I found two references in
        the security considerations.

    (c) Remove reference [8].

  In section 4, the document says:
  >
  > Note that in some existing 802.11 implementations, steps 1-4 are
  > performed by firmware in rapid succession (note that even in these
  > implementations step 3 is sometimes performed in a host driver,
  > especially for newer WPA implementations). ...
  >
  Earlier, there is a discussion of 802.11i.  Here, WAP is discussed.
  The relationship of the two is going to be lost on most readers.  I
  think it is best to refer to IEEE 802 standards, and avoid the WiFi
  Alliance marketing terms.
2005-01-31
04 Russ Housley [Ballot comment]
In section 6: s/IEEE 802.11k subgroup/IEEE 802.11k task group/
2005-01-31
04 Russ Housley [Ballot Position Update] New position, Discuss, has been recorded for Russ Housley by Russ Housley
2005-01-26
04 Scott Hollenbeck [Ballot Position Update] New position, No Objection, has been recorded for Scott Hollenbeck by Scott Hollenbeck
2005-01-25
04 Thomas Narten
[Ballot comment]
>    otherwise be possible.  By tunneling data between the old and new
>    access routers, it is possible to provide IP …
[Ballot comment]
>    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. 

s/nAR/NAR/?
2005-01-25
04 Thomas Narten Placed on agenda for telechat - 2005-02-03 by Thomas Narten
2005-01-25
04 Thomas Narten [Ballot Position Update] New position, Yes, has been recorded for Thomas Narten
2005-01-25
04 Thomas Narten Ballot has been issued by Thomas Narten
2005-01-25
04 Thomas Narten Created "Approve" ballot
2005-01-25
04 (System) Ballot writeup text was added
2005-01-25
04 (System) Last call text was added
2005-01-25
04 (System) Ballot approval text was added
2005-01-25
04 Thomas Narten State Changes to IESG Evaluation from AD Evaluation by Thomas Narten
2005-01-25
04 Thomas Narten State Changes to AD Evaluation from Publication Requested by Thomas Narten
2005-01-25
04 Thomas Narten State Change Notice email list have been change to gab@sun.com, mccap@lucent.com from gab@sun.com, gab@sun.com
2004-11-04
04 Dinara Suleymanova Draft Added by Dinara Suleymanova in state Publication Requested
2004-10-26
03 (System) New version available: draft-ietf-mipshop-80211fh-03.txt
2004-10-08
02 (System) New version available: draft-ietf-mipshop-80211fh-02.txt
2004-07-15
01 (System) New version available: draft-ietf-mipshop-80211fh-01.txt
2004-02-10
00 (System) New version available: draft-ietf-mipshop-80211fh-00.txt