From exim@www1.ietf.org Mon Mar 1 10:25:45 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04268 for ; Mon, 1 Mar 2004 10:25:45 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxpID-0008LX-VI for sipping-emergency-archive@odin.ietf.org; Mon, 01 Mar 2004 10:25:17 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i21FPHJd032077 for sipping-emergency-archive@odin.ietf.org; Mon, 1 Mar 2004 10:25:17 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxpID-0008LH-QI for sipping-emergency-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 10:25:17 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04061 for ; Mon, 1 Mar 2004 10:25:14 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AxpIB-00077K-00 for sipping-emergency-web-archive@ietf.org; Mon, 01 Mar 2004 10:25:15 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Axol0-00073m-00 for sipping-emergency-web-archive@ietf.org; Mon, 01 Mar 2004 09:51:00 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AxoXD-0003T8-00 for sipping-emergency-web-archive@ietf.org; Mon, 01 Mar 2004 09:36:43 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by mx2.foretec.com with esmtp (Exim 4.24) id 1AxoGo-0002JW-9v for sipping-emergency-web-archive@ietf.org; Mon, 01 Mar 2004 09:19:46 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxoGj-0002tP-6O for sipping-emergency-web-archive@ietf.org; Mon, 01 Mar 2004 09:19:41 -0500 Date: Mon, 01 Mar 2004 09:19:41 -0500 Message-ID: <20040301141941.27462.7335.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: sipping-emergency-web-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, sipping-emergency-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for sipping-emergency-web-archive@ietf.org: List Password // URL ---- -------- sipping-emergency@ietf.org imavoz https://www1.ietf.org/mailman/options/sipping-emergency/sipping-emergency-web-archive%40ietf.org From exim@www1.ietf.org Thu Mar 4 03:03:19 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26360 for ; Thu, 4 Mar 2004 03:03:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aynoi-0006r9-10 for sipping-emergency-archive@odin.ietf.org; Thu, 04 Mar 2004 03:02:52 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2482poC026353 for sipping-emergency-archive@odin.ietf.org; Thu, 4 Mar 2004 03:02:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aynoh-0006qw-Nm for sipping-emergency-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 03:02:51 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26317 for ; Thu, 4 Mar 2004 03:02:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aynod-0001Zm-00 for sipping-emergency-web-archive@ietf.org; Thu, 04 Mar 2004 03:02:47 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AynnA-00012q-00 for sipping-emergency-web-archive@ietf.org; Thu, 04 Mar 2004 03:01:17 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Aynkx-0000Ua-00 for sipping-emergency-web-archive@ietf.org; Thu, 04 Mar 2004 02:58:59 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by mx2.foretec.com with esmtp (Exim 4.24) id 1Aynkz-0000Z0-Pi for sipping-emergency-web-archive@ietf.org; Thu, 04 Mar 2004 02:59:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aynl0-0006RU-4i for sipping-emergency-web-archive@ietf.org; Thu, 04 Mar 2004 02:59:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AynkY-0006PL-Nn for sipping-emergency@optimus.ietf.org; Thu, 04 Mar 2004 02:58:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25737 for ; Thu, 4 Mar 2004 02:58:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AynkU-0000Te-00 for sipping-emergency@ietf.org; Thu, 04 Mar 2004 02:58:30 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aynjc-0000IO-00 for sipping-emergency@ietf.org; Thu, 04 Mar 2004 02:57:36 -0500 Received: from mailgate.pit.comms.marconi.com ([169.144.68.6]) by ietf-mx with esmtp (Exim 4.12) id 1Aynj4-00005l-00 for sipping-emergency@ietf.org; Thu, 04 Mar 2004 02:57:02 -0500 Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id i247uXaZ016616 for ; Thu, 4 Mar 2004 02:56:33 -0500 (EST) Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id CAA20165 for ; Thu, 4 Mar 2004 02:56:33 -0500 (EST) Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19) id ; Thu, 4 Mar 2004 02:56:33 -0500 Message-ID: <313680C9A886D511A06000204840E1CF070B6496@whq-msgusr-02.pit.comms.marconi.com> From: "Rosen, Brian" To: "'sipping-emergency@ietf.org'" Date: Thu, 4 Mar 2004 02:56:32 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Sipping-emergency] Mandatory use of contact element in pidf-lo Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Nadine pointed out that one of the things you want to know about a location report is who created it. If it was wrong in some way, you would then use that information to figure out who made a mistake. There is a contact element defined in the pidf-lo. I think we could mandate its use in the location reported in an emergency call. One issue is whether we would prefer it to be a sip uri as the document suggests, or an http uri, which might provide more information. Brian _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency From exim@www1.ietf.org Tue Mar 9 15:03:23 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18482 for ; Tue, 9 Mar 2004 15:03:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0nRI-0000jG-1p for sipping-emergency-archive@odin.ietf.org; Tue, 09 Mar 2004 15:02:56 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i29K2u4n002794 for sipping-emergency-archive@odin.ietf.org; Tue, 9 Mar 2004 15:02:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0nRH-0000iw-T1 for sipping-emergency-web-archive@optimus.ietf.org; Tue, 09 Mar 2004 15:02:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18454 for ; Tue, 9 Mar 2004 15:02:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B0nRE-000139-00 for sipping-emergency-web-archive@ietf.org; Tue, 09 Mar 2004 15:02:53 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B0nQH-0000su-00 for sipping-emergency-web-archive@ietf.org; Tue, 09 Mar 2004 15:01:53 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B0nPP-0000jK-00 for sipping-emergency-web-archive@ietf.org; Tue, 09 Mar 2004 15:00:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0nPR-0007Jw-VZ for sipping-emergency-web-archive@ietf.org; Tue, 09 Mar 2004 15:01:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0nPJ-0007Ec-FN for sipping-emergency@optimus.ietf.org; Tue, 09 Mar 2004 15:00:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18302 for ; Tue, 9 Mar 2004 15:00:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B0nPG-0000hv-00 for sipping-emergency@ietf.org; Tue, 09 Mar 2004 15:00:50 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B0nOO-0000Xv-00 for sipping-emergency@ietf.org; Tue, 09 Mar 2004 14:59:57 -0500 Received: from reliant.cs.columbia.edu ([128.59.16.60]) by ietf-mx with esmtp (Exim 4.12) id 1B0nNV-0000NR-00 for sipping-emergency@ietf.org; Tue, 09 Mar 2004 14:59:02 -0500 Received: from reliant.cs.columbia.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 9A2AF4D070 for ; Tue, 9 Mar 2004 14:57:24 -0500 (EST) Received: from bear.cs.columbia.edu (bear.cs.columbia.edu [128.59.16.121]) by reliant.cs.columbia.edu (Postfix) with ESMTP id 7BDCD4D610 for ; Tue, 9 Mar 2004 06:30:23 -0500 (EST) Received: from cs.columbia.edu (pool-138-89-69-144.mad.east.verizon.net [138.89.69.144]) (authenticated bits=0) by bear.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id i29BVtfG021019 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 9 Mar 2004 06:31:55 -0500 Message-ID: <404DAB25.7010306@cs.columbia.edu> Date: Tue, 09 Mar 2004 06:31:49 -0500 From: Henning Schulzrinne User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040219 X-Accept-Language: en-us, en, de MIME-Version: 1.0 To: sipping-emergency@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 4.5.0.92886, Antispam-Core: 4.0.4.92622, Antispam-Data: 2004.3.8.93754 X-PerlMx-Spam: Gauge=XIII, Probability=13%, Report='X_NJABL_DUL 1, URI_HEAVY 0.206, __SANE_MSGID 0, __USER_AGENT 0, X_ACCEPT_LANG 0, __MIME_VERSION 0, __TO_MALFORMED_2 0, SUBJECT_IS_LIST 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __MIME_TEXT_ONLY 0, __MOZILLA_MSGID 0, RCVD_IN_NJABL_ORG 0, __HAS_MSGID 0, USER_AGENT 0.000' Content-Transfer-Encoding: 7bit Subject: [Sipping-emergency] 'sos' draft discussion on URI mailing list Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit As suggested by Rohan, I sent a brief note to the URI mailing list; see archives at http://lists.w3.org/Archives/Public/uri/ _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency From exim@www1.ietf.org Tue Mar 9 15:07:20 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19058 for ; Tue, 9 Mar 2004 15:07:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0nV7-0003ch-Fg for sipping-emergency-archive@odin.ietf.org; Tue, 09 Mar 2004 15:06:53 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i29K6rd9013919 for sipping-emergency-archive@odin.ietf.org; Tue, 9 Mar 2004 15:06:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0nV7-0003c2-7Z for sipping-emergency-web-archive@optimus.ietf.org; Tue, 09 Mar 2004 15:06:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18984 for ; Tue, 9 Mar 2004 15:06:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B0nV4-0001mK-00 for sipping-emergency-web-archive@ietf.org; Tue, 09 Mar 2004 15:06:50 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B0nUD-0001cB-00 for sipping-emergency-web-archive@ietf.org; Tue, 09 Mar 2004 15:05:58 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B0nTK-0001SI-00 for sipping-emergency-web-archive@ietf.org; Tue, 09 Mar 2004 15:05:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0nTM-0002Ym-5s for sipping-emergency-web-archive@ietf.org; Tue, 09 Mar 2004 15:05:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0nTI-0002XK-SA for sipping-emergency@optimus.ietf.org; Tue, 09 Mar 2004 15:05:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18705 for ; Tue, 9 Mar 2004 15:04:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B0nTF-0001RZ-00 for sipping-emergency@ietf.org; Tue, 09 Mar 2004 15:04:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B0nSM-0001H7-00 for sipping-emergency@ietf.org; Tue, 09 Mar 2004 15:04:02 -0500 Received: from cs.cs.columbia.edu ([128.59.16.20]) by ietf-mx with esmtp (Exim 4.12) id 1B0nRa-00015b-00 for sipping-emergency@ietf.org; Tue, 09 Mar 2004 15:03:14 -0500 Received: from magnum.cs.columbia.edu (IDENT:root@magnum.cs.columbia.edu [128.59.16.117]) by cs.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i29K22Jw001764 for ; Tue, 9 Mar 2004 15:02:02 -0500 (EST) Received: from cs.columbia.edu (chairpc.cs.columbia.edu [128.59.16.206]) by magnum.cs.columbia.edu (8.11.6/8.9.3) with ESMTP id i29K22C17791 for ; Tue, 9 Mar 2004 15:02:02 -0500 Message-ID: <404E22BA.2000501@cs.columbia.edu> Date: Tue, 09 Mar 2004 15:02:02 -0500 From: Henning Schulzrinne User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040219 X-Accept-Language: en-us, en MIME-Version: 1.0 To: sipping-emergency@ietf.org Subject: Re: [Sipping-emergency] 'sos' draft discussion on URI mailing list References: <404DAB25.7010306@cs.columbia.edu> In-Reply-To: <404DAB25.7010306@cs.columbia.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Well, once the silly W3 system actually *lets* me post... Henning Schulzrinne wrote: > As suggested by Rohan, I sent a brief note to the URI mailing list; see > archives at http://lists.w3.org/Archives/Public/uri/ > > > > _______________________________________________ > Sipping-emergency mailing list > Sipping-emergency@ietf.org > https://www1.ietf.org/mailman/listinfo/sipping-emergency _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency From exim@www1.ietf.org Sun Mar 14 02:21:20 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05752 for ; Sun, 14 Mar 2004 02:21:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2PvX-0002lM-Qw for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 02:20:51 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2E7KpCa010593 for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 02:20:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2PvV-0002kU-LP for sipping-emergency-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 02:20:49 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05714 for ; Sun, 14 Mar 2004 02:20:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2PvS-00010o-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 02:20:46 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2PuU-0000xB-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 02:19:47 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B2Pti-0000tZ-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 02:18:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2Ptk-00028W-Qv for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 02:19:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2PtY-00025R-Vd for sipping-emergency@optimus.ietf.org; Sun, 14 Mar 2004 02:18:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05562 for ; Sun, 14 Mar 2004 02:18:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2PtV-0000sL-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 02:18:45 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2Psa-0000o5-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 02:17:49 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1B2Pri-0000f1-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 02:16:54 -0500 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 13 Mar 2004 23:20:37 +0000 Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i2E7GNK2029760 for ; Sat, 13 Mar 2004 23:16:23 -0800 (PST) Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id XAA28290 for ; Sat, 13 Mar 2004 23:16:22 -0800 (PST) Message-Id: <4.3.2.7.2.20040314005715.02794f00@localhost> X-Sender: jmpolk@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 14 Mar 2004 01:16:29 -0600 To: sipping-emergency@ietf.org From: "James M. Polk" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Sipping-emergency] PIDF-LO Emergency Additions for consideration Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 All A group of us in Seoul reacted to the discussion in SIPPING and Geopriv regarding where certain requirements should be met regarding added information within a SIP INVITE message. I initiated most of the confusion by listing several requirements that were brought to my attention (due to me writing (with Brian Rosen) the Location Conveyance in SIP ID) as being necessary within the message (I might not have explained very well that the message needed these elements - SIP itself did not necessarily). You can review my preso from the softarmor site for what was presented. The group of us (Brian, Henning, myself, Keith Drage, Hannes Tschofenig and Nadine Abbott) distilled to two the list of 5 or 6 that should be addressed within the PIDF-LO ID for now. Jon (that doc's author) is already aware of 1 of these, and has heard about the other - but didn't know to my knowledge which set of additional elements we'd chosen. We agreed this reflector would be the first to see the list before it's offered to the Geopriv list during that ID's WGLC. We want to request that the two additional information elements be: 1. by what mechanism did the UAC receive its LI from (.11, GPS, manual entry, Triangulation, DHCP) by name, not number i.e: *not* 1=GPS 2=DHCP etc I think this list is going to have to be IANA registered for this effort for consistency. 2. what organization was that LI field value provided by (in the form of a URI) comments? cheers, James ******************* Truth is not to be argued... it is to be presented _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency From exim@www1.ietf.org Sun Mar 14 15:00:10 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03602 for ; Sun, 14 Mar 2004 15:00:10 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2blk-0004bA-9r for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 14:59:42 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2EJxVLf017369 for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 14:59:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2blj-0004W4-BL for sipping-emergency-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 14:59:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03488 for ; Sun, 14 Mar 2004 14:59:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2blg-0003Ik-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:59:28 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2bkh-00036H-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:58:27 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B2bkG-0002yA-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:58:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2bkI-0003Zt-FI for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:58:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2X16-0007oT-JE for sipping-emergency@optimus.ietf.org; Sun, 14 Mar 2004 09:55:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21605 for ; Sun, 14 Mar 2004 09:55:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2X13-0007Wc-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 09:55:01 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2X05-0007Ok-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 09:54:01 -0500 Received: from cs.columbia.edu ([128.59.16.20]) by ietf-mx with esmtp (Exim 4.12) id 1B2Wz7-0007Hr-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 09:53:01 -0500 Received: from bear.cs.columbia.edu (IDENT:XLu6JpSO51EVm+mjp3r+vs3KS55cpSXF@bear.cs.columbia.edu [128.59.16.121]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i2EEqwNC027768 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Sun, 14 Mar 2004 09:52:58 -0500 (EST) Received: from cs.columbia.edu (pool-138-89-69-144.mad.east.verizon.net [138.89.69.144]) (authenticated bits=0) by bear.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id i2EEqvfG001542 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 14 Mar 2004 09:52:58 -0500 Message-ID: <405471C3.7020506@cs.columbia.edu> Date: Sun, 14 Mar 2004 09:52:51 -0500 From: Henning Schulzrinne User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040219 X-Accept-Language: en-us, en, de MIME-Version: 1.0 To: "James M. Polk" CC: sipping-emergency@ietf.org Subject: Re: [Sipping-emergency] PIDF-LO Emergency Additions for consideration References: <4.3.2.7.2.20040314005715.02794f00@localhost> In-Reply-To: <4.3.2.7.2.20040314005715.02794f00@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,CELL_PHONE_BOOST autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit > 1. by what mechanism did the UAC receive its LI from (.11, GPS, > manual entry, Triangulation, DHCP) by name, not number > > i.e: *not* > 1=GPS > 2=DHCP > etc > > I think this list is going to have to be IANA registered for this > effort for consistency. Indeed. This would be something simple like gps (I think more clearly distinguishes this from the next item below.) Text could be something like: The element describes the way that the location information in the location object was derived. Its value is drawn from a set of IANA-registered tokens that include GPS: Global Positioning System A-GPS: GPS with assistance manual: entered manually by an operator or user, e.g., based on subscriber billing or service location information DHCP: provided by DHCP [geo,civil] triangulation: triangulated from time-of-arrival, signal strength or similar measurements cell: location of the cellular radio antenna or 802.11 access point > > 2. what organization was that LI field value provided by (in the > form of a URI) sip:foo@bar.com One question is whether (2) is meant for human consumption or for some robot. If human consumption, we don't have to say much more than 'URI identifying the entity that calculated the geospatial or civil location information. This allows the recipient to determine, for example, if the location information was provided by the target itself or some third party and may allow the recipient to contact the entity identified by the URI to report errors.'. If suitable for a robot, we would have to define what kind of information such a robot would find useful, such as - some standard-format contact information (like a vCard) - some description of the likely accuracy of the measurement method I think at this point we need to provide precise text. If we're unable to do that, it probably indicates that the concepts are too fuzzy and insufficiently baked for inclusion. Henning _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency From exim@www1.ietf.org Sun Mar 14 15:18:46 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05769 for ; Sun, 14 Mar 2004 15:18:46 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2c3t-0006vX-Pb for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 15:18:17 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2EKIHOU026620 for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 15:18:17 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2c3t-0006vC-Kf for sipping-emergency-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 15:18:17 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05615 for ; Sun, 14 Mar 2004 15:18:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2c3s-0006Du-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 15:18:16 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2c2N-0005na-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 15:16:44 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1B2c0S-0005Qx-03 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 15:14:44 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by mx2.foretec.com with esmtp (Exim 4.24) id 1B2bkb-0006iZ-42 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:58:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2bkU-0003gS-1s for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:58:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2XuI-0006Ry-5O for sipping-emergency@optimus.ietf.org; Sun, 14 Mar 2004 10:52:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24005 for ; Sun, 14 Mar 2004 10:52:02 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2XuF-0005rb-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 10:52:03 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2XtK-0005m0-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 10:51:07 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1B2XsV-0005aw-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 10:50:15 -0500 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 14 Mar 2004 07:54:00 +0000 Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i2EFngK2016117; Sun, 14 Mar 2004 07:49:43 -0800 (PST) Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id HAA22147; Sun, 14 Mar 2004 07:49:41 -0800 (PST) Message-Id: <4.3.2.7.2.20040314094926.027abf00@localhost> X-Sender: jmpolk@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 14 Mar 2004 09:49:48 -0600 To: Henning Schulzrinne From: "James M. Polk" Subject: Re: [Sipping-emergency] PIDF-LO Emergency Additions for consideration Cc: sipping-emergency@ietf.org In-Reply-To: <40547BA2.9080302@cs.columbia.edu> References: <4.3.2.7.2.20040314092252.02771948@localhost> <4.3.2.7.2.20040314005715.02794f00@localhost> <4.3.2.7.2.20040314005715.02794f00@localhost> <4.3.2.7.2.20040314092252.02771948@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 At 10:34 AM 3/14/2004 -0500, Henning Schulzrinne wrote: >More detail is better, so I agree with your suggestion of splitting >things. I would suggest that once we have reached closure in this >subgroup, that we send text to the geopriv mailing list, so that it is >part of the official last-call record. I agree >James M. Polk wrote: > >>Below is good with one exception: >>I think the 802.11 method type should be unique, as it has some unique >>properties associated with distance (within) from the Access Point >>antenna that might prove useful from an accuracy/resolution point of view >>during the dispatch of police/fire/ambulance personnel. cheers, James ******************* Truth is not to be argued... it is to be presented _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency From exim@www1.ietf.org Sun Mar 14 21:33:59 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19695 for ; Sun, 14 Mar 2004 21:33:59 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2hv1-0007zZ-M1 for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 21:33:32 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2F2XV8u030715 for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 21:33:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2hv1-0007zK-GM for sipping-emergency-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 21:33:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19664 for ; Sun, 14 Mar 2004 21:33:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2huy-00040e-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 21:33:28 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2hu8-0003u1-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 21:32:37 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B2htX-0003nQ-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 21:31:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2htZ-0007qz-A3 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 21:32:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2htC-0007qH-KF for sipping-emergency@optimus.ietf.org; Sun, 14 Mar 2004 21:31:38 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19595 for ; Sun, 14 Mar 2004 21:31:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2ht9-0003mH-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 21:31:36 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2hs4-0003en-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 21:30:29 -0500 Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1B2hrd-0003Ys-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 21:30:01 -0500 Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.30; FreeBSD) id 1B2hrc-000H0q-Ft; Mon, 15 Mar 2004 02:30:00 +0000 To: Henning Schulzrinne cc: "James M. Polk" , sipping-emergency@ietf.org Subject: Re: [Sipping-emergency] PIDF-LO Emergency Additions for consideration In-Reply-To: Message from Henning Schulzrinne of "Sun, 14 Mar 2004 09:52:51 EST." <405471C3.7020506@cs.columbia.edu> Date: Sun, 14 Mar 2004 18:30:00 -0800 From: Allison Mankin Message-Id: Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 > > 2. what organization was that LI field value provided by (in the > form of a URI) > > sip:foo@bar.com Henning and James, Could you give more explanation of what you mean by the organzation that provided the LI field value? What would the field be set to for GPS? Could we (here) get a better feel for what use you expect the emergency center to make of this info? Allison _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency From exim@www1.ietf.org Sun Mar 14 22:27:58 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21451 for ; Sun, 14 Mar 2004 22:27:58 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2ilH-0002wp-VC for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 22:27:32 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2F3RVRL011325 for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 22:27:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2ilH-0002wa-Q9 for sipping-emergency-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 22:27:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21439 for ; Sun, 14 Mar 2004 22:27:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2ilE-0002Qy-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 22:27:28 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2ikH-0002L8-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 22:26:30 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B2ijn-0002FO-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 22:25:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2ijq-0002v6-06 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 22:26:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2ijO-0002uC-Fa for sipping-emergency@optimus.ietf.org; Sun, 14 Mar 2004 22:25:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21374 for ; Sun, 14 Mar 2004 22:25:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2ijL-0002Em-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 22:25:31 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2iiQ-00028q-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 22:24:35 -0500 Received: from cs.columbia.edu ([128.59.16.20]) by ietf-mx with esmtp (Exim 4.12) id 1B2iiE-00022X-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 22:24:22 -0500 Received: from bear.cs.columbia.edu (IDENT:gBljN4h26hiWVyKluSoUYaiDYmHKS4iE@bear.cs.columbia.edu [128.59.16.121]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i2F3MNNC011942 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Sun, 14 Mar 2004 22:22:23 -0500 (EST) Received: from cs.columbia.edu (pool-138-89-69-144.mad.east.verizon.net [138.89.69.144]) (authenticated bits=0) by bear.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id i2F3MMfG023492 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 14 Mar 2004 22:22:22 -0500 Message-ID: <40552168.6080807@cs.columbia.edu> Date: Sun, 14 Mar 2004 22:22:16 -0500 From: Henning Schulzrinne User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040219 X-Accept-Language: en-us, en, de MIME-Version: 1.0 To: Allison Mankin CC: "James M. Polk" , sipping-emergency@ietf.org Subject: Re: [Sipping-emergency] PIDF-LO Emergency Additions for consideration References: <200403150230.i2F2URNC006272@cs.columbia.edu> In-Reply-To: <200403150230.i2F2URNC006272@cs.columbia.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit > Henning and James, > > Could you give more explanation of what you mean by the organzation > that provided the LI field value? This would be the responsible source of the data. > > What would the field be set to for GPS? For 'handset' location determination, there could be two options: (1) omitting the information implies that this was derived by the target itself (2) or the identifier (e.g., SIP URI) of the target could be used This seems useful primarily if the location information was determined by a third party. The slightly tricky part is that this could be considered to overlap with an S/MIME signature, but it is somewhat different: the signature indicates who vouches for the information, while the information here indicates who generated the information. > > Could we (here) get a better feel for what use you expect the emergency > center to make of this info? The discussion so far has been primarily for debugging purposes, if I understand James' and Nadine's comments. For example, if the information turns out to be wrong or dubious, the PSAP would then have somebody to ask about this and find out what happened. I believe this type of information is included in existing location conveyance mechanisms, although I'd like to be convinced that a URI would indeed allow lossless relaying of such information. > > Allison > _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency From exim@www1.ietf.org Sun Mar 14 23:39:17 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23517 for ; Sun, 14 Mar 2004 23:39:17 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2jsH-0007dz-MI for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 23:38:49 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2F4cnCC029377 for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 23:38:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2jsH-0007dk-HZ for sipping-emergency-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 23:38:49 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23442 for ; Sun, 14 Mar 2004 23:38:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2jsF-0002KW-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 23:38:47 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2jrK-0002Bd-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 23:37:51 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B2jqV-00022z-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 23:36:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2jqW-0007J0-R5 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 23:37:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2jq3-0007IZ-DS for sipping-emergency@optimus.ietf.org; Sun, 14 Mar 2004 23:36:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23302 for ; Sun, 14 Mar 2004 23:36:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2jq0-000206-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 23:36:29 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2jp5-0001u5-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 23:35:32 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1B2joH-0001iU-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 23:34:41 -0500 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-5.cisco.com with ESMTP; 14 Mar 2004 20:34:31 -0800 Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i2F4YAK2002928; Sun, 14 Mar 2004 20:34:10 -0800 (PST) Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id UAA02357; Sun, 14 Mar 2004 20:34:08 -0800 (PST) Message-Id: <4.3.2.7.2.20040314223222.036b0f00@localhost> X-Sender: jmpolk@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 14 Mar 2004 22:34:15 -0600 To: Henning Schulzrinne , Allison Mankin From: "James M. Polk" Subject: Re: [Sipping-emergency] PIDF-LO Emergency Additions for consideration Cc: sipping-emergency@ietf.org In-Reply-To: <40552168.6080807@cs.columbia.edu> References: <200403150230.i2F2URNC006272@cs.columbia.edu> <200403150230.i2F2URNC006272@cs.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Allison I believe Henning answered the questions well, from my POV Do you have further comments that I can add more to? At 10:22 PM 3/14/2004 -0500, Henning Schulzrinne wrote: >>Henning and James, >>Could you give more explanation of what you mean by the organzation >>that provided the LI field value? > >This would be the responsible source of the data. > >>What would the field be set to for GPS? > >For 'handset' location determination, there could be two options: >(1) omitting the information implies that this was derived by the target >itself >(2) or the identifier (e.g., SIP URI) of the target could be used > >This seems useful primarily if the location information was determined by >a third party. > >The slightly tricky part is that this could be considered to overlap with >an S/MIME signature, but it is somewhat different: the signature indicates >who vouches for the information, while the information here indicates who >generated the information. > > >>Could we (here) get a better feel for what use you expect the emergency >>center to make of this info? > >The discussion so far has been primarily for debugging purposes, if I >understand James' and Nadine's comments. For example, if the information >turns out to be wrong or dubious, the PSAP would then have somebody to ask >about this and find out what happened. > >I believe this type of information is included in existing location >conveyance mechanisms, although I'd like to be convinced that a URI would >indeed allow lossless relaying of such information. > > >>Allison > >_______________________________________________ >Sipping-emergency mailing list >Sipping-emergency@ietf.org >https://www1.ietf.org/mailman/listinfo/sipping-emergency cheers, James ******************* Truth is not to be argued... it is to be presented _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency From exim@www1.ietf.org Tue Mar 30 17:46:33 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19799 for ; Tue, 30 Mar 2004 17:46:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8Rjk-0006YH-7K for sipping-emergency-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:36 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2EK0n9Q020010 for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 15:00:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2bmy-0005Bi-L0 for sipping-emergency-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 15:00:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03648 for ; Sun, 14 Mar 2004 15:00:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2bmv-0003bZ-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 15:00:45 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2blQ-0003Fi-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:59:13 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B2bkP-000315-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:58:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2bkS-0003ej-2R for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:58:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2Xfm-0004Lc-Jb for sipping-emergency@optimus.ietf.org; Sun, 14 Mar 2004 10:37:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23170 for ; Sun, 14 Mar 2004 10:37:03 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2Xfk-00047W-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 10:37:04 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2Xem-0003zF-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 10:36:05 -0500 Received: from cs.columbia.edu ([128.59.16.20]) by ietf-mx with esmtp (Exim 4.12) id 1B2Xdr-0003sG-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 10:35:07 -0500 Received: from bear.cs.columbia.edu (IDENT:mzfDsAt0CZ+MJ6QRqh8gEBFvXpNxJ9fW@bear.cs.columbia.edu [128.59.16.121]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i2EFZ4NC005641 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Sun, 14 Mar 2004 10:35:04 -0500 (EST) Received: from cs.columbia.edu (pool-138-89-69-144.mad.east.verizon.net [138.89.69.144]) (authenticated bits=0) by bear.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id i2EFZ3fG004423 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 14 Mar 2004 10:35:03 -0500 Message-ID: <40547BA2.9080302@cs.columbia.edu> Date: Sun, 14 Mar 2004 10:34:58 -0500 From: Henning Schulzrinne User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040219 X-Accept-Language: en-us, en, de MIME-Version: 1.0 To: "James M. Polk" CC: sipping-emergency@ietf.org Subject: Re: [Sipping-emergency] PIDF-LO Emergency Additions for consideration References: <4.3.2.7.2.20040314005715.02794f00@localhost> <4.3.2.7.2.20040314005715.02794f00@localhost> <4.3.2.7.2.20040314092252.02771948@localhost> In-Reply-To: <4.3.2.7.2.20040314092252.02771948@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,CELL_PHONE_BOOST autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit More detail is better, so I agree with your suggestion of splitting things. I would suggest that once we have reached closure in this subgroup, that we send text to the geopriv mailing list, so that it is part of the official last-call record. James M. Polk wrote: > Below is good with one exception: > > I think the 802.11 method type should be unique, as it has some unique > properties associated with distance (within) from the Access Point > antenna that might prove useful from an accuracy/resolution point of > view during the dispatch of police/fire/ambulance personnel. > > > At 09:52 AM 3/14/2004 -0500, Henning Schulzrinne wrote: > >>> 1. by what mechanism did the UAC receive its LI from (.11, GPS, >>> manual entry, Triangulation, DHCP) by name, not number >>> i.e: *not* >>> 1=GPS >>> 2=DHCP >>> etc >>> I think this list is going to have to be IANA registered for this >>> effort for consistency. >> >> >> Indeed. This would be something simple like >> >> gps >> >> (I think more clearly distinguishes this from the next item >> below.) >> >> Text could be something like: >> >> The element describes the way that the location information >> in the location object was derived. Its value is drawn from a set of >> IANA-registered tokens that include >> >> GPS: Global Positioning System >> >> A-GPS: GPS with assistance >> >> manual: entered manually by an operator or user, e.g., based on >> subscriber billing or service location information >> >> DHCP: provided by DHCP [geo,civil] >> >> triangulation: triangulated from time-of-arrival, signal strength or >> similar measurements >> >> cell: location of the cellular radio antenna or 802.11 access point >> >> >>> 2. what organization was that LI field value provided by (in the >>> form of a URI) >> >> >> sip:foo@bar.com >> >> One question is whether (2) is meant for human consumption or for some >> robot. If human consumption, we don't have to say much more than 'URI >> identifying the entity that calculated the geospatial or civil >> location information. This allows the recipient to determine, for >> example, if the location information was provided by the target itself >> or some third party and may allow the recipient to contact the entity >> identified by the URI to report errors.'. >> >> If suitable for a robot, we would have to define what kind of >> information such a robot would find useful, such as >> >> - some standard-format contact information (like a vCard) >> - some description of the likely accuracy of the measurement method >> >> I think at this point we need to provide precise text. If we're unable >> to do that, it probably indicates that the concepts are too fuzzy and >> insufficiently baked for inclusion. >> >> Henning > > > > cheers, > James > > ******************* > Truth is not to be argued... it is to be presented _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency From exim@www1.ietf.org Tue Mar 30 17:55:39 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21656 for ; Tue, 30 Mar 2004 17:55:39 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8Rjd-0006YH-Vo for sipping-emergency-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:30 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2EK0okh020521 for sipping-emergency-archive@odin.ietf.org; Sun, 14 Mar 2004 15:00:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2bn0-0005Jx-N1 for sipping-emergency-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 15:00:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03661 for ; Sun, 14 Mar 2004 15:00:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2bmx-0003bs-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 15:00:47 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2blT-0003GJ-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:59:16 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B2bkS-0002yk-00 for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:58:12 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2bkQ-0003dS-Vf for sipping-emergency-web-archive@ietf.org; Sun, 14 Mar 2004 14:58:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B2Xaw-0003hr-4L for sipping-emergency@optimus.ietf.org; Sun, 14 Mar 2004 10:32:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22838 for ; Sun, 14 Mar 2004 10:32:02 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B2Xat-0003Y5-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 10:32:03 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B2XZx-0003RE-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 10:31:05 -0500 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1B2XZ4-0003FA-00 for sipping-emergency@ietf.org; Sun, 14 Mar 2004 10:30:10 -0500 Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i2EFTcaD011364; Sun, 14 Mar 2004 07:29:38 -0800 (PST) Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id HAA13978; Sun, 14 Mar 2004 07:29:37 -0800 (PST) Message-Id: <4.3.2.7.2.20040314092252.02771948@localhost> X-Sender: jmpolk@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 14 Mar 2004 09:29:44 -0600 To: Henning Schulzrinne From: "James M. Polk" Subject: Re: [Sipping-emergency] PIDF-LO Emergency Additions for consideration Cc: sipping-emergency@ietf.org In-Reply-To: <405471C3.7020506@cs.columbia.edu> References: <4.3.2.7.2.20040314005715.02794f00@localhost> <4.3.2.7.2.20040314005715.02794f00@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: sipping-emergency-admin@ietf.org Errors-To: sipping-emergency-admin@ietf.org X-BeenThere: sipping-emergency@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,CELL_PHONE_BOOST autolearn=no version=2.60 Below is good with one exception: I think the 802.11 method type should be unique, as it has some unique properties associated with distance (within) from the Access Point antenna that might prove useful from an accuracy/resolution point of view during the dispatch of police/fire/ambulance personnel. At 09:52 AM 3/14/2004 -0500, Henning Schulzrinne wrote: >>1. by what mechanism did the UAC receive its LI from (.11, GPS, >> manual entry, Triangulation, DHCP) by name, not number >> i.e: *not* >> 1=GPS >> 2=DHCP >> etc >> I think this list is going to have to be IANA registered for this >> effort for consistency. > >Indeed. This would be something simple like > >gps > >(I think more clearly distinguishes this from the next item below.) > >Text could be something like: > >The element describes the way that the location information in >the location object was derived. Its value is drawn from a set of >IANA-registered tokens that include > >GPS: Global Positioning System > >A-GPS: GPS with assistance > >manual: entered manually by an operator or user, e.g., based on subscriber >billing or service location information > >DHCP: provided by DHCP [geo,civil] > >triangulation: triangulated from time-of-arrival, signal strength or >similar measurements > >cell: location of the cellular radio antenna or 802.11 access point > > >>2. what organization was that LI field value provided by (in the >> form of a URI) > >sip:foo@bar.com > >One question is whether (2) is meant for human consumption or for some >robot. If human consumption, we don't have to say much more than 'URI >identifying the entity that calculated the geospatial or civil location >information. This allows the recipient to determine, for example, if the >location information was provided by the target itself or some third party >and may allow the recipient to contact the entity identified by the URI to >report errors.'. > >If suitable for a robot, we would have to define what kind of information >such a robot would find useful, such as > >- some standard-format contact information (like a vCard) >- some description of the likely accuracy of the measurement method > >I think at this point we need to provide precise text. If we're unable to >do that, it probably indicates that the concepts are too fuzzy and >insufficiently baked for inclusion. > >Henning cheers, James ******************* Truth is not to be argued... it is to be presented _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency