Internet DRAFT - draft-davey-mpls-rsvp-ipv6-unnum
draft-davey-mpls-rsvp-ipv6-unnum
Network Working Group A. Davey
INTERNET-DRAFT N. Neate
Updates: RFC3477 Data Connection Ltd (DCL)
Proposed category: Standards Track
Expires: August 2005
February 2005
Signalling Unnumbered Links in Resource ReSerVation Protocol -
Traffic Engineering (RSVP-TE) in an IPv6 Network
<draft-davey-mpls-rsvp-ipv6-unnum-00.txt>
Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
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/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright Notice
Copyright (C) The Internet Society 2005. All Rights Reserved.
Abstract
Currently, RSVP-TE signalling over unnumbered links identifies
routers using 32-bit Router IDs [RFC3477]. Traffic engineering
extensions to IGP protocols for use in IPv6 networks use 128-bit IPv6
addresses to identify routers [OSPFv3-TE], [ISIS-TE]. This document
specifies extensions for RSVP-TE signalling over unnumbered links to
use 128-bit Router IDs in an IPv6 network.
Davey and Neate Internet Draft [Page 1]
Internet Draft Signalling Unnumbered Links in IPv6 February 2005
1. Terms
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.
2. Overview
Supporting RSVP-TE over unnumbered links in an IPv6 network (that is,
links that do not have global-scope IPv6 addresses) involves two
components: (a) the ability to carry (TE) information about
unnumbered links in IGP TE extensions (ISIS or OSPFv3), and (b) the
ability to specify unnumbered links in RSVP-TE signalling. The
former is covered in [OSPFv3-TE] and [ISIS-TE]. The focus of this
document is on the latter.
Currently, RSVP-TE signalling for unnumbered links does not support
unnumbered links in an IPv6 network because it does not provide a way
to identify a router using a 128-bit IPv6 address in its
LSP_TUNNEL_INTERFACE_ID, Explicit Route and Record Route Objects.
This document proposes simple extensions that allow RSVP-TE
signalling over unnumbered links [RFC3477] to be used in an IPv6
network.
3. Definition of Terms
3.1 IPv6 Router IDs
In the context of this document, the term "IPv6 Router ID" means a
stable IPv6 address of an LSR that is always reachable if there is
any connectivity to the LSR. If OSPFv3 is being used as the IGP then
the IPv6 Router ID SHOULD be set to the "Router IPv6 Address" as
defined in [OSPFv3-TE]. If IS-IS is being used as the IGP then the
IPv6 Router ID SHOULD be set to the "IPv6 TE Router ID" as defined in
[ISIS-TE].
3.2 Interface IDs
In this document, Interface IDs are as defined in [RFC3477].
Davey and Neate Internet Draft [Page 2]
Internet Draft Signalling Unnumbered Links in IPv6 February 2005
4. Definition of Objects and Subobjects
4.1 LSP_TUNNEL_INTERFACE_ID Object
[RFC3477] states that if an LSR that originates an LSP advertises
this LSP as an unnumbered Forwarding Adjacency in IS-IS or OSPF (see
[LSP-HIER]), or the LSR uses the Forwarding Adjacency formed by this
LSP as an unnumbered component link of a bundled link (see
[LINK-BUNDLE]), the LSR MUST allocate an identifier to that
Forwarding Adjacency (just like for any other unnumbered link).
Moreover, the path message used for establishing the LSP that forms a
Forwarding Adjacency MUST contain the LSP_TUNNEL_INTERFACE_ID object,
as described in [RFC3477].
For IPv6 networks, the LSP_TUNNEL_INTERFACE_ID object has a class
number of 193, C-Type of 2 (suggested value; to be assigned by
IANA) and length of 24. The format is given 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface ID (32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Davey and Neate Internet Draft [Page 3]
Internet Draft Signalling Unnumbered Links in IPv6 February 2005
4.2 Explicit Route Object
A new subobject of the Explicit Route Object (ERO) is used to specify
unnumbered links in an IPv6 network. This subobject has the
following format.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|L| Type | Length | Reserved (MUST be zero) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface ID (32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Type is 5, Unnumbered Interface ID for IPv6 network (suggested
value; to be assigned by IANA). The Length is 24.
The Interface ID is the identifier assigned to the link by the LSR
specified by the IPv6 Router ID.
4.3 Record Router Object
A new subobject of the Record Route Object (RRO) is used to record
that the LSP path traversed an unnumbered link in an IPv6 network.
This subobject has the following format.
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 | Flags | Reserved (MBZ)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Router ID (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface ID (32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Davey and Neate Internet Draft [Page 4]
Internet Draft Signalling Unnumbered Links in IPv6 February 2005
The Type is 5, Unnumbered Interface ID for IPv6 network (suggested
value; to be assigned by IANA); the Length is 24. Flags are as
defined in [RFC3477].
5. Processing of objects
The processing of the objects and subobjects defined above is the
same as the processing for the equivalent objects and subobjects
defined in [RFC3477].
6. Security Considerations
This document raises no new security considerations.
7. IANA Considerations
This document defines a new C-type of 2, forward/reverse interface ID
for IPv6 networks, for the LSP_TUNNEL_INTERFACE_ID object.
This document also defines the new subobject type of 5, unnumbered
interface ID for IPv6 network, for the EXPLICIT_ROUTE object and the
ROUTE_RECORD object.
8. References
8.1 Normative References
[RFC3477] K.Kompella and Y.Rekhter, "Signalling Unnumbered Links in
Resource ReSerVation Protocol - Traffic Engineering
(RSVP-TE)", RFC3477, January 2003.
[OSPFv3-TE]
K. Ishiguro and T. Takada, "Traffic Engineering Extensions
to OSPF version 3", draft-ietf-ospf-ospfv3-traffic-02.txt,
July 2004 (work in progress).
[ISIS-TE] J. Harrison, J. Berger and M. Bartlett, "IPv6 Traffic
Engineering in IS-IS", draft-ietf-isis-ipv6-te-00.txt,
January 2005 (work in progress).
8.2 Informative References
[LSP-HIER]
Kompella, K. and Y. Rekhter, "LSP Hierarchy with
Generalized MPLS TE" (work in progress).
[LINK-BUNDLE]
Kompella, K., Rekhter, Y. and L. Berger, "Link Bundling
in MPLS Traffic Engineering" (work in progress).
Davey and Neate Internet Draft [Page 5]
Internet Draft Signalling Unnumbered Links in IPv6 February 2005
9. Authors' Address
Alan Davey
Data Connection Ltd
100 Church Street
EN2 6BQ
U.K.
Phone: +44 20 8366 1177
Email: alan.davey@dataconnection.com
Nic Neate
Data Connection Ltd
100 Church Street
EN2 6BQ
U.K.
Phone: +44 20 8366 1177
Email: nic.neate@dataconnection.com
10. Full Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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.
This document may not be modified, and derivative works of it may
not be created, except to publish it as an RFC and to translate it
into languages other than English.
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights 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; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in IETF Documents can be
found in BCP 78 and BCP 79.
Davey and Neate Internet Draft [Page 6]
Internet Draft Signalling Unnumbered Links in IPv6 February 2005
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Davey and Neate Internet Draft [Page 7]
