draft-ietf-mext-nemo-pd-05.txt   draft-ietf-mext-nemo-pd-06.txt 
Mobility Extensions for IPv6 R. Droms Mobility Extensions for IPv6 R. Droms
(MEXT) P. Thubert (MEXT) P. Thubert
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track F. Dupont Intended status: Standards Track F. Dupont
Expires: December 30, 2010 ISC Expires: February 23, 2011 ISC
W. Haddad W. Haddad
Ericsson Ericsson
CJ. Bernardos CJ. Bernardos
UC3M UC3M
June 28, 2010 August 22, 2010
DHCPv6 Prefix Delegation for NEMO DHCPv6 Prefix Delegation for NEMO
draft-ietf-mext-nemo-pd-05 draft-ietf-mext-nemo-pd-06
Abstract Abstract
One aspect of network mobility support is the assignment of a prefix One aspect of network mobility support is the assignment of a prefix
or prefixes to a Mobile Router (MR) for use on the links in the NEMO. or prefixes to a Mobile Router (MR) for use on the links in the NEMO.
DHCPv6 prefix delegation can be used for this configuration task. DHCPv6 prefix delegation can be used for this configuration task.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on December 30, 2010. This Internet-Draft will expire on February 23, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 14 skipping to change at page 2, line 14
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. DHCPv6 Prefix Delegation of Mobile Network Prefixes . . . . . 4 3. DHCPv6 Prefix Delegation of Mobile Network Prefixes . . . . . 4
3.1. Exchanging DHCPv6 messages when MR is not at home . . . . 5 3.1. Exchanging DHCPv6 messages when the MR is not at home . . 5
3.1.1. Relay agent configuration . . . . . . . . . . . . . . 6 3.1.1. Relay agent configuration . . . . . . . . . . . . . . 6
3.1.2. Transmission of DHCPv6 messages . . . . . . . . . . . 7 3.1.2. Transmission of DHCPv6 messages . . . . . . . . . . . 7
3.1.3. Receipt of DHCPv6 messages . . . . . . . . . . . . . . 7 3.1.3. Receipt of DHCPv6 messages . . . . . . . . . . . . . . 7
3.2. Exchanging DHCPv6 messages when MR is at home . . . . . . 7 3.2. Exchanging DHCPv6 messages when MR is at home . . . . . . 7
3.3. Selecting an HA that provides DHCPv6PD . . . . . . . . . . 8 3.3. Selecting an HA that provides DHCPv6PD . . . . . . . . . . 8
3.4. Minimizing DHCPv6PD messages . . . . . . . . . . . . . . . 9 3.4. Minimizing DHCPv6PD messages . . . . . . . . . . . . . . . 9
3.5. Other DHCPv6 functions . . . . . . . . . . . . . . . . . . 9 3.5. Other DHCPv6 functions . . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Revision -00 . . . . . . . . . . . . . . . . . . . . . . . 11 7.1. Revision -00 . . . . . . . . . . . . . . . . . . . . . . . 11
7.2. Revision -01 . . . . . . . . . . . . . . . . . . . . . . . 11 7.2. Revision -01 . . . . . . . . . . . . . . . . . . . . . . . 11
7.3. Revision -02 . . . . . . . . . . . . . . . . . . . . . . . 11 7.3. Revision -02 . . . . . . . . . . . . . . . . . . . . . . . 11
7.4. Revision -04 . . . . . . . . . . . . . . . . . . . . . . . 12 7.4. Revision -04 . . . . . . . . . . . . . . . . . . . . . . . 12
7.5. Revision -05 . . . . . . . . . . . . . . . . . . . . . . . 12 7.5. Revision -05 . . . . . . . . . . . . . . . . . . . . . . . 12
7.6. Revision -06 . . . . . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . . 13 8.2. Informative References . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
One aspect of network mobility support is the assignment of a prefix One aspect of network mobility support is the assignment of a prefix
or prefixes to a Mobile Router for use on the links in the NEMO. or prefixes to a Mobile Router for use on the links in the NEMO.
DHCPv6 prefix delegation [RFC3633] (DHCPv6PD) can be used for this DHCPv6 prefix delegation [RFC3633] (DHCPv6PD) can be used for this
skipping to change at page 3, line 25 skipping to change at page 3, line 25
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [RFC2119]. document are to be interpreted as described in RFC2119 [RFC2119].
The following terms used in this document are defined in the IPv6 The following terms used in this document are defined in the IPv6
Addressing Architecture document [RFC4291]: Addressing Architecture document [RFC4291]:
Link-Local Unicast address Link-Local Unicast address
Link-Local Scope Multicast address Link-Local Scope Multicast address
The following terms used in this document are defined in the mobile The following terms used in this document are defined in the Mobile
IPv6 specification [I-D.ietf-mext-rfc3775bis]: IPv6 specification [I-D.ietf-mext-rfc3775bis]:
Home Agent (HA) Home Agent (HA)
Home Link Home Link
The following terms used in this document are defined in the Mobile The following terms used in this document are defined in the Mobile
Network terminology document [RFC4885]: Network terminology document [RFC4885]:
Mobile Router (MR) Mobile Router (MR)
skipping to change at page 4, line 9 skipping to change at page 4, line 9
Requesting Router (RR; acts as a DHCPv6 client) Requesting Router (RR; acts as a DHCPv6 client)
DHCPv6 Relay Agent (DRA) DHCPv6 Relay Agent (DRA)
The following acronym is used in this document: The following acronym is used in this document:
DHCPv6PD: DHCPv6 Prefix Delegation DHCPv6PD: DHCPv6 Prefix Delegation
3. DHCPv6 Prefix Delegation of Mobile Network Prefixes 3. DHCPv6 Prefix Delegation of Mobile Network Prefixes
The NEMO Basic protocol [RFC3963] extends the mobile IPv6 protocol The NEMO Basic Support protocol [RFC3963] extends the Mobile IPv6
[I-D.ietf-mext-rfc3775bis] to enable network mobility. In this protocol [I-D.ietf-mext-rfc3775bis] to enable network mobility. In
extension, an MR uses the mobile IPv6 protocol to establish and this extension, an MR uses the Mobile IPv6 protocol to establish and
maintain a session with its HA, and uses bidirectional tunneling maintain a session with its HA, and uses bidirectional tunneling
between the MR and HA to provide a path through which nodes attached between the MR and HA to provide a path through which nodes attached
to links in the NEMO can maintain connectivity with nodes not in the to links in the NEMO can maintain connectivity with nodes not in the
NEMO. NEMO.
The requirements for NEMO [RFC4885] include the ability of the MR to The requirements for NEMO [RFC4885] include the ability of the MR to
receive delegated prefixes that can then be assigned to links in the receive delegated prefixes that can then be assigned to links in the
NEMO. DHCPv6PD can be used to meet this requirement for prefix NEMO. DHCPv6PD can be used to meet this requirement for prefix
delegation. delegation.
skipping to change at page 4, line 33 skipping to change at page 4, line 33
MR assumes the role of the RR when located at home, and the role of a MR assumes the role of the RR when located at home, and the role of a
DRA co-located with the RR function, when the MR is away from home. DRA co-located with the RR function, when the MR is away from home.
When the MR is not at home, the HA and MR exchange DHCPv6PD protocol When the MR is not at home, the HA and MR exchange DHCPv6PD protocol
messages as specified in RFC3775bis. This means that messages sent messages as specified in RFC3775bis. This means that messages sent
by the MR include the Home Address destination option and messages by the MR include the Home Address destination option and messages
sent by the HA make use of a Routing Header type 2. See Figure 1 for sent by the HA make use of a Routing Header type 2. See Figure 1 for
the deployment topologies when the MR is at home and when it is the deployment topologies when the MR is at home and when it is
visiting a foreign network. visiting a foreign network.
---- ---- ------ ------
| MR |----------------| HA | | MR |----------------| HA |
|(RR)| (home network) |(DR)| |(RR)| (home network) |(DR)|
---- ---- ------ ------
----- /-----------\ ---- ------- /-----------\ ------
| MR |----| Internet |-----| HA | | MR |----| Internet |-----| HA |
|(RR) | \-----------/ |(DR)| |(RR) | \-----------/ |(DR)|
|(DRA)| ---- |(DRA)| ------
----- -------
(visited network) (visited network)
Figure 1: Deployment topologies of the use of DHCPv6PD for delegation Figure 1: Deployment topologies of the use of DHCPv6PD for delegation
of MNPs of MNPs
The DHCPv6PD server is provisioned with prefixes to be assigned using The DHCPv6PD server is provisioned with prefixes to be assigned using
any of the prefix assignment mechanisms described in the DHCPv6PD any of the prefix assignment mechanisms described in the DHCPv6PD
specifications. Other updates to the HA data structures required as specifications. Other updates to the HA data structures required as
a side effect of prefix delegation are specified by the particular a side effect of prefix delegation are specified by the particular
network mobility protocol. For example, in the case of Basic Network network mobility protocol. For example, in the case of Basic Network
Mobility Support [RFC3963], the HA would add an entry in its binding Mobility Support [RFC3963], the HA would add an entry in its binding
cache registering the delegated prefix to the MR to which the prefix cache registering the delegated prefix to the MR to which the prefix
was delegated. was delegated.
3.1. Exchanging DHCPv6 messages when MR is not at home 3.1. Exchanging DHCPv6 messages when the MR is not at home
The case when the MR is away from home is described in this section. The case when the MR is away from home is described in this section.
Section 3.2 describes the protocol operation for the case the MR is Section 3.2 describes the protocol operation for the case when the MR
attached to its home link. is attached to its home link.
The MR MUST register at the HA (i.e. by sending a Binding Update to The MR MUST register at the HA (i.e. by sending a Binding Update to
the HA) before initiating a DHCPv6 message exchange for prefix the HA) before initiating a DHCPv6 message exchange for prefix
delegation. Since the MR may not have yet requested any prefixes, delegation. Since the MR may not have yet requested any prefixes,
implicit BU signaling MUST be used. While using the NEMO Basic implicit BU signaling MUST be used. While using the NEMO Basic
Support protocol with DHCPv6PD, implicit BU signaling is the default Support protocol with DHCPv6PD, implicit BU signaling is the default
mode of operation. mode of operation.
If the MR does not have any active delegated prefixes (with unexpired If the MR does not have any active delegated prefixes (with unexpired
leases), the MR initiates a DHCPv6 message exchange with a DHCPv6 leases), the MR initiates a DHCPv6 message exchange with a DHCPv6
skipping to change at page 5, line 40 skipping to change at page 5, line 40
use as MNPs. The HA, upon reception of the implicit BU from the MR, use as MNPs. The HA, upon reception of the implicit BU from the MR,
selects (in case this was not pre-configured already) the prefixes selects (in case this was not pre-configured already) the prefixes
that would then be delegated to the MR via DHCPv6PD. The HA, once that would then be delegated to the MR via DHCPv6PD. The HA, once
the DHCPv6 signaling has been completed, adds an entry in its binding the DHCPv6 signaling has been completed, adds an entry in its binding
cache including the delegated prefixes. cache including the delegated prefixes.
In case the MR has one or more active delegated prefixes -- as for In case the MR has one or more active delegated prefixes -- as for
example if the MR reboots or the MNP(s) currently used by the is example if the MR reboots or the MNP(s) currently used by the is
about to expire -- the MR initiates a DHCPv6 message exchange with a about to expire -- the MR initiates a DHCPv6 message exchange with a
DHCPv6 Rebind message as described in section 18.1.2 of RFC 3315 and DHCPv6 Rebind message as described in section 18.1.2 of RFC 3315 and
section 12.1 of RFC 3633. In this case, only one BU signaling section 12.1 of RFC 3633.
sequence is required.
A DHPCv6 relay agent function [RFC3315] is used at the MR. This A DHPCv6 relay agent function [RFC3315] is used at the MR. This
relay agent function is co-located in the MR with the DHCPv6 client relay agent function is co-located in the MR with the DHCPv6 client
function (see Figure 2). The DHCPv6 signaling between the MR and the function (see Figure 2). The DHCPv6 signaling between the MR and the
HA are exchanged between the DHCPv6 relay agent in the MR and the HA are exchanged between the DHCPv6 relay agent in the MR and the
DHCPv6 server on the HA. DHCPv6 messages from the MR to the HA are DHCPv6 server on the HA. DHCPv6 messages from the MR to the HA are
unicast packets sent from the global unicast HoA of the MR to the unicast packets sent from the unicast HoA of the MR to the global
global unicast address of the HA, and therefore the Home Address unicast address of the HA, and therefore the Home Address destination
destination option is. DHCPv6 replies from the HA to the MR are sent option is used. DHCPv6 replies from the HA to the MR are sent using
using the Routing Header type 2, as specified in RFC3775bis. The the Routing Header type 2, as specified in RFC3775bis. The DHCPv6
DHCPv6 client in the MR hands any outbound DHCPv6 messages to the co- client in the MR hands any outbound DHCPv6 messages to the co-located
located relay agent. Responses from the DHCPv6 server are delivered relay agent. Responses from the DHCPv6 server are delivered to the
to the relay agent function in the MR, which extracts the relay agent function in the MR, which extracts the encapsulated
encapsulated message and delivers it to the DHCPv6 client in the MR. message and delivers it to the DHCPv6 client in the MR.
MR ----------------------------- --------
(RR) HA | MR | | HA |
(DRA) (DR) | (RR) (DRA) | | (DR) |
| Binding Update | ---------------------------- --------
|------------------------>| | | Binding Update |
| (HoA, CoA) | | |------------------------>|
| | | | (HoA, CoA) |
| Binding Ack | | | |
|<------------------------| | | Binding Ack |
-- | | | |<------------------------|
/ \ | | | | |
\ *| | | DHCPv6 Solicit | DHCPv6 Solicit |
DHCPv6 -- >| DHCPv6 Solicit | |..................>|--=====================->|
Solicit |--=====================->| | | |
| | | DHCPv6 Advertise | DHCPv6 Advertise |
| DHCPv6 Advertise | |<..................|<-=====================--|
-- |<-=====================--| | | |
/ \ | | | DHCPv6 Request | DHCPv6 Request |
\ *| DHCPv6 Request | |..................>|--=====================->|
DHCPv6 -- >|--=====================->| | | |
Request | | | DHCPv6 Reply | DHCPv6 Reply |
| DHCPv6 Reply | |<..................|<-=====================--|
|<-=====================--| | | (Mobile Network Prefix) |
| (Mobile Network Prefix) | | | |
| |
Figure 2: Signaling sequence when the MR is not at home Figure 2: Signaling sequence when the MR is not at home
Note that an MR using DHCPv6PD to obtain the set of prefixes to be Note that an MR using DHCPv6PD to obtain the set of prefixes to be
used as MNPs cannot derive its HoA from an MNP (as the MR does not used as MNPs cannot derive its HoA from an MNP (as the MR does not
know them before registering to the HA), unless it obtains the know them before registering to the HA). Therefore, the MR is
prefixes while at attached to the home link. Therefore, the MR is
assigned its HoA from the prefix on its Home Link. assigned its HoA from the prefix on its Home Link.
3.1.1. Relay agent configuration 3.1.1. Relay agent configuration
The use of the relay agent function in the MR allows the MR to The use of the relay agent function in the MR allows the MR to
unicast DHCPv6 messages to the DHCPv6 server. The relay agent MUST unicast DHCPv6 messages to the DHCPv6 server. The relay agent MUST
be configured with the address of the DHCPv6 server. For the be configured with the address of the DHCPv6 server. For the
purposes of NEMO, the relay agent assumes that the HA for the MR purposes of NEMO, the relay agent assumes that the HA for the MR
hosts the DHCPv6 server. Therefore, the MR MUST configure the DHCPv6 hosts the DHCPv6 server. Therefore, the MR MUST configure the DHCPv6
relay agent to forward DHCPv6 messages to the HA. relay agent to forward DHCPv6 messages to the HA.
skipping to change at page 7, line 19 skipping to change at page 7, line 19
message is passed to the DHCP relay agent is beyond the scope of this message is passed to the DHCP relay agent is beyond the scope of this
document. The relay agent encapsulates the message from the client document. The relay agent encapsulates the message from the client
according to RFC 3315 in a Relay-forward message and sends the according to RFC 3315 in a Relay-forward message and sends the
resulting DHCPv6 message to the HA. The relay agent sets the fields resulting DHCPv6 message to the HA. The relay agent sets the fields
in the Relay-forward message as follows: in the Relay-forward message as follows:
msg-type RELAY-FORW msg-type RELAY-FORW
hop-count 1 hop-count 1
link-address A non-link-local address from the MR egress interface link-address The home address of the MR
(e.g., home address) used to send packets between the
HA and the MR
peer-address A non-link-local address from the MR egress interface peer-address A non-link-local address from the MR egress interface
(e.g., home address) used to send packets between the (e.g., home address) used to send packets between the
HA and the MR HA and the MR
options MUST include a "Relay Message option" [RFC3315]; MAY options MUST include a "Relay Message option" [RFC3315]; MAY
include other options added by the relay agent. include other options added by the relay agent.
3.1.3. Receipt of DHCPv6 messages 3.1.3. Receipt of DHCPv6 messages
skipping to change at page 8, line 5 skipping to change at page 8, line 5
3.2. Exchanging DHCPv6 messages when MR is at home 3.2. Exchanging DHCPv6 messages when MR is at home
When the MR is on its home link, the HA uses the home link to When the MR is on its home link, the HA uses the home link to
exchange DHCPv6PD messages with the MR (Figure 3). In this case, the exchange DHCPv6PD messages with the MR (Figure 3). In this case, the
DHCPv6 co-located relay function is disabled. It is the DHCPv6 co-located relay function is disabled. It is the
responsibility of the implementation to determine when the MR is on responsibility of the implementation to determine when the MR is on
its home link. The Home Link Detection mechanism is described in the its home link. The Home Link Detection mechanism is described in the
section 11.5.2 of RFC3775bis. section 11.5.2 of RFC3775bis.
MR HA -------- --------
(RR) (DR) | MR | | HA |
| (RR) | | (DR) |
-------- --------
| | | |
| DHCPv6 Solicit | | DHCPv6 Solicit |
|------------------------>| |------------------------>|
| | | |
| DHCPv6 Advertise | | DHCPv6 Advertise |
|<------------------------| |<------------------------|
| | | |
| DHCPv6 Request | | DHCPv6 Request |
|------------------------>| |------------------------>|
| | | |
skipping to change at page 10, line 13 skipping to change at page 10, line 14
MUST be used to secure the DHCPv6 signaling. In the following, we MUST be used to secure the DHCPv6 signaling. In the following, we
describe the Security Policy Database (SPD) and Security Association describe the Security Policy Database (SPD) and Security Association
Database (SAD) entries necessary to protect the DHCPv6 signaling. We Database (SAD) entries necessary to protect the DHCPv6 signaling. We
use the same format than that used by of [RFC4877]. The SPD and SAD use the same format than that used by of [RFC4877]. The SPD and SAD
entries are only example configurations. A particular mobile router entries are only example configurations. A particular mobile router
implementation and a home agent implementation could configure implementation and a home agent implementation could configure
different SPD and SAD entries as long as they provide the required different SPD and SAD entries as long as they provide the required
security of the DHCPv6 signaling messages. security of the DHCPv6 signaling messages.
For the examples described in this document, a mobile router with For the examples described in this document, a mobile router with
home address, "home_address_1", and a home agent with address, home address "home_address_1", and a home agent with address
"home_agent_1" are assumed. If the home address of the mobile router "home_agent_1" are assumed. If the home address of the mobile router
changes, the SPD and SAD entries need to be re-created or updated for changes, the SPD and SAD entries need to be re-created or updated for
the new home address. the new home address.
mobile router SPD-S: mobile router SPD-S:
- IF local_address = home_address_1 & - IF local_address = home_address_1 &
remote_address = home_agent_1 & proto = UDP & remote_address = home_agent_1 & proto = UDP &
local_port = any & remote_port = DHCP local_port = any & remote_port = DHCP
Then use SA1 (OUT) and SA2 (IN) Then use SA1 (OUT) and SA2 (IN)
skipping to change at page 12, line 38 skipping to change at page 12, line 38
Security considerations include now the issue of the HA enforcing Security considerations include now the issue of the HA enforcing
that the MR registers the prefixes that were delegated to it via that the MR registers the prefixes that were delegated to it via
DHCPv6PD. DHCPv6PD.
Since RFC3775bis specifies that MR and HA operate in RO mode when Since RFC3775bis specifies that MR and HA operate in RO mode when
sending traffic between them, the term tunnel has been removed. sending traffic between them, the term tunnel has been removed.
Some typos detected and corrected. Some typos detected and corrected.
7.6. Revision -06
Some nits fixed.
8. References 8. References
8.1. Normative References 8.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.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
skipping to change at page 13, line 23 skipping to change at page 13, line 27
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[RFC4877] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with [RFC4877] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with
IKEv2 and the Revised IPsec Architecture", RFC 4877, IKEv2 and the Revised IPsec Architecture", RFC 4877,
April 2007. April 2007.
8.2. Informative References 8.2. Informative References
[I-D.ietf-mext-rfc3775bis] [I-D.ietf-mext-rfc3775bis]
Johnson, D., Perkins, C., and J. Arkko, "Mobility Support Perkins, C., Johnson, D., and J. Arkko, "Mobility Support
in IPv6", draft-ietf-mext-rfc3775bis-05 (work in in IPv6", draft-ietf-mext-rfc3775bis-06 (work in
progress), October 2009. progress), July 2010.
[RFC4885] Ernst, T. and H-Y. Lach, "Network Mobility Support [RFC4885] Ernst, T. and H-Y. Lach, "Network Mobility Support
Terminology", RFC 4885, July 2007. Terminology", RFC 4885, July 2007.
Authors' Addresses Authors' Addresses
Ralph Droms Ralph Droms
Cisco Cisco
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
 End of changes. 23 change blocks. 
64 lines changed or deleted 66 lines changed or added

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