RE: [Voip-location] [Geopriv] Registration of additional PIDF-LOMethods

There may be a way to accommodate both of these.

It is possible, using a specific scenario as an example, that the method
by which the switch Ethernet port used by a device was identified by
SNMP bridge MIB queries rather than using DHCP relay. Ultimately, the
location of the other end of the Ethernet cable is determined by
consulting a wire-map database.

So, this is a scenario where wire-map applies but DHCP does not.

My understanding is that "DHCP" specifically means wire-map where the
protocol used to deliver the port identity was DHCP relay.

I don't think PSAP operators would care what protocol was used to
deliver the port identity for the purpose of consulting the wire-map.
However, if they know how to parse the token "DHCP" then I guess it
doesn't really matter.

On the other hand, it wouldn't be good practice to use "DHCP" when DHCP
wasn't involved at all.

In order to maintain "backward compatibility" as it were, can we
standardize an interpretation of:

DHCP - Location determined by wire-map lookup based on switch port
information transferred by DHCP relay

Wire-map - Location determined by wire-map lookup based on switch port
information

The latter is a super-set of the former and is correct in either case.
The former is a specific case. The PSAP operator can interpret both
similarly as far as understanding the kind of accuracy implications.

Cheers,
Martin

> -----Original Message-----
> From: voip-location-bounces@cs.columbia.edu [mailto:voip-location-
> bounces@cs.columbia.edu] On Behalf Of James M. Polk
> Sent: Friday, 31 March 2006 9:56 AM
> To: Winterbottom, James; Abbott, Nadine B; geopriv@ietf.org
> Cc: voip-location@cs.columbia.edu
> Subject: Re: [Voip-location] [Geopriv] Registration of additional
PIDF-
> LOMethods
>
> At 04:13 PM 3/30/2006 -0600, Winterbottom, James wrote:
> >But that is my entire point James, Method is a parameter describing
how
> >location was determined NOT how it was delivered.
>
> no, that's not the intend of <method>
>
> >They are not the same
> >thing!
>
> You're right, but you'll read below what was intended in 4119
>
> Learning location through DHCP over a wire (because the LG knows how
it
> received location) is "DHCP"
>
> Learning location through DHCP over WiFi (because the LG knows how it
> received location) is "802.11"
>
> This was all hammered out at the Seoul IETF
>
>
> >If I were to use VLAN or VPI/VCI identifiers as keys to my database
to
> >determine location, I could quite easily use wiremap as my method,
but
> >it would be ludicrous to suggest that I put a method of DHCP.
>
> You're using Method differently than 4119 is. Method was created to
give
> to the PSAP operator as an indication of how the caller learned the
> location they gave the operator. The feeling was at the time that
over
> time, operators would learn through experience how much to trust each
> Method given, and to tell first responders some things learned through
> dispatch experience. This is not something we could have specified,
> because there is nothing like this type of location acquisition in the
> circuit or wireless world today.
>
> Method was not intended to be in a database, it was to be used to give
the
> operator an indication. We didn't know what a creative SW engineer of
an
> operator station w/could come up with as far as something relational
> depending on the PIDF-LO indication for different methods, but knowing
> location was learned for a AP means the operator needs to tell the
> responder the caller can be 100m from that position with an up and
down
> angle allowing different floors of a building to take into account.
> Whereas, this would not be true if location were learned from a wire,
> which
> means a jack on a wall.
>
> >Hopefully
> >this clarifies the issue, method describes how location was
determined,
> >not the type of access, and not how location was delievered.
>
> Well, no, because I wrote the original text for the Method section of
> 4119,
> and that's not what I had in mind when I wrote it - and the WG
approved
> it.
> So, it appears someone's made a assumption/conclusion that is not
based on
> what happened then. I'm sorry.
>
>
>
>
> > > -----Original Message-----
> > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > Sent: Friday, 31 March 2006 8:05 AM
> > > To: Winterbottom, James; Abbott, Nadine B; geopriv@ietf.org
> > > Cc: voip-location@cs.columbia.edu
> > > Subject: RE: [Geopriv] Registration of additional PIDF-LO Methods
> > >
> > > James
> > >
> > > DHCP Relay is used in 802.11 deliveries too...
> > >
> > > At 11:33 AM 3/30/2006 -0600, Winterbottom, James wrote:
> > > >James,
> > > >
> > > >My recommendation is to update the DHCP description to say where
> > > >DHCP-relay is used only, and we could indicate for the generic
> >wiremap
> > > >that this is not to be used where a specific method is described.
> > > >
> > > >This will avoid confusion.
> > > >
> > > >Cheers
> > > >James
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > > > Sent: Friday, 31 March 2006 3:30 AM
> > > > > To: Abbott, Nadine B; Winterbottom, James; geopriv@ietf.org
> > > > > Cc: voip-location@cs.columbia.edu
> > > > > Subject: RE: [Geopriv] Registration of additional PIDF-LO
Methods
> > > > >
> > > > > Nadine/James
> > > > >
> > > > > So, how do you separate "DHCP" stating it is for "wireline
> >access"?
> > > > >
> > > > > Where cannot someone get confused?
> > > > >
> > > > > At 10:52 AM 3/30/2006 -0500, Abbott, Nadine B wrote:
> > > > > >"Wiremap" seems to have a meaning that is more specific to
how
> >the
> > > > > >location information is created/maintained, and has a less
> > > > > >protocol-specific connotation than use of DHCP.
> > > > > >
> > > > > >Nadine
> > > > > >
> > > > > >-----Original Message-----
> > > > > >From: James M. Polk [mailto:jmpolk@cisco.com]
> > > > > >Sent: Wednesday, March 29, 2006 10:29 PM
> > > > > >To: Winterbottom, James; geopriv@ietf.org
> > > > > >Cc: voip-location@cs.columbia.edu
> > > > > >Subject: Re: [Geopriv] Registration of additional PIDF-LO
Methods
> > > > > >
> > > > > >James
> > > > > >
> > > > > >I want you to remove "wiremap" as it is a direct duplicate to
> >"DHCP"
> > > >as
> > > > > >defined in RFC4119 and what's exactly in the IANA description
on
> >the
> > > > > >link you have below. Leaving it here will cause confusion.
> > > > > >
> > > > > >I am curious about the differences between "A-GPS" and
"Device
> > > >Assisted
> > > > > >GPS"?
> > > > > >
> > > > > >At 02:35 PM 3/24/2006 -0600, Winterbottom, James wrote:
> > > > > > >Content-Type: multipart/alternative;
> > > > > > >
> > > >boundary="--=_NextPart_ST_14_35_13_Friday_March_24_2006_25372"
> > > > > > >Content-class: urn:content-classes:message
> > > > > > >
> > > > > > >Hi All,
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >For those interested I have registered quite a number of
> >additional
> > > > > > ><method> types for the PIDF-LO. These are largely, but not
> > > >exclusively,
> > > > > >
> > > > > > >wireless determination types.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> >
><http://www.iana.org/assignments/method-tokens>http://www.iana.org/assi
> > > > > > >gnments/method-tokens
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >Cheers
> > > > > > >
> > > > > > >James
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> >
>-----------------------------------------------------------------------
> > > > > > >------------------------- This message is for the
designated
> > > >recipient
> > > > > > >only and may contain privileged, proprietary, or otherwise
> >private
> > > > > > >information.
> > > > > > >If you have received it in error, please notify the sender
> > > >immediately
> > > > > > >and delete the original. Any unauthorized use of this email
is
> > > > > > >prohibited.
> > > > > >
> > > >
> >
>-----------------------------------------------------------------------
> > > > > > >-------------------------
> > > > > > >[mf2]
> > > > > > >_______________________________________________
> > > > > > >Geopriv mailing list
> > > > > > >Geopriv@ietf.org
> > > > > > >https://www1.ietf.org/mailman/listinfo/geopriv
> > > > > >
> > > > > >_______________________________________________
> > > > > >Geopriv mailing list
> > > > > >Geopriv@ietf.org
> > > > > >https://www1.ietf.org/mailman/listinfo/geopriv
> > > >
> > >
> >
>-----------------------------------------------------------------------
> >--
> > > -----------------------
> > > >This message is for the designated recipient only and may
> > > >contain privileged, proprietary, or otherwise private
information.
> > > >If you have received it in error, please notify the sender
> > > >immediately and delete the original. Any unauthorized use of
> > > >this email is prohibited.
> > >
> >
>-----------------------------------------------------------------------
> >--
> > > -----------------------
> > > >[mf2]
> >
>
>-----------------------------------------------------------------------

--
> -----------------------
> >This message is for the designated recipient only and may
> >contain privileged, proprietary, or otherwise private information.
> >If you have received it in error, please notify the sender
> >immediately and delete the original.  Any unauthorized use of
> >this email is prohibited.
>
>-----------------------------------------------------------------------
--
> -----------------------
> >[mf2]
> _______________________________________________
> Voip-location mailing list
> Voip-location@cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/voip-location
------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www1.ietf.org/mailman/listinfo/geopriv