draft-ietf-lisp-ms-09.txt   draft-ietf-lisp-ms-10.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: January 1, 2012 June 30, 2011 Expires: January 8, 2012 July 7, 2011
LISP Map Server LISP Map Server
draft-ietf-lisp-ms-09.txt draft-ietf-lisp-ms-10.txt
Abstract Abstract
This draft describes the LISP Map Server (LISP-MS), a computing This draft describes the LISP Map Server (LISP-MS), a computing
system which provides a simplified LISP protocol interface as a system which provides a simplified LISP protocol interface as a
"front end" to the Endpoint-ID (EID) to Routing Locator (RLOC) "front end" to the Endpoint-ID (EID) to Routing Locator (RLOC)
mapping database and associated virtual network of LISP protocol mapping database and associated virtual network of LISP protocol
elements. elements.
The purpose of the Map Server is to reduce implementation and The purpose of the Map Server is to reduce implementation and
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 January 1, 2012. This Internet-Draft will expire on January 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 14 skipping to change at page 15, line 14
7. Security Considerations 7. Security Considerations
The 2-way nonce exchange documented in [LISP] can be used to avoid The 2-way nonce exchange documented in [LISP] can be used to avoid
ITR spoofing attacks. 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-160 [RFC2104] and should support use of HMAC-SHA-256-128
[RFC4634] (SHA-256 truncated to 128 bits). [RFC6234] (SHA-256 truncated to 128 bits).
During experimental and prototype deployment, authentication key During experimental and prototype deployment, authentication key
changes will be manual. Should LISP and its components be considered changes will be manual. Should LISP and its components be considered
for IETF standardization, further work will be required to follow the for IETF standardization, further work will be required to follow the
BCP 107 [RFC4107] recommendations on automated key management. BCP 107 [RFC4107] recommendations on automated key 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.
skipping to change at page 16, line 24 skipping to change at page 16, line 24
"Locator/ID Separation Protocol (LISP)", "Locator/ID Separation Protocol (LISP)",
draft-ietf-lisp-14.txt (work in progress), June 2011. draft-ietf-lisp-14.txt (work in progress), June 2011.
[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.
[RFC4634] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms [RFC6234] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms
(SHA and HMAC-SHA)", RFC 4634, July 2006. (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.
[I-D.murphy-bgp-secr] [I-D.murphy-bgp-secr]
Murphy, S., "BGP Security Analysis", Murphy, S., "BGP Security Analysis",
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 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/