From nobody Sun Aug 9 02:00:31 2015 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 CF6481ACE77 for ; Sun, 9 Aug 2015 02:00:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 imIBj7Baq71S for ; Sun, 9 Aug 2015 02:00:28 -0700 (PDT) Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A93081ACE72 for ; Sun, 9 Aug 2015 02:00:28 -0700 (PDT) Received: by pdrg1 with SMTP id g1so60498071pdr.2 for ; Sun, 09 Aug 2015 02:00:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=+9U9IyEE5SAPVSykZE6An7kfrcpDE/F7UTeMFmIvRAA=; b=rgdMA4iTeBjYxAlpNc+E2uz4qRNs6L8TeVK54IoTMWjMn25sJV+i7NYQwevFjpz3DU ADG9saLWQeajzralZPMLfHjTmur/Z5wz5FDuN7wm7pmNfR/eLZioxKPQOeAvMRFSjiNR 9cIwh17tAe0SoU3e738rRRXtP0oDv5DPIeyHnebH1vICh/eKHT25TQ94JGxSheLa3928 63a2tQ8KiCf3HMZmcO/mqZ0jr93EBE/KTmvqlkKDjPFMryUjtAY4CJtQ3u2C0kSXP15i xp1FRLkMWD0TbDKd2hYRid6+raGChtydkJFEIgwBNzQhJKq42bojL1PtkLHA5jhV8/nw ntjA== X-Received: by 10.70.51.8 with SMTP id g8mr32817009pdo.50.1439110828348; Sun, 09 Aug 2015 02:00:28 -0700 (PDT) Received: from [192.168.1.100] ([1.144.29.7]) by smtp.gmail.com with ESMTPSA id ns14sm15892400pdb.17.2015.08.09.02.00.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Aug 2015 02:00:27 -0700 (PDT) From: James Winterbottom Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: <2B2ED92C-FF9E-428B-989F-C4F08F87AE04@gmail.com> Date: Sun, 9 Aug 2015 19:00:23 +1000 To: "ecrit_ietf.org" Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Archived-At: Subject: [Ecrit] draft-ietf-ecrit-held-routing 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: Sun, 09 Aug 2015 09:00:30 -0000 Hi All, The only comments received during the WGLC were from Keith Drage and I = believe that I addressed all of these in a rev of the draft but I = haven=E2=80=99t heard anything back. Keith, can you please confirm that your issues have all been addressed = by the new text and if they have then can we please move the draft = forward? Cheers James From nobody Mon Aug 10 16:33:24 2015 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 597B01A1B61; Mon, 10 Aug 2015 16:33:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 nj03sGXu8YXD; Mon, 10 Aug 2015 16:33:22 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 66E5D1A1B11; Mon, 10 Aug 2015 16:33:19 -0700 (PDT) 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: 6.4.0 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20150810233319.27776.86859.idtracker@ietfa.amsl.com> Date: Mon, 10 Aug 2015 16:33:19 -0700 Archived-At: Cc: ecrit@ietf.org Subject: [Ecrit] Last Call: (Additional Data Related to an Emergency Call) to Proposed Standard X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2015 23:33:23 -0000 The IESG has received a request from the Emergency Context Resolution with Internet Technologies WG (ecrit) to consider the following document: - 'Additional Data Related to an Emergency Call' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2015-08-24. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract When an emergency call is sent to a Public Safety Answering Point (PSAP), the originating device, the access network provider to which the device is connected, and all service providers in the path of the call have information about the call, the caller or the location which is helpful for the PSAP to have in handling the emergency. This document describes data structures and mechanisms to convey such data to the PSAP. The intent is that every emergency call carry the information described here using the mechanisms described here. The mechanisms permit the data to be conveyed by reference (as an external resource) or by value (within the body of a SIP message or a location object). This follows the tradition of prior emergency services standardization work where data can be conveyed by value within the call signaling (i.e., in the body of the SIP message) or by reference. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-ecrit-additional-data/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-ecrit-additional-data/ballot/ No IPR declarations have been submitted directly on this I-D. From nobody Tue Aug 11 04:07:46 2015 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 B80541A879B; Tue, 11 Aug 2015 04:07:44 -0700 (PDT) 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 brHqAIEdGW4f; Tue, 11 Aug 2015 04:07:43 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 877F11A8777; Tue, 11 Aug 2015 04:07:43 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.4.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150811110743.23776.62645.idtracker@ietfa.amsl.com> Date: Tue, 11 Aug 2015 04:07:43 -0700 Archived-At: Cc: ecrit@ietf.org Subject: [Ecrit] I-D Action: draft-ietf-ecrit-data-only-ea-10.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, 11 Aug 2015 11:07:44 -0000 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 : Data-Only Emergency Calls Authors : Brian Rosen Henning Schulzrinne Hannes Tschofenig Filename : draft-ietf-ecrit-data-only-ea-10.txt Pages : 22 Date : 2015-08-11 Abstract: RFC 6443 'Framework for Emergency Calling Using Internet Multimedia' describes how devices use the Internet to place emergency calls and how Public Safety Answering Points (PSAPs) can handle Internet multimedia emergency calls natively. The exchange of multimedia traffic typically involves a SIP session establishment starting with a SIP INVITE that negotiates various parameters for that session. In some cases, however, the transmission of application data is everything that is needed. Examples of such environments include a temperature sensors issuing alerts, or vehicles sending crash data. Often these alerts are conveyed as one-shot data transmissions. These type of interactions are called 'data-only emergency calls'. This document describes a container for the data based on the Common Alerting Protocol (CAP) and its transmission using the SIP MESSAGE transaction. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ecrit-data-only-ea/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-ecrit-data-only-ea-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-data-only-ea-10 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 nobody Thu Aug 20 05:40:58 2015 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 435BC1A01C6; Wed, 19 Aug 2015 15:23:03 -0700 (PDT) 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 ajTnfyaRJdcL; Wed, 19 Aug 2015 15:23:01 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B74931A017C; Wed, 19 Aug 2015 15:23:01 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Liaison Statement Management Tool To: "Marc Linsner" , "Roger Marshall" X-Test-IDTracker: no X-IETF-IDTracker: 6.4.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150819222301.4436.84786.idtracker@ietfa.amsl.com> Date: Wed, 19 Aug 2015 15:23:01 -0700 Archived-At: X-Mailman-Approved-At: Thu, 20 Aug 2015 05:40:57 -0700 Cc: geopriv@ietf.org, Ben Campbell , Emergency Context Resolution with Internet Technologies Discussion List , Barry Leiba , CM8655@att.com Subject: [Ecrit] New Liaison Statement, "Emergency Location Standardization Effort at ATIS " 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: Wed, 19 Aug 2015 22:23:03 -0000 Title: Emergency Location Standardization Effort at ATIS Submission Date: 2015-08-19 URL of the IETF Web page: https://datatracker.ietf.org/liaison/1427/ From: ATIS ELOC TF (Peter Musgrove ) To: Emergency Context Resolution with Internet Technologies (Marc Linsner , Roger Marshall ) Cc: Barry Leiba ,Ben Campbell ,Alissa Cooper ,Emergency Context Resolution with Internet Technologies Discussion List , geopriv@ietf.org Response Contact: CM8655@att.com, Christian.Militeau@intrado.com Technical Contact: Purpose: For information Body: See attachment. Attachments: Emergency Location Standardization Effort at ATIS https://datatracker.ietf.org/documents/LIAISON/liaison-2015-08-19-atis-eloc-tf-ecrit-emergency-location-standardization-effort-at-atis-attachment-1.pdf From nobody Mon Aug 24 13:46:36 2015 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 D2FED1B2B1C for ; Mon, 24 Aug 2015 13:46:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 wsPlNmmTSlLv for ; Mon, 24 Aug 2015 13:46:33 -0700 (PDT) Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98DC71B2B14 for ; Mon, 24 Aug 2015 13:46:33 -0700 (PDT) Received: by pacdd16 with SMTP id dd16so104963411pac.2 for ; Mon, 24 Aug 2015 13:46:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:references:to:message-id :mime-version; bh=aP3i1pZsy7Y1bCyQbcGOYoc37RHwDFuf/QgMZAvwJZg=; b=Q7PHoy0c8fMlBWPtkxy9kU/Qz9au7fPqtOizJPiw9fUnQvqnwdRccRWmpELikJqkFG CtW35bcTSjtGHaIW3vp9nPeueStZEAD5U6qt5Xk7V3fexvaLizLBzsQJpFFIWtPur32x kesedExMskkXpdklUnbLV1eZjZvlfAnZWEKuNzmTpyM6Vo+iz/hSRPPHLyBSO6F1tvmY ziwklCV0DSiqHmY/kdSEymiQlZCKJElBWsHM5LTXA7FMxqRWVUj1W+uFw/UAMU7QO9/P 94n59U87Dvz4SqyNs8Z1+tMjGqytCPcXHVZer2+1zhh+rHG2liDA856L+O4Z185hXOcL 3QSw== X-Received: by 10.68.68.175 with SMTP id x15mr49327948pbt.10.1440449193350; Mon, 24 Aug 2015 13:46:33 -0700 (PDT) Received: from [192.168.1.102] ([1.144.22.8]) by smtp.gmail.com with ESMTPSA id i7sm18414129pdo.84.2015.08.24.13.46.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Aug 2015 13:46:32 -0700 (PDT) From: James Winterbottom Content-Type: multipart/alternative; boundary="Apple-Mail=_F8AB34DE-F0A0-42F0-9F77-2FDA5A2F7C13" Date: Tue, 25 Aug 2015 06:46:27 +1000 References: <2B2ED92C-FF9E-428B-989F-C4F08F87AE04@gmail.com> To: "ecrit_ietf.org" Message-Id: <5C6923E9-AAB9-4AAF-A59B-2CC5618529C5@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) Archived-At: Subject: [Ecrit] Fwd: draft-ietf-ecrit-held-routing 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: Mon, 24 Aug 2015 20:46:35 -0000 --Apple-Mail=_F8AB34DE-F0A0-42F0-9F77-2FDA5A2F7C13 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi All, I sent this message back on the 9th of August and haven=E2=80=99t had a = response. Chairs can we please proceed to the next step? Cheers James > Begin forwarded message: >=20 > From: James Winterbottom > Subject: draft-ietf-ecrit-held-routing > Date: 9 August 2015 7:00:23 pm AEST > To: "ecrit_ietf.org" >=20 > Hi All, >=20 > The only comments received during the WGLC were from Keith Drage and I = believe that I addressed all of these in a rev of the draft but I = haven=E2=80=99t heard anything back. >=20 > Keith, can you please confirm that your issues have all been addressed = by the new text and if they have then can we please move the draft = forward? >=20 > Cheers > James >=20 --Apple-Mail=_F8AB34DE-F0A0-42F0-9F77-2FDA5A2F7C13 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi All,

I = sent this message back on the 9th of August and haven=E2=80=99t had a = response.

Chairs= can we please proceed to the next step?

Cheers
James



Begin forwarded message:

From: = James Winterbottom <a.james.winterbottom@gmail.com>
Subject: = draft-ietf-ecrit-held-routing
Date: = 9 August 2015 7:00:23 pm = AEST
To: = "ecrit_ietf.org" <ecrit@ietf.org>

Hi All,

The only comments received during the WGLC = were from Keith Drage and I believe that I addressed all of these in a = rev of the draft but I haven=E2=80=99t heard anything back.

Keith, can you please confirm that your issues = have all been addressed by the new text and if they have then can we = please move the draft forward?

Cheers
James

= --Apple-Mail=_F8AB34DE-F0A0-42F0-9F77-2FDA5A2F7C13-- From nobody Wed Aug 26 11:09:27 2015 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 8E86B1B2E1C; Wed, 26 Aug 2015 11:09:25 -0700 (PDT) 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 pWztHu6IYvpK; Wed, 26 Aug 2015 11:09:24 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C0D51B2D1F; Wed, 26 Aug 2015 11:09:24 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.4.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150826180924.8936.18009.idtracker@ietfa.amsl.com> Date: Wed, 26 Aug 2015 11:09:24 -0700 Archived-At: Cc: ecrit@ietf.org Subject: [Ecrit] I-D Action: draft-ietf-ecrit-additional-data-34.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: Wed, 26 Aug 2015 18:09:25 -0000 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 Authors : Randall Gellens Brian Rosen Hannes Tschofenig Roger Marshall James Winterbottom Filename : draft-ietf-ecrit-additional-data-34.txt Pages : 110 Date : 2015-08-26 Abstract: When an emergency call is sent to a Public Safety Answering Point (PSAP), the originating device, the access network provider to which the device is connected, and all service providers in the path of the call have information about the call, the caller or the location which is helpful for the PSAP to have in handling the emergency. This document describes data structures and mechanisms to convey such data to the PSAP. The intent is that every emergency call carry the information described here using the mechanisms described here. The mechanisms permit the data to be conveyed by reference (as an external resource) or by value (within the body of a SIP message or a location object). This follows the tradition of prior emergency services standardization work where data can be conveyed by value within the call signaling (i.e., in the body of the SIP message) or by reference. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ecrit-additional-data/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-ecrit-additional-data-34 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-additional-data-34 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 nobody Mon Aug 31 07:23:47 2015 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 196091B39DD for ; Mon, 31 Aug 2015 07:23:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.377 X-Spam-Level: X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 EUJUlhfmHsul for ; Mon, 31 Aug 2015 07:23:44 -0700 (PDT) Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25B591B4029 for ; Mon, 31 Aug 2015 07:23:44 -0700 (PDT) Received: by qkfs65 with SMTP id s65so3947753qkf.2 for ; Mon, 31 Aug 2015 07:23:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=3rYr4kuHu0xXd/k5WNrf3mp4zMDsD6urcm/IVWJ0Pdc=; b=lkvNHwIWNu3o+67HJnc4WKECC4HyF4gO905ZIJfU6bC7Kf9gYCMMUY9Bg6oyvphF+M LQTdjpyhJzIyAL8I6EceYDknYsajPlAW/57+LkKgat8yZpAf3FHjO9cEe/OZVv7jYmTC ZgiDgn6SqsKBsFzcHQCgYFpXxNF/wVTUZ0MVtKZYQsA3rPKhoJgzgnMNcxQ0AfT58HNu D63/niS0xQfkqyV46jdmn0isumHwxvm89UySVoW9+Upvxj/Zsp7Ddlur+gDBv+KWpA7A eUSpKoCEk0ueZHWyArIsM0ABSURwuhZDdzDt+AJHOya12uOG73vS8zyClOB5Rtt5ZQ+5 KipQ== MIME-Version: 1.0 X-Received: by 10.55.209.135 with SMTP id o7mr9354665qkl.16.1441031023336; Mon, 31 Aug 2015 07:23:43 -0700 (PDT) Received: by 10.55.22.203 with HTTP; Mon, 31 Aug 2015 07:23:43 -0700 (PDT) Date: Mon, 31 Aug 2015 16:23:43 +0200 Message-ID: From: Laura Liess To: marc.linsner@cisco.com, rmarshall@telecomsys.com Content-Type: multipart/alternative; boundary=001a1149aea841a562051e9c2ec4 Archived-At: Cc: "ecrit@ietf.org" Subject: [Ecrit] Progress of draft-ietf-ecrit-held-routing-03 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: Mon, 31 Aug 2015 14:23:46 -0000 --001a1149aea841a562051e9c2ec4 Content-Type: text/plain; charset=UTF-8 Hi Marc and Roger, we had a WGLC for the draft and all comments raised there were addressed in the new version 03. Is there any reason not to progress with the draft to the next step? Thank you Laura --001a1149aea841a562051e9c2ec4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Marc and Roger,=C2=A0

