Re: [Ecrit] draft-ietf-ecrit-additional-data-11: multiple entities adding data

Brian Rosen <br@brianrosen.net> Tue, 06 August 2013 18:12 UTC

Return-Path: <br@brianrosen.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 5403221E8098 for <ecrit@ietfa.amsl.com>; Tue, 6 Aug 2013 11:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.518
X-Spam-Level:
X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.458, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 QzS-xFP+JYDw for <ecrit@ietfa.amsl.com>; Tue, 6 Aug 2013 11:11:58 -0700 (PDT)
Received: from mail-pb0-f47.google.com (mail-pb0-f47.google.com [209.85.160.47]) by ietfa.amsl.com (Postfix) with ESMTP id 3FEE721F9C13 for <ecrit@ietf.org>; Tue, 6 Aug 2013 11:11:58 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so786687pbb.34 for <ecrit@ietf.org>; Tue, 06 Aug 2013 11:11:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=//gjLeBD8eMQtN978/zVOzI47dH6bWgPTXQckht0I5w=; b=MNcBUrik6UHigsfA1y0N6DhPdD5TA/4XmFesM04NvflZ7/QpxyRUCANr7i2/1neH8Z VwB4rBw4+r8pxij4d+yoqmVpUBFwAanZ/ewqz+XoAoCv7u2BzPf8BUML7MvGeW6A/gEF OWoPVQ4OGQ3fHWGqfXzXyHGO0+iBQMRjdqvaIiRjJDq5JLFdb1aNEndV2lWi9Lgi4bvQ E3vkrbc4OXYcNE4i8gB+k6pw9+aGrfHDX2FoK2FP7CeV2STW2jcKWBa5fRl/seZ+jqLi kNbgn61SzHb1Bcb/lnYU07rbCSCfnbiCQSala369ah+nc/ryLaH/agdViKtGcItHj1zm SVCw==
X-Gm-Message-State: ALoCoQnIoOMFWrbTlAuK7klSBJClLKVFYQim9w1NvSoKOczPfM7jY2eWb0K8qInOQFHHzCMYf1F0
MIME-Version: 1.0
X-Received: by 10.68.223.225 with SMTP id qx1mr2834796pbc.157.1375812717863; Tue, 06 Aug 2013 11:11:57 -0700 (PDT)
Received: by 10.70.23.225 with HTTP; Tue, 6 Aug 2013 11:11:57 -0700 (PDT)
X-Originating-IP: [24.112.236.47]
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C41F05A@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C41F05A@ESESSMB209.ericsson.se>
Date: Tue, 06 Aug 2013 14:11:57 -0400
Message-ID: <CAOPrzE37Lx-qxCCmRJ5RJX29t7EVyFZkESAEnAK5wCSySJDodw@mail.gmail.com>
From: Brian Rosen <br@brianrosen.net>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="047d7b16051553770e04e34b5c16"
Cc: ecrit <ecrit@ietf.org>
Subject: Re: [Ecrit] draft-ietf-ecrit-additional-data-11: multiple entities adding data
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: Tue, 06 Aug 2013 18:12:03 -0000

Not sure pictures in ascii art would help, but more words might.

My usual example is a medical sensor based device adds some, a specialized
service provider who services the device adds some and a communications
service provider adds some.  all of thise go in the SIP message.  then the
access network sends some in the PIDF.

With respect to multiple entities adding data, proxies can't add bodies,
but B2BUAs can.

However, you have pointed out a problem that arose in the evolution of the
mechanism.  Originally, there was an outer envelope wit the blocks inside
it.  That would let us know the source of each block because the data
provider block is required.   The current mechanism doesn't have that.
 It's a problem.

Brian

On Tuesday, August 6, 2013, Christer Holmberg wrote:

>  Hi,
>
> The draft talks about all kind of different entities that might add
> additional data to an emergency call.
>
> First, I think it would be good to have some pictures showing a
> few different scenarios.
>
> Second, the draft doesn't seem to describe the case where multiple
> entities are adding data - for the same call. Will multiple MIMEs etc be
> used, are there restrictions, etc etc etc? OR, is it not allowed to begin
> with?
>
> Regards,
>
> Christer
>
>
>
> Sent from *Windows* using *TouchDown* (www.nitrodesk.com)
>