draft-ietf-mip4-fmipv4-04.txt   draft-ietf-mip4-fmipv4-05.txt 
MIP4 Working Group Rajeev. Koodli MIP4 Working Group Rajeev Koodli
Internet-Draft Charles. Perkins Internet-Draft Charles Perkins
Intended status: Experimental Nokia Research Center Intended status: Experimental Nokia Research Center
Expires: August 27, 2007 February 23, 2007 Expires: September 1, 2007 February 28, 2007
Mobile IPv4 Fast Handovers Mobile IPv4 Fast Handovers
draft-ietf-mip4-fmipv4-04.txt draft-ietf-mip4-fmipv4-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 27, 2007. This Internet-Draft will expire on September 1, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document adapts the Mobile IPv6 Fast Handovers to improve delay This document adapts the Mobile IPv6 Fast Handovers to improve delay
and packet loss resulting from Mobile IPv4 handover operations. and packet loss resulting from Mobile IPv4 handover operations.
Specifically, this document addresses movement detection, IP address Specifically, this document addresses movement detection, IP address
skipping to change at page 2, line 31 skipping to change at page 2, line 31
6.5.2. Handover Acknowledge (HAck) . . . . . . . . . . . . . 17 6.5.2. Handover Acknowledge (HAck) . . . . . . . . . . . . . 17
7. Option Formats . . . . . . . . . . . . . . . . . . . . . . . . 19 7. Option Formats . . . . . . . . . . . . . . . . . . . . . . . . 19
7.1. Link-Layer Address Option Format . . . . . . . . . . . . . 19 7.1. Link-Layer Address Option Format . . . . . . . . . . . . . 19
7.2. New IPv4 Address Option Format . . . . . . . . . . . . . . 20 7.2. New IPv4 Address Option Format . . . . . . . . . . . . . . 20
7.3. New Router Prefix Information Option . . . . . . . . . . . 21 7.3. New Router Prefix Information Option . . . . . . . . . . . 21
8. Security Considerations . . . . . . . . . . . . . . . . . . . 22 8. Security Considerations . . . . . . . . . . . . . . . . . . . 22
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 23 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 23
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
11.1. Normative References . . . . . . . . . . . . . . . . . . . 23 11.1. Normative References . . . . . . . . . . . . . . . . . . . 23
11.2. Informative References . . . . . . . . . . . . . . . . . . 23 11.2. Informative References . . . . . . . . . . . . . . . . . . 24
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 24 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 26 Intellectual Property and Copyright Statements . . . . . . . . . . 26
1. Introduction 1. Introduction
This document adapts the fast handover specification [rfc4068] to This document adapts the fast handover specification [rfc4068] to
IPv4 networks. The fast handover protocol specified in this document IPv4 networks. The fast handover protocol specified in this document
is particularly interesting for operation over links such as IEEE 802 is particularly interesting for operation over links such as IEEE 802
wireless links. Fast handovers are not typically needed for wired wireless links. Fast handovers are not typically needed for wired
media due to the relatively large delays attributable to establishing media due to the relatively large delays attributable to establishing
new connections in today's wired networks. Mobile IPv4 [rfc3344] new connections in today's wired networks. Mobile IPv4 [rfc3344]
skipping to change at page 20, line 27 skipping to change at page 20, line 27
7: No fast handovers support available for the access point 7: No fast handovers support available for the access point
identified by the LLA identified by the LLA
Length: The length of the option (including the Type, Length Length: The length of the option (including the Type, Length
and Option-Code fields) in units of 8 octets. and Option-Code fields) in units of 8 octets.
Link-Layer Address: The variable length link-layer address. Link-Layer Address: The variable length link-layer address.
The content and format of this field (including byte and bit The content and format of this field (including byte and bit
ordering) depends on the specific link-layer in use. ordering) depends on the specific link-layer in use.
Depending on the size of the individual LLA option, appropriate There is no length field for the LLA itself. Implementations must
padding MUST be used to ensure that the entire option size is a determine the length of the LLA based on the specific link technology
multiple of 8 octets. where the protocol is run. The total size of the LLA option itself
must be a multiple of 8 octets. Hence, padding may be necessary
depending on the size of the LLA used. In such a case, the padN
option [rfc2460] MUST be used. As an example, when the LLA is 6
bytes (meaning 7 bytes of padding is necessary to bring the LLA
option length to 2), the padN option will have a length field of 5
and 5 bytes of zero-valued octets (see [rfc2460]).
7.2. New IPv4 Address Option Format 7.2. New IPv4 Address Option Format
This option is used to provide the new router's IPv4 address or the This option is used to provide the new router's IPv4 address or the
NCoA in PrRtAdv, as well as PCoA and NCoA in HI and HAck messages. NCoA in PrRtAdv, as well as PCoA and NCoA in HI and HAck messages.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Option-Code | Reserved | | Type | Length | Option-Code | Reserved |
skipping to change at page 23, line 32 skipping to change at page 23, line 36
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[rfc1256] Deering, S., "ICMP Router Discovery Messages", RFC 1256, [rfc1256] Deering, S., "ICMP Router Discovery Messages", RFC 1256,
September 1991. September 1991.
[rfc2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
[rfc3344] Perkins (Editor), C., "IP Mobility Support for IPv4", [rfc3344] Perkins (Editor), C., "IP Mobility Support for IPv4",
RFC 3344, August 2002. RFC 3344, August 2002.
[rfc4065] Kempf, J., "Instructions for Seamoby and Experimental [rfc4065] Kempf, J., "Instructions for Seamoby and Experimental
Mobility Protocol IANA Allocations", RFC 4065, July 2005. Mobility Protocol IANA Allocations", RFC 4065, July 2005.
[rfc4068] Koodli (Editor), R., "Fast Handovers for Mobile IPv6", [rfc4068] Koodli (Editor), R., "Fast Handovers for Mobile IPv6",
RFC 4068, July 2005. RFC 4068, July 2005.
11.2. Informative References 11.2. Informative References
 End of changes. 8 change blocks. 
10 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/