Network Working Group D. Lewis
Internet-Draft D. Meyer
Intended status: Experimental V. Fuller
Expires: November 2, 2008 Cisco Systems, Inc.
May 1, 2008
LISP EID Block
draft-meyer-lisp-eid-block-01.txt
Status of this Memo
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.
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.
This Internet-Draft will expire on November 2, 2008.
Abstract
This is a direction to IANA to allocate a /8 IPv6 prefix for use with
the Locator/ID Separation Protocol (LISP) and LISP Alternative
Topology (LISP+ALT) mapping system.
Lewis, et al. Expires November 2, 2008 [Page 1]
Internet-Draft LISP EID Block May 2008
Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . . . 7
Lewis, et al. Expires November 2, 2008 [Page 2]
Internet-Draft LISP EID Block May 2008
1. Requirements Notation
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 [RFC2119].
2. Introduction
This is a direction to IANA to allocate a /8 IPv6 prefix for use with
the Locator/ID Separation Protocol (LISP) [LISP] and LISP Alternative
Topology (LISP+ALT) [LISP+ALT] mapping system. This block will be
used as global Endpoint ID (EID) space (Section 3) for the LISP+ALT
mapping system.
It is proposed that the IANA allocate 0100::/8 for this purpose.
3. Definition of Terms
LISP+ALT operates on two name spaces and introduces a new network
element, the LISP+ALT Router (see below). This section provides
high-level definitions of the LISP+ALT name spaces, network elements,
and message types.
The LISP Alternative Topology (LAT): The virtual overlay network
made up of Generic Routing Encapsulation (GRE) tunnels between EID
Prefix Aggregators. The Border Gateway Protocol (BGP) runs
between LISP+ALT routers and is used to carry reachability
information for EID prefixes.
Legacy Internet: The portion of the Internet which does not run LISP
and does not participate in LISP+ALT.
LISP+ALT Router: The devices which run on the LAT. The LAT is a
static network built with GRE tunnels. LISP+ALT routers are
deployed in a hierarchy which matches the EID prefix allocation
hierarchy. LISP+ALT routers at each level in the this hierarchy
are responsible for aggregating all EID prefixes learned from
LISP+ALT routers logically "below" them and advertising summary
prefixes to the LISP+ALT routers logically "above" them. All
prefix learning and propagation between levels is done using BGP.
LISP+ALT routers at the lowest level, or "edge", of the LAT learn
EID prefixes either over a BGP or LISP TCP session to ETRs.
Lewis, et al. Expires November 2, 2008 [Page 3]
Internet-Draft LISP EID Block May 2008
The primary function of LISP+ALT routers is to provide a
lightweight forwarding infrastructure for LISP control-plane
messages (Map-Request and Map-Reply), and to transport data
packets when the packet has the same destination address in both
the inner (encapsulating) destination and outer destination
addresses ((i.e., a Data Probe packet).
Endpoint ID (EID): A 32- or 128-bit value used in the source and
destination fields of the first (most inner) LISP header of a
packet. A packet that is emitted by a system contains EIDs in its
headers and LISP headers are prepended only when the packet
reaches an Ingress Tunnel Router (ITR) on the data path to the
destination EID.
In LISP+ALT, EID-prefixes MUST BE assigned in a hierarchical
manner (in power-of-two) such that they can be aggregated by LISP+
ALT routers. In addition, a site may have site-local structure in
how EIDs are topologically organized (subnetting) for routing
within the site; this structure is not visible to the global
routing system.
EID-Prefix Aggregate: A set of EID-prefixes said to be aggregatable
in the [RFC4632] sense. That is, an EID-Prefix aggregate is
defined to be a single contiguous power-of-two EID-prefix block.
Such a block is characterized by a prefix and a length.
Routing Locator (RLOC): An IP address of an egress tunnel router
(ETR). It is the output of a EID-to-RLOC mapping lookup. An EID
maps to one or more RLOCs. Typically, RLOCs are numbered from
topologically-aggregatable blocks that are assigned to a site at
each point to which it attaches to the global Internet; where the
topology is defined by the connectivity of provider networks,
RLOCs can be thought of as Provider Aggregatable (PA) addresses.
Note that in LISP+ALT, RLOCs are not carried by LISP+ALT routers.
EID-to-RLOC Mapping: A binding between an EID and the RLOC-set that
can be used to reach the EID. The term "mapping" refers to an
EID-to-RLOC mapping.
EID Prefix Reachability: An EID prefix is said to be "reachable" if
one or more of its locators are reachable. That is, an EID prefix
is reachable if the ETR (or its proxy) that is authoritative for a
given EID-to-RLOC mapping is reachable.
Default Mapping: A Default Mapping is a mapping entry for EID-
prefix 0.0.0.0/0. It maps to a locator-set used for all EIDs in
the Internet. If there is a more specific EID-prefix in the
mapping cache it overrides the Default Mapping entry. The Default
Lewis, et al. Expires November 2, 2008 [Page 4]
Internet-Draft LISP EID Block May 2008
Mapping route can be learned by configuration or from a Map-Reply
message.
Default Route: A Default Route in the context of LISP+ALT is a EID-
prefix value of 0.0.0.0/0 which is advertised by BGP on top of the
LAT. The Default Route is used to realize a path for Data Probe
and Map-Request packets.
4. Security Considerations
This document introduces no new security considerations.
5. Acknowledgments
Marla Azinger, Chris Morrow, and Peter Schoenmaker all made
insightful comments on early versions of this draft.
6. IANA Considerations
This document instructs the IANA to allocate a /8 IPv6 prefix for
LISP and LISP+ALT deployment. It is proposed that the IANA allocate
0100::/8 for this purpose.
7. References
7.1. Normative References
[LISP] Farinacci, D., Fuller, V., Oran, D., and D. Meyer,
"Locator/ID Separation Protocol (LISP)",
draft-farinacci-lisp-07 (work in progress), Apr 2008.
[LISP+ALT] Farinacci, D., Fuller, V., and D. Meyer, "LISP
Alternative Topology (LISP+ALT)",
draft-fuller-lisp-alt-02 (work in progress), Apr
2008.
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, February 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing
Lewis, et al. Expires November 2, 2008 [Page 5]
Internet-Draft LISP EID Block May 2008
(CIDR): The Internet Address Assignment and Aggregation
Plan", BCP 122, RFC 4632, August 2006.
7.2. Informative References
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC2993] Hain, T., "Architectural Implications of NAT", RFC 2993,
November 2000.
Authors' Addresses
Darrel Lewis
Cisco Systems, Inc.
Email: darlewis@cisco.com
David Meyer
Cisco Systems, Inc.
Email: dmm@cisco.com
Vince Fuller
Cisco Systems, Inc.
Email: vaf@cisco.com
Lewis, et al. Expires November 2, 2008 [Page 6]
Internet-Draft LISP EID Block May 2008
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
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, THE IETF TRUST 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.
Intellectual Property
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 RFC documents can be
found in BCP 78 and BCP 79.
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.
Lewis, et al. Expires November 2, 2008 [Page 7]