draft-farinacci-lisp-geo-04.txt   draft-farinacci-lisp-geo-05.txt 
Network Working Group D. Farinacci Network Working Group D. Farinacci
Internet-Draft lispers.net Internet-Draft lispers.net
Intended status: Experimental October 23, 2017 Intended status: Experimental April 16, 2018
Expires: April 26, 2018 Expires: October 18, 2018
LISP Geo-Coordinate Use-Cases LISP Geo-Coordinate Use-Cases
draft-farinacci-lisp-geo-04 draft-farinacci-lisp-geo-05
Abstract Abstract
This draft describes how Geo-Coordinates can be used in the LISP This draft describes how Geo-Coordinates can be used in the LISP
Architecture and Protocols. Architecture and Protocols.
Status of This Memo Status of This Memo
This Internet-Draft is submitted 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.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 26, 2018. This Internet-Draft will expire on October 18, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 2, line 19 skipping to change at page 2, line 19
3. Geo-Points in RLOC-records . . . . . . . . . . . . . . . . . 3 3. Geo-Points in RLOC-records . . . . . . . . . . . . . . . . . 3
4. Geo-Prefixes in EID-records and RLOC-records . . . . . . . . 3 4. Geo-Prefixes in EID-records and RLOC-records . . . . . . . . 3
5. Geo-Prefix and Geo-Point Encodings . . . . . . . . . . . . . 5 5. Geo-Prefix and Geo-Point Encodings . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 9 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 9
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 9 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 9
B.1. Changes to draft-farinacci-lisp-geo-04.txt . . . . . . . 9 B.1. Changes to draft-farinacci-lisp-geo-05.txt . . . . . . . 9
B.2. Changes to draft-farinacci-lisp-geo-03.txt . . . . . . . 9 B.2. Changes to draft-farinacci-lisp-geo-04.txt . . . . . . . 9
B.3. Changes to draft-farinacci-lisp-geo-02.txt . . . . . . . 9 B.3. Changes to draft-farinacci-lisp-geo-03.txt . . . . . . . 9
B.4. Changes to draft-farinacci-lisp-geo-01.txt . . . . . . . 9 B.4. Changes to draft-farinacci-lisp-geo-02.txt . . . . . . . 9
B.5. Changes to draft-farinacci-lisp-geo-00.txt . . . . . . . 10 B.5. Changes to draft-farinacci-lisp-geo-01.txt . . . . . . . 10
B.6. Changes to draft-farinacci-lisp-geo-00.txt . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The LISP architecture and protocols [RFC6830] introduces two new The LISP architecture and protocols [RFC6830] introduces two new
numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
(RLOCs) which are intended to replace most use of IP addresses on the (RLOCs) which are intended to replace most use of IP addresses on the
Internet. To provide flexibility for current and future Internet. To provide flexibility for current and future
applications, these values can be encoded in LISP control messages applications, these values can be encoded in LISP control messages
using a general syntax that includes Address Family Identifier (AFI) using a general syntax that includes Address Family Identifier (AFI)
skipping to change at page 8, line 39 skipping to change at page 8, line 39
acee-ospf-geo-location-05 (work in progress), October acee-ospf-geo-location-05 (work in progress), October
2017. 2017.
[I-D.chen-idr-geo-coordinates] [I-D.chen-idr-geo-coordinates]
Chen, E., Shen, N., and R. Raszuk, "Carrying Geo Chen, E., Shen, N., and R. Raszuk, "Carrying Geo
Coordinates in BGP", draft-chen-idr-geo-coordinates-02 Coordinates in BGP", draft-chen-idr-geo-coordinates-02
(work in progress), October 2016. (work in progress), October 2016.
[I-D.farinacci-lisp-name-encoding] [I-D.farinacci-lisp-name-encoding]
Farinacci, D., "LISP Distinguished Name Encoding", draft- Farinacci, D., "LISP Distinguished Name Encoding", draft-
farinacci-lisp-name-encoding-04 (work in progress), farinacci-lisp-name-encoding-05 (work in progress), March
September 2017. 2018.
[I-D.ietf-lisp-sec] [I-D.ietf-lisp-sec]
Maino, F., Ermagan, V., Cabellos-Aparicio, A., and D. Maino, F., Ermagan, V., Cabellos-Aparicio, A., and D.
Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-13 Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-14
(work in progress), September 2017. (work in progress), October 2017.
[I-D.jeong-its-v2i-problem-statement] [I-D.jeong-its-v2i-problem-statement]
Jeong, J. and T. Oh, "Problem Statement for Vehicle-to- Jeong, J. and T. Oh, "Problem Statement for Vehicle-to-
Infrastructure Networking", draft-jeong-its-v2i-problem- Infrastructure Networking", draft-jeong-its-v2i-problem-
statement-02 (work in progress), July 2016. statement-02 (work in progress), July 2016.
[I-D.shen-isis-geo-coordinates] [I-D.shen-isis-geo-coordinates]
Shen, N. and E. Chen, "Carrying Geo Coordinates Shen, N. and E. Chen, "Carrying Geo Coordinates
Information In IS-IS", draft-shen-isis-geo-coordinates-04 Information In IS-IS", draft-shen-isis-geo-coordinates-04
(work in progress), October 2017. (work in progress), October 2017.
skipping to change at page 9, line 24 skipping to change at page 9, line 24
A special thanks goes to Enke Chen, Acee Lindem, and Naiming Shen for A special thanks goes to Enke Chen, Acee Lindem, and Naiming Shen for
collaboarting on a consistent geo-location encoding format with OSPF collaboarting on a consistent geo-location encoding format with OSPF
[I-D.acee-ospf-geo-location], IS-IS [I-D.shen-isis-geo-coordinates], [I-D.acee-ospf-geo-location], IS-IS [I-D.shen-isis-geo-coordinates],
and BGP [I-D.chen-idr-geo-coordinates] protocols. and BGP [I-D.chen-idr-geo-coordinates] protocols.
Appendix B. Document Change Log Appendix B. Document Change Log
[RFC Editor: Please delete this section on publication as RFC.] [RFC Editor: Please delete this section on publication as RFC.]
B.1. Changes to draft-farinacci-lisp-geo-04.txt B.1. Changes to draft-farinacci-lisp-geo-05.txt
o Posted April 2018.
o Update document timer and references.
B.2. Changes to draft-farinacci-lisp-geo-04.txt
o Posted October 2017. o Posted October 2017.
o Update document timer and references. o Update document timer and references.
B.2. Changes to draft-farinacci-lisp-geo-03.txt B.3. Changes to draft-farinacci-lisp-geo-03.txt
o Posted April 2017. o Posted April 2017.
o Update document timer. o Update document timer.
B.3. Changes to draft-farinacci-lisp-geo-02.txt B.4. Changes to draft-farinacci-lisp-geo-02.txt
o Posted October 2016. o Posted October 2016.
o Change format of the Geo-Coordinates LCAF Type to be compatible o Change format of the Geo-Coordinates LCAF Type to be compatible
with equivalent proposals for OSPF, IS-IS, and BGP. with equivalent proposals for OSPF, IS-IS, and BGP.
o Add to the Security Considerations section to BCP160 compliance. o Add to the Security Considerations section to BCP160 compliance.
B.4. Changes to draft-farinacci-lisp-geo-01.txt B.5. Changes to draft-farinacci-lisp-geo-01.txt
o Posted October 2016. o Posted October 2016.
o Clarify that the Geo-Coordinates LCAF type should be encoded o Clarify that the Geo-Coordinates LCAF type should be encoded
inside an Instance-ID LCAF type when VPNs are used. inside an Instance-ID LCAF type when VPNs are used.
o Indiate what the value of the Altitude field is when not included o Indiate what the value of the Altitude field is when not included
in a message. Since this draft shortens the field, a new value is in a message. Since this draft shortens the field, a new value is
specified in this draft for not conveying an Altitude value in a specified in this draft for not conveying an Altitude value in a
message. message.
B.5. Changes to draft-farinacci-lisp-geo-00.txt B.6. Changes to draft-farinacci-lisp-geo-00.txt
o Initial draft posted April 2016. o Initial draft posted April 2016.
Author's Address Author's Address
Dino Farinacci Dino Farinacci
lispers.net lispers.net
San Jose, CA San Jose, CA
USA USA
 End of changes. 12 change blocks. 
19 lines changed or deleted 26 lines changed or added

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