From iesg-secretary@ietf.org Fri Dec 6 09:31:51 2013 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF7D1ADF6E; Fri, 6 Dec 2013 09:31:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LnslrC2DhV22; Fri, 6 Dec 2013 09:31:49 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 37E1E1AE078; Fri, 6 Dec 2013 09:31:48 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131206173148.2680.64807.idtracker@ietfa.amsl.com> Date: Fri, 06 Dec 2013 09:31:48 -0800 Cc: ecrit WG Subject: [Ecrit] WG Action: Rechartered Emergency Context Resolution with Internet Technologies (ecrit) X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.15 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Dec 2013 17:31:51 -0000 The Emergency Context Resolution with Internet Technologies (ecrit) working group in the Real-time Applications and Infrastructure Area of the IETF has been rechartered. For additional information please contact the Area Directors or the WG Chairs. Emergency Context Resolution with Internet Technologies (ecrit) ------------------------------------------------ Current Status: Active WG Chairs: Marc Linsner Roger Marshall Assigned Area Director: Richard Barnes Mailing list Address: ecrit@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/ecrit Archive: http://www.ietf.org/mail-archive/web/ecrit/ Charter: In a number of areas, the public switched telephone network (PSTN) has been configured to recognize an explicitly specified number (usually one that is short and easily memorized) as a request for emergency services. These numbers (e.g., 911, 112) are related to an emergency service context and depend on a broad, regional configuration of service contact methods and a geographically-constrained approach for service delivery. These calls are intended to be delivered to special call centers equipped to manage emergency response. Successful delivery of an emergency service call within those systems requires an association of both the physical location of the originating device along with appropriate call routing to an emergency service center. Calls placed using Internet technologies do not use the same systems mentioned above to achieve those same goals, and the common use of overlay networks and tunnels (either as VPNs or for mobility) makes meeting these goals even more challenging. There are, however, Internet technologies available to manage location and to perform call routing. This working group has described where and how these mechanisms may be used. The group specified how location data and call routing information are used to enable communication between a user and a relevant emergency response center [RFC6443,RFC6444]. Though the term "call routing" is used, it should be understood that some of the mechanisms described might be used to enable other types of media streams. Beyond human initiated emergency call request mechanisms, this group will develop new methods to enable non-human-initiated requests for emergency assistance, such as sensor initiated emergency requests. The working group will also address topics required for the operation of emergency calling systems, such as: authentication of location, management of the service URN namespace, augmented information that could assist emergency call takers or responders. Explicitly outside the scope of this group is the question of pre- emption or prioritization of emergency services traffic in the network. This group is considering emergency services calls which might be made by any user of the Internet, as opposed to government or military services that may impose very different authentication and routing requirements. While this group anticipates a close working relationship with groups such as NENA, EENA, 3GPP, and ETSI , any solution presented must be general enough to be potentially useful in or across multiple regions or jurisdictions, and it must be possible to use without requiring a single, central authority. Further, it must be possible for multiple delegations within a jurisdiction to be handled independently, things such as call routing for specific emergency types, media types, language contents, etc., may be routed differently depending on established policies and availability. This working group will address privacy and security concerns within its documents. Milestones: Done - Informational RFC containing terminology definitions and the requirements Done - An Informational document describing the threats and security considerations Done - A Standards Track RFC describing how to identify a session set-up request is to an emergency response center Done - A Standards Track RFC describing how to route an emergency call based on location information Done - An Informational document describing the Mapping Protocol Architecture Done - Submit 'Location Hiding: Problem Statement and Requirements' to the IESG for consideration as an Informational RFC. Done - Submit 'Framework for Emergency Calling using Internet Multimedia' to the IESG for consideration as an Informational RFC. Done - Submit 'Best Current Practice for Communications Services in support of Emergency Calling' to the IESG for consideration as a BCP document Done - Submit 'LoST Extension for returning Boundary Information for Services' to the IESG for consideration as an Experimental RFC Done - Submit 'Synchronizing Location-to-Service Translation (LoST) Protocol based Service Boundaries and Mapping Elements' to the IESG for consideration as an Experimental RFC Done - Submit 'Public Safety Answering Point (PSAP) Callbacks' to the IESG for consideration as an Informational RFC Done - Submit 'Extensions to the Emergency Services Architecture for dealing with Unauthenticated and Unauthorized Devices' to the IESG for consideration as a Standards Track RFC Nov 2013 - Submit 'Common Alerting Protocol (CAP) based Data-Only Emergency Alerts using the Session Initiation Protocol (SIP)' to the IESG for consideration as an Experimental RFC Nov 2013 - Submit 'Trustworthy Location Information' to the IESG for consideration as an Informational RFC Dec 2013 - Submit 'Additional Data related to a Call for Emergency Call Purposes' to the IESG for consideration as a Standards Track RFC Dec 2013 - Submit a draft 'Policy for defining new service-identifying labels' to the IESG for consideration as BCP Dec 2013 - Submit a draft 'URN For Country Specific Emergency Services' to the IESG for consideration as a Standards Track RFC Mar 2014 - Submit 'Using Imprecise Location for Emergency Call Routing' to the IESG for consideration as an Informational RFC From md3135@att.com Tue Dec 10 03:58:12 2013 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 276071ADF5E for ; Tue, 10 Dec 2013 03:58:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.5 X-Spam-Level: X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NOcWLZiOWeEQ for ; Tue, 10 Dec 2013 03:58:10 -0800 (PST) Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 66B1D1ADFDA for ; Tue, 10 Dec 2013 03:58:10 -0800 (PST) Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-7.2.1-0) over TLS secured channel with ESMTP id dc107a25.0.977214.00-2344.2729519.nbfkord-smmo06.seg.att.com (envelope-from ); Tue, 10 Dec 2013 11:58:05 +0000 (UTC) X-MXL-Hash: 52a701cd52ac84cf-3a8844ab7e0487030cfbeacbf060a544efb5c23d Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id rBABw4LV028817 for ; Tue, 10 Dec 2013 06:58:04 -0500 Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id rBABw0FT028799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 10 Dec 2013 06:58:01 -0500 Received: from MISOUT7MSGHUB9C.ITServices.sbc.com (MISOUT7MSGHUB9C.itservices.sbc.com [144.151.223.82]) by mlpi409.sfdc.sbc.com (RSA Interceptor) for ; Tue, 10 Dec 2013 11:57:49 GMT Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUB9C.ITServices.sbc.com ([144.151.223.82]) with mapi id 14.03.0158.001; Tue, 10 Dec 2013 06:57:49 -0500 From: "DOLLY, MARTIN C" To: "ecrit@ietf.org" Thread-Topic: draft-gellens-ecrit-car-crash-01.txt Thread-Index: Ac71nwtx6fpoiUAiTh2UdJeWku3IDQ== Date: Tue, 10 Dec 2013 11:57:48 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.175.91.60] Content-Type: multipart/alternative; boundary="_000_E42CCDDA6722744CB241677169E83656024AF821MISOUT7MSGUSR9I_" MIME-Version: 1.0 X-RSA-Inspected: yes X-RSA-Classifications: public X-AnalysisOut: [v=2.0 cv=KeZlR3kD c=1 sm=1 a=dhB6nF3YHL5t/Ixux6cINA==:17 a] X-AnalysisOut: [=vQHSn-Hx5_wA:10 a=ofMgfj31e3cA:10 a=78j-lUiEoQgA:10 a=BLc] X-AnalysisOut: [eEmwcHowA:10 a=zQP7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=FyKqOVF3V] X-AnalysisOut: [fAA:10 a=ieZRCVFN__UgTJXg670A:9 a=CjuIK1q_8ugA:10 a=qM39co] X-AnalysisOut: [r4HRgA:10 a=Hz7IrDYlS0cA:10 a=D2m8250wwrsA:10 a=QWGd7FfjDa] X-AnalysisOut: [4A:10 a=3dM4P6mxlTiSElIdvYAA:9 a=_W_S_7VecoQA:10 a=frz4AuC] X-AnalysisOut: [g-hUA:10 a=DV2FbbhnbVGzR82D:21] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)] X-MAIL-FROM: X-SOURCE-IP: [144.160.229.24] Subject: [Ecrit] draft-gellens-ecrit-car-crash-01.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 11:58:12 -0000 --_000_E42CCDDA6722744CB241677169E83656024AF821MISOUT7MSGUSR9I_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Greetings, We support draft-gellens-ecrit-car-crash-01.txt being adopted as a working = group document. Regards, Martin Dolly Lead Member Technical Staff Core & Government/Regulatory Standards AT&T Standards and Industry Alliances md3135@att.com +1-609-903-3360 --_000_E42CCDDA6722744CB241677169E83656024AF821MISOUT7MSGUSR9I_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Greetings,
 
