From nobody Wed Apr 17 13:10:25 2019 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 B62F512000F; Wed, 17 Apr 2019 13:10:23 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: ecrit@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.95.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: ecrit@ietf.org Message-ID: <155553182366.21318.15159303965693495791@ietfa.amsl.com> Date: Wed, 17 Apr 2019 13:10:23 -0700 Archived-At: Subject: [Ecrit] I-D Action: draft-ietf-ecrit-data-only-ea-18.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Apr 2019 20:10:24 -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 WG of the IETF. Title : Data-Only Emergency Calls Authors : Brian Rosen Henning Schulzrinne Hannes Tschofenig Randall Gellens Filename : draft-ietf-ecrit-data-only-ea-18.txt Pages : 22 Date : 2019-04-17 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 Session Initiation Protocol (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 are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-ecrit-data-only-ea-18 https://datatracker.ietf.org/doc/html/draft-ietf-ecrit-data-only-ea-18 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-data-only-ea-18 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 Apr 18 11:43:41 2019 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 57352120127; Thu, 18 Apr 2019 11:43:40 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Allison Mankin via Datatracker To: X-Test-IDTracker: no X-IETF-IDTracker: 6.95.0 Auto-Submitted: auto-generated Precedence: bulk Cc: allison.mankin@gmail.com, Allison Mankin , iesg-secretary@ietf.org, ecrit-chairs@ietf.org, draft-ietf-ecrit-data-only-ea@ietf.org, ecrit@ietf.org Message-ID: <155561302032.25554.13634351916486478779.idtracker@ietfa.amsl.com> Date: Thu, 18 Apr 2019 11:43:40 -0700 Archived-At: Subject: [Ecrit] Publication has been requested for draft-ietf-ecrit-data-only-ea-18 X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Apr 2019 18:43:41 -0000 Allison Mankin has requested publication of draft-ietf-ecrit-data-only-ea-18 as Proposed Standard on behalf of the ECRIT working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-ecrit-data-only-ea/ From nobody Fri Apr 26 10:34:16 2019 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 7E2A4120165; Fri, 26 Apr 2019 10:34:15 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: ecrit@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.95.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: ecrit@ietf.org Message-ID: <155630005542.6808.12487261633630322586@ietfa.amsl.com> Date: Fri, 26 Apr 2019 10:34:15 -0700 Archived-At: Subject: [Ecrit] I-D Action: draft-ietf-ecrit-lost-planned-changes-03.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2019 17:34:16 -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 WG of the IETF. Title : Validation of Locations Around a Planned Change Author : Brian Rosen Filename : draft-ietf-ecrit-lost-planned-changes-03.txt Pages : 17 Date : 2019-04-26 Abstract: This document defines an extension to LoST (RFC5222) that allows a planned change to the data in the LoST server to occur. Records that previously were valid will become invalid at a date in the future, and new locations will become valid after the date. The extension adds two elements to the request: A URI to be used to inform the LIS that previously valid locations will be invalid after the planned change date, and add a date which requests the server to perform validation as of the date specified. It also adds an optional Time-To-Live element to the response, which informs clients about the current expected lifetime of the validation. This document also provides a conventional XML schema for LoST, as backwards compatible alternative to the RelaxNG schema in RFC5222 The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ecrit-lost-planned-changes/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-ecrit-lost-planned-changes-03 https://datatracker.ietf.org/doc/html/draft-ietf-ecrit-lost-planned-changes-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-lost-planned-changes-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/