draft-ietf-lisp-ms-05.txt   draft-ietf-lisp-ms-06.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: October 28, 2010 April 26, 2010 Expires: April 21, 2011 October 18, 2010
LISP Map Server LISP Map Server
draft-ietf-lisp-ms-05.txt draft-ietf-lisp-ms-06.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 simple LISP protocol interface as a "front system which provides a simple LISP protocol interface as a "front
end" to the Endpoint-ID (EID) to Routing Locator (RLOC) mapping end" to the Endpoint-ID (EID) to Routing Locator (RLOC) mapping
database and associated virtual network of LISP protocol elements. database and associated virtual network of LISP protocol elements.
The purpose of the Map-Server is to simplify the implementation and The purpose of the Map-Server is to simplify the implementation and
operation of LISP Ingress Tunnel Routers (ITRs) and Egress Tunnel operation of LISP Ingress Tunnel Routers (ITRs) and Egress Tunnel
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 October 28, 2010. This Internet-Draft will expire on April 21, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 3, line 33 skipping to change at page 3, line 33
Conceptually, LISP Map-Servers share some of the same basic Conceptually, LISP Map-Servers share some of the same basic
configuration and maintenance properties as Domain Name System (DNS) configuration and maintenance properties as Domain Name System (DNS)
[RFC1035] servers and caching resolvers. With this in mind, this [RFC1035] servers and caching resolvers. With this in mind, this
specification borrows familiar terminology (resolver and server) from specification borrows familiar terminology (resolver and server) from
the DNS specifications. the DNS 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, this is not intended to preclude the use of Map- Resolver operation, this is not intended to preclude the use of Map-
Servers and Map-Resolvers as a a standardized interface for ITRs and Servers and Map-Resolvers as a standardized interface for ITRs and
ETRs to access other mapping database systems. ETRs to access other mapping database systems.
2. Definition of Terms 2. Definition of Terms
Map-Server: a network infrastructure component which learns EID-to- Map-Server: a network infrastructure component which learns EID-to-
RLOC mapping entries from an authoritative source (typically, an RLOC mapping entries from an authoritative source (typically, an
ETR, through static configuration or another out-of-band mechanism ETR, through static configuration or another out-of-band mechanism
may be used). A Map-Server publishes these mappings in the may be used). A Map-Server publishes these mappings in the
distributed mapping database. distributed mapping database.
skipping to change at page 12, line 11 skipping to change at page 12, line 11
group or either S-BGP [I-D.murphy-bgp-secr] or soBGP group or either S-BGP [I-D.murphy-bgp-secr] or soBGP
[I-D.white-sobgparchitecture] should they be developed and widely [I-D.white-sobgparchitecture] should they be developed and widely
deployed. deployed.
7. References 7. References
7.1. Normative References 7.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-04.txt (work in progress), April 2010. draft-ietf-lisp-alt-05.txt (work in progress),
October 2010.
[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-07.txt (work in progress), April 2010. draft-ietf-lisp-09.txt (work in progress), October 2010.
[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.
[RFC2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96 within [RFC2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96 within
ESP and AH", RFC 2404, November 1998. ESP and AH", RFC 2404, November 1998.
[RFC4634] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms [RFC4634] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms
(SHA and HMAC-SHA)", RFC 4634, July 2006. (SHA and HMAC-SHA)", RFC 4634, July 2006.
skipping to change at page 12, line 45 skipping to change at page 12, line 46
draft-murphy-bgp-secr-04 (work in progress), draft-murphy-bgp-secr-04 (work in progress),
November 2001. November 2001.
[I-D.white-sobgparchitecture] [I-D.white-sobgparchitecture]
White, R., "Architecture and Deployment Considerations for White, R., "Architecture and Deployment Considerations for
Secure Origin BGP (soBGP)", Secure Origin BGP (soBGP)",
draft-white-sobgparchitecture-00 (work in progress), draft-white-sobgparchitecture-00 (work in progress),
May 2004. May 2004.
[LISP-MN] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "LISP [LISP-MN] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "LISP
Mobile Node Architecture", draft-meyer-lisp-mn-01.txt Mobile Node Architecture", draft-meyer-lisp-mn-03.txt
(work in progress), February 2010. (work in progress), August 2010.
[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.
Appendix A. Acknowledgments Appendix A. Acknowledgments
The authors would like to thank Greg Schudel, Darrel Lewis, John The authors would like to thank Greg Schudel, Darrel Lewis, John
Zwiebel, Andrew Partan, Dave Meyer, Isidor Kouvelas, Jesper Skriver, Zwiebel, Andrew Partan, Dave Meyer, Isidor Kouvelas, Jesper Skriver,
and members of the lisp@ietf.org mailing list for their feedback and and members of the lisp@ietf.org mailing list for their feedback and
 End of changes. 7 change blocks. 
8 lines changed or deleted 9 lines changed or added

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