[New I-D] Configured Tunnel End Point Option for PPP IPV6CP
Soohong Daniel Park <[email protected]>
| Newsgroups | gmane.ietf.pppext |
|---|---|
| Message-ID | <[email protected]> |
I don't exactly know this draft is useful in this w.g.
Please let me know if I am missing something...
=================================================
Subject: Configured Tunnel End Point Option for PPP IPV6CP
Abstract:
The Point-to-Point Protocol (PPP) provides a standard method for
transporting multi-protocol datagrams over point-to-point links.
PPP defines an extensible Link Control Protocol and a family of
Network Control Protocols (NCPs) for establishing and configuring
different network-layer protocols. In particular, for the newly
deployed IPv6 networks to interoperate with vastly deployed IPv4
networks, various transition mechanisms had been proposed. One such
mechanism is configured tunnels.
This document extends the NCP for establishing and configuring
Version 6 of the Internet Protocol (IPv6) over PPP, defining the
negotiation of available Configured Tunnel End Point (CTEP) IPv6
addresses to reach the IPv6 nodes which are separated by IPv4
networks.
=================================================
Best wishes...
Daniel (Soohong Daniel Park)
Mobile Platform Laboratory, SAMSUNG Electronics.
draft-daniel-pppext-ipv6-ctep-00.txt
(text/plain, 13.4 KB)
Network Working Group Soohong Daniel Park
INTERNET-DRAFT SAMSUNG Electronics
Expires: July 2004 January 2004
Configured Tunnel End Point Option for PPP IPV6CP
<draft-daniel-pppext-ipv6-ctep-00.txt>
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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".
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
The Point-to-Point Protocol (PPP) provides a standard method for
transporting multi-protocol datagrams over point-to-point links.
PPP defines an extensible Link Control Protocol and a family of
Network Control Protocols (NCPs) for establishing and configuring
different network-layer protocols. In particular, for the newly
deployed IPv6 networks to interoperate with vastly deployed IPv4
networks, various transition mechanisms had been proposed. One such
mechanism is configured tunnels.
This document extends the NCP for establishing and configuring
Version 6 of the Internet Protocol (IPv6) over PPP, defining the
negotiation of available Configured Tunnel End Point (CTEP) IPv6
addresses to reach the IPv6 nodes which are separated by IPv4
networks.
Park Expires - April 2004 [Page 1]
INTERNET-DRAFT CTEP Option for PPP IPV6CP January 2004
Table of Contents
1. Introduction..................................................2
1.1 Conventions used in this document........................2
2. IPV6CP Configuration Tunnel End Point (CTEP) Option...........2
3. Security Considerations.......................................4
4. References....................................................4
5. Author's Address..............................................5
1. Introduction
The Point-to-Point Protocol (PPP) [STD51] provides a standard method
for transporting multi-protocol datagrams over point-to-point links.
PPP defines an extensible Link Control Protocol and a family of
Network Control Protocols (NCPs) for establishing and configuring
different network-layer protocols. Moreover, in the initial
deployment of IPv6, the IPv6 nodes may need to communicate with the
other IPv6 nodes via IPv4 networks. Configured tunnels [TRANS]
provide a way to encapsulate the IPv6 packets in IPv4 packets and
tunnel them in the IPv4 network.
This document extends the NCP for establishing and configuring
Version 6 of the Internet Protocol (IPV6) over PPP [RFC2472],
defining the negotiation of available Configured Tunnel End Point
(CTEP) IPv6 addresses. This extension defines a new option called
Configured Tunnel End Point (CTEP) by which the remote peer can
notify the client with the list of end point of the configured
tunnels to the various IPv6 networks separated by the IPv4 networks.
1.1 Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC 2119].
2. IPV6CP Configuration Tunnel End Point (CTEP) Option
This configuration option defines a method for negotiating with the
remote peer the IPv6 addresses of configured tunnel end point to be
used on the local end of the link. It means this option gives the
information to the nodes about the Configured Tunnel End Point
[TRANS] to be contacted for reaching the nodes in the various IPv6
networks which are separated by IPv4 networks. If the local peer
requests and invalid TEP address (which it will typically do
Park Expires - April 2004 [Page 2]
INTERNET-DRAFT CTEP Option for PPP IPV6CP January 2004
intentionally) the remote peer specifies the address by NAKing this
option, and returning the IPv6 address of a valid TEP addresses.
The format of the Configured Tunnel End Point option is as shown
below:
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 | prefix-len | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
+ +
| Destination prefix (16 bytes) |
+ +
| |
+ +-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
+ +
| Configured TEP address (16 bytes) |
+ +
| |
+ +-+-+-+-+-+-+-+-+
| | prefix-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| Destination prefix (16 bytes) |
+ +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| Configured TEP address (16 bytes) |
+ +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . .
+-+-+-+-+-+-+-+
Park Expires - April 2004 [Page 3]
INTERNET-DRAFT CTEP Option for PPP IPV6CP January 2004
o Type: to be defined
o Length:
Total length of the prefix-len, Destination Prefix and
Configured Tunnel Address lists in octets; It should be a
multiple of 33.
o prefix-len: prefix length of the Destination Prefix
o Destination Prefix: An IPv6 Prefix;
o Configured TEP Address:
IPv6 Address of the Configured TEP. If all
sixteen octets are set to zero, it indicates an explicit request
that the peer provide the address information in a Config-Nak
packet.
o Default: No address is provided.
The nodes are expected to install the routes identified by the
tuples <Destination Prefix/prefix-len, Configured TEP Address> once
they receive this option from the remote peer.
3. Security Considerations
The use of this extension is as secure as the link itself.
4. References
4.1 Normative References
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997
[STD51] W. Simpson, Editor, "The Point-to-Point Protocol
(PPP)", STD 51, RFC 1661, July 1994
[RFC2472] Haskin, D., E. Allen, "IP Version 6 over PPP", RFC
2472, December 1998
4.2 Informative References
[TRANS] R. Gilligan, E. Nordmark, "Transition Mechanisms for
IPv6 Hosts and Routers", RFC 2893, August 2000.
Park Expires - April 2004 [Page 4]
INTERNET-DRAFT CTEP Option for PPP IPV6CP January 2004
5. Acknowledgements
A major portion of the text in this memo was stolen from <draft-
ietf-pppext-ipv6-dns-addr-03.txt> and <draft-daniel-dhc-dhcpv6-ctep-
opt-01.txt>. Specially thanks are authors of above drafts due to
their useful contributions.
6. Author's Address
Soohong Daniel Park
Mobile Platform Laboratory,
SAMSUNG Electronics
Korea
Phone: +82-31-200-3728
EMail: [email protected]
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances
of licenses to be made available, or the result of an attempt made
to obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification
can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement
Park Expires - April 2004 [Page 5]
INTERNET-DRAFT CTEP Option for PPP IPV6CP January 2004
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Park Expires - April 2004 [Page 6]