draft-ietf-lisp-ms-12.txt   draft-ietf-lisp-ms-13.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: April 27, 2012 October 25, 2011 Expires: June 8, 2012 December 6, 2011
LISP Map Server Interface LISP Map Server Interface
draft-ietf-lisp-ms-12.txt draft-ietf-lisp-ms-13.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 April 27, 2012. This Internet-Draft will expire on June 8, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 15, line 13 skipping to change at page 15, line 13
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
to avoid ITR spoofing attacks. to avoid ITR spoofing attacks.
To publish an authoritative EID-to-RLOC mapping with a Map Server, an To publish an authoritative EID-to-RLOC mapping with a Map Server, an
ETR includes authentication data that is a hash of the message using ETR includes authentication data that is a hash of the message using
pair-wise shared key. An implementation must support use of HMAC- pair-wise shared key. An implementation must support use of HMAC-
SHA-1-160 [RFC2104] and should support use of HMAC-SHA-256-128 SHA-1-96 [RFC2104] and should support use of HMAC-SHA-256-128
[RFC6234] (SHA-256 truncated to 128 bits). [RFC6234] (SHA-256 truncated to 128 bits).
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
 End of changes. 4 change blocks. 
4 lines changed or deleted 4 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/