draft-ietf-ipv6-compression-nego-v2-01.txt   draft-ietf-ipv6-compression-nego-v2-02.txt 
IPv6 Working Group S.Varada (Editor) IPv6 Working Group S.Varada (Editor)
Internet Draft Transwitch Internet Draft Transwitch
Category: Standards track October 2007 Obsoletes: RFC 2472 (if approved) February 2008
Category: Standards track
Negotiation for IPv6 datagram compression using IPv6 Control Protocol Negotiation for IPv6 datagram compression using IPv6 Control Protocol
<draft-ietf-ipv6-compression-nego-v2-01.txt> <draft-ietf-ipv6-compression-nego-v2-02.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
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 36
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 IETF Trust (2007). Copyright (C) The IETF Trust (2008).
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.
The IPv6 Control Protocol (IPv6CP), which is an NCP for a PPP The IPv6 Control Protocol (IPV6CP), which is an NCP for a PPP
link, allows for the negotiation of desirable parameters for the link, allows for the negotiation of desirable parameters for an
IPv6 interface over PPP. IPv6 interface over PPP.
This document defines the IPv6 datagram compression option that This document defines the IPv6 datagram compression option that
can be negotiated by a node on the link through the IPv6CP. can be negotiated by a node on the link through the IPV6CP.
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. IPV6CP Configuration Options...................................3 2. IPV6CP Configuration Options...................................3
2.1 IPv6-Compression-Protocol..................................3 2.1 IPv6-Compression-Protocol..................................3
3. Security Considerations........................................4 3. Security Considerations........................................5
4. IANA Considerations............................................5 4. IANA Considerations............................................5
5. Acknowledgments................................................5 5. Acknowledgments................................................6
6. References.....................................................6 6. References.....................................................6
6.1 Normative References.......................................6 6.1 Normative References.......................................6
6.2 Informative References.....................................6 6.2 Informative References.....................................6
Editor's Address..................................................6 Editor's Address..................................................7
IPR Notice ......................................................6 IPR Notice ......................................................7
Copyright Notice and Disclaimer...................................7 Copyright Notice and Disclaimer...................................8
1. Introduction 1. Introduction
PPP [1] has three main components: PPP [1] 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 2, line 49 skipping to change at page 3, line 5
established and optional facilities have been negotiated as established and optional facilities have been negotiated as
needed by the LCP, PPP must send NCP packets to choose and needed by the LCP, PPP must send NCP packets to choose and
configure one or more network-layer protocols. Once each of the configure one or more network-layer protocols. Once each of the
chosen network-layer protocols has been configured, datagrams chosen network-layer protocols has been configured, datagrams
from each network-layer protocol can be sent over the link. The from each network-layer protocol can be sent over the link. The
link will remain configured for communications until 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.).
In the IPv6 over PPP specification [2], the NCP, or IPv6CP, for In the IPv6 over PPP specification [2], the NCP, or IPV6CP, for
establishing and configuring the IPv6 over PPP is defined. The establishing and configuring IPv6 over PPP is defined. The
same specification defines the Interface Identifier parameter, same specification defines the Interface Identifier parameter,
which can be used to generate link-local and global unique IPv6 which can be used to generate link-local and global unique IPv6
addresses, for negotiation. addresses, for negotiation.
In this specification, the compression parameter for use in IPv6 In this specification, the compression parameter for use in IPv6
datagram compression is defined. datagram compression is defined. Together with RFC 5072 [2], this
document obsoletes RFC 2472 [13]. However, no protocol changes
have been introduced over RFC 2472.
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 [3]. in [3].
2. IPV6CP Configuration Options 2. 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 parameters. IPV6CP uses the same Configuration Option format as
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.
The only IPV6CP option defined in this document is the IPv6- The only IPV6CP option defined in this document is the IPv6-
Compression-Protocol. The Type field for this IPV6CP Option is as Compression-Protocol. The Type field for this IPV6CP Option is as
follows: follows:
2 IPv6-Compression-Protocol 2 IPv6-Compression-Protocol
Note that the up-to-date values of the IPV6CP Option Type field Note that the up-to-date values of the IPV6CP Option Type field
are specified in the on-line database of "Assigned Numbers" are specified in the on-line database of "Assigned Numbers"
maintained at IANA [4]. maintained at IANA [7].
2.1 IPv6-Compression-Protocol 2.1 IPv6-Compression-Protocol
Description Description
This Configuration Option provides a way to negotiate the use of a This Configuration Option provides a way to negotiate the use of a
specific IPv6 packet compression protocol. The specific IPv6 packet compression protocol. The
IPv6-Compression-Protocol Configuration Option is used to indicate IPv6-Compression-Protocol Configuration Option is used to indicate
the ability to receive compressed packets. Each end of the link the ability to receive compressed packets. Each end of the link
MUST separately request this option if bi-directional compression MUST separately request this option if bi-directional compression
is desired. By default, compression is not enabled. is desired. By 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 datagrams and is not to be confused with compression resulting
from negotiations via Compression Control Protocol (CCP), which from a compression method negotiated via the PPP Compression
potentially affect all datagrams. Control Protocol (CCP) [12], which potentially affects all
datagrams.
A summary of the IPv6-Compression-Protocol Configuration Option A summary of the IPv6-Compression-Protocol Configuration Option
format is shown below. The fields are transmitted from left to format is shown below. The fields are transmitted from left to
right. 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 4, line 34 skipping to change at page 4, line 40
>= 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 the compression protocol desired. Values for this field are
always the same as the PPP Data Link Layer Protocol field always the same as the PPP Data Link Layer Protocol field
values for that same compression protocol. values for that same compression protocol.
No IPv6-Compression-Protocol field values are currently IPv6-Compression-Protocol field values have been assigned in
assigned. Specific assignments will be made in documents that [14] for IPv6 Header Compression (004f), [4, 5] for IP Header
Compression (0061), and [6] for Robust Header compression
(ROHC) (0003). Other assignments can be made in documents that
define specific compression algorithms. define specific compression algorithms.
Data Data
The Data field is zero or more octets and contains additional The Data field is zero or more octets and contains additional
data as determined by the particular compression protocol. data as determined by the particular compression protocol.
Default Default
No IPv6 compression protocol enabled. No IPv6 compression protocol enabled.
skipping to change at page 5, line 4 skipping to change at page 5, line 10
Data Data
The Data field is zero or more octets and contains additional The Data field is zero or more octets and contains additional
data as determined by the particular compression protocol. data as determined by the particular compression protocol.
Default Default
No IPv6 compression protocol enabled. No IPv6 compression protocol enabled.
3. Security Considerations 3. Security Considerations
Lack of proper link security, such as authentication, prior to Lack of proper link security, such as authentication, prior to
the data transfer may lead to such attacks as the man-in-the data transfers may enable man-in-the middle attacks
middle resulting in the loss of data integrity and resulting in the loss of data integrity and confidentiality. The
confidentiality. The mechanisms that are appropriate for ensuring mechanisms that are appropriate for ensuring PPP link security
PPP link security are addressed below together with the reference are addressed below together with the reference to a generic
to a generic threat model. threat model.
The mechanisms that are appropriate for ensuring PPP link The mechanisms that are appropriate for ensuring PPP link
Security are: 1) Access Control Lists that apply filters on Security are: 1) Access Control Lists that apply filters on
traffic received over the link for enforcing admission policy, 2) traffic received over the link for enforcing admission policy, 2)
an Authentication protocol that facilitates negotiations between an Authentication protocol that facilitates negotiations between
peers [5] to select an authentication method (e.g., MD5 [6]) for peers [8] to select an authentication method (e.g., MD5 [9]) for
validation of the peer, and 3) an Encryption protocol that validation of the peer, and 3) an Encryption control protocol
facilitates negotiations between peers to select encryption that facilitates negotiations between peers to select encryption
algorithms (or, crypto-suites) to ensure data confidentiality algorithms (or, crypto-suites) to ensure data confidentiality
[7]). [10]).
There are certain threats associated with peer interactions on a There are certain threats associated with peer interactions on a
PPP link even with one or more of the above security measures in PPP link even with one or more of the above security measures in
place. For instance, using MD5 authentication method [6] exposes place. For instance, using the MD5 authentication method [9]
one to replay attack, where in which, an attacker could intercept exposes one to replay attacks, in which an attacker could
and replay a station's identity and password hash to get access intercept and replay a station's identity and password hash to
to a network. The user of this specification is advised to refer get access to a network. The user of this specification is
to [5], which presents a generic threat model, for an advised to refer to [8], which presents a generic threat model,
understanding of the threats posed to the security of a link. The for an understanding of the threats posed to the security of a
reference [5] also gives framework to specify requirements for link. The reference [8] also gives a framework to specify
the selection of an authentication method for a given requirements for the selection of an authentication method for a
application. given application.
4. IANA Considerations 4. IANA Considerations
The author has no specific recommendations for the IANA on the There are no specific recommendations for the IANA on the
assignment of a value for the Type field of IPv6 datagram assignment of values for the Type field of the IPv6 datagram
compression option specified in this specification. The current compression option specified in section 2.1 of this document. The
assignment is up-to-date at [4]. However, the IANA should take current assignment is up-to-date at [7].
note that the PPP Data Link Layer number for the
IPV6-Compression-Protocol configuration option is same as that of No action is needed either for the assignment of the
the IPV6CP Configuration options, which is listed in the IPv6-Compression-Protocol values, as such values have already
RFC 3818 [8]. To insure proper review of the same, the Editor been defined by other documents listed in the Section 2.1. Values
Would like to place it under IETF consensus process. for this field are always the same as the PPP Data Link Layer
field values for that same compression protocol. As a result,
future allocation of these values is governed by RFC 3818 [11]
that requires IETF consensus process.
5. Acknowledgments 5. Acknowledgments
The editor is grateful to Jari Arkko for the direction provided on The editor is grateful to Jari Arkko for the direction provided on
this draft and James Carlson for helpful suggestions. this draft and James Carlson for helpful suggestions.
Acknowledgements are also due to D. Haskins and E. Allen for the
specification work done in RFC 2023 and RFC 2472.
6. References 6. References
6.1 Normative References 6.1 Normative References
[1] Simpson, W., "The Point-to-Point Protocol," STD 51, RFC 1661, [1] Simpson, W., "The Point-to-Point Protocol", STD 51, RFC 1661,
July 1994. July 1994.
[2] Allen, E., Haskin, D., and, S. Varada, Ed., "IPv6 over PPP," [2] Allen, E., Haskin, D., and, S. Varada, Ed., "IPv6 over PPP",
RFC 5072, September 2007. RFC 5072, September 2007.
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement [3] 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.
[4] Degermark M., B. Nordgren, and S. Pink, "IP Header Compression",
RFC 2507, February 1999.
[5] Koren T., S. Casner, and C. Bormann, "IP Header Compression Over
PPP", RFC 3544, July 2003.
[6] Bormann C., "Robust Header Compression (ROHC) over PPP", RFC
3241, April 2002.
6.2 Informative References 6.2 Informative References
[4] IANA, "Assigned Numbers," http://www.iana.org/numbers.html [7] IANA, "Assigned Numbers", http://www.iana.org/numbers.html
[5] Aboba, R., Blunk, L., Vollbrecht, J., Carlson, J., and [8] Aboba, R., Blunk, L., Vollbrecht, J., Carlson, J., and
H. Levkowetz,Ed., "Extensible Authentication Protocol," RFC H. Levkowetz,Ed., "Extensible Authentication Protocol", RFC
3748, June 2004. 3748, June 2004.
[6] Rivest, R., "The MD5 Message-Digest Algorithm," RFC 1321, April [9] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, April
1992. 1992.
[7] Meyer, G., "The PPP Encryption Control Protocol (ECP)," RFC [10] Meyer, G., "The PPP Encryption Control Protocol (ECP)", RFC
1968, June 1996. 1968, June 1996.
[8] Schryver, V., ?IANA Considerations for the Point-to-Point [11] Schryver, V., "IANA Considerations for the Point-to-Point
Protocol (PPP),? RFC 3818, June 2004. Protocol (PPP)", RFC 3818, June 2004.
[12] Rand, D., "The PPP Compression Control Protocol(CCP)", RFC 1962,
June 1996.
[13] Haskin D., and E. Allen, "IP Version 6 over PPP", RFC 2472,
December 1998.
[14] Haskin D., and E. Allen, "IP Version 6 over PPP", RFC 2023,
October 1996.
Editor's Address Editor's Address
Srihari Varada Srihari Varada
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@ieee.org EMail: varada@ieee.org
skipping to change at page 7, line 28 skipping to change at page 8, line 13
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 IETF Trust (2007). This document is subject to Copyright (C) The IETF Trust (2008). This document is subject to
the rights, licenses and restrictions contained in BCP 78, and the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their 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, THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
 End of changes. 31 change blocks. 
58 lines changed or deleted 89 lines changed or added

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