--- 1/draft-ietf-netmod-geo-location-03.txt 2020-03-02 15:13:26.915027026 -0800 +++ 2/draft-ietf-netmod-geo-location-04.txt 2020-03-02 15:13:26.995029054 -0800 @@ -1,18 +1,18 @@ Network Working Group C. Hopps Internet-Draft LabN Consulting, L.L.C. -Intended status: Standards Track 13 February 2020 -Expires: 16 August 2020 +Intended status: Standards Track 1 March 2020 +Expires: 2 September 2020 - YANG Geo Location - draft-ietf-netmod-geo-location-03 + A YANG Grouping for Geographic Locations + draft-ietf-netmod-geo-location-04 Abstract 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 @@ -22,21 +22,21 @@ 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 16 August 2020. + This Internet-Draft will expire on 2 September 2020. Copyright Notice Copyright (c) 2020 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 @@ -109,21 +109,21 @@ 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 + (http://www.iau.org). The default "astronomical-body" value is "earth". 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 Positioning System (GPS) among many others. We define an IANA registry for specifying standard values for the "geodetic-datum". @@ -552,22 +552,20 @@ all the location values. As the URI is a string, all values are specifies as strings and so are capable of as much precision as required. URI values can be mapped to and from the YANG grouping, with the caveat that some loss of precision (in the extremes) may occur due to the YANG grouping using decimal64 values rather than strings. 5.1.2. W3C - See https://w3c.github.io/geolocation-api/#dom-geolocationposition. - W3C Defines a geo-location API in [W3CGEO]. We show a snippet of code below which defines the geo-location data for this API. This is used by many application (e.g., Google Maps API). interface GeolocationPosition { readonly attribute GeolocationCoordinates coords; readonly attribute DOMTimeStamp timestamp; }; interface GeolocationCoordinates { @@ -669,23 +667,23 @@ "gml:validTime" can either be an Instantaneous measure ("gml:TimeInstant") or a time period ("gml:TimePeriod"). The instantaneous "gml:TimeInstant" is mappable to and from the YANG grouping "timestamp" value, and values down to the resolution of seconds for "gml:TimePeriod" can be mapped using the using the "valid-for" node of the YANG grouping. 5.1.4. KML KML 2.2 [KML22] (formerly Keyhole Markup Language) was submitted by - Google to Open Geospatial Consortium (OGC) - https://www.opengeospatial.org/ and was adopted. The latest version - as of this writing is KML 2.3 [KML23]. This schema includes + Google to the Open Geospatial Consortium, + (https://www.opengeospatial.org/) and was adopted. The latest + version as of this writing is KML 2.3 [KML23]. This schema includes geographic location data in some of its objects (e.g., "kml:Point" or "kml:Camera" objects). This data is provided in string format and corresponds to the [W3CGEO] values. The timestamp value is also specified as a string as in our YANG grouping. KML has some special handling for the height value useful for visualization software, "kml:altitudeMode". These values for "kml:altitudeMode" include indicating the height is ignored ("clampToGround"), in relation to the location's ground level ("relativeToGround"), or in relation to the geodetic datum @@ -791,45 +789,46 @@ [ISO.6709.2008] International Organization for Standardization, "ISO 6709:2008 Standard representation of geographic point location by coordinates.", 2008. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . - [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC - 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, - May 2017, . - [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, . + [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC + 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, + May 2017, . + [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, . [WGS84] National Imagery and Mapping Agency., "National Imagery and Mapping Agency Technical Report 8350.2, Third - Edition.", 3 January 2000, . + Edition.", 3 January 2000, + . 9. Informative References [ISO.19136.2007] International Organization for Standardization, "ISO 19136:2007 Geographic information -- Geography Markup - Language (GML)". + Language (GML)", March 2020. [KML22] Wilson, T., Ed., "OGC KML (Version 2.2)", 14 April 2008, . [KML23] Burggraf, D., Ed., "OGC KML 2.3", 4 August 2015, . [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource @@ -839,22 +838,22 @@ [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, . [W3CGEO] Popescu, A., "Geolocation API Specification", 8 November - 2016, . + 2016, . Appendix A. Examples Below is a fictitious module that uses the geo-location grouping. module example-uses-geo-location { namespace "urn:example:example-uses-geo-location"; prefix ugeo; import ietf-geo-location { prefix geo; }