draft-ietf-ipv6-over-ppp-v2-02.txt   draft-ietf-ipv6-over-ppp-v2-03.txt 
Internet Draft S.Varada (Transwitch) IPv6 Working Group S.Varada (Editor)
Document: draft-ietf-ipv6-over-ppp-v2-02.txt D.Haskins Internet-Draft Transwitch
Expires: December 2005 Ed Allen Obsoletes: RFC 2472 (if approved) D.Haskins
Category: Standards track Ed Allen
IP Version 6 over PPP IP Version 6 over PPP
<draft-ietf-ipv6-over-ppp-v2-02.txt> <draft-ietf-ipv6-over-ppp-v2-03.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any 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 aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 36 skipping to change at page 1, line 37
progress." 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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The IETF Trust (2007).
Abstract Abstract
The Point-to-Point Protocol (PPP) provides a standard method of The Point-to-Point Protocol (PPP) provides a standard method of
encapsulating Network Layer protocol information over encapsulating Network Layer protocol information over
point-to-point links. PPP also defines an extensible Link Control point-to-point links. PPP also defines an extensible Link Control
Protocol, and proposes a family of Network Control Protocols Protocol, and proposes a family of Network Control Protocols
(NCPs) for establishing and configuring different network-layer (NCPs) for establishing and configuring different network-layer
protocols. protocols.
skipping to change at page 2, line 5 skipping to change at page 2, line 4
The Point-to-Point Protocol (PPP) provides a standard method of The Point-to-Point Protocol (PPP) provides a standard method of
encapsulating Network Layer protocol information over encapsulating Network Layer protocol information over
point-to-point links. PPP also defines an extensible Link Control point-to-point links. PPP also defines an extensible Link Control
Protocol, and proposes a family of Network Control Protocols Protocol, and proposes a family of Network Control Protocols
(NCPs) for establishing and configuring different network-layer (NCPs) for establishing and configuring different network-layer
protocols. protocols.
This document defines the method for sending IPv6 packets over PPP This document defines the method for sending IPv6 packets over PPP
links, the NCP for establishing and configuring the IPv6 over PPP links, the NCP for establishing and configuring the IPv6 over PPP
and the method for forming IPv6 link-local addresses on PPP links. and the method for forming IPv6 link-local addresses on PPP links.
It also specifies the conditions for performing Duplicate Address It also specifies the conditions for performing Duplicate Address
Detection on IPv6 global unicast addresses configured for PPP Detection on IPv6 global unicast addresses configured for PPP
links either through stateful or stateless address links either through stateful or stateless address
autoconfiguration. autoconfiguration.
This document is an update to RFC 2472 and, hence, obsoletes it. This document obsoletes RFC 2472.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
1.1 Specification of Requirements..............................3 1.1 Specification of Requirements..............................3
2. Sending IPv6 Datagrams.........................................3 2. Sending IPv6 Datagrams.........................................3
3. A PPP Network Control Protocol for IPv6........................3 3. A PPP Network Control Protocol for IPv6........................3
4. IPV6CP Configuration Options...................................4 4. IPV6CP Configuration Options...................................4
4.1 Interface-Identifier.......................................5 4.1 Interface-Identifier.......................................5
4.2 IPv6-Compression-Protocol.................................10 5. Stateless Autoconfiguration and Link-Local Addresses..........10
5. Stateless Autoconfiguration and Link-Local Addresses..........11 6. Security Considerations.......................................11
6. Security Considerations.......................................12 7. IANA Considerations...........................................12
7. Acknowledgments...............................................12 8. Acknowledgments...............................................12
8. References....................................................13 9. References....................................................12
8.1 Normative References......................................13 9.1 Normative References......................................12
8.2 Informative references....................................13 9.2 Informative references....................................13
Appendix A: Global Scope Addresses..............................14 Appendix A: Global Scope Addresses..............................13
Appendix B: Changes from RFC-2472...............................14 Appendix B: Changes from RFC-2472...............................14
Authors' Addresses...............................................14 Authors' Addresses...............................................14
IPR Disclosure...................................................14 IPR Notice .....................................................14
IPR Notice .....................................................15
Copyright Notice and Disclaimer..................................15 Copyright Notice and Disclaimer..................................15
1. Introduction 1. Introduction
PPP has three main components: PPP has three main components:
1) A method for encapsulating datagrams over serial links. 1) A method for encapsulating datagrams over serial links.
2) A Link Control Protocol (LCP) for establishing, configuring, 2) A Link Control Protocol (LCP) for establishing, configuring,
and testing the data-link connection. and testing the data-link connection.
skipping to change at page 3, line 15 skipping to change at page 3, line 13
from each network-layer protocol can be sent over the link. from each network-layer protocol can be sent over the link.
In this document, the NCP for establishing and configuring the In this document, the NCP for establishing and configuring the
IPv6 over PPP is referred as the IPv6 Control Protocol (IPV6CP). IPv6 over PPP is referred as the IPv6 Control Protocol (IPV6CP).
The link will remain configured for communications until The link will remain configured for communications until
explicit LCP or NCP packets close the link down, or until some explicit LCP or NCP packets close the link down, or until some
external event occurs (power failure at the other end, carrier external event occurs (power failure at the other end, carrier
drop, etc.). drop, etc.).
This document obsoletes the earlier specification from RFC 2472
[8]. Changes from RFC 2472 are listed in Appendix B.
1.1 Specification of Requirements 1.1 Specification of Requirements
In this document, several words are used to signify the In this document, several words are used to signify the
requirements of the specification. requirements of the specification.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described "OPTIONAL" in this document are to be interpreted as described
in [7]. in [7].
skipping to change at page 4, line 45 skipping to change at page 4, line 48
IPV6CP Configuration Options allow negotiation of desirable IPv6 IPV6CP Configuration Options allow negotiation of desirable IPv6
parameters. IPV6CP uses the same Configuration Option format parameters. IPV6CP uses the same Configuration Option format
defined for LCP [1] but with a separate set of Options. If a defined for LCP [1] but with a separate set of Options. If a
Configuration Option is not included in a Configure-Request Configuration Option is not included in a Configure-Request
packet, the default value for that Configuration Option is packet, the default value for that Configuration Option is
assumed. assumed.
Up-to-date values of the IPV6CP Option Type field are specified Up-to-date values of the IPV6CP Option Type field are specified
in the on-line database of "Assigned Numbers" maintained at in the on-line database of "Assigned Numbers" maintained at
IANA [4]. Current values are assigned as follows: IANA [4]. Current value is assigned as follows:
1 Interface-Identifier 1 Interface-Identifier
2 IPv6-Compression-Protocol
The only IPV6CP options defined in this document are Interface The only IPV6CP option defined in this document is the Interface
Identifier and IPv6-Compression-Protocol. Any other IPV6CP Identifier. Any other IPV6CP configuration options that can be
configuration options that can be defined over time are to be defined over time are to be defined in separate documents.
defined in separate documents.
4.1 Interface-Identifier 4.1 Interface-Identifier
Description Description
This Configuration Option provides a way to negotiate an unique This Configuration Option provides a way to negotiate an unique
64-bit interface identifier to be used for the address 64-bit interface identifier to be used for the address
autoconfiguration [3] at the local end of the link (see autoconfiguration [3] at the local end of the link (see
section 5). A Configure-Request MUST contain exactly one section 5). A Configure-Request MUST contain exactly one
instance of the Interface-Identifier option [1]. The interface instance of the Interface-Identifier option [1]. The interface
identifier MUST be unique within the PPP link; i.e. upon identifier MUST be unique within the PPP link; i.e. upon
completion of the negotiation different Interface-Identifier completion of the negotiation different Interface-Identifier
values are to be selected for the ends of the PPP link. The values are to be selected for the ends of the PPP link. The
interface identifier MAY also be unique over a broader scope. interface identifier may also be unique over a broader scope.
Before this Configuration Option is requested, an implementation Before this Configuration Option is requested, an implementation
chooses its tentative Interface-Identifier. The non-zero value of chooses its tentative Interface-Identifier. The non-zero value of
the tentative Interface-Identifier SHOULD be chosen such that the the tentative Interface-Identifier SHOULD be chosen such that the
value is unique to the link and, preferably, consistently value is unique to the link and, preferably, consistently
reproducible across initializations of the IPV6CP finite state reproducible across initializations of the IPV6CP finite state
machine (administrative Close and reOpen, reboots, etc). The machine (administrative Close and reOpen, reboots, etc). The
rationale for preferring a consistently reproducible unique rationale for preferring a consistently reproducible unique
interface identifier to a completely random interface identifier interface identifier to a completely random interface identifier
is to provide stability to global scope addresses (see Appendix A) is to provide stability to global scope addresses (see Appendix A)
skipping to change at page 5, line 48 skipping to change at page 5, line 49
The following are methods for choosing the tentative Interface The following are methods for choosing the tentative Interface
Identifier in the preference order: Identifier in the preference order:
1)If an IEEE global identifier (EUI-48 or EUI-64) is 1)If an IEEE global identifier (EUI-48 or EUI-64) is
available anywhere on the node, it should be used to available anywhere on the node, it should be used to
construct the tentative Interface-Identifier due to its construct the tentative Interface-Identifier due to its
uniqueness properties. When extracting an IEEE global uniqueness properties. When extracting an IEEE global
identifier from another device on the node, care should be identifier from another device on the node, care should be
taken that the extracted identifier is presented in taken that the extracted identifier is presented in
canonical ordering [8]. canonical ordering [14].
The only transformation from an EUI-64 identifier is to invert The only transformation from an EUI-64 identifier is to invert
the "u" bit (universal/local bit in IEEE EUI-64 terminology). the "u" bit (universal/local bit in IEEE EUI-64 terminology).
For example, for a globally unique EUI-64 identifier of the For example, for a globally unique EUI-64 identifier of the
form: form:
most-significant least significant most-significant least significant
bit bit bit bit
|0 1|1 3|3 4|4 6| |0 1|1 3|3 4|4 6|
|0 5|6 1|2 7|8 3| |0 5|6 1|2 7|8 3|
+----------------+----------------+----------------+----------------+ +----------------+----------------+----------------+----------------+
|cccccc0gcccccccc|cccccccceeeeeeee|eeeeeeeeeeeeeeee|eeeeeeeeeeeeeeee| |cccccc0gcccccccc|cccccccceeeeeeee|eeeeeeeeeeeeeeee|eeeeeeeeeeeeeeee|
skipping to change at page 7, line 51 skipping to change at page 8, line 4
following ways: following ways:
If the two Interface-Identifiers are different but the received If the two Interface-Identifiers are different but the received
Interface-Identifier is zero, a Configure-Nak is sent with a Interface-Identifier is zero, a Configure-Nak is sent with a
non-zero Interface-Identifier value suggested for use by the non-zero Interface-Identifier value suggested for use by the
remote peer. Such a suggested Interface-Identifier MUST be remote peer. Such a suggested Interface-Identifier MUST be
different from the Interface-Identifier of the last different from the Interface-Identifier of the last
Configure-Request sent to the peer. It is recommended that the Configure-Request sent to the peer. It is recommended that the
value suggested be consistently reproducible across value suggested be consistently reproducible across
initializations of the IPV6CP finite state machine (administrative initializations of the IPV6CP finite state machine (administrative
Close and reOpen, reboots, etc). The "u" universal/local) bit of Close and reOpen, reboots, etc). The "u" (universal/local) bit of
the suggested identifier MUST be set to zero (0) regardless of its the suggested identifier MUST be set to zero (0) regardless of its
source unless the globally unique EUI-48/EUI-64 derived source unless the globally unique EUI-48/EUI-64 derived
identifier is provided for the exclusive use by the remote peer. identifier is provided for the exclusive use by the remote peer.
If the two Interface-Identifiers are different and the received If the two Interface-Identifiers are different and the received
Interface-Identifier is not zero, the Interface-Identifier MUST be Interface-Identifier is not zero, the Interface-Identifier MUST be
acknowledged, i.e. a Configure-Ack is sent with the requested acknowledged, i.e. a Configure-Ack is sent with the requested
Interface-Identifier, meaning that the responding peer agrees with Interface-Identifier, meaning that the responding peer agrees with
the Interface-Identifier requested. the Interface-Identifier requested.
If the two Interface-Identifiers are equal and are not zero, If the two Interface-Identifiers are equal and are not zero,
Configure-Nak MUST be sent specifying a different non-zero Configure-Nak MUST be sent specifying a different non-zero
Interface-Identifier value suggested for use by the remote peer. Interface-Identifier value suggested for use by the remote peer.
It is recommended that the value suggested be consistently It is recommended that the value suggested be consistently
reproducible across initializations of the IPV6CP finite state reproducible across initializations of the IPV6CP finite state
machine (administrative Close and reOpen, reboots, etc). The "u" machine (administrative Close and reOpen, reboots, etc). The "u"
universal/local) bit of the suggested identifier MUST be set to (universal/local) bit of the suggested identifier MUST be set to
zero (0) regardless of its source unless the globally unique zero (0) regardless of its source unless the globally unique
EUI-48/EUI-64 derived identifier is provided for the exclusive use EUI-48/EUI-64 derived identifier is provided for the exclusive use
by the remote peer. by the remote peer.
If the two Interface-Identifiers are equal to zero, the Interface If the two Interface-Identifiers are equal to zero, the Interface
Identifiers negotiation MUST be terminated by transmitting the Identifiers negotiation MUST be terminated by transmitting the
Configure-Reject with the Interface-Identifier value set to zero. Configure-Reject with the Interface-Identifier value set to zero.
In this case a unique Interface-Identifier can not be negotiated. In this case a unique Interface-Identifier can not be negotiated.
If a Configure-Request is received with the Interface-Identifier If a Configure-Request is received with the Interface-Identifier
Configuration Option and the receiving peer does not implement Configuration Option and the receiving peer does not implement
this option, Configure-Rej is sent. this option, Configure-Rej is sent.
A new Configure-Request SHOULD NOT be sent to the peer until A new Configure-Request SHOULD NOT be sent to the peer until
normal processing would cause it to be sent (that is, until a normal processing would cause it to be sent (that is, until a
Configure-Nak is received or the Restart timer runs out). Configure-Nak is received or the Restart timer runs out [1]).
A new Configure-Request MUST NOT contain the Interface-Identifier A new Configure-Request MUST NOT contain the Interface-Identifier
option if a valid Interface-Identifier Configure-Reject is option if a valid Interface-Identifier Configure-Reject is
received. received.
Reception of a Configure-Nak with a suggested Interface-Identifier Reception of a Configure-Nak with a suggested Interface-Identifier
different from that of the last Configure-Nak sent to the peer different from that of the last Configure-Nak sent to the peer
indicates an unique Interface-Identifier. In this case a new indicates an unique Interface-Identifier. In this case a new
Configure-Request MUST be sent with the identifier value suggested Configure-Request MUST be sent with the identifier value suggested
in the last Configure-Nak from the peer. But if the received in the last Configure-Nak from the peer. But if the received
skipping to change at page 9, line 42 skipping to change at page 9, line 44
Interface-Identifier (LS Bytes) | Interface-Identifier (LS Bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
1 1
Length Length
10 10
Interface-Identifier Interface-Identifier
The 64-bit Interface-Identifier which is very likely to be The 64-bit Interface-Identifier, which is very likely to be
unique on the link or zero if a good source of uniqueness unique on the link, or zero if a good source of uniqueness
can not be found. can not be found.
Default Default
If no valid interface identifier can be successfully If no valid interface identifier can be successfully
negotiated, no default Interface-Identifier value should be negotiated, no default Interface-Identifier value should be
assumed. The procedures for recovering from such a case are assumed. The procedures for recovering from such a case are
unspecified. One approach is to manually configure the unspecified. One approach is to manually configure the
interface identifier of the interface. interface identifier of the interface.
4.2 IPv6-Compression-Protocol
Description
This Configuration Option provides a way to negotiate the use of a
specific IPv6 packet compression protocol. The
IPv6-Compression-Protocol Configuration Option is used to indicate
the ability to receive compressed packets. Each end of the link
must separately request this option if bi-directional compression
is desired. By default, compression is not enabled.
IPv6 compression negotiated with this option is specific to IPv6
datagrams and is not to be confused with compression resulting
from negotiations via Compression Control Protocol (CCP), which
potentially effect all datagrams.
A summary of the IPv6-Compression-Protocol Configuration Option
format is shown below. The fields are transmitted from left to
right.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | IPv6-Compression-Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data ...
+-+-+-+-+
Type
2
Length
>= 4
IPv6-Compression-Protocol
The IPv6-Compression-Protocol field is two octets and indicates
the compression protocol desired. Values for this field are
always the same as the PPP Data Link Layer Protocol field
values for that same compression protocol.
No IPv6-Compression-Protocol field values are currently
assigned. Specific assignments will be made in documents that
define specific compression algorithms.
Data
The Data field is zero or more octets and contains additional
data as determined by the particular compression protocol.
Default
No IPv6 compression protocol enabled.
5. Stateless Autoconfiguration and Link-Local Addresses 5. Stateless Autoconfiguration and Link-Local Addresses
The Interface Identifier of IPv6 unicast addresses [6] of a PPP The Interface-Identifier of IPv6 unicast addresses [6] of a PPP
interface, SHOULD be negotiated in the IPV6CP phase of the PPP interface, SHOULD be negotiated in the IPV6CP phase of the PPP
connection setup (see section 4.1). If no valid Interface connection setup (see section 4.1). If no valid Interface
Identifier has been successfully negotiated, procedures for Identifier has been successfully negotiated, procedures for
recovering from such a case are unspecified. One approach is to recovering from such a case are unspecified. One approach is to
manually configure the Interface-Identifier of the interface. manually configure the Interface-Identifier of the interface.
The negotiated Interface-Identifier is used by the local end of The negotiated Interface-Identifier is used by the local end of
the PPP link to autoconfigure IPv6 link-local unicast address for the PPP link to autoconfigure IPv6 link-local unicast address for
the PPP interface. However, it SHOULD NOT be assumed that the the PPP interface. However, it SHOULD NOT be assumed that the
same Interface-Identifier is used in configuring global unicast same Interface-Identifier is used in configuring global unicast
addresses for the PPP interface using IPv6 stateless address addresses for the PPP interface using IPv6 stateless address
autoconfiguration [3]. The PPP peer MAY generate one or more autoconfiguration [3]. The PPP peer MAY generate one or more
Interface Identifiers, for instance, using a method described in Interface Identifiers, for instance, using a method described in
[9], to autoconfigure one or more global unicast addresses. [9], to autoconfigure one or more global unicast addresses.
As long as the Interface-Identifier is negotiated in the IPV6CP As long as the Interface-Identifier is negotiated in the IPV6CP
phase of the PPP connection setup, it is redundant to perform phase of the PPP connection setup, it is redundant to perform
duplicate address detection (DAD) as a part of the IPv6 Stateless duplicate address detection (DAD) as a part of the IPv6 Stateless
Address Autoconfiguration protocol [3] on the IPv6 link-local Address Autoconfiguration protocol [3] on the IPv6 link-local
address generated by the PPP peer. It MAY also be redundant to address generated by the PPP peer. It may also be redundant to
perform DAD on any global unicast addresses configured (using an perform DAD on any global unicast addresses configured (using an
Interface-Identifier that is either negotiated during IPV6CP or Interface-Identifier that is either negotiated during IPV6CP or
generated, for instance, as per [9]) for the interface as part of generated, for instance, as per [9]) for the interface as part of
the IPv6 Stateless Address Autoconfiguration protocol [3] provided the IPv6 Stateless Address Autoconfiguration protocol [3] provided
that the following two conditions are met: that the following two conditions are met:
1) The prefixes advertised, through the Router Advertisement 1) The prefixes advertised, through the Router Advertisement
messages, by the access router terminating the PPP link are messages, by the access router terminating the PPP link are
exclusive to the PPP link. exclusive to the PPP link.
skipping to change at page 12, line 38 skipping to change at page 11, line 25
+----------+------------------------+-----------------------------+ +----------+------------------------+-----------------------------+
|1111111010| 0 | Interface-Identifier | |1111111010| 0 | Interface-Identifier |
+----------+------------------------+-----------------------------+ +----------+------------------------+-----------------------------+
The most significant 10 bits of the address is the Link-Local The most significant 10 bits of the address is the Link-Local
prefix FE80::. 54 zero bits pad out the address between the prefix FE80::. 54 zero bits pad out the address between the
Link-Local prefix and the Interface-Identifier fields. Link-Local prefix and the Interface-Identifier fields.
6. Security Considerations 6. Security Considerations
The IPv6 Control Protocol extension to PPP can be used with all Lack of link security, such as authentication, trigger the
defined PPP authentication and encryption mechanisms. security concerns raised in [3] when stateless address auto-
configuration method is employed for the generation of global
unicast IPv6 addresses out of interface identifiers that are
either negotiated through the IPV6CP or generated, for instance,
using a method described in [9]. Thus, the mechanisms that are
appropriate for ensuring PPP link security are addressed below
together with the reference to a generic threat model.
The information learned via the NCP protocol SHOULD not be trusted The mechanisms that are appropriate for ensuring PPP link
for making security relevant decisions. Security are: 1) Access Control Lists that apply filters on
traffic received over the link for enforcing admission policy, 2)
an Authentication protocol that facilitates negotiations between
peers [15] to select an authentication method (e.g., MD5 [16])
for validation of the peer, and 3) an Encryption protocol that
facilitates negotiations between peers to select encryption
algorithms (or, crypto-suites) to ensure data confidentiality
[17]).
7. Acknowledgments There are certain threats associated with peer interactions on a
PPP link even with one or more of the above security measures in
place. For instance, using MD5 authentication method [16] exposes
one to replay attack, where in which, an attacker could intercept
and replay a station's identity and password hash to get access to
a network. The user of this specification is advised to refer to
[15], which presents a generic threat model, for an understanding
of the threats posed to the security of a link. The reference
[15] also gives framework to specify requirements for the
selection of an authentication method for a given application.
7. IANA Considerations
The editor has no specific recommendations for the IANA on the
assignment of a value for the Type field of IPv6 datagram
Interface-Identifier option specified in this specification. The
current assignment is up-to-date at [4]. However, the reference
to the RFC number needs to be updated.
8. Acknowledgments
This document borrows from the Magic-Number LCP option and as such This document borrows from the Magic-Number LCP option and as such
is partially based on previous work done by the PPP working group. is partially based on previous work done by the PPP working group.
The editor is grateful for the input provided by members of the The editor is grateful for the input provided by members of the
IPv6 community in the spirit of updating the RFC 2472. Thanks, in IPv6 community in the spirit of updating the RFC 2472. Thanks, in
particular, go to Pete Barany and Karim El-malki for their particular, go to Pete Barany and Karim El-malki for their
technical contributions. Also, thanks to Alex Conta for a technical contributions. Also, thanks to Alex Conta, for a
thorough reviewing and Pekka Savola for the nits. thorough reviewing, Stephen Kent, for helping with security
aspects, Spencer Dawkins and Pekka Savola for the nits. Finally,
the author is grateful to Jari Arkko, for his initiation to bring
closure to this specification.
8. References 9. References
8.1 Normative References 9.1 Normative References
[1] Simpson, W., "The Point-to-Point Protocol", STD 51, RFC [1] Simpson, W., "The Point-to-Point Protocol," STD 51, RFC
1661, July 1994. 1661, July 1994.
[2] Deering, S., and R. Hinden, Editors, "Internet Protocol, [2] Deering, S., and R. Hinden, Editors, "Internet Protocol,
Version 6 (IPv6) Specification", RFC 2460, December 1998. Version 6 (IPv6) Specification," RFC 2460, December 1998.
[3] Thomson, S., and T. Narten, "IPv6 Stateless Address [3] Thomson, S., and T. Narten, "IPv6 Stateless Address
Autoconfiguration", RFC 2462, December 1998. Autoconfiguration," RFC 2462, December 1998.
[4] IANA, "Assigned Numbers", http://www.iana.org/numbers.html [4] IANA, "Assigned Numbers," http://www.iana.org/numbers.html
[5] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) [5] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)
Registration Authority", April 2004. Registration Authority", April 2004.
[6] Hinden, R., and S. Deering, "IP Version 6 Addressing [6] Hinden, R., and S. Deering, "IP Version 6 Addressing
Architecture", RFC 3513, July 1998. Architecture", RFC 4291, February 2006.
[7] Bradner, S., "Key words for use in RFCs to Indicate Requirement [7] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels," BCP 14, RFC 2119, March 1997. Levels," BCP 14, RFC 2119, March 1997.
[8] Narten T., and C. Burton, "A Caution On The Canonical Ordering [8] Haskin D., and E. Allen, "IP Version 6 over PPP," RFC 2472,
Of Link-Layer Addresses,÷ RFC 2469, December 1998. December 1998.
[9] Narten T., and R. Draves, "Privacy Extensions for Stateless [9] Narten T., et. al., " Privacy Extensions for Stateless Address
Address Autoconfiguration in IPv6,÷ RFC 3041, January 2001. Autoconfiguration in IPv6," draft-ietf-ipv6-privacy-addrs-v2-
05, August 2006.
8.2 Informative references 9.2 Informative references
[10] 3GPP2 X.S0011-002-C v1.0, "cdma2000 Wireless IP Network [10] 3GPP2 X.S0011-002-C v1.0, "cdma2000 Wireless IP Network
Standard: Simple IP and Mobile IP Access Services,÷ September Standard: Simple IP and Mobile IP Access Services," September
2003. 2003.
[11] 3GPP TS 29.061 V6.4.0, "Interworking between the Public Land [11] 3GPP TS 29.061 V6.4.0, "Interworking between the Public Land
Mobile Network (PLMN) Supporting packet based services and Mobile Network (PLMN) Supporting packet based services and
Packet Data Networks (PDN) (Release 6),÷ April 2005. Packet Data Networks (PDN) (Release 6)," April 2005.
[12] Droms, E., et al., ˘Dynamic Host Configuration Protocol for [12] Droms, E., et al., "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6),÷ RFC 3315, July 2003. IPv6 (DHCPv6)," RFC 3315, July 2003.
[13] 3GPP TS 23.060 v6.8.0, ˘General Packet Radio Service (GPRS); [13] 3GPP TS 23.060 v6.8.0, "General Packet Radio Service (GPRS);
Service description; Stage 2 (Release 6),÷ March 2005. Service description; Stage 2 (Release 6)," March 2005.
[14] Narten T., and C. Burton, "A Caution On The Canonical Ordering
Of Link-Layer Addresses," RFC 2469, December 1998.
[15] Aboba, R., et. al., "Extensible Authentication Protocol," RFC
3748, June 2004.
[16] Rivest, R., "The MD5 Message-Digest Algorithm," RFC 1321, April
1992.
[17] Meyer, G., "The PPP Encryption Control Protocol (ECP)," RFC
1968, June 1996.
Appendix A: Global Scope Addresses Appendix A: Global Scope Addresses
A node on the PPP link MUST create global unicast addresses either A node on the PPP link MUST create global unicast addresses either
through stateless or stateful address auto-configuration through stateless or stateful address auto-configuration
mechanisms. In the stateless address auto-configuration [3], the mechanisms. In the stateless address auto-configuration [3], the
node relies on sub-net prefixes advertised by the router via the node relies on sub-net prefixes advertised by the router via the
Router Advertisement messages to obtain global unicast addresses Router Advertisement messages to obtain global unicast addresses
from an interface identifier. In the stateful address auto- from an interface identifier. In the stateful address auto-
configuration, the host relies on a Stateful Server, like, DHCPv6 configuration, the host relies on a Stateful Server, like, DHCPv6
skipping to change at page 14, line 25 skipping to change at page 14, line 18
Appendix B: Changes from RFC-2472 Appendix B: Changes from RFC-2472
The following changes were made from RFC-2472 "IPv6 over PPP": The following changes were made from RFC-2472 "IPv6 over PPP":
- Minor updates to sections 3 and 4 - Minor updates to sections 3 and 4
- Updated the text in section 4.1 to include the reference to - Updated the text in section 4.1 to include the reference to
Appendix A and minor text clarifications. Appendix A and minor text clarifications.
- Updated the text in Section 5 to: (a) option the use of one or - Removed the section 4.2 on IPv6-Compression-Protocol, based on
more Interface-Identifiers generated, other than the IPV6CP the IESG recommendation, and created a new standards track
negotiated, in the creation of global unicast addresses, and draft to cover the negotiation of IPv6 datagram compression
(b) identify cases against the DAD of created non-link-local protocol using IPV6CP.
addresses.
- Updated the text in Section 5 to: (a) allow the use of one or
more Interface-Identifiers generated by a peer, in addition to
the use of Interface-identifier negotiated between peers of the
link, in the creation of global unicast addresses for the local
PPP interface, and (b) identify cases against the DAD of
created non-link-local addresses.
- Added new and updated references. - Added new and updated references.
- Added the Appendix A - Added the Appendix A
Authors' Addresses Authors' Addresses
Dimitry Haskin Dimitry Haskin
Ed Allen Ed Allen
Srihari Varada (Editor) Srihari Varada (Editor)
TranSwitch Corporation TranSwitch Corporation
3 Enterprise Dr. 3 Enterprise Dr.
Shelton, CT 06484. US. Shelton, CT 06484. US.
Phone: +1 203 929 8810 Phone: +1 203 929 8810
EMail: varada@txc.com EMail: varada@txc.com
IPR Disclosure
By submitting this Internet-Draft, each author represents that
any 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 aware will be disclosed, in accordance with Section 6 of
BCP 79.
IPR Notice IPR Notice
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed Intellectual Property Rights or other rights that might be claimed
to pertain to the implementation or use of the technology to pertain to the implementation or use of the technology
described in this document or the extent to which any license described in this document or the extent to which any license
under such rights might or might not be available; nor does it under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any represent that it has made any independent effort to identify any
such rights. Information on the procedures with respect to rights such rights. Information on the procedures with respect to rights
in RFC documents can be found in BCP 78 and BCP 79. in RFC documents can be found in BCP 78 and BCP 79.
skipping to change at page 15, line 33 skipping to change at page 15, line 24
at http://www.ietf.org/ipr. at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention The IETF invites any interested party to bring to its attention
any copyrights, patents or patent applications, or other any copyrights, patents or patent applications, or other
proprietary rights that may cover technology that may be required proprietary rights that may cover technology that may be required
to implement this standard. Please address the information to the to implement this standard. Please address the information to the
IETF at ietf-ipr@ietf.org. IETF at ietf-ipr@ietf.org.
Copyright Notice and Disclaimer Copyright Notice and Disclaimer
Copyright (C) The Internet Society (2005). This document is Copyright (C) The IETF Trust (2007). This document is subject to
subject to the rights, licenses and restrictions contained in BCP the rights, licenses and restrictions contained in BCP 78, and
78, and except as set forth therein, the authors retain all their except as set forth therein, the authors retain all their rights.
rights.
This document and the information contained herein are provided This document and the information contained herein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
PARTICULAR PURPOSE. FOR A PARTICULAR PURPOSE.
 End of changes. 44 change blocks. 
129 lines changed or deleted 121 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/