From nobody Mon Mar 11 11:25:30 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 51C0A131189; Mon, 11 Mar 2019 11:25: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.93.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: ecrit@ietf.org Message-ID: <155232872327.23172.10675118743649722006@ietfa.amsl.com> Date: Mon, 11 Mar 2019 11:25:23 -0700 Archived-At: Subject: [Ecrit] I-D Action: draft-ietf-ecrit-data-only-ea-17.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: Mon, 11 Mar 2019 18:25:28 -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-17.txt Pages : 22 Date : 2019-03-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) 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-17 https://datatracker.ietf.org/doc/html/draft-ietf-ecrit-data-only-ea-17 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-data-only-ea-17 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 Mar 11 11:29:26 2019 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 9CFDD130E72 for ; Mon, 11 Mar 2019 11:29:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.89 X-Spam-Level: X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com 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 11DlVXTkIX01 for ; Mon, 11 Mar 2019 11:29:15 -0700 (PDT) Received: from mail-yw1-xc31.google.com (mail-yw1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (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 136F713116B for ; Mon, 11 Mar 2019 11:29:15 -0700 (PDT) Received: by mail-yw1-xc31.google.com with SMTP id j66so1754121ywc.10 for ; Mon, 11 Mar 2019 11:29:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=51H1SpafsyVomI83X632GGuw+yhJj33RReXgB5Jr5Cg=; b=kRdUkJQ4pnuOFt8yieGM1O3bI3hAuHfxQyBVnEvOx4csezaMA4qYxamSd9tNHWmoC5 ruDEacmmYT+kquo7hUzL3qRbR2AUxYgyY4t72AvZz0wIfyLhmq93nVQG0fgA8x9RBdsY e3o0gZGdyyoUx+HKHEweWgBe+RxB7kI/eHOMCjxM0k2vly8Fq3uCZUyxXpA8ZiF0LK+Q VPfu/0Ro/A9942nDLhJUshckTc+Qt42+JOFTk80UCopTHjhYsFf3DxQrwUpcEKElaBeW O84XHzi17MdX6B+OV+CPwvtKFze9631ec5Gu5zSt6gMEA1FJ+w7/9AFKHNLO6tcuomxw VSfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=51H1SpafsyVomI83X632GGuw+yhJj33RReXgB5Jr5Cg=; b=PbvC3UVz4lOjch09m2f7jai3kRvNP7r43VxiCLQ5GuEn89TG0Cy5h+D5XxfXN8IBvG e1ozZkJ3ViXEUI2qeNnwIY+0ShNckQEEfyRwdHnuatNCCTF75olfbblznCVokASBuzyL 8qHsLgLi8H2FDoXT/t2wFcWQ1S7n58AgDzIKr9tetflxQ/WAQmyQ8IxRckVaYfsWMYjI hpNRExLo28LS9kCo1o8Hkko8qoAvCG3LsxGhtJFmBkkOANCUUmtDxnr4i8ZFF0Y0+833 EH31S1odfFOooJRhyUd88z5LiKtsHya3stT1R1C6PHLhSacWnvCEf/GF4R8q+9nZMWUK b6jw== X-Gm-Message-State: APjAAAXmt0PdWSp+j2YA1FNk7VwwQUoja5g5d5Esm9UMSPTEmkrNMod3 UKafgjLU74COhLukNcI2pStmNNKN58U= X-Google-Smtp-Source: APXvYqzbEbpAUzKSHr8NVNNJEeHpw0ufT6IAXQT8Mx4XJUV3vRpSYpJz71x+XSmm0mujxpRSTXJJjQ== X-Received: by 2002:a25:40d8:: with SMTP id n207mr29284257yba.427.1552328954042; Mon, 11 Mar 2019 11:29:14 -0700 (PDT) Received: from brians-mbp.lan ([148.64.109.153]) by smtp.gmail.com with ESMTPSA id d85sm2445488ywd.96.2019.03.11.11.29.13 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Mar 2019 11:29:13 -0700 (PDT) From: Brian Rosen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Date: Mon, 11 Mar 2019 11:29:10 -0700 References: <155232872327.23172.10675118743649722006@ietfa.amsl.com> To: ECRIT In-Reply-To: <155232872327.23172.10675118743649722006@ietfa.amsl.com> Message-Id: X-Mailer: Apple Mail (2.3445.102.3) Archived-At: Subject: Re: [Ecrit] I-D Action: draft-ietf-ecrit-data-only-ea-17.txt X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2019 18:29:25 -0000 This version has a minor update to the CAP message construction text. = If the element is required in a CAP message (although the draft = recommends not using ), conversion from PIDF-LO to is = complicated by the fact that the spec only allows 2D circles and = polygons. This version points that out and suggests conversions from = other permitted PIDF-LO shapes as appropriate. Brian > On Mar 11, 2019, at 11:25 AM, internet-drafts@ietf.org wrote: >=20 >=20 > 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. >=20 > Title : Data-Only Emergency Calls > Authors : Brian Rosen > Henning Schulzrinne > Hannes Tschofenig > Randall Gellens > Filename : draft-ietf-ecrit-data-only-ea-17.txt > Pages : 22 > Date : 2019-03-11 >=20 > 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. >=20 > 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. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-ecrit-data-only-ea/ >=20 > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-ecrit-data-only-ea-17 > https://datatracker.ietf.org/doc/html/draft-ietf-ecrit-data-only-ea-17 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-ecrit-data-only-ea-17 >=20 >=20 > 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. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Ecrit mailing list > Ecrit@ietf.org > https://www.ietf.org/mailman/listinfo/ecrit