
From wwwrun@rfc-editor.org  Tue Sep  7 22:24:15 2010
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 165BE3A67A6 for <ecrit@core3.amsl.com>; Tue,  7 Sep 2010 22:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.037
X-Spam-Level: 
X-Spam-Status: No, score=-102.037 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, J_CHICKENPOX_25=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hc-7f6tdUj+9 for <ecrit@core3.amsl.com>; Tue,  7 Sep 2010 22:24:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id A65033A679F for <ecrit@ietf.org>; Tue,  7 Sep 2010 22:24:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 01341E06DF; Tue,  7 Sep 2010 22:24:40 -0700 (PDT)
To: hardie@qualcomm.com, andy@hxr.us, hgs+ecrit@cs.columbia.edu, Hannes.Tschofenig@nsn.com, gonzalo.camarillo@ericsson.com, rjsparks@nostrum.com, marc.linsner@cisco.com, rbarnes@bbn.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20100908052441.01341E06DF@rfc-editor.org>
Date: Tue,  7 Sep 2010 22:24:40 -0700 (PDT)
X-Mailman-Approved-At: Wed, 08 Sep 2010 08:51:29 -0700
Cc: ecrit@ietf.org, rfc-editor@rfc-editor.org
Subject: [Ecrit] [Technical Errata Reported] RFC5222 (2511)
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2010 05:24:15 -0000

The following errata report has been submitted for RFC5222,
"LoST: A Location-to-Service Translation Protocol".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5222&eid=2511

--------------------------------------
Type: Technical
Reported by: Martin Thomson <martin.thomson@andrew.com>

Section: 8.3.5, 8.4.2

Original Text
-------------
In 8.3.5:
     <locationValidation>
       <valid>country A1 A3 A6</valid>
       <invalid>PC</invalid>
       <unchecked>HNO</unchecked>
     </locationValidation>

In 8.4.2:
   ... Each element contains a list of tokens separated by
   whitespace, enumerating the civic location labels used in child
   elements of the <civicAddress> element.  ...
and:
   The example shown in Figure 5 and in Figure 6 indicates that the
   tokens 'country', 'A1', 'A3', and 'A6' have been validated by the
   LoST server.  ...

Corrected Text
--------------
In 8.3.5:
     <locationValidation
        xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
       <valid>ca:country ca:A1 ca:A3 ca:A6</valid>
       <invalid>ca:PC</invalid>
       <unchecked>ca:HNO</unchecked>
     </locationValidation>

In 8.4.2:
   ... Each element contains a list of qualified element names separated by
   whitespace, enumerating child elements of the <civicAddress> element.  ...
and:
   The example shown in Figure 5 and in Figure 6 indicates that the
   tokens 'country', 'A1', 'A3', and 'A6' from [RFC5139] have been validated
   by the LoST server.  ...

Notes
-----
It's not clear from the description how the location validation response elements are to be interpreted.  The example seems to indicate that the local name (only) for the civic address elements is used.  On the other hand, the schema seems to imply that, because this is a list of xs:QName, a qualified name is used for each.  The text itself is ambiguous.

Using the local name only could result in errors - it would be possible (albeit inadvisable) to extend RFC 5139 with an element that had the same local name as an existing element or an element in another extension.  As long as the namespace is distinct, this is perfectly legal, but it could lead to a naming conflict here.

With this interpretation, the elements in the example in 8.3.5 indicate elements from the LoST namespace (urn:ietf:params:xml:ns:lost1), rather than the civic address namespace (urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr).

Updating the description in 8.4.2 and the example in 8.3.5 would ensure that this doesn't result in interoperability problems.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5222 (draft-ietf-ecrit-lost-10)
--------------------------------------
Title               : LoST: A Location-to-Service Translation Protocol
Publication Date    : August 2008
Author(s)           : T. Hardie, A. Newton, H. Schulzrinne, H. Tschofenig
Category            : PROPOSED STANDARD
Source              : Emergency Context Resolution with Internet Technologies
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG

