RE: [Geopriv] Confirmation of GEOPRIV IETF 68 Working Group Hums

"James M. Polk" <[email protected]>
Newsgroups gmane.ietf.general,gmane.ietf.geopriv
Message-ID <[email protected]>
Martin

Exactly what products support HELD right now?

If you want location verification and location signing - are these 
deployed today?

Doesn't all these mean something has to be changed or upgraded?

Broadband providers in the US have given away FREE home routers to 
enable a service as recently as a year ago.  So, taking the stance 
that this won't happen is looking facts to the contrary in the eye 
and saying "that didn't happen" *or* "that's not going to happen"....

At 04:34 PM 4/19/2007, Dawson, Martin wrote:
>Does DHCP require a change to the residential CPE James? How long is it
>going to take to change every residential router in the world? Do you
>think it is an unreasonable requirement to not have to do this?
>
>You can't just object to HELD on the basis that you think it's been
>misrepresented. I don't accept that it has - but in any case, it's not a
>technical rationale.
>
>Cheers,
>Martin
>
>
>
>-----Original Message-----
>From: James M. Polk [mailto:[email protected]]
>Sent: Friday, 20 April 2007 7:31 AM
>To: Dawson, Martin; John Schnizlein; Andrew Newton
>Cc: GEOPRIV WG; Allison Mankin; [email protected]
>Subject: RE: [Geopriv] Confirmation of GEOPRIV IETF 68 Working Group
>Hums
>
>At 04:20 PM 4/19/2007, Dawson, Martin wrote:
> >"DHCP is not adequate because it doesn't meet multiple sets of
> >requirements as documented multiple times ..."
>
>bologna
>
>"documented multiple times" means in individual submissions
>
>of which, zero facts were presented to substantiate
>
>If DHCP were so inadequate, why is the DSL forum now going to specify
>it? Why does PacketCable define it?  These were fairly recent moves...
>
>And, how many times has HELD been presented as if it were a product
>of an IETF WG?
>
>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]

_______________________________________________
Ietf mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ietf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.