LISP Geo-Coordinate Use-Cases
draft-farinacci-lisp-geo-07
|
| Document |
Type |
|
Active Internet-Draft (candidate for lisp WG)
|
|
Last updated |
|
2019-04-11
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Call For Adoption By WG Issued
Polled for WG adoption but not adopted
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group D. Farinacci
Internet-Draft lispers.net
Intended status: Experimental April 11, 2019
Expires: October 13, 2019
LISP Geo-Coordinate Use-Cases
draft-farinacci-lisp-geo-07
Abstract
This draft describes how Geo-Coordinates can be used in the LISP
Architecture and Protocols.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 13, 2019.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Farinacci Expires October 13, 2019 [Page 1]
Internet-Draft LISP Geo-Coordinate Use-Cases April 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 2
3. Geo-Points in RLOC-records . . . . . . . . . . . . . . . . . 3
4. Geo-Prefixes in EID-records and RLOC-records . . . . . . . . 3
5. Geo-Prefix and Geo-Point Encodings . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 9
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 9
B.1. Changes to draft-farinacci-lisp-geo-07 . . . . . . . . . 9
B.2. Changes to draft-farinacci-lisp-geo-06 . . . . . . . . . 9
B.3. Changes to draft-farinacci-lisp-geo-05 . . . . . . . . . 9
B.4. Changes to draft-farinacci-lisp-geo-04 . . . . . . . . . 9
B.5. Changes to draft-farinacci-lisp-geo-03 . . . . . . . . . 9
B.6. Changes to draft-farinacci-lisp-geo-02 . . . . . . . . . 10
B.7. Changes to draft-farinacci-lisp-geo-01 . . . . . . . . . 10
B.8. Changes to draft-farinacci-lisp-geo-00 . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
The LISP architecture and protocols [RFC6830] introduces two new
numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
(RLOCs) which are intended to replace most use of IP addresses on the
Internet. To provide flexibility for current and future
applications, these values can be encoded in LISP control messages
using a general syntax that includes Address Family Identifier (AFI)
[RFC1700].
This specification introduces the use of Geo-Coordinates that can be
used in EID-records and RLOC-records of LISP control messages. The
encoding format is specified in [RFC8060] as the "Geo-Coordinates
LCAF Type".
2. Definition of Terms
Geo-Point is a Geo-Coordinate according to [GEO] that defines a
point from parameters Latitude, Longitude, and Altitude.
Geo-Prefix forms a circle of a geographic area made up of a Geo-
Point and a Radius. A Geo-Point is known to be "more-specific"
than a Geo-Prefix when its physical location is within the
geographic circle.
Farinacci Expires October 13, 2019 [Page 2]
Internet-Draft LISP Geo-Coordinate Use-Cases April 2019
3. Geo-Points in RLOC-records
Geo-Points can accompany an RLOC-record to determine the physical
location of an ETR or RTR. This can aid in determining geographical
distance when topological distance is inaccurate or hidden. When
Show full document text