YANG Geo Location

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2019-02-26
Replaced by draft-ietf-netmod-geo-location
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Additional URLs
- Yang catalog entry for ietf-geo-location@2019-02-17.yang
- Yang catalog entry for ietf-uses-geo-location@2019-02-02.yang
- Yang impact analysis for draft-chopps-netmod-geo-location
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           C. Hopps
Internet-Draft                                   LabN Consulting, L.L.C.
Intended status: Standards Track                        26 February 2019
Expires: 30 August 2019

                           YANG Geo Location


   This document defines a generic geographical location object YANG
   grouping.  The geographical location grouping is intended to be used
   in YANG models for specifying a location on or in reference to the
   Earth or any other astronomical object.

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 30 August 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.

Table of Contents

   1.  Introduction
       1.1.  Terminology
   2.  The Geo Location Object
       2.1.  Frame of Reference
       2.2.  Location
       2.3.  Motion
       2.4.  Tree
   3.  YANG Module
   4.  ISO 6709:2008 Conformance
   5.  Usability
       5.1.  Portability
             5.1.1.  IETF URI Value
             5.1.2.  W3C
             5.1.3.  Geography Markup Language (GML)
             5.1.4.  KML
   6.  IANA Considerations
       6.1.  Geodetic System Value Registry
   7.  Security Considerations
   8.  Normative References
   9.  Informative References
   Appendix A.  Examples
   Appendix B.  Acknowledgements
   Author's Address

1.  Introduction

   In many applications we would like to specify the location of
   something geographically.  Some examples of locations in networking
   might be the location of data center, a rack in an internet exchange
   point, a router, a firewall, a port on some device, or it could be
   the endpoints of a fiber, or perhaps the failure point along a fiber.

   Additionally, while this location is typically relative to The Earth,
   it does not need to be.  Indeed it is easy to imagine a network or
   device located on The Moon, on Mars, on Enceladus (the moon of
   Saturn) or even a comet (e.g., 67p/churyumov-gerasimenko).

   Finally, one can imagine defining locations using a different frames
   of reference or even alternate systems (e.g., a simulations or
   virtual realities).

   This document defines a "geo-location" YANG grouping that allows for
   all of the above data to be captured.

   This specification conforms to [ISO.6709.2008].

   The YANG data model described in this document conforms to the
   Network Management Datastore Architecture defined in [RFC8342].

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119] [RFC8174] when, and only when, they appear in all capitals,
   as shown here.

2.  The Geo Location Object

2.1.  Frame of Reference

   The frame of reference ("reference-frame") defines what the location
   values refer to and their meaning.  The referred to object can be any
   astronomical body.  It could be a planet such as The Earth or Mars, a
   moon such as Enceladus, an asteroid such as Ceres, or even a comet
   such as 1P/Halley.  This value is specified in "astronomical-body"
   and is defined by the International Astronomical Union
   (http://www.iau.org), The default "astronomical-body" value is

   In addition to identifying the astronomical body we also need to
   define the meaning of the coordinates (e.g., latitude and longitude)
   and the definition of 0-height.  This is done with a "geodetic-datum"
   value.  The default value for "geodetic-datum" is "wgs-84" (i.e., the
   World Geodetic System, [WGS84]), which is used by the Global
Show full document text