We support draft-gellens-ecrit-car-crash-01.txt being adopted as a wor= king group document.
 
Regards,
 
Martin Dolly
Lead Member Technical Staff
Core & Government/Regulatory Standards
AT&T St= andards and Industry Alliances
md3135@att.com
+1-609-903-3360
 
 
 
 --_000_E42CCDDA6722744CB241677169E83656024AF821MISOUT7MSGUSR9I_-- From internet-drafts@ietf.org Tue Dec 10 05:28:28 2013 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AFB71ADF32; Tue, 10 Dec 2013 05:28:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4mih9r5N-j83; Tue, 10 Dec 2013 05:28:26 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 23FED1ACB4E; Tue, 10 Dec 2013 05:28:26 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131210132825.25421.53265.idtracker@ietfa.amsl.com> Date: Tue, 10 Dec 2013 05:28:25 -0800 Cc: ecrit@ietf.org Subject: [Ecrit] I-D Action: draft-ietf-ecrit-country-emg-urn-02.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.15 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 13:28:28 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Emergency Context Resolution with Interne= t Technologies Working Group of the IETF. Title : URN For Country Specific Emergency Services Author(s) : Christer Holmberg Ivo Sedlacek Filename : draft-ietf-ecrit-country-emg-urn-02.txt Pages : 7 Date : 2013-12-10 Abstract: This document updates section 4.2 of RFC 5031, in order to allow the registration of service URNs with the 'sos' service type for emergency services that, at the time of registration, are offered in one country only. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ecrit-country-emg-urn There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-ecrit-country-emg-urn-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-ecrit-country-emg-urn-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From christer.holmberg@ericsson.com Thu Dec 19 00:30:39 2013 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0601AE081 for ; Thu, 19 Dec 2013 00:30:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vHmmI7ZrXDJb for ; Thu, 19 Dec 2013 00:30:37 -0800 (PST) Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 689951AE207 for ; Thu, 19 Dec 2013 00:30:36 -0800 (PST) X-AuditID: c1b4fb38-b7f2c8e000006d25-9e-52b2aea93463 Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id A2.89.27941.9AEA2B25; Thu, 19 Dec 2013 09:30:34 +0100 (CET) Received: from ESESSMB209.ericsson.se ([169.254.9.201]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.02.0347.000; Thu, 19 Dec 2013 09:30:17 +0100 From: Christer Holmberg To: "ecrit@ietf.org" Thread-Topic: Suggested changes based on IESG review: draft-ietf-ecrit-country-emg-urn Thread-Index: Ac78k0zIFrH8LLZvSNSbnAZ3VG2Ypg== Date: Thu, 19 Dec 2013 08:30:17 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B1C5D8B99@ESESSMB209.ericsson.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.19] Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C5D8B99ESESSMB209erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrPLMWRmVeSWpSXmKPExsUyM+Jvre6qdZuCDGY85rBY2Zpv0f/gOqNF 46KnrA7MHkuW/GTy+HL5M1sAUxSXTUpqTmZZapG+XQJXxu4/21gLpitVTNuxh62B8bFsFyMn h4SAicT3lT2MELaYxIV769m6GLk4hASOMErc6j/GDJIQEljCKLF+gmEXIwcHm4CFRPc/bZCw iICqxIYzK8F6mQUqJH5On8IKUiIsECzRM8cHoiRC4snMZUwQtp7Ek8nHwGwWoNYJ60+yg9i8 Ar4Ss3+/YQWxGYFO+H5qDRPESHGJW0/mM0GcJiCxZM95ZghbVOLl43+sELaiRPvTBqgT8iVe XPzMDDFTUOLkzCcsExiFZyEZNQtJ2SwkZRBxHYkFuz+xQdjaEssWvmaGsc8ceMyELL6AkX0V I0dxanFSbrqRwSZGYKQc3PLbYgfj5b82hxilOViUxHk/vnUOEhJITyxJzU5NLUgtii8qzUkt PsTIxMEp1cBoxuL35cLBmVo9N/hvLE2PqT7RqftGlUdjlcOCqQUpN6e/rr7ifcnyZOKn6qgH ihbSjG+yWnxzNt9knxXWFdhv5y+RujO4sI779dnbJddbhOt28XbO4891dFmjm2azmufjgc6G iy+X+abqim96FyMQ12H3J8wvU2DlekX9rTdznt8IdVJ79UmJpTgj0VCLuag4EQBEgyWrYgIA AA== Cc: "ecrit-chairs@tools.ietf.org" , "ecrit-ads@tools.ietf.org" Subject: [Ecrit] Suggested changes based on IESG review: draft-ietf-ecrit-country-emg-urn X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Dec 2013 08:30:39 -0000 --_000_7594FB04B1934943A5C02806D1A2204B1C5D8B99ESESSMB209erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, As part of the IESG review of draft-ietf-ecrit-country-emg-urn-02, there ar= e a couple of change suggestions which I'd like to verify with the communit= y. First, it has been suggested to remove sections 3 (Problem statement) and 4= (Requirement) from the document, as section 1 (Introduction) already descr= ibes the issue and how the draft addresses it. Second, it has been suggested to: - remove section 5.2 (existing RFC 5031 section); and - change section 5.3 (updated RFC 5031 section) so that section 5.3 only co= ntains the updated paragraph of RFC 5031 During the review, there has been confusion about what is existing text, an= d what the draft updates, so the suggested changes would make it more clear= . Unless people object, I intend to implement the suggested changes. Regards, Christer --_000_7594FB04B1934943A5C02806D1A2204B1C5D8B99ESESSMB209erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

As part of the IESG review of draft-ietf-ecrit-count= ry-emg-urn-02, there are a couple of change suggestions which I’d lik= e to verify with the community.

 

First, it has been suggested to remove sections 3 (P= roblem statement) and 4 (Requirement) from the document, as section 1 (Intr= oduction) already describes the issue and how the draft addresses it.<= /o:p>

 

Second, it has been suggested to:

 

- remove section 5.2 (existing RFC 5031 section); an= d

- change section 5.3 (updated RFC 5031 section) so t= hat section 5.3 only contains the updated paragraph of RFC 5031<= /p>

 

During the review, there has been confusion about wh= at is existing text, and what the draft updates, so the suggested changes w= ould make it more clear.

 

Unless people object, I intend to implement the sugg= ested changes.

 

Regards,

 

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1C5D8B99ESESSMB209erics_--