draft-ietf-mip4-nemo-v4-base-09.txt   draft-ietf-mip4-nemo-v4-base-10.txt 
MIP4 K. Leung MIP4 K. Leung
Internet-Draft G. Dommety Internet-Draft G. Dommety
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: August 20, 2008 V. Narayanan Expires: August 21, 2008 V. Narayanan
Qualcomm, Inc. Qualcomm, Inc.
A. Petrescu A. Petrescu
Motorola Motorola
February 17, 2008 February 18, 2008
Network Mobility (NEMO) Extensions for Mobile IPv4 Network Mobility (NEMO) Extensions for Mobile IPv4
draft-ietf-mip4-nemo-v4-base-09.txt draft-ietf-mip4-nemo-v4-base-10.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 38 skipping to change at page 1, line 38
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 20, 2008. This Internet-Draft will expire on August 21, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes a protocol for supporting Mobile Networks This document describes a protocol for supporting Mobile Networks
between a Mobile Router and a Home Agent by extending the Mobile IPv4 between a Mobile Router and a Home Agent by extending the Mobile IPv4
protocol. A Mobile Router is responsible for the mobility of one or protocol. A Mobile Router is responsible for the mobility of one or
skipping to change at page 8, line 21 skipping to change at page 8, line 21
4. Mobile Network Extensions 4. Mobile Network Extensions
4.1. Representing a Subnet 4.1. Representing a Subnet
Since the protocol extensions presented in this document concentrate Since the protocol extensions presented in this document concentrate
on treatment of prefixes, subnets and network masks it is important on treatment of prefixes, subnets and network masks it is important
to choose an all-encompassing wire representation of subnets, as to choose an all-encompassing wire representation of subnets, as
generic as possible. generic as possible.
A subnet can easily be represented as address/prefix length, as in A subnet can easily be represented as address/prefix length, as in
192.168.1.1/24. This is interpreted as the subnet being the first 192.0.2.0/24. This is interpreted as the subnet being the first
leftmost 24 bits of the address 192.168.1.1, i.e. 192.168.1. This leftmost 24 bits of the address 192.0.2.0, i.e. 192.0.2. This
representation corresponds to an underlying forwarding system which representation corresponds to an underlying forwarding system which
uses longest-prefix match rules. It is typically in widespread uses longest-prefix match rules. It is typically in widespread
deployment in the Internet. deployment in the Internet.
In a Mobile Network Extension, this representation is expressed by In a Mobile Network Extension, this representation is expressed by
the tuple of Prefix and Prefix Length fields. the tuple of Prefix and Prefix Length fields.
On another hand, some forwarding systems don't use longest-prefix On another hand, some forwarding systems don't use longest-prefix
match rules. In these cases it is important to provide the more match rules. In these cases it is important to provide the more
generic way of representing subnets by using non-contiguous sets of generic way of representing subnets by using non-contiguous sets of
1bits as netmasks. For example, 255.255.0.255 is a perfectly legal 1bits as netmasks. For example, 255.255.0.255 is a perfectly legal
netmask which, when applied to an address like 192.168.1.1 gives the netmask which, when applied to an address like 192.0.2.1 gives the
network part 192.168.x.1, the third 'x' byte acting alone as the host network part 192.0.x.1, the third 'x' byte acting alone as the host
part. part.
In a Mobile Network Extension, this non-contiguous netmask In a Mobile Network Extension, this non-contiguous netmask
representation is expressed by the tuple of Prefix and Optional representation is expressed by the tuple of Prefix and Optional
Netmask fields (Prefix Length field being ignored). Netmask fields (Prefix Length field being ignored).
The two representation methods (address/prefix and address/netmask) The two representation methods (address/prefix and address/netmask)
are alternative and only one method of representation is used by a are alternative and only one method of representation is used by a
Mobile Network Extension. Mobile Network Extension.
skipping to change at page 9, line 37 skipping to change at page 9, line 37
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
Mobile Network Extension (skippable type range to be assigned Mobile Network Extension (skippable type range to be assigned
by IANA). by IANA).
Length: Length:
Decimal 6 or decimal 10, not any other. If the masking is Decimal 6 or decimal 10, not any other. If the masking is
expressed as Prefix/Prefix Length (e.g. 192.168.1.1/24), the expressed as Prefix/Prefix Length (e.g. 192.0.2.1/24), the
value of this Length field is decimal 6 and the Optional value of this Length field is decimal 6 and the Optional
Netmask field is absent. If the masking is expressed as Netmask field is absent. If the masking is expressed as
Prefix and Netmask (e.g. 192.168.1.1 255.255.0.255) then the Prefix and Netmask (e.g. 192.0.2.1 255.255.0.255) then the
value of this Length field is decimal 10, the Optional value of this Length field is decimal 10, the Optional
Netmask field is present and the value of the Prefix Length Netmask field is present and the value of the Prefix Length
field is set to all-zero by sender and ignored by receiver. field is set to all-zero by sender and ignored by receiver.
Sub-Type: Sub-Type:
TBA (Mobile Network Request) TBA (Mobile Network Request)
Prefix Length: Prefix Length:
skipping to change at page 11, line 35 skipping to change at page 11, line 35
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
TBA Mobile Network Extension (skippable type range to be TBA Mobile Network Extension (skippable type range to be
assigned by IANA). assigned by IANA).
Length: Length:
Decimal 8 or decimal 12, not any other. If the masking is Decimal 8 or decimal 12, not any other. If the masking is
expressed as Prefix/Prefix Length (e.g. 192.168.1.1/24), the expressed as Prefix/Prefix Length (e.g. 192.0.2.1/24), the
value of this Length field is decimal 8 and the Optional value of this Length field is decimal 8 and the Optional
Netmask field is absent. If the masking is expressed as Netmask field is absent. If the masking is expressed as
Prefix and Netmask (e.g. 192.168.1.1 255.255.0.255) then the Prefix and Netmask (e.g. 192.0.2.1 255.255.0.255) then the
value of this Length field is decimal 12, the Optional value of this Length field is decimal 12, the Optional
Netmask field is present and the value of the Prefix Length Netmask field is present and the value of the Prefix Length
field set to all-zero by sender and ignored by receiver. field set to all-zero by sender and ignored by receiver.
Sub-Type: Sub-Type:
TBA (Explicit Mode Acknowledgement) TBA (Explicit Mode Acknowledgement)
TBA (Implicit Mode Acknowledgement) TBA (Implicit Mode Acknowledgement)
skipping to change at page 25, line 49 skipping to change at page 26, line 5
[RFC2794] Calhoun, P. and C. Perkins, "Mobile IP Network Access [RFC2794] Calhoun, P. and C. Perkins, "Mobile IP Network Access
Identifier Extension for IPv4", RFC 2794, March 2000. Identifier Extension for IPv4", RFC 2794, March 2000.
[RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, [RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344,
August 2002. August 2002.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4885] Ernst, T. and H-Y. Lach, "Network Mobility Support
Terminology", RFC 4885, July 2007.
13.2. Informative References 13.2. Informative References
[I-D.ietf-mip4-nemov4-fa] [I-D.ietf-mip4-nemov4-fa]
Tsirtsis, G., Park, V., Narayanan, V., and K. Leung, "FA Tsirtsis, G., Park, V., Narayanan, V., and K. Leung, "FA
extensions to NEMOv4 Base", draft-ietf-mip4-nemov4-fa-01 extensions to NEMOv4 Base", draft-ietf-mip4-nemov4-fa-02
(work in progress), November 2007. (work in progress), November 2007.
[RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. [RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P.
Thubert, "Network Mobility (NEMO) Basic Support Protocol", Thubert, "Network Mobility (NEMO) Basic Support Protocol",
RFC 3963, January 2005. RFC 3963, January 2005.
[RFC4885] Ernst, T. and H-Y. Lach, "Network Mobility Support
Terminology", RFC 4885, July 2007.
Appendix A. ChangeLog Appendix A. ChangeLog
[RFC Editor: please remove this section prior to publication. (said [RFC Editor: please remove this section prior to publication. (said
IESG member Russ Housley on 6th of February 2008: "Please delete IESG member Russ Housley on 6th of February 2008: "Please delete
Appendix A before publication as an RFC.")] Appendix A before publication as an RFC.")]
The changes are listed in reverse chronological order, most recent The changes are listed in reverse chronological order, most recent
changes appearing at the top of the list. changes appearing at the top of the list.
From draft-ietf-mip4-nemo-v4-base-09.txt to
draft-ietf-mip4-nemo-v4-base-10.txt:
o Changed "192.168.1.1" notation to "192.0.2.0" documentation style
addresses, as suggested by idnits.
From draft-ietf-mip4-nemo-v4-base-08.txt to From draft-ietf-mip4-nemo-v4-base-08.txt to
draft-ietf-mip4-nemo-v4-base-09.txt, following IANA and IESG draft-ietf-mip4-nemo-v4-base-09.txt, following IANA and IESG
comments: comments:
o Introduced an Optional Netmask field in both registrations and o Introduced an Optional Netmask field in both registrations and
replies. This is used when address/prefixlength is not a replies. This is used when address/prefixlength is not a
sufficient expression of network mask, for example when the subnet sufficient expression of network mask, for example when the subnet
mask needs to be expressed as a non-contiguous set of 1bits (e.g. mask needs to be expressed as a non-contiguous set of 1bits (e.g.
255.255.0.255). Also described the reasoning of this in a section 255.255.0.255). Also described the reasoning of this in a section
of its own. of its own.
 End of changes. 14 change blocks. 
16 lines changed or deleted 22 lines changed or added

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