Subject: RE: LLDP-MED and Phone BCP (Re: [Ecrit] New phonebcpdraftwassubmitted)

From: [email-masked]
Date: Thu, 13 Jul 2006 09:26:00 -0400

[off list]
Hi Marc,
Assuming you are going to rebut, could you please re-subject the thread? 
It is now waaaaay off the original topic, distracting, and there may be 
others interested in the new topic that have fallen asleep.
-- Peter

"Marc Linsner" <[email-masked]>
12.07.06 19:21

        To:     "'Winterbottom, James'" <[email-masked]>
        cc:     [email-masked]
        Subject:        RE: LLDP-MED and Phone BCP (Re: [Ecrit] New phonebcpdraftwassubmitted)

Please identify the non-mobile application(s) that use geo and are 
required to convey uncertainty.
 
-Marc-

Marc, this has nothing to do with mobile. It is to do with the potential 
for massive errors to be introduced by the encoding technique used in 
RFC-3825. Please see appendix A of PIDF-LO profile for more details. 

From: Marc Linsner [mailto:[email-masked]] 
Sent: Wednesday, 12 July 2006 11:34 PM
To: Winterbottom, James; 'Stark, Barbara'; 'Andrew Newton'; 'Rohan Mahy'
Cc: 'Rosen, Brian'; [email-masked]
Subject: RE: LLDP-MED and Phone BCP (Re: [Ecrit] New phonebcpdraftwassubmitted)
 
As stated in RFC3825, it is applicable to non-mobile environments.
 
-Marc-

From: Winterbottom, James [mailto:[email-masked]] 
Sent: Tuesday, July 11, 2006 11:39 PM
To: Stark, Barbara; Andrew Newton; Rohan Mahy
Cc: Rosen, Brian; [email-masked]
Subject: RE: LLDP-MED and Phone BCP (Re: [Ecrit] New phonebcpdraftwassubmitted)
 
I would be very cautious about recommending the use of RFC-3825 encoding 
to report emergency locations given the issues raised at IETF-65 in Dallas 
that are yet to be adequately resolved. In NENA we put a caveat around its 
use to the effect that location provided in this manner must be regarded 
as a point only, and that encodings for resolution must be ignored.
 
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] 
*****
The information transmitted is intended only for the person or entity to 
which it is addressed and may contain confidential, proprietary, and/or 
privileged material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon this information by 
persons or entities other than the intended recipient is prohibited. If 
you received this in error, please contact the sender and delete the 
material from all computers. 162

------------------------------------------------------------------------------------------------
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] _______________________________________________
Ecrit mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ecrit

_______________________________________________
Ecrit mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ecrit