From stpeter@stpeter.im  Tue Sep 21 10:26:49 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A448A28C0E0 for <ecrit@core3.amsl.com>; Tue, 21 Sep 2010 10:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWAagzCXWWox for <ecrit@core3.amsl.com>; Tue, 21 Sep 2010 10:26:48 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id B3E2D3A69D2 for <ecrit@ietf.org>; Tue, 21 Sep 2010 10:26:48 -0700 (PDT)
Received: from dhcp-64-101-72-245.cisco.com (dhcp-64-101-72-245.cisco.com [64.101.72.245]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 56A8E40074; Tue, 21 Sep 2010 11:32:02 -0600 (MDT)
Message-ID: <4C98EAEF.6010402@stpeter.im>
Date: Tue, 21 Sep 2010 11:27:11 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.12) Gecko/20100914 Thunderbird/3.0.8
MIME-Version: 1.0
To: ecrit@ietf.org
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Rosen, Brian" <Brian.Rosen@neustar.biz>
Subject: [Ecrit] NENA URN namespace registration
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 17:26:49 -0000

Folks, I'm the sponsoring Area Director for an Internet-Draft that
requests registration of a URN namespace identifier for the National
Emergency Number Association (NENA):

https://datatracker.ietf.org/doc/draft-rosen-urn-nena/

I'd appreciate feedback from folks on this list as input to the IESG's
decision process (e.g., feedback regarding the relationship between the
proposed urn:nena:* tree and the urn:service:* tree registered by RFC
5031). I've deferred the ballot on this I-D for two weeks to enable
discussion on this list, so if you have comments please provide them
before October 7.

Thanks!

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From brian.rosen@neustar.biz  Tue Sep 21 11:06:44 2010
Return-Path: <brian.rosen@neustar.biz>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0535E3A6A9C for <ecrit@core3.amsl.com>; Tue, 21 Sep 2010 11:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.986
X-Spam-Level: 
X-Spam-Status: No, score=-1.986 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JE4kRGyqp6dr for <ecrit@core3.amsl.com>; Tue, 21 Sep 2010 11:06:42 -0700 (PDT)
Received: from neustar.com (mx2.neustar.com [156.154.25.104]) by core3.amsl.com (Postfix) with ESMTP id 6D7E83A68E3 for <ecrit@ietf.org>; Tue, 21 Sep 2010 11:06:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1285092427; x=1600449189; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=02zGuLqGzcw9KvEBZ7SdP TiY42g9s8YIlV8Wuovx5Qo=; b=DkOf/rv3C1vg60Kc6oqXStTVPj1DbiLx2QQxP tlE0Pzof9y+0mbsR5DT+llop9CjCe3mFj5huGTk/PQ4AIgjYA==
Received: from ([10.31.13.242]) by chihiron1.nc.neustar.com with ESMTP with TLS id 5202942.31635594; Tue, 21 Sep 2010 14:07:06 -0400
Received: from STNTEXCH01.cis.neustar.com ([fe80::31b6:4d09:2ada:e6c0]) by STNTEXCHHT03.cis.neustar.com ([::1]) with mapi; Tue, 21 Sep 2010 14:07:06 -0400
From: "Rosen, Brian" <Brian.Rosen@neustar.biz>
To: ecrit <ecrit@ietf.org>
Date: Tue, 21 Sep 2010 14:07:03 -0400
Thread-Topic: [Ecrit] NENA URN namespace registration
Thread-Index: ActZt8wZIrAD25FdSJ+sxUHyxqdRrw==
Message-ID: <767DAF36-7E2E-4B9C-BDB7-F832A2A6A27D@neustar.biz>
References: <4C98EAEF.6010402@stpeter.im>
In-Reply-To: <4C98EAEF.6010402@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA==
x-ems-stamp: LlNA1v4hj8GTImGLiRa8fw==
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Ecrit] NENA URN namespace registration
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 18:06:44 -0000

This namespace is being requested by NENA for a number of things, but one o=
f them is to define additional services for LoST that would only be used in=
 an Emergency Services IP Network (ESInet).  For example, we plan to use a =
