draft-ietf-ipngwg-pppext-ipv6cp-03.txt   rfc2023.txt 
Internet Engineering Task Force Network Working Group D. Haskin
INTERNET-DRAFT Dimitry Haskin Request for Comments: 2023 E. Allen
Expires November 1996 Ed Allen Category: Standards Track Bay Networks, Inc.
<draft-ietf-ipngwg-pppext-ipv6cp-03.txt> Bay Networks, Inc. October 1996
May 1996
IP Version 6 over PPP IP Version 6 over PPP
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document specifies an Internet standards track protocol for the
documents of the Internet Engineering Task Force (IETF), its Internet community, and requests discussion and suggestions for
areas, and its working groups. Note that other groups may also improvements. Please refer to the current edition of the "Internet
distribute working documents as Internet-Drafts. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as
``work in progress.''
To learn the current status of any Internet-Draft, please check
the ``1id-abstracts.txt'' listing contained in the Internet-
Drafts Shadow Directories on ftp.is.co.za (Africa),
nic.nordu.net (Europe), munnari.oz.au (Pacific Rim),
ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast).
Abstract Abstract
The Point-to-Point Protocol (PPP) [1] provides a standard method of The Point-to-Point Protocol (PPP) [1] provides a standard method of
encapsulating Network Layer protocol information over point-to-point encapsulating Network Layer protocol information over point-to-point
links. PPP also defines an extensible Link Control Protocol, and links. PPP also defines an extensible Link Control Protocol, and
proposes a family of Network Control Protocols (NCPs) for proposes a family of Network Control Protocols (NCPs) for
establishing and configuring different network-layer protocols. establishing and configuring different network-layer protocols.
This document defines the method for transmission of IP Version 6 [2] This document defines the method for transmission of IP Version 6 [2]
packets over PPP links as well as the Network Control Protocol (NCP) packets over PPP links as well as the Network Control Protocol (NCP)
for establishing and configuring the IPv6 over PPP. It also specifies for establishing and configuring the IPv6 over PPP. It also specifies
the method of forming IPv6 link-local addresses on PPP links. the method of forming IPv6 link-local addresses on PPP links.
Table of Contents Table of Contents
1. Introduction .......................................... 2 1. Introduction .......................................... 2
1.1. Specification of Requirements ...................... 3 1.1. Specification of Requirements ...................... 2
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 ............... 4 4. IPV6CP Configuration Options .......................... 4
4.1. Interface-Token ................................... 4
4. IPV6CP Configuration Options .......................... 5 4.2. IPv6-Compression-Protocol.......................... 7
4.1. Interface-Token ................................... 8
4.2. IPv6-Compression-Protocol
5. Stateless Autoconfiguration and Link-Local Addresses .. 9 5. Stateless Autoconfiguration and Link-Local Addresses .. 9
A. IPV6CP Recommended Options ............................. 9
A. IPV6CP Recommended Options ............................. 10
Security Considerations ....................................... 10 Security Considerations ....................................... 10
References .................................................... 10 References .................................................... 10
Acknowledgments ............................................... 10 Acknowledgments ............................................... 10
Authors' Addresses ............................................ 10
Authors' Addresses ............................................ 11
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 41 skipping to change at page 3, line 10
MAY This word, or the adjective "optional", means that this MAY This word, or the adjective "optional", means that this
item is one of an allowed set of alternatives. An item is one of an allowed set of alternatives. An
implementation which does not include this option MUST be implementation which does not include this option MUST be
prepared to inter-operate with another implementation which prepared to inter-operate with another implementation which
does include the option. does include the option.
2. Sending IPv6 Datagrams 2. Sending IPv6 Datagrams
Before any IPv6 packets may be communicated, PPP must reach the Before any IPv6 packets may be communicated, PPP must reach the
Network-Layer Protocol phase, and the IPv6 Control Protocol must reach Network-Layer Protocol phase, and the IPv6 Control Protocol must
the Opened state. reach the Opened state.
Exactly one IPv6 packet is encapsulated in the Information field of Exactly one IPv6 packet is encapsulated in the Information field of
PPP Data Link Layer frames where the Protocol field indicates type PPP Data Link Layer frames where the Protocol field indicates type
hex 0057 (Internet Protocol Version 6). hex 0057 (Internet Protocol Version 6).
The maximum length of an IPv6 packet transmitted over a PPP link is The maximum length of an IPv6 packet transmitted over a PPP link is
the same as the maximum length of the Information field of a PPP data the same as the maximum length of the Information field of a PPP data
link layer frame. PPP links supporting IPv6 must allow at least 576 link layer frame. PPP links supporting IPv6 must allow at least 576
octets in the information field of a data link layer frame. octets in the information field of a data link layer frame.
skipping to change at page 4, line 25 skipping to change at page 3, line 37
as the Link Control Protocol (LCP). IPV6CP packets may not be as the Link Control Protocol (LCP). IPV6CP packets may not be
exchanged until PPP has reached the Network-Layer Protocol phase. exchanged until PPP has reached the Network-Layer Protocol phase.
IPV6CP packets received before this phase is reached should be IPV6CP packets received before this phase is reached should be
silently discarded. silently discarded.
The IPv6 Control Protocol is exactly the same as the Link Control The IPv6 Control Protocol is exactly the same as the Link Control
Protocol [1] with the following exceptions: Protocol [1] with the following exceptions:
Data Link Layer Protocol Field Data Link Layer Protocol Field
Exactly one IPV6CP packet is encapsulated in the Information field Exactly one IPV6CP packet is encapsulated in the Information field
of PPP Data Link Layer frames where the Protocol field indicates of PPP Data Link Layer frames where the Protocol field indicates
type hex 8057 (IPv6 Control Protocol). type hex 8057 (IPv6 Control Protocol).
Code field Code field
Only Codes 1 through 7 (Configure-Request, Configure-Ack, Only Codes 1 through 7 (Configure-Request, Configure-Ack,
Configure-Nak, Configure-Reject, Terminate-Request, Terminate-Ack Configure-Nak, Configure-Reject, Terminate-Request, Terminate-Ack
and Code-Reject) are used. Other Codes should be treated as and Code-Reject) are used. Other Codes should be treated as
unrecognized and should result in Code-Rejects. unrecognized and should result in Code-Rejects.
Timeouts Timeouts
IPV6CP packets may not be exchanged until PPP has reached the IPV6CP packets may not be exchanged until PPP has reached the
Network-Layer Protocol phase. An implementation should be Network-Layer Protocol phase. An implementation should be prepared
prepared to wait for Authentication and Link Quality Determination to wait for Authentication and Link Quality Determination to finish
to finish before timing out waiting for a Configure-Ack or other before timing out waiting for a Configure-Ack or other response. It
response. It is suggested that an implementation give up only is suggested that an implementation give up only after user
after user intervention or a configurable amount of time. intervention or a configurable amount of time.
Configuration Option Types Configuration Option Types
IPV6CP has a distinct set of Configuration Options, which are IPV6CP has a distinct set of Configuration Options, which are
defined below. defined below.
4. IPV6CP Configuration Options 4. IPV6CP Configuration Options
IPV6CP Configuration Options allow negotiation of desirable IPv6 IPV6CP Configuration Options allow negotiation of desirable IPv6
parameters. IPV6CP uses the same Configuration Option format defined parameters. IPV6CP uses the same Configuration Option format defined
for LCP [1], with a separate set of Options. If a Configuration for LCP [1], with a separate set of Options. If a Configuration
Option is not included in a Configure-Request packet, the default Option is not included in a Configure-Request packet, the default
value for that Configuration Option is assumed. value for that Configuration Option is assumed.
Up-to-date values of the IPV6CP Option Type field are specified in Up-to-date values of the IPV6CP Option Type field are specified in
the most recent "Assigned Numbers" RFC [5]. Current values are the most recent "Assigned Numbers" RFC [5]. Current values are
assigned as follows: assigned as follows:
1 Interface-Token 1 Interface-Token
2 IPv6-Compression-Protocol 2 IPv6-Compression-Protocol
4.1. Interface-Token 4.1. Interface-Token
Description Description
This Configuration Option provides a way to negotiate a unique This Configuration Option provides a way to negotiate a unique
32-bit interface token to be used for the address 32-bit interface token to be used for the address
autoconfiguration [3] at the local end of the link (see section 5). autoconfiguration [3] at the local end of the link (see section
The interface token MUST be unique within the PPP link; i.e. upon 5). The interface token MUST be unique within the PPP link; i.e.
completion of the negotiation different Interface-Token values are upon completion of the negotiation different Interface-Token
to be selected for the ends of the PPP link. values are to be selected for the ends of the PPP link.
Before this Configuration Option is requested, an implementation Before this Configuration Option is requested, an implementation
must choose its tentative Interface-Token. It is recommended that must choose its tentative Interface-Token. It is recommended that
a non-zero value be chosen in the most random manner possible in a non-zero value be chosen in the most random manner possible in
order to guarantee with very high probability that an order to guarantee with very high probability that an
implementation will arrive at a unique token value. A good way to implementation will arrive at a unique token value. A good way to
choose a unique random number is to start with a unique seed. choose a unique random number is to start with a unique seed.
Suggested sources of uniqueness include machine serial numbers, Suggested sources of uniqueness include machine serial numbers,
other network hardware addresses, system clocks, etc. Note that it other network hardware addresses, system clocks, etc. Note that it
may not be sufficient to use a link-layer address alone as the may not be sufficient to use a link-layer address alone as the
seed, since it will not always be unique. Thus it is suggested seed, since it will not always be unique. Thus it is suggested
that the seed should be calculated from a variety of sources that that the seed should be calculated from a variety of sources that
are likely to be different even on identical systems and as many are likely to be different even on identical systems and as many
sources as possible be used simultaneously. Good sources of sources as possible be used simultaneously. Good sources of
uniqueness or randomness are required for the Interface-Token uniqueness or randomness are required for the Interface-Token
negotiation to succeed. If a good source of randomness cannot be negotiation to succeed. If a good source of randomness cannot be
found, it is recommended that a zero value be used for the found, it is recommended that a zero value be used for the
Interface-Token transmitted in the Configure-Request. In this case Interface-Token transmitted in the Configure-Request. In this
the PPP peer may provide a valid non-zero Interface-Token in its case the PPP peer may provide a valid non-zero Interface-Token in
response as described below. Note that if at least one of the PPP its response as described below. Note that if at least one of the
peers is able to generate a unique random number, the token PPP peers is able to generate a unique random number, the token
negotiation will succeed. negotiation will succeed.
When a Configure-Request is received with the Interface-Token When a Configure-Request is received with the Interface-Token
Configuration Option and the receiving peer implements this option, Configuration Option and the receiving peer implements this
the received Interface-Token is compared with the Interface-Token option, the received Interface-Token is compared with the
of the last Configure-Request sent to the peer. Depending on the Interface-Token of the last Configure-Request sent to the peer.
result of the comparison an implementation MUST respond in one of Depending on the result of the comparison an implementation MUST
the following ways: respond in one of the following ways:
If the two Interface-Tokens are different but the received If the two Interface-Tokens are different but the received
Interface-Token is zero, a Configure-Ack is sent with a non-zero Interface-Token is zero, a Configure-Ack is sent with a non-zero
Interface-Token value suggested for use by the remote peer. Interface-Token value suggested for use by the remote peer. Such
Such a suggested Interface-Token MUST be different from the a suggested Interface-Token MUST be different from the Interface-
Interface-Token of the last Configure-Request sent to the peer. Token of the last Configure-Request sent to the peer.
If the two Interface-Tokens are different and the received If the two Interface-Tokens are different and the received
Interface-Token is not zero, the Interface-Token MUST be Interface-Token is not zero, the Interface-Token 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-Token, meaning that the responding peer agrees with Interface-Token, meaning that the responding peer agrees with the
the Interface-Token requested. Interface-Token requested.
If the two Interface-Tokens are equal and are not zero, a If the two Interface-Tokens are equal and are not zero, a
Configure-Nak MUST be sent specifying a different non-zero Configure-Nak MUST be sent specifying a different non-zero
Interface-Token value suggested for use by the remote peer. Interface-Token value suggested for use by the remote peer.
If the two Interface-Tokens are equal to zero, the If the two Interface-Tokens are equal to zero, the Interface-
Interface-Tokens negotiation MUST be terminated by transmitting Tokens negotiation MUST be terminated by transmitting the
the Configure-Reject with the Interface-Token value set to zero. Configure-Reject with the Interface-Token value set to zero. In
In this case a unique Interface-Token can not be negotiated. this case a unique Interface-Token can not be negotiated.
If a Configure-Request is received with the Interface-Token If a Configure-Request is received with the Interface-Token
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 normal A new Configure-Request SHOULD NOT be sent to the peer until
processing would cause it to be sent (that is, until a Configure- normal processing would cause it to be sent (that is, until a
Nak is received or the Restart timer runs out). Configure-Nak is received or the Restart timer runs out).
A new Configure-Request MUST NOT contain the Interface-Token option A new Configure-Request MUST NOT contain the Interface-Token
if a valid Interface-Token Configure-Reject is received. option if a valid Interface-Token Configure-Reject is received.
Reception of a Configure-Nak with a suggested Interface-Token Reception of a Configure-Nak with a suggested Interface-Token
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 a unique Interface-Token. In this case a new Configure- indicates a unique Interface-Token. In this case a new
Request MUST be sent with the token value suggested in the last Configure-Request MUST be sent with the token value suggested in
Configure-Nak from the peer. But if the received Interface-Token the last Configure-Nak from the peer. But if the received
is equal to the one sent in the last Configure-Nak, a new Interface-Token is equal to the one sent in the last Configure-
Interface-Token MUST be chosen. In this case, a new Configure- Nak, a new Interface-Token MUST be chosen. In this case, a new
Request SHOULD be sent with the new tentative Interface-Token. Configure-Request SHOULD be sent with the new tentative
This sequence (transmit Configure-Request, receive Configure- Interface-Token. This sequence (transmit Configure-Request,
Request, transmit Configure-Nak, receive Configure-Nak) might receive Configure-Request, transmit Configure-Nak, receive
occur a few times, but it is extremely unlikely to occur Configure-Nak) might occur a few times, but it is extremely
repeatedly. More likely, the Interface-Tokens chosen at either end unlikely to occur repeatedly. More likely, the Interface-Tokens
will quickly diverge, terminating the sequence. chosen at either end will quickly diverge, terminating the
sequence.
If negotiation about the Interface-Token is required, and the peer If negotiation about the Interface-Token is required, and the peer
did not provide the option in its Configure-Request, the option did not provide the option in its Configure-Request, the option
SHOULD be appended to a Configure-Nak. The tentative value of the SHOULD be appended to a Configure-Nak. The tentative value of the
Interface-Token given must be acceptable as the remote Interface-Token given must be acceptable as the remote Interface-
Interface-Token; i.e. should be different from the token value Token; i.e. should be different from the token value selected for
selected for the local end of the PPP link. The next Configure- the local end of the PPP link. The next Configure-Request from
Request from the peer may include this option. If the next the peer may include this option. If the next Configure-Request
Configure-Request does not include this option the peer MUST NOT does not include this option the peer MUST NOT send another
send another Configure-Nak with this option included. It should Configure-Nak with this option included. It should assume that the
assume that the peer's implementation does not support this option. peer's implementation does not support this option.
By default, an implementation SHOULD attempt to negotiate the By default, an implementation SHOULD attempt to negotiate the
Interface-Token for its end of the PPP connection. Interface-Token for its end of the PPP connection.
A summary of the Interface-Token Configuration Option format is A summary of the Interface-Token Configuration Option format is
shown below. The fields are transmitted from left to right. shown below. The fields are transmitted from left to right.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 8, line 12 skipping to change at page 7, line 31
6 6
Interface-Token Interface-Token
The 32-bit Interface-Token which is very likely to be unique on The 32-bit Interface-Token which is very likely to be unique on
the link or zero if a good source of uniqueness can not be found. the link or zero if a good source of uniqueness can not be found.
Default Token Value Default Token Value
If no valid interface token can be successfully negotiated, If no valid interface token can be successfully negotiated, no
no default Interface-Token value should be assumed. The procedures default Interface-Token value should be assumed. The procedures
for recovering from such a case are unspecified. One approach is for recovering from such a case are unspecified. One approach is
to manually configure the interface token of the interface. to manually configure the interface token of the interface.
4.2. IPv6-Compression-Protocol 4.2. IPv6-Compression-Protocol
Description Description
This Configuration Option provides a way to negotiate the use of This Configuration Option provides a way to negotiate the use of a
a specific IPv6 packet compression protocol. The IPv6-Compression- specific IPv6 packet compression protocol. The IPv6-Compression-
Protocol Configuration Option is used to indicate the ability to Protocol Configuration Option is used to indicate the ability to
receive compressed packets. Each end of the link must separately receive compressed packets. Each end of the link must separately
request this option if bi-directional compression is desired. By request this option if bi-directional compression is desired. By
default, compression is not enabled. default, compression is not enabled.
IPv6 compression negotiated with this option is specific to IPv6 IPv6 compression negotiated with this option is specific to IPv6
datagrams and is not to be confused with compression resulting from datagrams and is not to be confused with compression resulting
negotiations via Compression Control Protocol (CCP), which from negotiations via Compression Control Protocol (CCP), which
potentially effect all datagrams. potentially effect all datagrams.
A summary of the IPv6-Compression-Protocol Configuration Option format A summary of the IPv6-Compression-Protocol Configuration Option
is shown below. The fields are transmitted from left to right. format is shown below. The fields are transmitted from left to
right.
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 | IPv6-Compression-Protocol | | Type | Length | IPv6-Compression-Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data ... | Data ...
+-+-+-+-+ +-+-+-+-+
Type Type
2 2
Length Length
>= 4 >= 4
IPv6-Compression-Protocol IPv6-Compression-Protocol
The IPv6-Compression-Protocol field is two octets and indicates The IPv6-Compression-Protocol field is two octets and indicates
the compression protocol desired. Values for this field are always the compression protocol desired. Values for this field are
the same as the PPP Data Link Layer Protocol field values for that always the same as the PPP Data Link Layer Protocol field values
same compression protocol. for that same compression protocol.
Up-to-date values of the IPv6-Compression-Protocol field are Up-to-date values of the IPv6-Compression-Protocol field are
specified in the most recent "Assigned Numbers" RFC [5]. specified in the most recent "Assigned Numbers" RFC [5].
Current values are assigned as follows: Current values are assigned as follows:
Value (in hex) Protocol Value (in hex) Protocol
004f IPv6 Header Compression 004f IPv6 Header Compression
Data Data
The Data field is zero or more octets and contains additional data The Data field is zero or more octets and contains additional data
as determined by the particular compression protocol. as determined by the particular compression protocol.
Default Default
No IPv6 compression protocol enabled. No IPv6 compression protocol enabled.
5. Stateless Autoconfiguration and Link-Local Addresses 5. Stateless Autoconfiguration and Link-Local Addresses
The interface token, which is used for forming IPv6 addresses of The interface token, which is used for forming IPv6 addresses of a
a PPP interface, SHOULD be negotiated in the IPV6CP phase of the PPP PPP interface, SHOULD be negotiated in the IPV6CP phase of the PPP
connection setup (see section 4.1). If no valid interface token has connection setup (see section 4.1). If no valid interface token has
been successfully negotiated, procedures for recovering from such been successfully negotiated, procedures for recovering from such a
a case are unspecified. One approach is to manually configure case are unspecified. One approach is to manually configure the
the interface token of the interface. interface token of the interface.
As long as the interface token is negotiated in the IPV6CP phase of As long as the interface token is negotiated in the IPV6CP phase of
the PPP connection setup, it is redundant to perform duplicate the PPP connection setup, it is redundant to perform duplicate
address detection as a part of the IPv6 Stateless Autoconfiguration address detection as a part of the IPv6 Stateless Autoconfiguration
protocol [3]. Therefore it is recommended that for PPP links with protocol [3]. Therefore it is recommended that for PPP links with
the IPV6CP Interface-Token option enabled the default value of the the IPV6CP Interface-Token option enabled the default value of the
DupAddrDetectTransmits autoconfiguration variable [3] be zero. DupAddrDetectTransmits autoconfiguration variable [3] be zero.
Link-local addresses of PPP interfaces have the following format: Link-local addresses of PPP interfaces have the following format:
skipping to change at page 10, line 30 skipping to change at page 10, line 11
Interface-Token Interface-Token
IPv6-Compression-Protocol IPv6-Compression-Protocol
Security Considerations Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
References References
[1] W. Simpson, "The Point-to-Point Protocol", RFC 1661, July 1994. [1] Simpson, W., "The Point-to-Point Protocol", STD 51, RFC 1661,
July 1994.
[2] S. Deering, R. Hinden, Editors, "Internet Protocol, Version 6 [2] Deering, S., and R. Hinden, Editors, "Internet Protocol,
(IPv6) Specification", RFC 1883, December 1995. Version 6 (IPv6) Specification", RFC 1883, December 1995.
[2] R. Hinden, S. Deering, "IP Version 6 Addressing Architecture", [2] Hinden, R., and S. Deering, "IP Version 6 Addressing
RFC 1884, December 1995. Architecture", RFC 1884, December 1995.
[3] S. Thomson, T. Narten, "IPv6 Stateless Address [3] Thomson, S., and T. Narten, "IPv6 Stateless Address
Autoconfiguration", Work in progress Autoconfiguration", RFC 1971, August 1996.
[4] T. Narten, E. Nordmark, W. A. Simpson, "Neighbor Discovery for [4] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery
IP Version 6 (IPv6)", Work in progress for IP Version 6 (IPv6)", RFC 1970, August 1996.
[5] J. Reynolds, J. Postel, "Assigned Numbers", RFC 1700, [5] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, RFC
October 1994. 1700, October 1994.
Acknowledgments Acknowledgments
This document borrows from the Magic-Number LCP option and as such is This document borrows from the Magic-Number LCP option and as such is
partially based on previous work done by the PPP working group. partially based on previous work done by the PPP working group.
Authors' Addresses Authors' Addresses
Dimitry Haskin Dimitry Haskin
Bay Networks, Inc. Bay Networks, Inc.
 End of changes. 42 change blocks. 
140 lines changed or deleted 121 lines changed or added

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