From exim@www1.ietf.org  Fri Apr  2 00:02:04 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 AAA09426
	for <sipping-emergency-archive@odin.ietf.org>; Fri, 2 Apr 2004 00:02:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9Dz6-0000w0-KO
	for sipping-emergency-archive@odin.ietf.org; Thu, 01 Apr 2004 21:00:40 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3220emi003580
	for sipping-emergency-archive@odin.ietf.org; Thu, 1 Apr 2004 21:00:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9CMR-000728-8c
	for sipping-emergency-web-archive@optimus.ietf.org; Thu, 01 Apr 2004 19:16:39 -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 TAA13035
	for <sipping-emergency-web-archive@ietf.org>; Thu, 1 Apr 2004 19:16:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9CMP-0000ST-00
	for sipping-emergency-web-archive@ietf.org; Thu, 01 Apr 2004 19:16:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9CLX-0000FU-00
	for sipping-emergency-web-archive@ietf.org; Thu, 01 Apr 2004 19:15:43 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9CKI-0007kV-00
	for sipping-emergency-web-archive@ietf.org; Thu, 01 Apr 2004 19:14:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B99oa-0003zy-D5
	for sipping-emergency-web-archive@ietf.org; Thu, 01 Apr 2004 16:33:32 -0500
Date: Thu, 01 Apr 2004 11:25:13 -0500
Message-ID: <20040401162513.11029.46720.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.7 required=5.0 tests=AWL,DATE_IN_PAST_03_06,
	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  Fri Apr  9 11:50: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 LAA03533
	for <sipping-emergency-archive@odin.ietf.org>; Fri, 9 Apr 2004 11:50:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BByGz-0006kn-5G
	for sipping-emergency-archive@odin.ietf.org; Fri, 09 Apr 2004 11:50:29 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i39FoTrC025958
	for sipping-emergency-archive@odin.ietf.org; Fri, 9 Apr 2004 11:50:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BByGy-0006kb-W5
	for sipping-emergency-web-archive@optimus.ietf.org; Fri, 09 Apr 2004 11:50:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03510
	for <sipping-emergency-web-archive@ietf.org>; Fri, 9 Apr 2004 11:50:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BByGx-0001fN-00
	for sipping-emergency-web-archive@ietf.org; Fri, 09 Apr 2004 11:50:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BByFv-0001XO-00
	for sipping-emergency-web-archive@ietf.org; Fri, 09 Apr 2004 11:49:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BByEb-0001Nk-00
	for sipping-emergency-web-archive@ietf.org; Fri, 09 Apr 2004 11:48:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BByEb-0006V8-Rq
	for sipping-emergency-web-archive@ietf.org; Fri, 09 Apr 2004 11:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BByEX-0006Ua-E3
	for sipping-emergency@optimus.ietf.org; Fri, 09 Apr 2004 11:47:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03399
	for <sipping-emergency@ietf.org>; Fri, 9 Apr 2004 11:47:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BByEV-0001N0-00
	for sipping-emergency@ietf.org; Fri, 09 Apr 2004 11:47:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BByD4-0001GF-00
	for sipping-emergency@ietf.org; Fri, 09 Apr 2004 11:46:27 -0400
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BByC6-00012u-00
	for sipping-emergency@ietf.org; Fri, 09 Apr 2004 11:45:26 -0400
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 i39FiVaZ018617;
	Fri, 9 Apr 2004 11:44:31 -0400 (EDT)
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 LAA10526;
	Fri, 9 Apr 2004 11:44:31 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <GSN666B6>; Fri, 9 Apr 2004 11:44:30 -0400
Message-ID: <313680C9A886D511A06000204840E1CF070B65FB@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'nena-ltd@cs.columbia.edu'" <nena-ltd@cs.columbia.edu>,
        "'sipping-emergency@ietf.org'" <sipping-emergency@ietf.org>
Date: Fri, 9 Apr 2004 11:44:30 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping-emergency] rosen-dns-sos, update and call for discussion
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: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>,
	<mailto:sipping-emergency-request@ietf.org?subject=unsubscribe>
List-Id: <sipping-emergency.ietf.org>
List-Post: <mailto:sipping-emergency@ietf.org>
List-Help: <mailto:sipping-emergency-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>,
	<mailto:sipping-emergency-request@ietf.org?subject=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

<note this message is addressed to two groups, the ietf sipping
emergency list and the nena-ltd list.  There is some overlap of
these lists, so some of you will get two copies.  Both lists are
closed lists, so it's a little hard to carry this discussion on
one list>

If you haven't read draft-rosen-dns-sos-00, please do so.

I have had a number of conversations with DNS knowledgeable people
who have raised significant objections to some of the proposal,
and we have reached a compromise which I will be describing in
a subsequent update of that document.  The essence of the
compromise is to move portions of the data that was proposed
to be in the DNS to an HTTP server, in xml form, and supply
a pointer to that data in the DNS entry.  The data proposed to
be moved is:
	The POLY information (polygon representing the border of the
	element)

	An enumeration of all the lower levels at a node, to facilitate
	searching

	information that requires access security (interior of a building
	being the most obvious candidate)

The basic structure of the proposal remains - a tree proposed to be
at sos.arpa, delegation to countries, and hierarchical levels roughly
matching the levels in a civil address, down to room level, pointers
to services responding to that location, etc.

There will also be the following additions:
	Postal addresses, with cross links between dispatch locations
	and postal addresses, allowing conversion.  This allows users
	to view the address in a form which he may be more familiar.
	(My home is an example; the postal address is in Mars, which is
	in Butler County, but my house is in Pine, which is in Allegheny
	County)

	Mechanisms to support street prefixes and postfixes (North, NW,
	Avenue/Street).  These will be separator conventions, such as
	fulton_nw).

I'd like to open a wider discussion on this proposal, and solicit
input on what other changes I should consider in this second version.

Brian

_______________________________________________
Sipping-emergency mailing list
Sipping-emergency@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-emergency