urn like urn:nena:service:police.dispatch to use LoST for a PSAP to determi=
ne how to route a call, or the data associated with a call used for dispatc=
h, to the police department serves the location of an incident.  This kind =
of routing would not be available to anyone outside the ESInet.   Similarly=
, in our ESInets, we will often have multistage routing.  These routing ste=
ps involve an initial route, determined by a LoST query, followed by an eva=
luation of a policy for the entity whose URI is determined by the query.  =
=20

For example, the normal "PSAP URI" that is obtained with urn:service:sos wo=
uld route to, perhaps, a state/province level ESRP.  That ESRP would query =
LoST and obtain, perhaps, the URI of a county level ESRP.  That ESRP might =
query LoST and obtain the actual PSAP URI.  However, suppose the county ESR=
P was unavailable due to flooding.  The policy for the country ESRP would s=
pecify an alternate route for the conditions (which would be an ESRP that w=
as currently able to handle the duty).  Each of the routes obtained by the =
internal ESRPs would use a different service urn in the urn:nena namespace =
in their LoST query.   There are pretty compelling reasons to have multilev=
el route decisions in North America. =20

None of this needs any IETF "supervision", since it's strictly limited to u=
se within our (private) IP networks.  We do have to mint service urns for t=
he purpose however.  We will use the IETF service urns exactly as IETF defi=
nes them.

NENA will have a registry for this namespace, and subregistries for urn:nen=
a:service.  The NENA Registry Service will have processes similar to IANA p=
rocesses for managing these name spaces.  The envisioned management policy =
for urn:nena and urn:nena:service is the NENA equivalent of "standards trac=
k RFC needed".  The registry contents will be public, and both text and xml=
 versions of them will be available.

Brian

On Sep 21, 2010, at 1:27 PM, Peter Saint-Andre wrote:

> Folks, I'm the sponsoring Area Director for an Internet-Draft that
> requests registration of a URN namespace identifier for the National
> Emergency Number Association (NENA):
>=20
> https://datatracker.ietf.org/doc/draft-rosen-urn-nena/
>=20
> I'd appreciate feedback from folks on this list as input to the IESG's
> decision process (e.g., feedback regarding the relationship between the
> proposed urn:nena:* tree and the urn:service:* tree registered by RFC
> 5031). I've deferred the ballot on this I-D for two weeks to enable
> discussion on this list, so if you have comments please provide them
> before October 7.
>=20
> Thanks!
>=20
> Peter
>=20
> --=20
> Peter Saint-Andre
> https://stpeter.im/
>=20
>=20
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit


From root@core3.amsl.com  Tue Sep 21 14:00:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ecrit@ietf.org
Delivered-To: ecrit@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id D2B723A67C2; Tue, 21 Sep 2010 14:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100921210001.D2B723A67C2@core3.amsl.com>
Date: Tue, 21 Sep 2010 14:00:01 -0700 (PDT)
Cc: ecrit@ietf.org
Subject: [Ecrit] I-D Action:draft-ietf-ecrit-additional-data-00.txt
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 21:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Emergency Context Resolution with Internet Technologies Working Group of the IETF.


	Title           : Additional Data related to an Emergency Call
	Author(s)       : B. Rosen, H. Tschofenig
	Filename        : draft-ietf-ecrit-additional-data-00.txt
	Pages           : 24
	Date            : 2010-09-21

When an emergency call is sent to a PSAP, the device that sends it,
as well as any service provider in the path of the call may have
information about the call which the PSAP may be able to use.  This
document describes an XML data structure that contains this kind of
information in a standardized form.  A URI that points to the
structure can be included in the SIP signaling with the call.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-additional-data-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ecrit-additional-data-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-09-21135539.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Tue Sep 21 14:15:05 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ecrit@ietf.org
Delivered-To: ecrit@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 1FBF33A6840; Tue, 21 Sep 2010 14:15:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100921211505.1FBF33A6840@core3.amsl.com>
Date: Tue, 21 Sep 2010 14:15:02 -0700 (PDT)
Cc: ecrit@ietf.org
Subject: [Ecrit] I-D Action:draft-ietf-ecrit-data-only-ea-00.txt
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 21:15:05 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Emergency Context Resolution with Internet Technologies Working Group of the IETF.


	Title           : Common Alerting Protocol (CAP) based Data-Only Emergency Alerts using the Session Initiation Protocol (SIP)
	Author(s)       : B. Rosen, et al.
	Filename        : draft-ietf-ecrit-data-only-ea-00.txt
	Pages           : 15
	Date            : 2010-09-21

