From nobody Fri Jul 1 14:41:11 2016 Return-Path: X-Original-To: ecrit@ietf.org Delivered-To: ecrit@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 94805126579; Fri, 1 Jul 2016 14:41:10 -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.25.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160701214110.24686.32166.idtracker@ietfa.amsl.com> Date: Fri, 01 Jul 2016 14:41:10 -0700 Archived-At: Cc: ecrit@ietf.org Subject: [Ecrit] I-D Action: draft-ietf-ecrit-ecall-08.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 21:41:10 -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 of the IETF. Title : Next-Generation Pan-European eCall Authors : Randall Gellens Hannes Tschofenig Filename : draft-ietf-ecrit-ecall-08.txt Pages : 35 Date : 2016-07-01 Abstract: This document describes how to use IP-based emergency services mechanisms to support the next generation of the Pan European in- vehicle emergency call service defined under the eSafety initiative of the European Commission (generally referred to as "eCall"). eCall is a standardized and mandated system for a special form of emergency calls placed by vehicles, providing real-time communications and an integrated set of related data. This document also registers a MIME Content Type and an Emergency Call Additional Data Block for the eCall vehicle data and metadata/ control data. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ecrit-ecall/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-ecrit-ecall-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-ecall-08 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 Fri Jul 1 14:46:34 2016 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EE0712D0C0 for ; Fri, 1 Jul 2016 14:46:32 -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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 CP_y4mnHiLR2 for ; Fri, 1 Jul 2016 14:46:30 -0700 (PDT) Received: from sea-mx-02.telecomsys.com (sea-mx-02.telecomsys.com [199.165.246.42]) (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 2CD5312B01C for ; Fri, 1 Jul 2016 14:46:30 -0700 (PDT) Received: from SEA-EXCAS-2.telecomsys.com (exc2010-local2.telecomsys.com [10.32.12.187]) by sea-mx-02.telecomsys.com (8.14.7/8.14.7) with ESMTP id u61LkK1I022081 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Fri, 1 Jul 2016 14:46:21 -0700 Received: from SEA-EXMB-3.telecomsys.com ([169.254.4.140]) by SEA-EXCAS-2.telecomsys.com ([10.32.12.187]) with mapi id 14.03.0248.002; Fri, 1 Jul 2016 14:46:20 -0700 From: Roger Marshall To: "ecrit@ietf.org" Thread-Topic: IETF96 ECRIT call for agenda items, IETF 96 Thread-Index: AdHT4eykZY7ZGnQxQ8iftwODJ6E1XA== Date: Fri, 1 Jul 2016 21:46:19 +0000 Message-ID: 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: multipart/alternative; boundary="_000_FBD5AAFFD0978846BF6D3FAB4C892ACC39916C64SEAEXMB3telecom_" MIME-Version: 1.0 Archived-At: Subject: [Ecrit] IETF96 ECRIT call for agenda items, IETF 96 X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 21:46:32 -0000 --_000_FBD5AAFFD0978846BF6D3FAB4C892ACC39916C64SEAEXMB3telecom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Please let the chairs know if you would like to request time to present at = Berlin in the ECRIT mtg. Include the topic/draft, and the time needed. Thanks in advance. Roger & Marc. ECRIT chairs NOTICE TO RECIPIENT: This email, including attachments, may contain informa= tion which is confidential, proprietary, attorney-client privileged and/or = controlled under U.S. export laws and regulations and may be restricted fro= m disclosure by applicable State and Federal law. Nothing in this email sha= ll create any legal binding agreement between the parties unless expressly = stated herein and provided by an authorized representative of Comtech Telec= ommunications Corp. or its subsidiaries. If you are not the intended recipi= ent of this message, be advised that any dissemination, distribution, or us= e of the contents of this message is strictly prohibited. If you received t= his message in error, please notify us immediately by return email and perm= anently delete all copies of the original email and any attached documentat= ion from any computer or other media. --_000_FBD5AAFFD0978846BF6D3FAB4C892ACC39916C64SEAEXMB3telecom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Please let the chairs know if you would like to requ= est time to present at Berlin in the ECRIT mtg.  Include the topic/dra= ft, and the time needed.

 

Thanks in advance.

 

Roger & Marc.

ECRIT chairs

=0A

<= span style=3D"font-family: ;">NOTICE TO RECIPIENT: This e= mail, including=0Aattachments, may contain information which is confidentia= l, proprietary,=0Aattorney-client privileged and/or controlled under U.S. e= xport laws and=0Aregulations and may be restricted from disclosure by appli= cable State and=0AFederal law. Nothing in this email shall create any legal= binding agreement=0Abetween the parties unless expressly stated herein and= provided by an authorized=0Arepresentative of Comtech Telecommunications C= orp. or its subsidiaries. If you=0Aare not the intended recipient of this m= essage, be advised that any=0Adissemination, distribution, or use of the co= ntents of this message is strictly=0Aprohibited. If you received this messa= ge in error, please notify us immediately=0Aby return email and permanently= delete all copies of the original email and any=0Aattached documentation f= rom any computer or other media.

=0A=0A=0A --_000_FBD5AAFFD0978846BF6D3FAB4C892ACC39916C64SEAEXMB3telecom_-- From nobody Wed Jul 6 02:39:02 2016 Return-Path: X-Original-To: ecrit@ietf.org Delivered-To: ecrit@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA3F12D0B1; Wed, 6 Jul 2016 02:38:57 -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.25.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160706093857.7802.11329.idtracker@ietfa.amsl.com> Date: Wed, 06 Jul 2016 02:38:57 -0700 Archived-At: Cc: ecrit@ietf.org Subject: [Ecrit] I-D Action: draft-ietf-ecrit-car-crash-08.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 09:38:57 -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 of the IETF. Title : Next-Generation Vehicle-Initiated Emergency Calls Authors : Randall Gellens Brian Rosen Hannes Tschofenig Filename : draft-ietf-ecrit-car-crash-08.txt Pages : 46 Date : 2016-07-06 Abstract: This document describes how to use IP-based emergency services mechanisms to support the next generation of emergency calls placed by vehicles (automatically in the event of a crash or serious incident, or manually invoked by a vehicle occupant) and conveying vehicle, sensor, and location data related to the crash or incident. Such calls are often referred to as "Automatic Crash Notification" (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the case of manual trigger. The "Advanced" qualifier refers to the ability to carry a richer set of data. This document also registers a MIME Content Type and an Emergency Call Additional Data Block for the vehicle, sensor, and location data (often referred to as "crash data" even though there is not necessarily a crash). An external specification for the data format, contents, and structure are referenced in this document. This document reuses the technical aspects of next-generation pan- European eCall (a mandated and standardized system for emergency calls by in-vehicle systems within Europe and other regions). However, this document specifies a different set of vehicle (crash) data, specifically, the Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set of Data (MSD). This document is an extension of the eCall document, with the primary differences being that this document makes the MSD data set optional and VEDS mandatory, and extends the eCall metadata/control object to permit greater functionality. This document also describes legacy (circuit- switched) ACN systems and their migration to next-generation emergency calling, to provide background information and context. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ecrit-car-crash/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-ecrit-car-crash-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-car-crash-08 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 Tue Jul 12 06:45:11 2016 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB1412D935 for ; Tue, 12 Jul 2016 06:45:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 ijBynIO5Gh6l for ; Tue, 12 Jul 2016 06:45:03 -0700 (PDT) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9924112DB9A for ; Tue, 12 Jul 2016 06:15:00 -0700 (PDT) X-AuditID: c1b4fb25-f79f26d00000327e-f3-5784ed527768 Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 66.F5.12926.25DE4875; Tue, 12 Jul 2016 15:14:58 +0200 (CEST) Received: from ESESSMB208.ericsson.se ([169.254.8.19]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0294.000; Tue, 12 Jul 2016 15:14:58 +0200 From: Christer Holmberg To: "ecrit@ietf.org" Thread-Topic: ecall: References to draft-additional-data Thread-Index: AQHR3D9jB5a0sQ8dJkOQSp8De1tFDQ== Date: Tue, 12 Jul 2016 13:14:58 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.6.5.160527 x-originating-ip: [153.88.183.17] Content-Type: multipart/alternative; boundary="_000_D3AAC8FEBCE3christerholmbergericssoncom_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnkeLIzCtJLcpLzFFi42KZGbHdUjfobUu4wb9JNhaNi56yOjB6LFny kymAMYrLJiU1J7MstUjfLoErY/eJGywFN6Urjk8tbGDcKd7FyMkhIWAi8b/rKRuELSZx4d56 IJuLQ0jgCKPEjQ/bmSCcxYwSC07NZe1i5OBgE7CQ6P6nDdIgIqAqseHMSkYQW1jAWOL9y68s EHELiY1P+tggbD2JWT3rmUFsFqD6uz+WsoLYvAJWEp9u3WYCsRmBFn8/tQbMZhYQl7j1ZD4T xEECEkv2nGeGsEUlXj7+B9YrCjTz+9fZzCDnSAgoSizvl4NojZc4+uIBO8R4QYmTM5+wTGAU noVk6iwkZbOQlEHEDSTen5vPDGFrSyxb+BrK1pfY+OUs4yygbcwC1hIv1yQjK1nAyLGKUbQ4 tTgpN93IWC+1KDO5uDg/Ty8vtWQTIzB6Dm75rbqD8fIbx0OMAhyMSjy8C+41hwuxJpYVV+Ye YpTgYFYS4W190xIuxJuSWFmVWpQfX1Sak1p8iFGag0VJnNf/pWK4kEB6YklqdmpqQWoRTJaJ g1OqgVHmZ+kLDbWCtIcXXDgOVotMPykeatB/nHOLm3riSV1d5XAJAz2Z92XpTcwWTRPNb+fv 8HCKn3mSf5L8PJ0Id7ctcQH/5365u+WuTMWzvBa2P2knJIy0+UVY/swvm6PrpJDm8XrLshif j50fIr5ynchY6uPy8sQZ3u6y3pQlwbOV36rY+WyZqcRSnJFoqMVcVJwIADLtEuaaAgAA Archived-At: Subject: [Ecrit] ecall: References to draft-additional-data X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2016 13:45:09 -0000 --_000_D3AAC8FEBCE3christerholmbergericssoncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, In general, think the draft still contains far too many references to draft= -additional-data. It=92s really confusing =96 especially since draft-ecall = only uses (as far as I understand) section 6 of draft-additional-data. In some places the text says: "the 'Emergency Call Data Types' IANA registry established in [I-D.ietf-ecr= it-additional-data].=94 You only need to write the name of the IANA registry =96 you don=92t need t= o write which specification created it. In some places the text says: =93mechanism in [I-D.ietf-ecrit-additional-data].=94 I think you should have one specific transport section in the draft, where = you describe how the information is transported in SIP messages (INFOs and = non-INFOs). For non-INFOs, you could refer to section 6 of draft-additional= -data, and for which SIP messages the rules apply. However, section 6 of draft-additional-data contains additional-data specif= ic text, so perhaps you need to be even more specific on exactly what you m= ean by =93mechanism=94. I think it would be better to update section 6 of d= raft-additional-data, to be more generic. Regards, Christer --_000_D3AAC8FEBCE3christerholmbergericssoncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <6227A9178D2E324B85DDF1C230E0E4EC@ericsson.com> Content-Transfer-Encoding: quoted-printable
Hi,

In general, think the draft still contains far too many references to = draft-additional-data. It=92s really confusing =96 especially since draft-e= call only uses (as far as I understand) section 6 of draft-additional-data.=

In some places the text says:

"= the 'Emergency Call Data Types' IANA registry established in [I-D.ietf-ecri= t-additional-data].=94

You only need to write the name of the IANA registry =96 you don=92t n= eed to write which specification created it.


In some places the text says:

=93mec= hanism in [I-D.ietf-ecrit-additional-data].=94

I think you should have one specific transport section in the draft, w= here you describe how the information is transported in SIP messages (INFOs= and non-INFOs). For non-INFOs, you could refer to section 6 of draft-addit= ional-data, and for which SIP messages the rules apply.

However, section 6 of draft-additional-data contains additional-data s= pecific text, so perhaps you need to be even more specific on exactly what = you mean by =93mechanism=94. I think it would be better to update section 6= of draft-additional-data, to be more generic.

Regards,

Christer
--_000_D3AAC8FEBCE3christerholmbergericssoncom_-- From nobody Wed Jul 13 15:34:46 2016 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B57612D916 for ; Wed, 13 Jul 2016 15:34:45 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version" X-Spam-Flag: NO X-Spam-Score: -3.187 X-Spam-Level: X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287] autolearn=unavailable autolearn_force=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 j4QxOmTVFCdM for ; Wed, 13 Jul 2016 15:34:44 -0700 (PDT) Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id BCD7912D8EB for ; Wed, 13 Jul 2016 15:26:28 -0700 (PDT) Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Wed, 13 Jul 2016 15:26:31 -0700 Mime-Version: 1.0 Message-Id: In-Reply-To: References: X-Mailer: Eudora for Mac OS X Date: Wed, 13 Jul 2016 15:25:09 -0700 To: Christer Holmberg , "ecrit@ietf.org" From: Randall Gellens Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Random-Sig-Tag: 1.0b28 X-Random-Sig-Tag: 1.0b28 X-Random-Sig-Tag: 1.0b28 Archived-At: Subject: Re: [Ecrit] ecall: References to draft-additional-data X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2016 22:34:45 -0000 Hi Christer, > In general, think the draft still contains far too many references > to draft-additional-data. It's really confusing - especially since > draft-ecall only uses (as far as I understand) section 6 of > draft-additional-data. > > In some places the text says: > > "the 'Emergency Call Data Types' IANA registry established in > [I-D.ietf-ecrit-additional-data]." > > You only need to write the name of the IANA registry - you don't > need to write which specification created it. OK, I've made these changes throughout -09. > In some places the text says: > > "mechanism in [I-D.ietf-ecrit-additional-data]." I can see how this could be confusing. I've created a new "Data Transport" section that describes exactly how the MSD and metadata/control blocks are attached, and then referred to that section rather than repeat the information about the CID and Call-Info and so forth, which means most references to the additional-data draft have now been deleted. > I think you should have one specific transport section in the > draft, where you describe how the information is transported in SIP > messages (INFOs and non-INFOs). For non-INFOs, you could refer to > section 6 of draft-additional-data, and for which SIP messages the > rules apply. In the new section, I've spelled out how the MSD and the metadata/control object are attached. > > However, section 6 of draft-additional-data contains > additional-data specific text, so perhaps you need to be even more > specific on exactly what you mean by "mechanism". I think it would > be better to update section 6 of draft-additional-data, to be more > generic. The revised text says how the data is attached. I think it's more clear and straightforward now. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly selected tag: --------------- "!sgub evah t'nseod CP sihT ?sgub naem ayaddahW" From nobody Mon Jul 18 06:00:22 2016 Return-Path: X-Original-To: ecrit@ietf.org Delivered-To: ecrit@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0512612D0CA; Mon, 18 Jul 2016 06:00:17 -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.28.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160718130017.24913.1214.idtracker@ietfa.amsl.com> Date: Mon, 18 Jul 2016 06:00:17 -0700 Archived-At: Cc: ecrit@ietf.org Subject: [Ecrit] I-D Action: draft-ietf-ecrit-data-only-ea-12.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2016 13:00:17 -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 of the IETF. Title : Data-Only Emergency Calls Authors : Brian Rosen Henning Schulzrinne Hannes Tschofenig Randall Gellens Filename : draft-ietf-ecrit-data-only-ea-12.txt Pages : 22 Date : 2016-07-18 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) handle Internet multimedia emergency calls natively. The exchange of multimedia traffic for emergency services 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 all that is needed. Examples of such environments include alerts issued by a temperature sensor, burglar alarm, or chemical spill sensor. 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-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-data-only-ea-12 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 Jul 18 07:09:42 2016 Return-Path: X-Original-To: ecrit@ietf.org Delivered-To: ecrit@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 708A812DA28; Mon, 18 Jul 2016 07:09:40 -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.28.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160718140940.24866.5207.idtracker@ietfa.amsl.com> Date: Mon, 18 Jul 2016 07:09:40 -0700 Archived-At: Cc: ecrit@ietf.org Subject: [Ecrit] I-D Action: draft-ietf-ecrit-similar-location-03.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2016 14:09:40 -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 of the IETF. Title : A LoST extension to return complete and similar location info Authors : Roger Marshall Jeff Martin Brian Rosen Filename : draft-ietf-ecrit-similar-location-03.txt Pages : 17 Date : 2016-07-18 Abstract: This document introduces a new way to provide returned location information in LoST responses that is either of a completed or similar form to the original input civic location, based on whether valid or invalid civic address elements are returned within the findServiceResponse message. This document defines a new extension to the findServiceResponse message within the LoST protocol [RFC5222] that enables the LoST protocol to return a completed civic address element set for a valid location response, and one or more suggested sets of similar location information for invalid LoST responses. These two types of civic addresses are referred to as either "complete location" or "similar location", and are included as a compilation of CAtype xml elements within the existing LoST findServiceResponse message structure. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ecrit-similar-location/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-ecrit-similar-location-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-similar-location-03 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 Tue Jul 19 04:00:36 2016 Return-Path: X-Original-To: ecrit@ietf.org Delivered-To: ecrit@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EE55712D12E; Tue, 19 Jul 2016 04:00:32 -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.28.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160719110032.20765.25281.idtracker@ietfa.amsl.com> Date: Tue, 19 Jul 2016 04:00:32 -0700 Archived-At: Cc: ecrit@ietf.org Subject: [Ecrit] I-D Action: draft-ietf-ecrit-data-only-ea-13.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 11:00:33 -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 of the IETF. Title : Data-Only Emergency Calls Authors : Brian Rosen Henning Schulzrinne Hannes Tschofenig Randall Gellens Filename : draft-ietf-ecrit-data-only-ea-13.txt Pages : 22 Date : 2016-07-19 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) handle Internet multimedia emergency calls natively. The exchange of multimedia traffic for emergency services 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 all that is needed. Examples of such environments include alerts issued by a temperature sensor, burglar alarm, or chemical spill sensor. 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-13 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-data-only-ea-13 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 Tue Jul 19 13:46:24 2016 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C746E12D8B0 for ; Tue, 19 Jul 2016 13:46:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 la-jE46Gm6sI for ; Tue, 19 Jul 2016 13:46:21 -0700 (PDT) Received: from sea-mx-02.telecomsys.com (sea-mx-02.telecomsys.com [199.165.246.42]) (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 E923712D8AE for ; Tue, 19 Jul 2016 13:46:20 -0700 (PDT) Received: from SEA-EXCAS-2.telecomsys.com (exc2010-local2.telecomsys.com [10.32.12.187]) by sea-mx-02.telecomsys.com (8.14.7/8.14.7) with ESMTP id u6JKk7Tp004211 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 19 Jul 2016 13:46:07 -0700 Received: from SEA-EXMB-1.telecomsys.com ([169.254.1.182]) by SEA-EXCAS-2.telecomsys.com ([10.32.12.187]) with mapi id 14.03.0248.002; Tue, 19 Jul 2016 13:46:07 -0700 From: Roger Marshall To: "ecrit@ietf.org" Thread-Topic: WGLC Announce: Data-Only Emergency Calls Thread-Index: AdHh/pGOyJxBPWiRSl6QnMmpW/luaw== Date: Tue, 19 Jul 2016 20:46:06 +0000 Message-ID: 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="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: [Ecrit] WGLC Announce: Data-Only Emergency Calls X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 20:46:23 -0000 Today starts a new working group last call for: Data-Only Emergency Calls http://datatracker.ietf.org/doc/draft-ietf-ecrit-data-only-ea/ Please review the document and send comments to the ECRIT mail list by CoB,= July 30, 2016. Thanks, Marc & Roger ECRIT Chairs _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www.ietf.org/mailman/listinfo/ecrit NOTICE TO RECIPIENT: This email, including attachments, may contain informa= tion which is confidential, proprietary, attorney-client privileged and/or = controlled under U.S. export laws and regulations and may be restricted fro= m disclosure by applicable State and Federal law. Nothing in this email sha= ll create any legal binding agreement between the parties unless expressly = stated herein and provided by an authorized representative of Comtech Telec= ommunications Corp. or its subsidiaries. If you are not the intended recipi= ent of this message, be advised that any dissemination, distribution, or us= e of the contents of this message is strictly prohibited. If you received t= his message in error, please notify us immediately by return email and perm= anently delete all copies of the original email and any attached documentat= ion from any computer or other media. From nobody Tue Jul 19 13:51:39 2016 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD1EE12D8D6 for ; Tue, 19 Jul 2016 13:51:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 rTmJyz6uwSmi for ; Tue, 19 Jul 2016 13:51:36 -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 4252812B05D for ; Tue, 19 Jul 2016 13:51:36 -0700 (PDT) Received: from SEA-EXCAS-1.telecomsys.com (exc2010-local1.telecomsys.com [10.32.12.186]) by sea-mx-01.telecomsys.com (8.14.7/8.14.7) with ESMTP id u6JKpVcW008128 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 19 Jul 2016 13:51:31 -0700 Received: from SEA-EXMB-1.telecomsys.com ([169.254.1.182]) by SEA-EXCAS-1.telecomsys.com ([10.32.12.186]) with mapi id 14.03.0248.002; Tue, 19 Jul 2016 13:51:31 -0700 From: Roger Marshall To: "ecrit@ietf.org" Thread-Topic: WGLC Announce: Validation of Locations Around a Planned Change Thread-Index: AdHh/vN/cuT8+hARSmCX95ckZrv5Nw== Date: Tue, 19 Jul 2016 20:51:30 +0000 Message-ID: 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="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: [Ecrit] WGLC Announce: Validation of Locations Around a Planned Change X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 20:51:38 -0000 Today starts a working group last call for: Validation of Locations Around a Planned Change http://tools.ietf.org/html/draft-ecrit-lost-planned-changes/ Please review the document and send comments to the ECRIT mail list by CoB,= July 30, 2016. Thanks, Marc & Roger ECRIT Chairs _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www.ietf.org/mailman/listinfo/ecrit NOTICE TO RECIPIENT: This email, including attachments, may contain informa= tion which is confidential, proprietary, attorney-client privileged and/or = controlled under U.S. export laws and regulations and may be restricted fro= m disclosure by applicable State and Federal law. Nothing in this email sha= ll create any legal binding agreement between the parties unless expressly = stated herein and provided by an authorized representative of Comtech Telec= ommunications Corp. or its subsidiaries. If you are not the intended recipi= ent of this message, be advised that any dissemination, distribution, or us= e of the contents of this message is strictly prohibited. If you received t= his message in error, please notify us immediately by return email and perm= anently delete all copies of the original email and any attached documentat= ion from any computer or other media. From nobody Tue Jul 19 13:53:38 2016 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4253E12D12F for ; Tue, 19 Jul 2016 13:53:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 vF7G9HK41yCY for ; Tue, 19 Jul 2016 13:53:34 -0700 (PDT) Received: from sea-mx-02.telecomsys.com (sea-mx-02.telecomsys.com [199.165.246.42]) (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 AD52012D128 for ; Tue, 19 Jul 2016 13:53:34 -0700 (PDT) Received: from SEA-EXCAS-1.telecomsys.com (exc2010-local1.telecomsys.com [10.32.12.186]) by sea-mx-02.telecomsys.com (8.14.7/8.14.7) with ESMTP id u6JKrSiJ016979 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 19 Jul 2016 13:53:28 -0700 Received: from SEA-EXMB-1.telecomsys.com ([169.254.1.182]) by SEA-EXCAS-1.telecomsys.com ([10.32.12.186]) with mapi id 14.03.0248.002; Tue, 19 Jul 2016 13:53:28 -0700 From: Roger Marshall To: "ecrit@ietf.org" Thread-Topic: WGLC Announce: A LoST extension to return complete and similar location info Thread-Index: AdHh/5kM7KlxIdBsQ4SdBwiTXBZrqg== Date: Tue, 19 Jul 2016 20:53:27 +0000 Message-ID: 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="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: [Ecrit] WGLC Announce: A LoST extension to return complete and similar location info X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 20:53:36 -0000 Today starts a working group last call for: A LoST extension to return complete and similar location info http://datatracker.ietf.org/doc/draft-ietf-ecrit-similar-location/ Please review the document and send comments to the ECRIT mail list by CoB,= July 30, 2016. Thanks, Marc & Roger ECRIT Chairs _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www.ietf.org/mailman/listinfo/ecrit NOTICE TO RECIPIENT: This email, including attachments, may contain informa= tion which is confidential, proprietary, attorney-client privileged and/or = controlled under U.S. export laws and regulations and may be restricted fro= m disclosure by applicable State and Federal law. Nothing in this email sha= ll create any legal binding agreement between the parties unless expressly = stated herein and provided by an authorized representative of Comtech Telec= ommunications Corp. or its subsidiaries. If you are not the intended recipi= ent of this message, be advised that any dissemination, distribution, or us= e of the contents of this message is strictly prohibited. If you received t= his message in error, please notify us immediately by return email and perm= anently delete all copies of the original email and any attached documentat= ion from any computer or other media. From nobody Tue Jul 19 14:03:11 2016 Return-Path: X-Original-To: ecrit@ietf.org Delivered-To: ecrit@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DB37C12D89B for ; Tue, 19 Jul 2016 14:03:09 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: X-Test-IDTracker: no X-IETF-IDTracker: 6.28.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160719210309.20761.97993.idtracker@ietfa.amsl.com> Date: Tue, 19 Jul 2016 14:03:09 -0700 From: IETF Secretariat Archived-At: Subject: [Ecrit] Milestones changed for ecrit WG X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 21:03:10 -0000 Changed milestone "Submit 'A Routing Request Extension for the HELD Protocol' to the IESG for consideration as a Standards Track RFC", resolved as "Done". Changed milestone "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", set due date to November 2016 from March 2016. Changed milestone "Submit ‘Internet Protocol-based In-Vehicle Emergency Calls‘ to the IESG for consideration as an Informational RFC", set due date to November 2016 from March 2016. Changed milestone "Submit ‘Next-Generation Pan-European eCall‘ to the IESG for consideration as an Informational RFC", set due date to November 2016 from March 2016. Changed milestone "Submit ‘A LoST extension to return complete and similar location info‘ to the IESG for consideration as an Informational RFC", set due date to November 2016 from March 2016. URL: https://datatracker.ietf.org/wg/ecrit/charter/ From nobody Tue Jul 19 16:39:15 2016 Return-Path: X-Original-To: ecrit@ietf.org Delivered-To: ecrit@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A53FB12D9AE for ; Tue, 19 Jul 2016 16:39:14 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: X-Test-IDTracker: no X-IETF-IDTracker: 6.28.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160719233914.20859.84791.idtracker@ietfa.amsl.com> Date: Tue, 19 Jul 2016 16:39:14 -0700 From: IETF Secretariat Archived-At: Subject: [Ecrit] Milestones changed for ecrit WG X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 23:39:14 -0000 Changed milestone "Submit ‘Internet Protocol-based In-Vehicle Emergency Calls‘ to the IESG for consideration as an Informational RFC", added draft-ietf-ecrit-car-crash to milestone. Changed milestone "Submit ‘Next-Generation Pan-European eCall‘ to the IESG for consideration as an Informational RFC", added draft-ietf-ecrit-ecall to milestone. Changed milestone "Submit ‘A LoST extension to return complete and similar location info‘ to the IESG for consideration as an Informational RFC", added draft-ietf-ecrit-similar-location to milestone. URL: https://datatracker.ietf.org/wg/ecrit/charter/ From nobody Thu Jul 21 05:32:14 2016 Return-Path: X-Original-To: ecrit@ietf.org Delivered-To: ecrit@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CDA312DBA9; Thu, 21 Jul 2016 05:32:12 -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.29.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160721123212.4441.21113.idtracker@ietfa.amsl.com> Date: Thu, 21 Jul 2016 05:32:12 -0700 Archived-At: Cc: ecrit@ietf.org Subject: [Ecrit] I-D Action: draft-ietf-ecrit-ecall-09.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 12:32:12 -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 of the IETF. Title : Next-Generation Pan-European eCall Authors : Randall Gellens Hannes Tschofenig Filename : draft-ietf-ecrit-ecall-09.txt Pages : 38 Date : 2016-07-21 Abstract: This document describes how to use IP-based emergency services mechanisms to support the next generation of the Pan European in- vehicle emergency call service defined under the eSafety initiative of the European Commission (generally referred to as "eCall"). eCall is a standardized and mandated system for a special form of emergency calls placed by vehicles, providing real-time communications and an integrated set of related data. This document also registers a MIME Content Type and an Emergency Call Additional Data Block for the eCall vehicle data and metadata/ control data. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ecrit-ecall/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-ecrit-ecall-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-ecall-09 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 Jul 21 06:39:23 2016 Return-Path: X-Original-To: ecrit@ietf.org Delivered-To: ecrit@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B5D12D57B; Thu, 21 Jul 2016 06:39:03 -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.29.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160721133903.4519.59261.idtracker@ietfa.amsl.com> Date: Thu, 21 Jul 2016 06:39:03 -0700 Archived-At: Cc: ecrit@ietf.org Subject: [Ecrit] I-D Action: draft-ietf-ecrit-ecall-10.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 13:39:03 -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 of the IETF. Title : Next-Generation Pan-European eCall Authors : Randall Gellens Hannes Tschofenig Filename : draft-ietf-ecrit-ecall-10.txt Pages : 38 Date : 2016-07-21 Abstract: This document describes how to use IP-based emergency services mechanisms to support the next generation of the Pan European in- vehicle emergency call service defined under the eSafety initiative of the European Commission (generally referred to as "eCall"). eCall is a standardized and mandated system for a special form of emergency calls placed by vehicles, providing real-time communications and an integrated set of related data. This document also registers a MIME Content Type and an Emergency Call Additional Data Block for the eCall vehicle data and metadata/ control data. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ecrit-ecall/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-ecrit-ecall-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-ecall-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 Jul 21 11:24:47 2016 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704D412D822 for ; Thu, 21 Jul 2016 11:24:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 f0qOpIWrbAxA for ; Thu, 21 Jul 2016 11:24:42 -0700 (PDT) Received: from sea-mx-02.telecomsys.com (sea-mx-02.telecomsys.com [199.165.246.42]) (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 1AEA912D7AF for ; Thu, 21 Jul 2016 11:24:42 -0700 (PDT) Received: from SEA-EXCAS-1.telecomsys.com (exc2010-local1.telecomsys.com [10.32.12.186]) by sea-mx-02.telecomsys.com (8.14.7/8.14.7) with ESMTP id u6LIOSji002965 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Thu, 21 Jul 2016 11:24:29 -0700 Received: from SEA-EXMB-1.telecomsys.com ([169.254.1.170]) by SEA-EXCAS-1.telecomsys.com ([10.32.12.186]) with mapi id 14.03.0248.002; Thu, 21 Jul 2016 11:24:28 -0700 From: Roger Marshall To: "ecrit@ietf.org" Thread-Topic: ECRIT Milestone updates & corrections Thread-Index: AdHjfPF1fPevwGaVTPypFIldJOuDzA== Date: Thu, 21 Jul 2016 18:24:27 +0000 Message-ID: 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: multipart/alternative; boundary="_000_FBD5AAFFD0978846BF6D3FAB4C892ACC39A920F0SEAEXMB1telecom_" MIME-Version: 1.0 Archived-At: Subject: [Ecrit] ECRIT Milestone updates & corrections X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 18:24:44 -0000 --_000_FBD5AAFFD0978846BF6D3FAB4C892ACC39A920F0SEAEXMB1telecom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We're in the process of updating the Milestones for ECRIT. There are 2 cha= nges being proposed. 1. Date change. The chairs have updated the Milestone dates for the follow= ing 4 Internet Drafts (changed from Mar 2016 to Nov 2016): Nov 2016 Submit 'A LoST extension to return complete and similar location i= nfo' to the IESG for consideration as an Informational RFC draft-ietf-ecrit-similar-location Nov 2016 Submit 'Next-Generation Pan-European eCall' to the IESG for consid= eration as an Informational RFC draft-ietf-ecrit-ecall Nov 2016 Submit 'Internet Protocol-based In-Vehicle Emergency Calls' to the= IESG for consideration as an Informational RFC draft-ietf-ecrit-car-crash Nov 2016 Submit 'Common Alerting Protocol (CAP) based Data-Only Emergency A= lerts using the Session Initiation Protocol (SIP)' to the IESG for consider= ation as an Experimental RFC 2. During the update process, an error was discovered in the type of RFC li= sted withing 3 of the Milestones - each indicating "Informational RFC", ins= tead of "Proposed Standard" as we believe should have been specified from t= he start. Each of these 3 drafts are currently, and have been, listed as "= std" from its -00 version, as listed in the xml source. (currently listed as an Informational RFC) (currently listed as an Informational RFC) > ipr=3D"trust200902" docName=3D"draft-ietf-ecrit-si= milar-location-03"> (currently listed as an Informational RFC) We Propose these additional changes to each of these 3 Milestones to the st= atus of "Proposed Standard". Please respond to the list by 7/30, if you object to making the above chang= es. Roger & Marc ECRIT Chairs NOTICE TO RECIPIENT: This email, including attachments, may contain informa= tion which is confidential, proprietary, attorney-client privileged and/or = controlled under U.S. export laws and regulations and may be restricted fro= m disclosure by applicable State and Federal law. Nothing in this email sha= ll create any legal binding agreement between the parties unless expressly = stated herein and provided by an authorized representative of Comtech Telec= ommunications Corp. or its subsidiaries. If you are not the intended recipi= ent of this message, be advised that any dissemination, distribution, or us= e of the contents of this message is strictly prohibited. If you received t= his message in error, please notify us immediately by return email and perm= anently delete all copies of the original email and any attached documentat= ion from any computer or other media. --_000_FBD5AAFFD0978846BF6D3FAB4C892ACC39A920F0SEAEXMB1telecom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

We’re in the process of updating the Milestone= s for ECRIT.  There are 2 changes being proposed.

 

1. Date change.  The chairs have updated the Mi= lestone dates for the following 4 Internet Drafts (changed from Mar 2016 to= Nov 2016):

 

Nov 2016 Submit ‘A LoST extension to return co= mplete and similar location info‘ to the IESG for consideration as an= Informational RFC

draft-ietf-ecrit-similar-location

 

Nov 2016 Submit ‘Next-Generation Pan-European = eCall‘ to the IESG for consideration as an Informational RFC

draft-ietf-ecrit-ecall

 

Nov 2016 Submit ‘Internet Protocol-based In-Ve= hicle Emergency Calls‘ to the IESG for consideration as an Informatio= nal RFC

draft-ietf-ecrit-car-crash

 

Nov 2016 Submit 'Common Alerting Protocol (CAP) base= d Data-Only Emergency Alerts using the Session Initiation Protocol (SIP)' t= o the IESG for consideration as an Experimental RFC

 

2. During the update process, an error was discovere= d in the type of RFC listed withing 3 of the Milestones – each indica= ting “Informational RFC”, instead of “Proposed Standard&#= 8221; as we believe should have been specified from the start.  Each of these 3 drafts are currently, and have been, listed as “std&= #8221; from its -00 version, as listed in the xml source.

 

<rfc category=3D"std" ipr=3D"trust= 200902" docName=3D"draft-ietf-ecrit-car-crash-08.txt"> (c= urrently listed as an Informational RFC)

<rfc category=3D"std" ipr=3D"trust= 200902" docName=3D"draft-ietf-ecrit-ecall-08.txt"> (curre= ntly listed as an Informational RFC)

<rfc category=3D"std" >> ipr=3D&q= uot;trust200902" docName=3D"draft-ietf-ecrit-similar-location-03&= quot;> (currently listed as an Informational RFC)

 

We Propose these additional changes to each of these= 3 Milestones to the status of “Proposed Standard”.<= /p>

 

Please respond to the list by 7/30, if you object to= making the above changes.

 

Roger & Marc

ECRIT Chairs

 

=0A

<= span style=3D"font-family: ;">NOTICE TO RECIPIENT: This e= mail, including=0Aattachments, may contain information which is confidentia= l, proprietary,=0Aattorney-client privileged and/or controlled under U.S. e= xport laws and=0Aregulations and may be restricted from disclosure by appli= cable State and=0AFederal law. Nothing in this email shall create any legal= binding agreement=0Abetween the parties unless expressly stated herein and= provided by an authorized=0Arepresentative of Comtech Telecommunications C= orp. or its subsidiaries. If you=0Aare not the intended recipient of this m= essage, be advised that any=0Adissemination, distribution, or use of the co= ntents of this message is strictly=0Aprohibited. If you received this messa= ge in error, please notify us immediately=0Aby return email and permanently= delete all copies of the original email and any=0Aattached documentation f= rom any computer or other media.

=0A=0A=0A --_000_FBD5AAFFD0978846BF6D3FAB4C892ACC39A920F0SEAEXMB1telecom_-- From nobody Thu Jul 21 12:41:00 2016 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DA5812D8C1 for ; Thu, 21 Jul 2016 12:40:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 Q1bjnQbzwjgP for ; Thu, 21 Jul 2016 12:40:58 -0700 (PDT) Received: from sea-mx-02.telecomsys.com (sea-mx-02.telecomsys.com [199.165.246.42]) (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 13B9E12D8BF for ; Thu, 21 Jul 2016 12:40:56 -0700 (PDT) Received: from SEA-EXCAS-1.telecomsys.com (exc2010-local1.telecomsys.com [10.32.12.186]) by sea-mx-02.telecomsys.com (8.14.7/8.14.7) with ESMTP id u6LJelfl006511 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Thu, 21 Jul 2016 12:40:47 -0700 Received: from SEA-EXMB-1.telecomsys.com ([169.254.1.170]) by SEA-EXCAS-1.telecomsys.com ([10.32.12.186]) with mapi id 14.03.0248.002; Thu, 21 Jul 2016 12:40:47 -0700 From: Roger Marshall To: "ecrit@ietf.org" Thread-Topic: Meeting Minutes Posted - IETF96 Thread-Index: AdHjh0/BFAEM1uEXT1yyuopVv4DvFA== Date: Thu, 21 Jul 2016 19:40:46 +0000 Message-ID: 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="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: [Ecrit] Meeting Minutes Posted - IETF96 X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 19:40:59 -0000 You can find the ECRIT/IETF96 meeting minutes for today's meeting in Berlin= , posted to the Materials Manager at: http://www.ietf.org/proceedings/96/minutes/minutes-96-ecrit Thanks to our anonymous etherpad note-taker! I've combined those notes wit= h ones I also recorded. Please let me know if there is any information that is not accurate, along = with the correction. Roger Marshall ECRIT Co-chair NOTICE TO RECIPIENT: This email, including attachments, may contain informa= tion which is confidential, proprietary, attorney-client privileged and/or = controlled under U.S. export laws and regulations and may be restricted fro= m disclosure by applicable State and Federal law. Nothing in this email sha= ll create any legal binding agreement between the parties unless expressly = stated herein and provided by an authorized representative of Comtech Telec= ommunications Corp. or its subsidiaries. If you are not the intended recipi= ent of this message, be advised that any dissemination, distribution, or us= e of the contents of this message is strictly prohibited. If you received t= his message in error, please notify us immediately by return email and perm= anently delete all copies of the original email and any attached documentat= ion from any computer or other media. From nobody Tue Jul 26 08:39:38 2016 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41BAE12DCCE for ; Tue, 26 Jul 2016 08:39:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 MYYr3KPzQLjE for ; Tue, 26 Jul 2016 08:39:30 -0700 (PDT) Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.167]) (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 8497C12DAB1 for ; Tue, 26 Jul 2016 08:06:27 -0700 (PDT) Received: from [85.158.137.67] by server-7.bemta-3.messagelabs.com id 7F/DB-03271-17C77975; Tue, 26 Jul 2016 15:06:25 +0000 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrNKsWRWlGSWpSXmKPExsXi7PqsVbewZnq 4wYRZghaNi56yOjB6LFnykymAMYo1My8pvyKBNWP65372glXaFd92XGdqYDyv0sXIySEh4CfR e+kaWxcjF4eQwF5Gidcvb7JCODcYJSa2djBDOKcZJaa8+sjSxcjBwSagJ3HxlQ1It4iAqsSGM ysZQWxhgRCJ5f/OM0HEQyVW7bvMCmHrSSz/9ZkFxGYBqt91YBuYzSvgI3Hyx3UwW0ggQOLlg9 PsIDanQKDElWMrweYwCshKbJj4DayGWUBc4tvRlcwQVwtILNlzHsoWlXj5+B8rhG0gsXXpPhY IW17i288ZjBC9ehI3pk5hg7C1JZYtfM0McYOgxMmZT6DqJSUOrrgB9qKQgIzE1i2KEK/PZJRY 1zefHaLGXuL/pR+MExilZiE5aRaSFbOQrJiFZMUCRpZVjBrFqUVlqUW6RkZ6SUWZ6RkluYmZO bqGBsZ6uanFxYnpqTmJScV6yfm5mxiBkVrPwMC4g3HqCb9DjJIcTEqivEwTpoUL8SXlp1RmJB ZnxBeV5qQWH2KU4eBQkuAVq54eLiRYlJqeWpGWmQNMGTBpCQ4eJRHegiqgNG9xQWJucWY6ROo Uo6KUOK80SJ8ASCKjNA+uDZamLjHKSgnzMjIwMAjxFKQW5WaWoMq/YhTnYFQShpjCk5lXAjf9 FdBiJqDFC3gmgywuSURISTUwOnYIPVPwOfguJ1e9Xz7riM0WFrlpB7YWvHrOl5W8QFTMILxrx zLNSlVxn8Q47Yu6Bic+3Yor0OuT3yXttyU+nvVgaN20UL6atP/fhXIEgxqDNq0MXbxyW6yQ1h mT8++WbLTYHmI/OXVFUazjru9+0fu2H3u416RmzSKWUt1QJo7ZHlaM/s+UWIozEg21mIuKEwG crKNDTgMAAA== X-Env-Sender: g.caron@bell.ca X-Msg-Ref: server-4.tower-139.messagelabs.com!1469545583!29463162!3 X-Originating-IP: [67.69.230.133] X-StarScan-Received: X-StarScan-Version: 8.77; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29262 invoked from network); 26 Jul 2016 15:06:25 -0000 Received: from tls.exchange.bell.ca (HELO Tls.exchange.bell.ca) (67.69.230.133) by server-4.tower-139.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 26 Jul 2016 15:06:25 -0000 X-CrossPremisesHeadersFilteredBySendConnector: EX13EDGE02-WYN.bell.corp.bce.ca Received: from DG2MBX04-WYN.bell.corp.bce.ca (198.235.102.33) by EX13EDGE02-WYN.bell.corp.bce.ca (198.235.68.44) with Microsoft SMTP Server id 15.0.1076.9; Tue, 26 Jul 2016 23:55:00 -0400 Received: from DG2MBX01-WYN.bell.corp.bce.ca (2002:8eb6:1213::8eb6:1213) by DG2MBX04-WYN.bell.corp.bce.ca (2002:8eb6:1216::8eb6:1216) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 26 Jul 2016 11:06:10 -0400 Received: from DG2MBX01-WYN.bell.corp.bce.ca ([fe80::d91e:3e92:8922:f20e]) by DG2MBX01-WYN.bell.corp.bce.ca ([fe80::d91e:3e92:8922:f20e%21]) with mapi id 15.00.1104.000; Tue, 26 Jul 2016 11:06:10 -0400 From: "Caron, Guy (A162859)" To: "ecrit@ietf.org" Thread-Topic: [Ecrit] WGLC Announce: Validation of Locations Around a Planned Change Thread-Index: AQHR508+XLMgL9h750ShdSW/ZvxTJw== Date: Tue, 26 Jul 2016 15:06:10 +0000 Message-ID: <41cf7576dad84d45a5171d262dd9f164@DG2MBX01-WYN.bell.corp.bce.ca> References: In-Reply-To: Accept-Language: fr-CA, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.28.92.1] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Received-SPF: SoftFail (EX13EDGE02-WYN.bell.corp.bce.ca: domain of transitioning g.caron@bell.ca discourages use of 198.235.102.33 as permitted sender) X-OrganizationHeadersPreserved: EX13EDGE02-WYN.bell.corp.bce.ca Archived-At: Subject: Re: [Ecrit] WGLC Announce: Validation of Locations Around a Planned Change X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2016 15:39:36 -0000 Hi ECRIT, I've reviewed this draft and finds the proposed mechanism helpful, well des= igned and ready for prime time. My review comments are in the sections belo= w where section A is for substantive comments and section B for editorial/c= osmetic comments. Thanks, Guy ////// START \\\\\\ Section A - Substantive Comments -------------------------------- a. The document uses the acronym "LI" but it is not defined, expanded or re= ferenced to anywhere. It is not even used in RFC5222. Consider replacing by= the generic term "location". b. In Section 3 - element, the length limit of the URI is d= efined as "less than 256 bytes". Consider changing to "256 bytes or less". c. In Section 5 - uri Not Stored Warning, it is mentioned the 'uriNotStored= ' is added to the exceptionContainer. I'm no RelaxNG expert but the excepti= onContainer doesn't seem to be extended to include uriNotStored in the Rela= xNG schema in Section 7; only the basic Exception pattern seems to be defin= ed. Section B - Editorial/Cosmetic ------------------------------ 1. The document uses delimiters (", ', <>) inconsistently when referring to= defined strings and terms. Consider using delimiters in a consistent way t= hroughout the document. An option would be to use <> for elements (e.g., ) and request/response (e.g., ), single q= uotes for attributes (e.g., 'asOf') and double quotes for general English t= erms (e.g., "as of now").=20 Abstract Section 2. "The extension adds two elements to the request: a URI to = be used to inform the LIS..." capitalize "a" after the colon. 3. Spell out "TTL" (i.e., "Time-to-Live") and replace "all queriers" with "= clients about" so that it reads "It also adds an optional Time-To-Live elem= ent to the response, which informs clients about the current expected lifet= ime of the validation." Introduction Section 4. First paragraph: Replace "lt;" by "<" in front of "findServiceResponse>"= . 5. First paragraph: Expand TTL to "Time-to-Live" and put TTL in parenthesis= so it would look like "Time-to-Live (TTL)". 6. Second paragraph: Add "-LO" after "PIDF". 7. Second paragraph: Replace "effectivity" (not a word) by "effective". 8. Third paragraph: Add a period at the end of the paragraph, after "revali= dation". 9. Sixth paragraph: Replace "lt;" by "<" in front of "findServiceResponse>"= . element Section 10. First paragraph: Capitalize "https". 11. First paragraph: Capitalize "uris" (i.e., "URIs") in the last two sente= nces of the paragraph. uri Not Stored Warning Section 12. Title: Capitalize "uri". 13. Capitalize "uri" in the last sentence. TTL in Response Section 14: Title: Spell-out TTL and put TTL in parenthesis (i.e., "Time-To-Live (T= TL)") 15. First paragraph: Add "attribute" after "'expires'" in the sentence star= ting with "The form of the element is the 'expires'...". 16. First paragraph: Replace "No Cache" and "No Expiration" by "NO-CACHE" a= nd "NO-EXPIRATION" respectively to reflect the actual values as defined in = RFC5222. 17. First paragraph: Change "...and MUST NOT be returned in TTL" to "... an= d MUST NOT be returned in the element". 18. Fourth paragraph: Add "value" after TTL in the first sentence. Security Considerations Section 19. Second paragraph: In the fourth sentence, add "attribute" after "uri" a= nd make byte plural (i.e., "The server MUST validate that the content of th= e uri attribute sent is syntactically valid and meets the 256 bytes limit") 20. Second paragraph: Capitalize "uri" and "http" in the last sentence. 21: Third paragraph: Delete "when" and capitalize "uri" in the first senten= ce (i.e., " The mutual authentication between client and server is RECOMMEN= DED for both the initial operation that requests storing the = URI...") \\\\\\ END ////// -----Message d'origine----- De=A0: Ecrit [mailto:ecrit-bounces@ietf.org] De la part de Roger Marshall Envoy=E9=A0: 19 juillet 2016 16:51 =C0=A0: ecrit@ietf.org Objet=A0: [Ecrit] WGLC Announce: Validation of Locations Around a Planned C= hange Today starts a working group last call for: Validation of Locations Around a Planned Change http://tools.ietf.org/html/= draft-ecrit-lost-planned-changes/ Please review the document and send comments to the ECRIT mail list by CoB,= July 30, 2016. Thanks, Marc & Roger ECRIT Chairs _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www.ietf.org/mailman/listinfo/ecrit NOTICE TO RECIPIENT: This email, including attachments, may contain informa= tion which is confidential, proprietary, attorney-client privileged and/or = controlled under U.S. export laws and regulations and may be restricted fro= m disclosure by applicable State and Federal law. Nothing in this email sha= ll create any legal binding agreement between the parties unless expressly = stated herein and provided by an authorized representative of Comtech Telec= ommunications Corp. or its subsidiaries. If you are not the intended recipi= ent of this message, be advised that any dissemination, distribution, or us= e of the contents of this message is strictly prohibited. If you received t= his message in error, please notify us immediately by return email and perm= anently delete all copies of the original email and any attached documentat= ion from any computer or other media. _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www.ietf.org/mailman/listinfo/ecrit From nobody Fri Jul 29 22:16:35 2016 Return-Path: X-Original-To: ecrit@ietfa.amsl.com Delivered-To: ecrit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C19B712D1E4; Fri, 29 Jul 2016 22:16:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.889 X-Spam-Level: X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=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 MNJf7moY4VcO; Fri, 29 Jul 2016 22:16:32 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 073B012D108; Fri, 29 Jul 2016 22:16:31 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id B0997B80299; Fri, 29 Jul 2016 22:16:31 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20160730051631.B0997B80299@rfc-editor.org> Date: Fri, 29 Jul 2016 22:16:31 -0700 (PDT) Archived-At: Cc: drafts-update-ref@iana.org, ecrit@ietf.org, rfc-editor@rfc-editor.org Subject: [Ecrit] RFC 7852 on Additional Data Related to an Emergency Call X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jul 2016 05:16:33 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7852 Title: Additional Data Related to an Emergency Call Author: R. Gellens, B. Rosen, H. Tschofenig, R. Marshall, J. Winterbottom Status: Standards Track Stream: IETF Date: July 2016 Mailbox: rg+ietf@randy.pensive.org, br@brianrosen.net, Hannes.Tschofenig@gmx.net, rmarshall@telecomsys.com, a.james.winterbottom@gmail.com Pages: 113 Characters: 239135 Updates: RFC 6443, RFC 6881 I-D Tag: draft-ietf-ecrit-additional-data-38.txt URL: https://www.rfc-editor.org/info/rfc7852 DOI: http://dx.doi.org/10.17487/RFC7852 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 as much of the information described here as possible 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. This document is a product of the Emergency Context Resolution with Internet Technologies Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC