--- 1/draft-ietf-netmod-geo-location-01.txt 2019-11-04 14:14:24.822953640 -0800 +++ 2/draft-ietf-netmod-geo-location-02.txt 2019-11-04 14:14:24.870954857 -0800 @@ -1,18 +1,18 @@ Network Working Group C. Hopps Internet-Draft LabN Consulting, L.L.C. -Intended status: Standards Track April 29, 2019 -Expires: October 31, 2019 +Intended status: Standards Track November 4, 2019 +Expires: May 7, 2020 YANG Geo Location - draft-ietf-netmod-geo-location-01 + draft-ietf-netmod-geo-location-02 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 October 31, 2019. + This Internet-Draft will expire on May 7, 2020. 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 @@ -65,21 +65,21 @@ 5.1.2. W3C . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.1.3. Geography Markup Language (GML) . . . . . . . . . . . 15 5.1.4. KML . . . . . . . . . . . . . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 6.1. Geodetic System Value Registry . . . . . . . . . . . . . 16 7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 8.1. Normative References . . . . . . . . . . . . . . . . . . 18 8.2. Informative References . . . . . . . . . . . . . . . . . 19 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 19 - Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 23 + Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 22 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 23 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. @@ -207,36 +207,37 @@ object that is at the location. Module authors are free to add these non-location attributes along with their use of this location grouping. 2.6. Tree The following is the YANG tree diagram [RFC8340] for the geo-location grouping. module: ietf-geo-location + grouping geo-location +-- geo-location +-- reference-frame | +-- alternate-system? string {alternate-systems}? | +-- astronomical-body? string | +-- geodetic-system | +-- geodetic-datum? string | +-- coord-accuracy? decimal64 | +-- height-accuracy? decimal64 - +-- (location) + +-- (location)? | +--:(ellipsoid) - | | +-- latitude degrees - | | +-- longitude degrees + | | +-- latitude? degrees + | | +-- longitude? degrees | | +-- height? decimal64 | +--:(cartesian) - | +-- x decimal64 - | +-- y decimal64 + | +-- x? decimal64 + | +-- y? decimal64 | +-- z? decimal64 +-- velocity | +-- v-north? decimal64 | +-- v-east? decimal64 | +-- v-up? decimal64 +-- timestamp? types:date-and-time Figure 1: Geo Location YANG tree diagram. 3. YANG Module @@ -253,43 +254,43 @@ "Christian Hopps "; // RFC Ed.: replace XXXX with actual RFC number and // remove this note. description "This module defines a grouping of a container object for specifying a location on or around an astronomical object (e.g., The Earth). - Copyright (c) 2018 IETF Trust and the persons identified as + Copyright (c) 2019 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). - The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL - NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', - 'MAY', and 'OPTIONAL' in this document are to be interpreted as - described in BCP 14 [RFC2119] [RFC8174] when, and only when, - they appear in all capitals, as shown here. - This version of this YANG module is part of RFC XXXX - (https://tools.ietf.org/html/rfcXXXX); see the RFC itself for - full legal notices."; + (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself + for full legal notices. // RFC Ed.: replace XXXX with actual RFC number and // remove this note. + The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + 'MAY', and 'OPTIONAL' in this document are to be interpreted as + described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, + they appear in all capitals, as shown here."; + revision 2019-02-17 { description "Initial Revision"; reference "RFC XXXX: YANG Geo Location"; } typedef degrees { type decimal64 { fraction-digits 16; } units "decimal degrees"; @@ -387,65 +388,59 @@ // If so need to decide if we have a boolean (to ground) // or an enumeration (e.g., local ground, sea-floor, // ground floor, containing object, ...) or even allow // for a string for most generic but least portable // comparable // leaf height-relative { // } } } choice location { - mandatory true; description "The location data either in lat/long or Cartesian values"; case ellipsoid { leaf latitude { type degrees; - mandatory true; description "The latitude value on the astronomical body. The definition and precision of this measurement is indicated by the reference-frame value."; - } leaf longitude { type degrees; - mandatory true; description "The longitude value on the astronomical body. The definition and precision of this measurement is indicated by the reference-frame."; } leaf height { type decimal64 { fraction-digits 6; } units "meters"; description "Height from a reference 0 value. The precision and '0' value is defined by the reference-frame."; } } case cartesian { leaf x { type decimal64 { fraction-digits 6; } - mandatory true; description "The X value as defined by the reference-frame."; } leaf y { type decimal64 { fraction-digits 6; } - mandatory true; description "The Y value as defined by the reference-frame."; } leaf z { type decimal64 { fraction-digits 6; } units "meters"; description "The Z value as defined by the reference-frame."; @@ -902,28 +897,28 @@ +--rw locatable-item* [name] +--rw name string +--rw geo-location +--rw reference-frame | +--rw alternate-system? string {alternate-systems}? | +--rw astronomical-body? string | +--rw geodetic-system | +--rw geodetic-datum? string | +--rw coord-accuracy? decimal64 | +--rw height-accuracy? decimal64 - +--rw (location) + +--rw (location)? | +--:(ellipsoid) - | | +--rw latitude degrees - | | +--rw longitude degrees + | | +--rw latitude? degrees + | | +--rw longitude? degrees | | +--rw height? decimal64 | +--:(cartesian) - | +--rw x decimal64 - | +--rw y decimal64 + | +--rw x? decimal64 + | +--rw y? decimal64 | +--rw z? decimal64 +--rw velocity | +--rw v-north? decimal64 | +--rw v-east? decimal64 | +--rw v-up? decimal64 +--rw timestamp? types:date-and-time Below is some example YANG XML data for the fictitious module that uses the geo-location grouping. @@ -960,20 +955,31 @@ moon me 0.67409 23.47298 + + Reference Frame Only + + + moon + + me + + + + Figure 4: Example XML data of geo location use. Appendix B. Acknowledgements We would like to thank Peter Lothberg for the motivation as well as help in defining a more broadly useful geographic location object.