The Common Alerting Protocol (CAP) is an XML document format for
exchanging emergency alerts and public warnings.  CAP is mainly used
for conveying alerts and warnings between authorities and from
authorities to citizen/individuals.  This document describes how
data-only emergency alerts allow to utilize the same CAP document
format.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-data-only-ea-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ecrit-data-only-ea-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-09-21140610.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Tue Sep 21 14:15:05 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ecrit@ietf.org
Delivered-To: ecrit@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 9B35C3A6812; Tue, 21 Sep 2010 14:15:05 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100921211505.9B35C3A6812@core3.amsl.com>
Date: Tue, 21 Sep 2010 14:15:05 -0700 (PDT)
Cc: ecrit@ietf.org
Subject: [Ecrit] I-D Action:draft-ietf-ecrit-unauthenticated-access-00.txt
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 21:15:05 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Emergency Context Resolution with Internet Technologies Working Group of the IETF.


	Title           : Extensions to the Emergency Services Architecture for dealing with Unauthenticated and Unauthorized Devices
	Author(s)       : H. Schulzrinne, et al.
	Filename        : draft-ietf-ecrit-unauthenticated-access-00.txt
	Pages           : 23
	Date            : 2010-09-21

The IETF emergency services architecture assumes that the calling
device has acquired rights to use the access network or that no
authentication is required for the access network, such as for public
wireless access points.  Subsequent protocol interactions, such as
obtaining location information, learning the address of the Public
Safety Answering Point (PSAP) and the emergency call itself are
largely decoupled from the underlying network access procedures.

In some cases, the device does not have credentials for network
access, does not have a VoIP provider or application service provider
(ASP), or the credentials have become invalid, e.g., because the user
has exhausted their prepaid balance or the account has expired.

This document provides a problem statement, introduces terminology
and describes an extension for the base IETF emergency services
architecture to address these scenarios.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-unauthenticated-access-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ecrit-unauthenticated-access-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-09-21140621.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Tue Sep 21 14:15:06 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ecrit@ietf.org
Delivered-To: ecrit@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id B0D863A686B; Tue, 21 Sep 2010 14:15:05 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100921211505.B0D863A686B@core3.amsl.com>
Date: Tue, 21 Sep 2010 14:15:05 -0700 (PDT)
Cc: ecrit@ietf.org
Subject: [Ecrit] I-D Action:draft-ietf-ecrit-trustworthy-location-00.txt
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 21:15:06 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Emergency Context Resolution with Internet Technologies Working Group of the IETF.


	Title           : Trustworthy Location Information
	Author(s)       : H. Tschofenig, et al.
	Filename        : draft-ietf-ecrit-trustworthy-location-00.txt
	Pages           : 27
	Date            : 2010-09-21

For some location-based applications, such as emergency calling or
roadside assistance, it appears that the identity of the requestor is
less important than accurate and trustworthy location information.
To ensure adequate help location has to be left untouched by the end
point or by entities in transit.

