Network Working Group D. Farinacci
Internet-Draft D. Meyer
Intended status: Experimental cisco Systems
Expires: October 15, 2010 J. Snijders
InTouch
April 13, 2010
LISP Canonical Address Format (LCAF)
draft-farinacci-lisp-lcaf-00
Abstract
This draft defines a canonical address format encoding used in LISP
control messages and in the encoding of lookup keys for the LISP
Mapping Database System.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and 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 October 15, 2010.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
Farinacci, et al. Expires October 15, 2010 [Page 1]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
3. LISP Canonical Address Format Encodings . . . . . . . . . . . 5
4. LISP Canonical Address Applications . . . . . . . . . . . . . 6
4.1. Segmentation using LISP . . . . . . . . . . . . . . . . . 6
4.2. Carrying AS Numbers in the Mapping Database . . . . . . . 7
4.3. Binding IPv4 and IPv6 Addresses . . . . . . . . . . . . . 8
4.4. Layer-2 VPNs . . . . . . . . . . . . . . . . . . . . . . . 9
4.5. ASCII Names in the Mapping Database . . . . . . . . . . . 9
4.6. Convey Application Specific Data . . . . . . . . . . . . . 10
4.7. Using Recursive LISP Canonical Address Encodings . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1. Normative References . . . . . . . . . . . . . . . . . . . 14
7.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
Farinacci, et al. Expires October 15, 2010 [Page 2]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
1. Introduction
The LISP architecture and protocols [LISP] introduces two new
numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
(RLOCs) which are intended to replace most use of IP addresses on the
Internet. To provide flexibility for current and future
applications, these values can be encoded in LISP control messages
using a general syntax that includes Address Family Identifier (AFI),
length, and value fields.
Currently defined AFIs include IPv4 and IPv6 addresses, which are
formatted according to code-points assigned in [AFI] as follows:
IPv4 Encoded Address:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 Encoded Address:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 2 | IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This document describes the currently-defined AFIs along with their
encodings and introduces the LISP Canonical Address Format (LCAF)
that can be used to define the LISP-specific encodings for arbitrary
AFI values.
Farinacci, et al. Expires October 15, 2010 [Page 3]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
2. Definition of Terms
Address Family Identifier (AFI): a term used to describe an address
encoding in a packet. An address family currently defined for
IPv4 or IPv6 addresses. See [AFI] and [RFC1700] for details. The
reserved AFI value of 0 is used in this specification to indicate
an unspecified encoded address where the the length of the address
is 0 bytes following the 16-bit AFI value of 0.
Unspecified Address 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 0 | <nothing follows AFI=0> |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value
used in the source and destination address fields of the first
(most inner) LISP header of a packet. The host obtains a
destination EID the same way it obtains a destination address
today, for example through a DNS lookup or SIP exchange. The
source EID is obtained via existing mechanisms used to set a
host's "local" IP address. An EID is allocated to a host from an
EID-prefix block associated with the site where the host is
located. An EID can be used by a host to refer to other hosts.
EIDs MUST NOT be used as LISP RLOCs. Note that EID blocks may be
assigned in a hierarchical manner, independent of the network
topology, to facilitate scaling of the mapping database. In
addition, an EID block assigned to a site may have site-local
structure (subnetting) for routing within the site; this structure
is not visible to the global routing system. When used in
discussions with other Locator/ID separation proposals, a LISP EID
will be called a "LEID". Throughout this document, any references
to "EID" refers to an LEID.
Routing Locator (RLOC): the IPv4 or IPv6 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 PA addresses.
Multiple RLOCs can be assigned to the same ETR device or to
multiple ETR devices at a site.
Farinacci, et al. Expires October 15, 2010 [Page 4]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
3. LISP Canonical Address Format Encodings
IANA has assigned AFI value 16387 (0x4003) to the LISP architecture
and protocols. This specification defines the encoding format of the
LISP Canonical Address (LCA).
The first 4 bytes of an LISP Canonical Address are followed by a
variable length of fields:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Flags | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Flags: this 4-bit field is for future definition and use. For now,
set to zero on transmission and ignored on receipt.
Type: this 4-bit field is specific to the LISP Canonical Address
formatted encodings, values are:
Type 0: Null Body Type
Type 1: Instance ID Type
Type 2: AS Number Type
Type 3: AFI List Type
Type 4: Application Data Type
Length: this 8-bit field is in units of bytes and covers all of the
LISP Canonical Address payload, the AFI=16387, Flags, Type, and
Length fields. The Length field cannot be less than 4. When it
is set to 4, the Type must be 0 (the Null Body Type). The Null
Body Type can be used to convey LCA Flags. When the LCA Flags are
all set to 0, the encoding is similar to an unspecified address
encoding of an AFI=0 address.
Farinacci, et al. Expires October 15, 2010 [Page 5]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
4. LISP Canonical Address Applications
4.1. Segmentation using LISP
When multiple organizations inside of a LISP site are using private
addresses [RFC1918] as EID-prefixes, their address spaces must remain
segregated due to possible address duplication. An Instance ID in
the address encoding can aid in making the entire AFI based address
unique.
Another use for the Instance ID LISP Canonical Address Format is when
creating multiple segmented VPNs inside of a LISP site where keeping
EID-prefix based subnets is desirable.
Instance ID LISP Canonical Address 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Flags | 1 | 4 + 4 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Instance ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of the AFI address that follows
including the AFI field itself.
Instance ID: the low-order 24-bits that can go into a LISP data
header when the I-bit is set. See [LISP] for details.
AFI = x: x can be any AFI value from [AFI].
This LISP Canonical Address Type can be used to encode either EID or
RLOC addresses.
Farinacci, et al. Expires October 15, 2010 [Page 6]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
4.2. Carrying AS Numbers in the Mapping Database
When an AS number is stored in the LISP Mapping Database System for
either policy or documentation reasons, it can be encoded in a LISP
Canonical Address.
AS Number LISP Canonical Address 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Flags | 2 | 4 + 4 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AS Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of the AFI address that follows
including the AFI field itself.
AS Number: the 32-bit AS number of the autonomous system that has
been assigned either the EID or RLOC that follows.
AFI = x: x can be any AFI value from [AFI].
This LISP Canonical Address Type can be used to encode either EID or
RLOC addresses. The former is used to describe the LISP-ALT AS
number the EID-prefix for the site is being carried for. The latter
is used to describe the AS that is carrying RLOC based prefixes in
the underlying routing system.
Farinacci, et al. Expires October 15, 2010 [Page 7]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
4.3. Binding IPv4 and IPv6 Addresses
When header translation between IPv4 and IPv6 is desirable an LISP
Canonical Address can use the AFI List Type to carry multiple AFIs in
one LCA AFI.
Binded Address LISP Canonical Address 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Flags | 3 | 4+2+4+2+16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address | AFI = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes is fixed at 28 when IPv4 and IPv6 AFI
encoded addresses are used.
This type of address format can be included in a Map-Request when the
address is being used as an EID, but the Mapping Database System
lookup destination can use only the IPv4 address. This is so a
Mapping Database Service Transport System, such as LISP-ALT [ALT],
can use the Map-Request destination address to route the control
message to the desired LISP site.
Farinacci, et al. Expires October 15, 2010 [Page 8]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
4.4. Layer-2 VPNs
When MAC addresses are stored in the LISP Mapping Database System,
the AFI List Type can be used to carry AFI 6.
MAC Address LISP Canonical Address 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Flags | 3 | 4 + 2 + 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 6 | Layer-2 MAC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... Layer-2 MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes is fixed at 12 when MAC address AFI encoded
addresses are used.
This address format can be used to connect layer-2 domains together
using LISP over an IPv4 or IPv6 core network to create a layer-2 VPN.
In this use-case, a MAC address is being used as an EID, and the
locator-set that this EID maps to can be an IPv4 or IPv6 RLOCs, or
even another MAC address being used as an RLOC.
4.5. ASCII Names in the Mapping Database
If DNS names or URIs are stored in the LISP Mapping Database System,
the AFI List Type can be used to carry an ASCII string where it is
delimited by length 'n' of the LCA Length encoding.
ASCII LISP Canonical Address 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Flags | 3 | 4 + 2 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 17 | DNS Name or URI ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes AFI=17 field and the null-terminated
ASCII string (the last byte of 0 is included).
Farinacci, et al. Expires October 15, 2010 [Page 9]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
4.6. Convey Application Specific Data
When a locator-set needs to be conveyed based on the type of
application or the Per-Hop Behavior (PHB) of a packet, the
Application Data Type can be used.
Application Data LISP Canonical Address 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Flags | 4 | 4 + 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP TOS, IPv6 TC, or Flow Label | Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Port | Remote Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes is fixed at 12.
IP TOS, IPv6 TC, or Flow Label: this field stores the 8-bit IPv4 TOS
field used in an IPv4 header, the 8-bit IPv6 Traffic Class or Flow
Label used in an IPv6 header.
Local Port/Remote Port: these fields are from the TCP, UDP, or SCTP
transport header.
Farinacci, et al. Expires October 15, 2010 [Page 10]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
4.7. Using Recursive LISP Canonical Address Encodings
When any combination of above is desirable, the AFI List Type value
can be used to carry within the LCA AFI another LCA AFI.
Recursive LISP Canonical Address 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Flags | 3 | 4+4+8+2+4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Flags | 4 | 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP TOS, IPv6 QQS or Flow Label | Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Port | Remote Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes is fixed at 22 when an AFI=1 IPv4 address is
included.
This format could be used by a Mapping Database Transport System,
such as LISP-ALT [ALT], where the AFI=1 IPv4 address is used as an
EID and placed in the Map-Request destination address by the sending
LISP system. The ALT system can deliver the Map-Request to the LISP
destination site independent of the Application Data Type AFI payload
values. When this AFI is processed by the destination LISP site, it
can return different locator-sets based on the type of application or
level of service that is being requested.
Farinacci, et al. Expires October 15, 2010 [Page 11]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
5. Security Considerations
There are no security considerations for this specification. The
security considerations are documented for the protocols that use
LISP Canonical Addressing. Refer to the those relevant
specifications.
Farinacci, et al. Expires October 15, 2010 [Page 12]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
6. IANA Considerations
The Address Family AFI definitions from [AFI] only allocate code-
points for the AFI value itself. The length of the address or entity
that follows is not defined and is implied based conventional
experience. Where LISP uses LISP Canonical Addresses specifically,
the address length definitions will be in this specification and take
precedent over any other specification.
Farinacci, et al. Expires October 15, 2010 [Page 13]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
7. References
7.1. Normative References
[RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700,
October 1994.
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, February 1996.
7.2. Informative References
[AFI] IANA, "Address Family Identifier (AFIs)", ADDRESS FAMILY
NUMBERS http://www.iana.org/numbers.html, Febuary 2007.
[ALT] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis, "LISP
Alternative Topology (LISP+ALT)",
draft-ietf-lisp-alt-04.txt (work in progress), March 2010.
[LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
"Locator/ID Separation Protocol (LISP)",
draft-ietf-lisp-07.txt (work in progress), April 2010.
Farinacci, et al. Expires October 15, 2010 [Page 14]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
Appendix A. Acknowledgments
The authors would like to thank Vince Fuller, Gregg Schudel, and
Jesper Skriver for their technical and editorial commentary.
Thanks also goes to Terry Manderson for assistance obtaining a LISP
AFI value from IANA.
Farinacci, et al. Expires October 15, 2010 [Page 15]
Internet-Draft LISP Canonical Address Format (LCAF) April 2010
Authors' Addresses
Dino Farinacci
cisco Systems
Tasman Drive
San Jose, CA 95134
USA
Email: dino@cisco.com
Dave Meyer
cisco Systems
170 Tasman Drive
San Jose, CA
USA
Email: dmm@cisco.com
Job Snijders
InTouch
A Middenweg 76
Amsterdam, Netherlands
Email: job@instituut.net
Farinacci, et al. Expires October 15, 2010 [Page 16]