draft-ietf-lisp-ms-14.txt   draft-ietf-lisp-ms-15.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: June 18, 2012 December 16, 2011 Expires: July 14, 2012 January 11, 2012
LISP Map Server Interface LISP Map Server Interface
draft-ietf-lisp-ms-14.txt draft-ietf-lisp-ms-15.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 June 18, 2012. This Internet-Draft will expire on July 14, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 13, line 26 skipping to change at page 13, line 26
During experimental and prototype deployment, all authentication key During experimental and prototype deployment, all authentication key
configuration will be manual. Should LISP and its components be configuration will be manual. Should LISP and its components be
considered for IETF standardization, further work will be required to considered for IETF standardization, further work will be required to
follow the BCP 107 [RFC4107] recommendations on automated key follow the BCP 107 [RFC4107] recommendations on automated key
management. management.
As noted in Section 4.2, a Map Server should verify that all EID- As noted in Section 4.2, a Map Server should verify that all EID-
prefixes registered by an ETR match configuration stored on the Map prefixes registered by an ETR match configuration stored on the Map
Server. Server.
The currently-defined authentication mechanism for Map-Register
messages does not provide protection against "replay" attacks by a
"man-in-the-middle". Additional work is needed in this area.
[LISP-SEC] defines a proposed mechanism for providing origin [LISP-SEC] defines a proposed mechanism for providing origin
authentication, integrity, anti-reply protection, and prevention of authentication, integrity, anti-replay protection, and prevention of
man-in-the-middle and "overclaiming" attacks on the Map-Request/ man-in-the-middle and "overclaiming" attacks on the Map-Request/
Map-Reply exchange. Work is ongoing on this and other proposals for Map-Reply exchange. Work is ongoing on this and other proposals for
resolving these open security issues resolving these open security issues
While beyond the scope of securing an individual Map Server or Map While beyond the scope of securing an individual Map Server or Map
Resolver, it should be noted that a BGP-based LISP+ALT network (if Resolver, it should be noted that a BGP-based LISP+ALT network (if
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. October 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-15.txt (work in progress), July 2011. draft-ietf-lisp-20.txt (work in progress), January 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.
 End of changes. 7 change blocks. 
6 lines changed or deleted 10 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/