[draft-ietf-geopriv-held-measurements-03] for the IEEE 802 considerations.
My comments follow:
In section 5.1 LLDP Measurements regarding the note:
I believe that technical capability originally specified in LLDP-MED is
now included in the 2009 revision of 802.1AB (IEEE Std 802.1AB - 2009).
Further, the 802.3 specific TLVs specified in 802.1AB clause 6.3 have
been superceded by IEEE Std 802.3bc - 2009 (as anticipated in Note 2 of
that sub-clause). Thus I suspect that the reference to LLDP - MED and
ANSI-TIA-1057 should be removed.
In the text below Figure 6, the measurement set seems to assume that
both the wifi end station and the access point are stationary. I'm not
clear whether we are attempting fully cope with the "in motion" case. We
can (at least) detect it and put in an indicator (e.g. some sort of
flag, etc. for whether location is changing within some time/distance
parameters).
Re: Page 19, flightTime: I don't believe that the statement "Measurement
of this value requires that stations synchronize their clocks" is
correct, at least for the nominally static case. It would be true if the
result were based on a 1 way measurement. However, if it is the average
of a 2 way measurement then any difference in local time-of-day would be
cancelled out (assuming matching clock rates). It would seem more useful
to allow the lesser constrained case.
In section 5.6, DSL Measurements {Full 2 paragraphs of text is
reproduced, my comments are in curly brackets}:
Digital Subscriber Line (DSL) networks rely on a range of network
technology {"technology" should be plural}. DSL deployments regularly
require cooperation between multiple organizations. These fall into two
broad categories: infrastructure providers and Internet service
providers (ISPs).
Infrastructure providers manage the bulk of the physical infrastructure
including cabling. End users obtain their service from an ISP {Insert:
"(Who may or may not be be the same entity as the infrastructure
provider)"}, which manages all aspects visible to the end user including
IP address allocation and operation of a LIS. See [DSL.TR025] and
[DSL.TR101] for further information on DSL network deployments and the
parameters that are available.
Exchange of measurement information between these organizations is
necessary for location information to be correctly generated. The
ISP LIS needs to acquire location information from the infrastructure
provider. However, {Insert: "since"} the infrastructure provider has
{Replace" "has" with "may have"} no knowledge of Device identifiers, it
can only identify a stream of data that is sent to the ISP. This is
resolved by passing measurement data relating to the Device to a LIS
operated by the infrastructure provider.
RE: 5.6.3. Ethernet VLAN Tag Measurements
There are several types of Ethernet VLANs in the world. This information
seems to be specific to a particular VLAN specification that does not
seem to be referenced.
RE: 11.2. Informative References
[ANSI-TIA-1057] I think this can be deleted now that the capability is
included in 802.1AB
[IEEE.8021AB] To both update the citation and correct its form, it
should be:
"IEEE Standard for Local and metropolitan area networks— Station and
Media Access Control Connectivity Discovery" IEEE Std 802.1AB™-2009
Since the specifications for the 802.3 TLVs in 802.1AB-2009 have been
superceded by IEEE Std 802.3bc - 2009 a citation should be added for it.
Since the current correct name for that standard is SO long and
unwieldly (and the next revision will shorted the 802.3 title to
"Standard for Ethernet") I suggest
"IEEE Standard for Local and metropolitan area networks— Part 3:
Amendment 2: Ethernet Organizationally Specific Type, Length, Value
(TLVs)" IEEE Std 802.3bc™-2009
Both 802.1AB - 2009 and 802.3bc - 2009 can be obtained at no charge from
http://standards.ieee.org/about/get/
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