This document lists different threats, an adversary model, outlines
three frequentlly discussed solutions and discusses operational
considerations.  Finally, the document concludes with a suggestion on
how to move forward.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-trustworthy-location-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ecrit-trustworthy-location-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-09-21140849.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Tue Sep 21 14:30:11 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ecrit@ietf.org
Delivered-To: ecrit@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id B10B73A67A3; Tue, 21 Sep 2010 14:30:09 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100921213010.B10B73A67A3@core3.amsl.com>
Date: Tue, 21 Sep 2010 14:30:09 -0700 (PDT)
Cc: ecrit@ietf.org
Subject: [Ecrit] I-D Action:draft-ietf-ecrit-psap-callback-00.txt
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 21:30:11 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Emergency Context Resolution with Internet Technologies Working Group of the IETF.


	Title           : Public Safety Answering Point (PSAP) Callbacks
	Author(s)       : H. Schulzrinne, et al.
	Filename        : draft-ietf-ecrit-psap-callback-00.txt
	Pages           : 18
	Date            : 2010-09-21

After an emergency call is completed (either prematurely terminated
by the emergency caller or normally by the call-taker) it is possible
that the call-taker feels the need for further communication or for a
clarification.  For example, the call may have been dropped by
accident without the call-taker having sufficient information about
the current situation of a wounded person.  A call-taker may trigger
a callback towards the emergency caller using the contact information
provided with the initial emergency call.  This callback could, under
certain circumstances, then be treated like any other call and as a
consequence, it may get blocked by authorization policies or may get
forwarded to an answering machine.

The IETF emergency services architecture addresses callbacks in a
limited fashion and thereby covers a couple of scenarios.  This
document discusses some shortcomings and raises the question whether
additional solution techniques are needed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-psap-callback-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ecrit-psap-callback-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-09-21141918.I-D@ietf.org>


--NextPart--

