Re: [Ecrit] I-D Action: draft-ietf-ecrit-additional-data-13.txt

Hannes Tschofenig <hannes.tschofenig@gmx.net> Wed, 16 October 2013 11:43 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 74B4411E81CB for <ecrit@ietfa.amsl.com>; Wed, 16 Oct 2013 04:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8hegOXdcA3r4 for <ecrit@ietfa.amsl.com>; Wed, 16 Oct 2013 04:43:31 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 0B36211E81CE for <ecrit@ietf.org>; Wed, 16 Oct 2013 04:43:28 -0700 (PDT)
Received: from [172.16.254.200] ([80.92.116.76]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0Lw2Sj-1VpOZG2Z25-017iZJ for <ecrit@ietf.org>; Wed, 16 Oct 2013 13:43:28 +0200
Message-ID: <525E7BFD.20703@gmx.net>
Date: Wed, 16 Oct 2013 13:43:57 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>, "ecrit@ietf.org" <ecrit@ietf.org>
References: <20131016091416.32193.78065.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B1C4BFFBE@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C4BFFBE@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:WMXkfUHTlYepaQJ1Wsr0oKS6pDyeuF2B9Bx2IEkVKVYN+oYUMn5 tmoPIKvKyCz0wxHUHev5thiloQNkPIQbh7nj1n+TRL1tol+GzFU3UhW/CvGvFwNOkMAEZPs qHXr071wgkxWbHke4luYYkHtblPAIJUGu8I8ET6jaVnJyTRbEoEQ0TqsfWEUBw5evEP1KNy qxnoyxpv2hTrvopENcdkQ==
Subject: Re: [Ecrit] I-D Action: draft-ietf-ecrit-additional-data-13.txt
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 11:43:36 -0000

Hi Christer,


with today's draft updates we have tried to address the feedback from 
Barbara. We will try to address your remarks within the next few days.

Sorry for the delay; we certainly haven't forgotten your review remarks.

Ciao
Hannes

On 10/16/2013 12:09 PM, Christer Holmberg wrote:
> Hi,
>
> I had some comments on v-11 of the draft, but I don't think they have been addressed in the new version.
>
> ----------------------
>
> Q1: 	Question on scope of the Contact URI, defined in section 3.1.5
> E-mail: 	http://www.ietf.org/mail-archive/web/ecrit/current/msg08641.html
>
> My issue was about the semantics/usage of the Contact URI, and whether it e.g. should be used for callbacks.
>
> Brian explained that that is not the purpose of the Contact URI, and indicated that some clarification text will be added. However, I see no such text.
>
> ----------------------
>
> Q2:	Question on possible conflict between language feature tag and data provider language, defined in section 3.1.6
> E-mail:	http://www.ietf.org/mail-archive/web/ecrit/current/msg08642.html
>
> My issue was why we couldn't use media feature tags, indicating the supported languages.
>
> ----------------------
>
> Q3:	Question on multiple entities adding data
> E-mail:	http://www.ietf.org/mail-archive/web/ecrit/current/msg08646.html
>
> My issue was whether multiple entities could add information, and whether multiple MIMEs would be used in such case, etc.
>
> I also requested some example pictures, showing a call where multiple types of entities add information.
>
> Related to this, James W asked whether a single entity should be allowed to enter multiple types of information.
>
> ----------------------
>
> Regards,
>
> Christer
>
>
>
> -----Original Message-----
> From: ecrit-bounces@ietf.org [mailto:ecrit-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: 16. lokakuuta 2013 12:14
> To: i-d-announce@ietf.org
> Cc: ecrit@ietf.org
> Subject: [Ecrit] I-D Action: draft-ietf-ecrit-additional-data-13.txt
>
>
> 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
> 	Author(s)       : Brian Rosen
>                            Hannes Tschofenig
>                            Roger Marshall
>                            Randall Gellens
>                            James Winterbottom
> 	Filename        : draft-ietf-ecrit-additional-data-13.txt
> 	Pages           : 86
> 	Date            : 2013-10-16
>
> Abstract:
>     When an emergency call is sent to a Public Safety Answering Point
>     (PSAP), the device that sends it, as well as any application service
>     provider in the path of the call, or access network provider through
>     which the call originated may have information about the call, the
>     caller or the location which the PSAP may be able to use.  This
>     document describes data structures and a mechanism to convey such
>     data to the PSAP.  The mechanism uses a Uniform Resource Identifier
>     (URI), which may point to either an external resource or an object in
>     the body of the SIP message.  The mechanism thus allows the data to
>     be passed by reference (when the URI points to an external resource)
>     or by value (when it points into the body of the message).  This
>     follows the tradition of prior emergency services standardization
>     work where data can be conveyed by value within the call signaling
>     (i.e., in body of the SIP message) and also 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:
> http://tools.ietf.org/html/draft-ietf-ecrit-additional-data-13
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-additional-data-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/
>
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit
>