I strongly object to this.
This document describes a specific way to extract information from a json
object. The use case is another standard that needs to do that. That document
needs a reference to a specific way to extract the information which will be
implemented interoperably by many ent
Thank you very much for your review.
The term we use for these kinds of “calls” has changed several times. There
really isn’t a great name.
In another forum, we’re calling them “non-human-initiated”, but that really
isn’t right either. If you press a button and a device sends your location and
I will contact Henning
Brian
On Feb 19, 2013, at 7:16 PM, Marc Petit-Huguenin
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Thanks Mary. I start working on this immediately.
>
> On 02/19/2013 04:06 PM, Mary Barnes wrote:
>> I am the assigned Gen-ART reviewer for this draft.
.
>
> On Mar 10, 2010, at 10:27 AM, Brian Rosen wrote:
>
>> The citation is the U.S. Regulatory spec, which is (barely) achievable.
>> There is a very long record available that documents the back and forth with
>> experts arguing on both sides. The conclusions o
level
is as good as we can get right now. For this document, that's good enough.
Brian
On 3/10/10 10:22 AM, "Henning Schulzrinne" wrote:
>
> On Mar 10, 2010, at 9:41 AM, Brian Rosen wrote:
>
>> This is a (probably pointless) discussion on the 100 meter uncertai
dy to give good results). I do think it's a minute or two.
Brian
On 3/10/10 9:28 AM, "Henning Schulzrinne" wrote:
>
> On Mar 10, 2010, at 8:36 AM, Brian Rosen wrote:
>
>> I suppose that it's conceivable that every carrier, the FCC, NENA and APCO
>>
://www.gpsworld.com/gnss-system/expert-advice-does-anybody-really-know-wha
> t-accuracy-is-4190
>
> for different perspectives. [The second one only mentions the median in the
> abstract, so it's theoretically possible that you could have trouble with 95%
> within 100m, but it
I will fix the nits as you suggest.
We have quite a bit of experience in the U.S. with what kind of GPS accuracy
we can get. There are millions of phones and tens of thousands of calls
annually using GPS positioning. It is quite difficult to achieve a 100
meter accuracy 95% of the time. Technol
The draft merely adds a field to a registry that requires specification
required and expert review. I think Informational is acceptable, but will
defer to chairs for concurrence.
The only restriction on content is in RFC4776 which states:
Component values MUST be encoded as UTF-8 [7]. They SH
I have not forgotten this. I have been asking around for other opinions.
I still find it hard to believe that:
sip:123;[EMAIL PROTECTED];user=dialstring
is preferable to:
sip:[EMAIL PROTECTED];user=dialstring;phone-context=dial.example.com
but if that is the way most people want it, it's not a
I think your proposed changes are fine, and I will modify the text as you
suggest.
Brian
-Original Message-
From: Tom-PT Taylor [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 26, 2006 8:36 AM
To: gen-art@ietf.org; iptel@ietf.org; [EMAIL PROTECTED]; Peterson, Jon
Subject: Gen-art review
11 matches
Mail list logo