we h= ad a WGLC for the draft and all comments raised there were addressed in the= new version 03. Is there any reason not to progress with the draft to the = next step?=C2=A0

Thank you
Laura=C2=A0
=C2=A0
--001a1149aea841a562051e9c2ec4-- From nobody Mon Aug 31 16:18:57 2015 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 64AB01B4414 for ; Mon, 31 Aug 2015 16:18:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 tWeopugMUOwT for ; Mon, 31 Aug 2015 16:18:54 -0700 (PDT) Received: from sea-mx-01.telecomsys.com (sea-mx-01.telecomsys.com [199.165.246.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E00C01B436C for ; Mon, 31 Aug 2015 16:18:54 -0700 (PDT) Received: from SEA-EXCAS-3.telecomsys.com (exc2010-local3.telecomsys.com [10.32.12.6]) by sea-mx-01.telecomsys.com (8.14.7/8.14.7) with ESMTP id t7VNIqvZ021206 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 31 Aug 2015 16:18:52 -0700 Received: from SEA-EXMB-1.telecomsys.com ([169.254.1.133]) by SEA-EXCAS-3.telecomsys.com ([10.32.12.6]) with mapi id 14.03.0248.002; Mon, 31 Aug 2015 16:18:52 -0700 From: Roger Marshall To: James Winterbottom , "ecrit_ietf.org" Thread-Topic: [Ecrit] draft-ietf-ecrit-held-routing Thread-Index: AQHQ0oHdzIsQK6ZQJUCOLHhQGQsfRZ4m4OtA Date: Mon, 31 Aug 2015 23:18:51 +0000 Message-ID: References: <2B2ED92C-FF9E-428B-989F-C4F08F87AE04@gmail.com> In-Reply-To: <2B2ED92C-FF9E-428B-989F-C4F08F87AE04@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.32.12.134] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: Subject: Re: [Ecrit] draft-ietf-ecrit-held-routing 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: Mon, 31 Aug 2015 23:18:56 -0000 S2VpdGgsIGRvIHRoZSBjaGFuZ2VzIHRoYXQgSmFtZXMgb2ZmZXJlZCBzYXRpc2Z5IHlvdXIgaXNz dWVzPyAgDQoNCi1yb2dlci4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEVj cml0IFttYWlsdG86ZWNyaXQtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEphbWVzIFdp bnRlcmJvdHRvbQ0KU2VudDogU3VuZGF5LCBBdWd1c3QgMDksIDIwMTUgMjowMCBBTQ0KVG86IGVj cml0X2lldGYub3JnDQpTdWJqZWN0OiBbRWNyaXRdIGRyYWZ0LWlldGYtZWNyaXQtaGVsZC1yb3V0 aW5nDQoNCkhpIEFsbCwNCg0KVGhlIG9ubHkgY29tbWVudHMgcmVjZWl2ZWQgZHVyaW5nIHRoZSBX R0xDIHdlcmUgZnJvbSBLZWl0aCBEcmFnZSBhbmQgSSBiZWxpZXZlIHRoYXQgSSBhZGRyZXNzZWQg YWxsIG9mIHRoZXNlIGluIGEgcmV2IG9mIHRoZSBkcmFmdCBidXQgSSBoYXZlbuKAmXQgaGVhcmQg YW55dGhpbmcgYmFjay4NCg0KS2VpdGgsIGNhbiB5b3UgcGxlYXNlIGNvbmZpcm0gdGhhdCB5b3Vy IGlzc3VlcyBoYXZlIGFsbCBiZWVuIGFkZHJlc3NlZCBieSB0aGUgbmV3IHRleHQgYW5kIGlmIHRo ZXkgaGF2ZSB0aGVuIGNhbiB3ZSBwbGVhc2UgbW92ZSB0aGUgZHJhZnQgZm9yd2FyZD8NCg0KQ2hl ZXJzDQpKYW1lcw0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXw0KRWNyaXQgbWFpbGluZyBsaXN0DQpFY3JpdEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0 Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9lY3JpdA0KDQpDT05GSURFTlRJQUxJVFkgTk9USUNFOiBU aGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWVzc2FnZSBtYXkgYmUgcHJpdmlsZWdl ZCBhbmQvb3IgY29uZmlkZW50aWFsLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBp ZW50LCBvciByZXNwb25zaWJsZSBmb3IgZGVsaXZlcmluZyB0aGlzIG1lc3NhZ2UgdG8gdGhlIGlu dGVuZGVkIHJlY2lwaWVudCwgYW55IHJldmlldywgZm9yd2FyZGluZywgZGlzc2VtaW5hdGlvbiwg ZGlzdHJpYnV0aW9uIG9yIGNvcHlpbmcgb2YgdGhpcyBjb21tdW5pY2F0aW9uIG9yIGFueSBhdHRh Y2htZW50KHMpIGlzIHN0cmljdGx5IHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRo aXMgbWVzc2FnZSBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGltbWVkaWF0ZWx5 LCBhbmQgZGVsZXRlIGl0IGFuZCBhbGwgYXR0YWNobWVudHMgZnJvbSB5b3VyIGNvbXB1dGVyIGFu ZCBuZXR3b3JrLg0K From nobody Mon Aug 31 21:35:06 2015 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 AE7121B7DC1; Mon, 31 Aug 2015 21:35:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.9 X-Spam-Level: X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2] 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 GOa4_cDZls37; Mon, 31 Aug 2015 21:35:01 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3D0E1B5D1A; Mon, 31 Aug 2015 21:35:00 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "Ben Campbell" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.4.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150901043500.19589.77818.idtracker@ietfa.amsl.com> Date: Mon, 31 Aug 2015 21:35:00 -0700 Archived-At: Cc: draft-ietf-ecrit-additional-data@ietf.org, ecrit@ietf.org, draft-ietf-ecrit-additional-data.ad@ietf.org, ecrit-chairs@ietf.org, draft-ietf-ecrit-additional-data.shepherd@ietf.org Subject: [Ecrit] Ben Campbell's Yes on draft-ietf-ecrit-additional-data-34: (with COMMENT) 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, 01 Sep 2015 04:35:03 -0000 Ben Campbell has entered the following ballot position for draft-ietf-ecrit-additional-data-34: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-ecrit-additional-data/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- This draft was clearly lots of work; thanks for making it happen. However, I have a number of comments: The shepherd’s writeup indicates that no XML or media type reviews were required—but this document contains a lot of XML (examples and schema), and a number of media type registrations. Is that an error in the writeup, or have those reviews been skipped? This draft implicitly assumes that the emergency calls are signaled with SIP. I don't dispute that assumption, but I think it should it's worth a paragraph stating it explicitly. -- section 2, 2nd paragraph: Are there any considerations for services provided with no "company" or "service provider" behind them? For example, lets say an individual hosts some VoIP related services for her own use (e.g. a SIP registrar, maybe a stun/turn server,etc) Are those in scope? I'm guessing not, since they would be unlikely to be registered with NENA, but it would be worth saying that explicitly. -- 3: Is there a critical need for the bit about "certain private-use situations"? That seems like license for abuse, without more elaboration about "prexisting relationship" and "privacy issues addressed". -- 4, third paragraph from end: Can you elaborate on what you mean by "at the same time"? Does that mean for the same call? Occurring in some interval of time ? -- 4.1.4 Is a provider limited to one type? If the same provider provides services in multiple categories, would they create multiple instances? -- 4.1.5: Do you intend 24x7 support to be a prerequisite to be a data provider? -- 4.1.7, Description: "Although multiple elements may be contained in a structure only one element SHOULD be provided. If more than one appears, the first SHOULD be used." When might it be reasonable to violate either of these SHOULDs? If the receiver should only look at the first entry why are multiple entries allowed at all? Also, it seems like there are vcard fields that are not useful to this purpose and might still have privacy implications. Do we really need people to send everything? -- 4.2.1, How Used..., last sentence: The term "wireless "needs more precision if you're going to use it in a 2119 expression. With a Wi-Fi handset connected to a wired Internet service count as wireless? How about a cordless phone? -- Figure 5: -Can the list of wireless types change over time? -I don't understand the full definition of "temp". Are these terms defined somewhere? -Do you really want "POTS" vs "PSTN"? -Is VoIP intentionally limited to OTT services? -- 4.3.3: What if the device model designation is not a number? -- 5, list item 1: "The "purpose" parameter also indicates the kind of data (by its MIME subtype) that is available at the URI" What happens if the URL points to something other than the indicated thing? - list item 2, last sentence: I gathered this section was an overview, since you have detailed procedures later. Please consider moving 2119 language to that section. -- Section 5, last paragraph: "only blocks in the registry are permitted to be sent using the mechanisms specified in this document" Are implementations supposed to check the registry at run time? (Also, that language sounds like it should be normative.) -- 5.1, last paragraph: "More than one Call-Info header field with a purpose value starting with ’EmergencyCallData’ can be expected, but at least one MUST be provided. The device MUST provide one if it knows no service provider is in the path of the call." What's the scope of the first MUST? Emergency calls? Is it possible the device doesn't know whether there is a service provider in the path? Should this say it MUST insert unless it knows there is a service provider in tHe path? -- 8: It might be worth discussing the potential harm done by a malicious proxy modifying a data element, or a compromised data source return incorrect information when dereferencing a URL. The first paragraph REQUIRES verification of requester credentials, but does specify the form of those credentials. Subsequent text talks about client-certs and PKI verification. Are other forms of credentials allows? (HTTP-digest, application level logins, etc). If client-certs are required, please say that explicitly. - "PSAPs and responder agencies SHOULD deploy a PKI " When might they not? What if they don't? - "emergency services authorities could obtain a credential from the DNS entry of the domain" Can you elaborate on that or cite something? - paragraph starting with "Much of the information supplied by service providers and devices is private and confidential": Seems like that should go in the privacy considerations. (And probably also the intro.) -- section 10: Many of the registry policies require experts to access whether an organization might be "legitimate" or "relevant". Are these reasonable expectations on the DEs? (I don't know the answer.) Nits and Editorial Comments: -- 4.2.1, Description: Currently, the only valid entries are... Current as of when? I suggest "The initially valid entries are..." -- 4.2.1, How Used... : "... service provider does not know ..." Does not know...what? (That's part of a long, convoluted sentence. Please consider breaking it into simpler sentences.) "... it is known to be valuable." Known by whom? -- 4.3.1, Description: "It is possible to receive two Additional Data Associated with a Call data structures,..." (Occurs in several places.) The naming is confusing. It's easy to read "additional data associated with..." as it's plain English meaning, rather than as a name. I suggest doing something more distinctive than capital letters. Perhaps quotes, or even an abbreviation. -- 4.3.7: That seems odd for this to be a subsection of the device information function. -- section 5: It seems awkard to use a numbered list for elements that are close to a page long each. This forces each to be a single, overlong paragraph. Please consider subsections. -- section 5, list item 2: "circumstances about the provision of the location" I'm not sure I understand the meaning of "provision" in this context. - Sentence starting with: "When the access network provider" This sentence provides context information that would have been useful to have at the start of the section. -- 5.4, 2nd paragraph: I think people are going to be confused and look for "by-reference" in 3204 or 3459. It might be worth re-citing 5621. --10: Some sections reference tables from other sections, and some include the tables directly. It would be nice to be consistent, one way or the other.