From rbarnes@bbn.com  Mon Sep 27 09:29:08 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5280A3A6C27 for <ecrit@core3.amsl.com>; Mon, 27 Sep 2010 09:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.474
X-Spam-Level: 
X-Spam-Status: No, score=-101.474 tagged_above=-999 required=5 tests=[AWL=-0.734, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vFGpL6oJ6x4T for <ecrit@core3.amsl.com>; Mon, 27 Sep 2010 09:29:07 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 344CF3A69B7 for <ecrit@ietf.org>; Mon, 27 Sep 2010 09:29:07 -0700 (PDT)
Received: from [192.1.255.185] (port=57314 helo=col-dhcp-192-1-255-185.bbn.com) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1P0GaI-0003v3-15 for ecrit@ietf.org; Mon, 27 Sep 2010 12:29:46 -0400
Message-Id: <AB85FDC4-0801-4D0F-B869-9B95A8031CFA@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: ecrit <ecrit@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 27 Sep 2010 12:29:42 -0400
X-Mailer: Apple Mail (2.936)
Subject: [Ecrit] FCC NoI regarding IP 9-1-1
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Sep 2010 16:29:08 -0000

Not directly ECRIT-related, but probably of interest to some:

FCC released a Notice of Inquiry last week seeking comment on  
emergency services for IP-enabled providers, including some questions  
about how location information should work in these cases.  Comment  
period is 30 days.

<http://www.fcc.gov/Daily_Releases/Daily_Business/2010/db0924/FCC-10-177A1.pdf 
 >

From rbarnes@bbn.com  Mon Sep 27 20:33:43 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 286B33A6A80 for <ecrit@core3.amsl.com>; Mon, 27 Sep 2010 20:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QjW5WKmCn5B for <ecrit@core3.amsl.com>; Mon, 27 Sep 2010 20:33:42 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 36F243A6814 for <ecrit@ietf.org>; Mon, 27 Sep 2010 20:33:42 -0700 (PDT)
Received: from [128.89.254.158] (port=63319 helo=[192.168.1.10]) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1P0QxS-000BRg-0c for ecrit@ietf.org; Mon, 27 Sep 2010 23:34:22 -0400
Message-Id: <DEE5202E-E3CF-475A-9D7B-F6506FF3D40C@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: ecrit <ecrit@ietf.org>
Content-Type: multipart/alternative; boundary=Apple-Mail-5-247499179
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 27 Sep 2010 23:34:20 -0400
X-Mailer: Apple Mail (2.936)
Subject: [Ecrit] lost-sync APPAREA review
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 03:33:43 -0000

--Apple-Mail-5-247499179
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Hey all,

Just to let you know, we just got back an APPAREA review on draft-ietf- 
ecrit-lost-sync.  There are some significant comments.

<http://www.ietf.org/mail-archive/web/apps-discuss/current/ 
msg01798.html>

--Richard
--Apple-Mail-5-247499179
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: 7bit

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hey all,<div><br></div><div>Just to let you know, we just got back an APPAREA review on draft-ietf-ecrit-lost-sync. &nbsp;There are some significant comments.</div><div><br></div><div>&lt;<a href="http://www.ietf.org/mail-archive/web/apps-discuss/current/msg01798.html">http://www.ietf.org/mail-archive/web/apps-discuss/current/msg01798.html</a>&gt;</div><div><br></div><div>--Richard</div></body></html>
--Apple-Mail-5-247499179--

From mccann.stephen@gmail.com  Mon Sep 27 23:54:09 2010
Return-Path: <mccann.stephen@gmail.com>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B71D3A6B28 for <ecrit@core3.amsl.com>; Mon, 27 Sep 2010 23:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xQlzrUUEPhNE for <ecrit@core3.amsl.com>; Mon, 27 Sep 2010 23:54:08 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 2D2613A6AFC for <ecrit@ietf.org>; Mon, 27 Sep 2010 23:54:08 -0700 (PDT)
Received: by bwz9 with SMTP id 9so5189644bwz.31 for <ecrit@ietf.org>; Mon, 27 Sep 2010 23:54:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=mhzlbXZxcbivwxYdd/cVzqzN3FT1aPZF5WMdhYTnG6A=; b=AoMbefo6yaiRpfPBFt3kwqUazrbPqj06Tv3o5JW8APTmiIGC26RwORALqhqf5kL89U fZjuMWbkuxyr7wfasC35dD2iAAtBlg2q27idUthcB2K5ZC629iensUEujL3CzGAF3ciW p9GmVlDxp5D+2zPHS2vTs+uh0qC2DIJ4St7wo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=SIEap9kkCKDMjtdWk4vtJyIKv1k4MuMrPvh/EUHyrLld5vr7k7iNkKqh0qh6qLGzhG 80HQbBSRktjhZhJ2jMvcOE76b8UHcfA2nobsIoenioNSMPtD3bGBLKJtkQ4AoXDU68N9 tQ1xCDqVqZNjGma7FrieoOIzqa/XPCktcsyCA=
MIME-Version: 1.0
Received: by 10.204.79.223 with SMTP id q31mr6241658bkk.92.1285656887900; Mon, 27 Sep 2010 23:54:47 -0700 (PDT)
Received: by 10.204.66.1 with HTTP; Mon, 27 Sep 2010 23:54:47 -0700 (PDT)
In-Reply-To: <CBF1D1A3-8098-4F1F-BEDA-E61A0F0C6BB4@bbn.com>
References: <CBF1D1A3-8098-4F1F-BEDA-E61A0F0C6BB4@bbn.com>
Date: Tue, 28 Sep 2010 07:54:47 +0100
Message-ID: <AANLkTin612yC_DbkOJA2FwOY8dC9jF6m+aGiPAwKKSjM@mail.gmail.com>
From: Stephen McCann <mccann.stephen@gmail.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ecrit <ecrit@ietf.org>
Subject: Re: [Ecrit] [Geopriv] FCC NoI regarding IP 9-1-1
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 06:54:09 -0000

Richard,
            do you know if there's an updated URL at the FCC, as this
link is no longer valid.

Kind regards

Stephen

On 27 September 2010 17:30, Richard L. Barnes <rbarnes@bbn.com> wrote:
> Not directly GEOPRIV-related, but probably of interest to some:
>
> FCC released a Notice of Inquiry last week seeking comment on emergency
> services for IP-enabled providers, including some questions about how
> location information should work in these cases. =A0Comment period is 30 =
days.
>
> <http://www.fcc.gov/Daily_Releases/Daily_Business/2010/db0924/FCC-10-177A=
1.pdf>
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv
>
