draft-ietf-lisp-ms-15.txt   draft-ietf-lisp-ms-16.txt 
Network Working Group V. Fuller Network Working Group V. Fuller
Internet-Draft D. Farinacci Internet-Draft D. Farinacci
Intended status: Experimental cisco Systems Intended status: Experimental cisco Systems
Expires: July 14, 2012 January 11, 2012 Expires: September 5, 2012 March 4, 2012
LISP Map Server Interface LISP Map Server Interface
draft-ietf-lisp-ms-15.txt draft-ietf-lisp-ms-16.txt
Abstract Abstract
This draft describes the Maping Service for the Locator Identifier This draft describes the Maping Service for the Locator Identifier
Separation Protocol (LISP), implemented by two new types of LISP- Separation Protocol (LISP), implemented by two new types of LISP-
speaking devices, the LISP Map Resolver and LISP Map Server, that speaking devices, the LISP Map Resolver and LISP Map Server, that
provides a simplified "front end" to for one or more Endpoint ID to provides a simplified "front end" to for one or more Endpoint ID to
Routing Locator mapping databases. Routing Locator mapping databases.
By using this service interface and communicating with Map Resolvers By using this service interface and communicating with Map Resolvers
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 14, 2012. This Internet-Draft will expire on September 5, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 5 skipping to change at page 3, line 38
to DNS caching resolvers. With this in mind, this specification to DNS caching resolvers. With this in mind, this specification
borrows familiar terminology (resolver and server) from the DNS borrows familiar terminology (resolver and server) from the DNS
specifications. specifications.
Note that while this document assumes a LISP+ALT database mapping Note that while this document assumes a LISP+ALT database mapping
infrastructure to illustrate certain aspects of Map Server and Map infrastructure to illustrate certain aspects of Map Server and Map
Resolver operation, the Mapping Service interface can (and likely Resolver operation, the Mapping Service interface can (and likely
will) be used by ITRs and ETRs to access other mapping database will) be used by ITRs and ETRs to access other mapping database
systems as the LISP infrastructure evolves. systems as the LISP infrastructure evolves.
Section 5 of this document notes a number of issues with the Map
Server and Map Resolver design that are not yet completely understood
and are subjects of further experimentation.
The LISP Mapping Service is an important component of the LISP
toolset. Issues and concerns about the deployment of LISP for
Internet traffic are discussed in [LISP].
2. Definition of Terms 2. Definition of Terms
Map Server: a network infrastructure component which learns of EID- Map Server: a network infrastructure component which learns of EID-
prefix mapping entries from an ETR, via the registration mechanism prefix mapping entries from an ETR, via the registration mechanism
described below, or some other authoritative source if one exists. described below, or some other authoritative source if one exists.
A Map Server publishes these EID-prefixes in a mapping database. A Map Server publishes these EID-prefixes in a mapping database.
Map Resolver: a network infrastructure component which accepts LISP Map Resolver: a network infrastructure component which accepts LISP
Encapsulated Map-Requests, typically from an ITR, determines Encapsulated Map-Requests, typically from an ITR, determines
whether or not the destination IP address is part of the EID whether or not the destination IP address is part of the EID
skipping to change at page 11, line 26 skipping to change at page 11, line 26
mechanisms for detecting and refreshing or removing stale, cached mechanisms for detecting and refreshing or removing stale, cached
information information
o Deployability and complexity trade-offs of implementing stronger o Deployability and complexity trade-offs of implementing stronger
security measures in both EID-prefix registration and Map-Request/ security measures in both EID-prefix registration and Map-Request/
Map-Reply processing Map-Reply processing
o Requirements for additional state in the registration process o Requirements for additional state in the registration process
between Map Servers and ETRs between Map Servers and ETRs
A discussion of other issues surrounding LISP deployment may also be
found in Section 15 of [LISP].
The authors expect that experimentation on the LISP pilot network The authors expect that experimentation on the LISP pilot network
will help answer open questions surrounding these and other issues. will help answer open questions surrounding these and other issues.
6. IANA Considerations 6. IANA Considerations
This document makes no request of the IANA. This document makes no request of the IANA.
7. Security Considerations 7. Security Considerations
The 2-way LISP header nonce exchange documented in [LISP] can be used The 2-way LISP header nonce exchange documented in [LISP] can be used
skipping to change at page 14, line 12 skipping to change at page 14, line 12
ALT is used as the mapping database infrastructure) can take ALT is used as the mapping database infrastructure) can take
advantage standards work on adding security to BGP. advantage standards work on adding security to BGP.
8. References 8. References
8.1. Normative References 8.1. Normative References
[ALT] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "LISP [ALT] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "LISP
Alternative Topology (LISP-ALT)", Alternative Topology (LISP-ALT)",
draft-ietf-lisp-alt-10.txt (work in progress), draft-ietf-lisp-alt-10.txt (work in progress),
October 2011. December 2011.
[LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, [LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
"Locator/ID Separation Protocol (LISP)", "Locator/ID Separation Protocol (LISP)",
draft-ietf-lisp-20.txt (work in progress), January 2012. draft-ietf-lisp-22.txt (work in progress), February 2012.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[RFC2104] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed- [RFC2104] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed-
Hashing for Message Authentication", RFC 2104, Hashing for Message Authentication", RFC 2104,
February 1997. February 1997.
[RFC6234] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms [RFC6234] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms
(SHA and SHA-based HMAC and HKDF)", RFC 6234, May 2011. (SHA and SHA-based HMAC and HKDF)", RFC 6234, May 2011.
8.2. Informative References 8.2. Informative References
[CONS] Farinacci, D., Fuller, V., and D. Meyer, "LISP-CONS: A [CONS] Farinacci, D., Fuller, V., and D. Meyer, "LISP-CONS: A
Content distribution Overlay Network Service for LISP", Content distribution Overlay Network Service for LISP",
draft-meyer-lisp-cons-04.txt (work in progress), draft-meyer-lisp-cons-04.txt (work in progress),
April 2008. April 2008.
[LISP-MN] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "LISP [LISP-MN] Farinacci, D., Lewis, D., Meyer, D., and C. White, "LISP
Mobile Node Architecture", draft-meyer-lisp-mn-05.txt Mobile Node Architecture", draft-meyer-lisp-mn-06.txt
(work in progress), May 2011. (work in progress), October 2011.
[LISP-SEC] [LISP-SEC]
Maino, F., Ermagan, V., Cabellos, A., Sanchez, D., and O. Maino, F., Ermagan, V., Cabellos, A., Sanchez, D., and O.
Bonaventure, "LISP-Security", draft-ietf-lisp-sec-00.txt Bonaventure, "LISP-Security", draft-ietf-lisp-sec-01.txt
(work in progress), July 2011. (work in progress), January 2012.
[NERD] Lear, E., "NERD: A Not-so-novel EID to RLOC Database", [NERD] Lear, E., "NERD: A Not-so-novel EID to RLOC Database",
draft-lear-lisp-nerd-08.txt (work in progress), draft-lear-lisp-nerd-08.txt (work in progress),
March 2010. March 2010.
[RFC4107] Bellovin, S. and R. Housley, "Guidelines for Cryptographic [RFC4107] Bellovin, S. and R. Housley, "Guidelines for Cryptographic
Key Management", BCP 107, RFC 4107, June 2005. Key Management", BCP 107, RFC 4107, June 2005.
Appendix A. Acknowledgments Appendix A. Acknowledgments
 End of changes. 9 change blocks. 
10 lines changed or deleted 21 lines changed or added

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