draft-ietf-netmod-geo-location-10.txt   draft-ietf-netmod-geo-location-11.txt 
Network Working Group C. Hopps Network Working Group C. Hopps
Internet-Draft LabN Consulting, L.L.C. Internet-Draft LabN Consulting, L.L.C.
Intended status: Standards Track 17 June 2021 Intended status: Standards Track 24 October 2021
Expires: 19 December 2021 Expires: 27 April 2022
A YANG Grouping for Geographic Locations A YANG Grouping for Geographic Locations
draft-ietf-netmod-geo-location-10 draft-ietf-netmod-geo-location-11
Abstract Abstract
This document defines a generic geographical location YANG grouping. This document defines a generic geographical location YANG grouping.
The geographical location grouping is intended to be used in YANG The geographical location grouping is intended to be used in YANG
models for specifying a location on or in reference to Earth or any models for specifying a location on or in reference to Earth or any
other astronomical object. other astronomical object.
Status of This Memo Status of This Memo
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 19 December 2021. This Internet-Draft will expire on 27 April 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 20 skipping to change at page 2, line 20
2.1. Frame of Reference . . . . . . . . . . . . . . . . . . . 3 2.1. Frame of Reference . . . . . . . . . . . . . . . . . . . 3
2.2. Location . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Location . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Motion . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.3. Motion . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4. Nested Locations . . . . . . . . . . . . . . . . . . . . 5 2.4. Nested Locations . . . . . . . . . . . . . . . . . . . . 5
2.5. Non-location Attributes . . . . . . . . . . . . . . . . . 5 2.5. Non-location Attributes . . . . . . . . . . . . . . . . . 5
2.6. Tree . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.6. Tree . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. ISO 6709:2008 Conformance . . . . . . . . . . . . . . . . . . 12 4. ISO 6709:2008 Conformance . . . . . . . . . . . . . . . . . . 12
5. Usability . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Usability . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1. Portability . . . . . . . . . . . . . . . . . . . . . . . 13 5.1. Portability . . . . . . . . . . . . . . . . . . . . . . . 13
5.1.1. IETF URI Value . . . . . . . . . . . . . . . . . . . 13 5.1.1. IETF URI Value . . . . . . . . . . . . . . . . . . . 14
5.1.2. W3C . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.1.2. W3C . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1.3. Geography Markup Language (GML) . . . . . . . . . . . 15 5.1.3. Geography Markup Language (GML) . . . . . . . . . . . 16
5.1.4. KML . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1.4. KML . . . . . . . . . . . . . . . . . . . . . . . . . 16
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
6.1. Geodetic System Values Registry . . . . . . . . . . . . . 17 6.1. Geodetic System Values Registry . . . . . . . . . . . . . 17
6.2. Updates to the IETF XML Registry . . . . . . . . . . . . 18 6.2. Updates to the IETF XML Registry . . . . . . . . . . . . 18
6.3. Updates to the YANG Module Names Registry . . . . . . . . 18 6.3. Updates to the YANG Module Names Registry . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 19 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19
8. Normative References . . . . . . . . . . . . . . . . . . . . 19 8. Normative References . . . . . . . . . . . . . . . . . . . . 20
9. Informative References . . . . . . . . . . . . . . . . . . . 20 9. Informative References . . . . . . . . . . . . . . . . . . . 21
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 22 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 22
Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . 24 Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . 25
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 25 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 26
1. Introduction 1. Introduction
In many applications we would like to specify the location of In many applications we would like to specify the location of
something geographically. Some examples of locations in networking something geographically. Some examples of locations in networking
might be the location of data center, a rack in an internet exchange 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 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. the endpoints of a fiber, or perhaps the failure point along a fiber.
Additionally, while this location is typically relative to Earth, it Additionally, while this location is typically relative to Earth, it
skipping to change at page 9, line 11 skipping to change at page 9, line 11
} }
description description
"A geodetic-datum defining the meaning of latitude, "A geodetic-datum defining the meaning of latitude,
longitude and height. The default when the longitude and height. The default when the
astronomical body is 'earth' is 'wgs-84' which is astronomical body is 'earth' is 'wgs-84' which is
used by the Global Positioning System (GPS). The used by the Global Positioning System (GPS). The
ASCII value SHOULD have upper case converted to lower ASCII value SHOULD have upper case converted to lower
case and not include control characters (i.e., values case and not include control characters (i.e., values
32..64, and 91..126). The IANA registry further 32..64, and 91..126). The IANA registry further
restricts the value by converting all spaces (' ') to restricts the value by converting all spaces (' ') to
dashes ('-')"; dashes ('-').
The specification for the geodetic-datum indicates
how accurately it models the astronomical body in
question, both for the 'horizontal'
latitude/longitude coordinates and for height
coordinates.";
reference reference
"IANA XXXX YANG Geographic Location Parameters, "IANA XXXX YANG Geographic Location Parameters,
Geodetic System Values"; Geodetic System Values";
} }
leaf coord-accuracy { leaf coord-accuracy {
type decimal64 { type decimal64 {
fraction-digits 6; fraction-digits 6;
} }
description description
"The accuracy of the latitude longitude pair for "The accuracy of the latitude longitude pair for
ellipsoidal coordinates, or the X, Y and Z components ellipsoidal coordinates, or the X, Y and Z components
for Cartesian coordinates. When coord-accuracy is for Cartesian coordinates. When coord-accuracy is
specified, it overrides the geodetic-datum implied specified, it indicates how precisely the coordinates
accuracy."; in the associated list of locations have been
determined with respect to the coordinate system
defined by the geodetic-datum. For example, there
might be uncertainty due to measurement error if an
experimental measurement was made to determine each
location.";
} }
leaf height-accuracy { leaf height-accuracy {
type decimal64 { type decimal64 {
fraction-digits 6; fraction-digits 6;
} }
units "meters"; units "meters";
description description
"The accuracy of height value for ellipsoidal "The accuracy of height value for ellipsoidal
coordinates, this value is not used with Cartesian coordinates, this value is not used with Cartesian
coordinates. When height-accuracy is specified, it coordinates. When height-accuracy is specified, it
overrides the geodetic-datum implied default."; indicates how precisely the heights in the
associated list of locations have been determined
with respect to the coordinate system defined by the
geodetic-datum. For example, there might be
uncertainty due to measurement error if an
experimental measurement was made to determine each
location.";
} }
} }
} }
choice location { choice location {
description description
"The location data either in lat/long or Cartesian values"; "The location data either in lat/long or Cartesian values";
case ellipsoid { case ellipsoid {
leaf latitude { leaf latitude {
type decimal64 { type decimal64 {
fraction-digits 16; fraction-digits 16;
 End of changes. 10 change blocks. 
16 lines changed or deleted 32 lines changed or added

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