draft-ietf-lisp-lig-02.txt   draft-ietf-lisp-lig-03.txt 
Network Working Group D. Farinacci Network Working Group D. Farinacci
Internet-Draft D. Meyer Internet-Draft D. Meyer
Intended status: Experimental cisco Systems Intended status: Experimental cisco Systems
Expires: October 7, 2011 April 5, 2011 Expires: January 10, 2012 July 9, 2011
LISP Internet Groper (LIG) LISP Internet Groper (LIG)
draft-ietf-lisp-lig-02 draft-ietf-lisp-lig-03
Abstract Abstract
A simple tool called the LISP Internet Groper or 'lig' can be used to A simple tool called the LISP Internet Groper or 'lig' can be used to
query the LISP mapping database. This draft describes how it works. query the LISP mapping database. This draft describes how it works.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on January 10, 2012.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 7, 2011.
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
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
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 5 3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 5
4. Basic Overview . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Basic Overview . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Implementation Details . . . . . . . . . . . . . . . . . . . . 9 5. Implementation Details . . . . . . . . . . . . . . . . . . . . 9
5.1. LISP Router Implementation . . . . . . . . . . . . . . . . 9 5.1. LISP Router Implementation . . . . . . . . . . . . . . . . 9
5.2. Public Domain Host Implementation . . . . . . . . . . . . 10 5.2. Public Domain Host Implementation . . . . . . . . . . . . 10
6. Testing the ALT . . . . . . . . . . . . . . . . . . . . . . . 12 6. Testing the ALT . . . . . . . . . . . . . . . . . . . . . . . 12
7. Future Enhancements . . . . . . . . . . . . . . . . . . . . . 13 7. Future Enhancements . . . . . . . . . . . . . . . . . . . . . 13
8. Deployed Network Diagnostic Tools . . . . . . . . . . . . . . 14 8. Deployed Network Diagnostic Tools . . . . . . . . . . . . . . 14
9. Security Considerations . . . . . . . . . . . . . . . . . . . 15 9. Security Considerations . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
10.1. Normative References . . . . . . . . . . . . . . . . . . . 16 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
10.2. Informative References . . . . . . . . . . . . . . . . . . 16 11.1. Normative References . . . . . . . . . . . . . . . . . . . 17
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 17 11.2. Informative References . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Requirements Notation 1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
LISP [LISP] specifies an architecture and mechanism for replacing the LISP [LISP] specifies an architecture and mechanism for replacing the
skipping to change at page 16, line 5 skipping to change at page 16, line 5
UPC, shows a geographical map indicating where each LISP site UPC, shows a geographical map indicating where each LISP site
resides. resides.
9. Security Considerations 9. Security Considerations
The use of lig does not affect the security of the LISP The use of lig does not affect the security of the LISP
infrastructure as it is simply a tool that facilities diagnostic infrastructure as it is simply a tool that facilities diagnostic
querying. See [LISP], [ALT], and [LISP-MS] for descriptions of the querying. See [LISP], [ALT], and [LISP-MS] for descriptions of the
security properties of the LISP infrastructure. security properties of the LISP infrastructure.
10. References 10. IANA Considerations
10.1. Normative References This document makes no request of the IANA.
11. References
11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
10.2. Informative References 11.2. Informative 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-ietfr-lisp-alt-06.txt (work in progress), draft-ietfr-lisp-alt-06.txt (work in progress).
March 2011.
[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-03.txt (work in progress), draft-meyer-lisp-cons-04.txt (work in progress).
November 2007.
[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-12.txt (work in progress), April 2011. draft-ietf-lisp-15.txt (work in progress).
[LISP-LIG] [LISP-LIG]
Farinacci, D. and D. Meyer, "LISP Internet Groper (LIG)", Farinacci, D. and D. Meyer, "LISP Internet Groper (LIG)",
draft-farinacci-lisp-lig-02.txt (work in progress), draft-farinacci-lisp-lig-02.txt (work in progress).
February 2010.
[LISP-MS] Farinacci, D. and V. Fuller, "LISP Map Server", [LISP-MS] Farinacci, D. and V. Fuller, "LISP Map Server",
draft-ietf-lisp-ms-07.txt (work in progress), March 2011. draft-ietf-lisp-ms-10.txt (work in progress).
[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.
Appendix A. Acknowledgments Appendix A. Acknowledgments
Thanks and kudos to John Zwiebel, Andrew Partan, Darrel Lewis, and Thanks and kudos to John Zwiebel, Andrew Partan, Darrel Lewis, and
Vince Fuller for providing critical feedback on the lig design and Vince Fuller for providing critical feedback on the lig design and
prototype implementations. These folks as well as all the people on prototype implementations. These folks as well as all the people on
lisp-beta@external.cisco.com who tested lig functionality and lisp-beta@external.cisco.com who tested lig functionality and
continue to do so, we extend our sincere thanks. continue to do so, we extend our sincere thanks.
This working group draft is based on individual contribution This working group draft is based on individual contribution
 End of changes. 16 change blocks. 
32 lines changed or deleted 27 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/