Re: [Ecrit] draft-ietf-ecrit-additional-data-11: multiple entities adding data
Brian Rosen <br@brianrosen.net> Wed, 07 August 2013 12:52 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 032D921E8115 for <ecrit@ietfa.amsl.com>; Wed, 7 Aug 2013 05:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.264
X-Spam-Level:
X-Spam-Status: No, score=-102.264 tagged_above=-999 required=5 tests=[AWL=-0.288, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 dvHRrI7UpgR0 for <ecrit@ietfa.amsl.com>; Wed, 7 Aug 2013 05:52:41 -0700 (PDT)
Received: from mail-pd0-f179.google.com (mail-pd0-f179.google.com [209.85.192.179]) by ietfa.amsl.com (Postfix) with ESMTP id B37F711E8124 for <ecrit@ietf.org>; Wed, 7 Aug 2013 05:52:32 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id v10so1361329pde.10 for <ecrit@ietf.org>; Wed, 07 Aug 2013 05:52:31 -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=zDcNvT0MIPm02ZNyihiOGgIeaM/qbTibzP/pQtV6VIw=; b=cAOAmnBOPrfqwbBZExdwR8eAL3MZrTXTiI8DFIqKskrJ2GeBwl+APhfovXj+mgQ1Jx s6n9kXclgaAcfrwdoOUeymHFCSVmW1Hc6b+ZuxRUV/CdJwSp0yRzmddv1W7TZLxLEtua 27loFgN/YzClyiaowpLz9QqmyRaPQ0W9N3oOQf5ToRXCcVRilhDMDi+the5CkuibLMv4 TGfuesjWRhB0n2IMRLANOqoyKaj0wDvsfDphIY4BVb+9aDpxyZ8Yt9GABgGXax9IWLdB M70Y/YCFKk+md/kNR9+4qHtv5ay+hN6z4qeLd7kTTCiof+SLThv/Zhsm+R9LcCkXwqjn uw0g==
X-Gm-Message-State: ALoCoQl56r5MZteihN3Q0kxpq2WlJl5f9AZx3nmDv54Yf9fq7nnCRo84bAtRXkf4K2gvZl3EUY+q
MIME-Version: 1.0
X-Received: by 10.68.223.225 with SMTP id qx1mr379436pbc.157.1375879949722; Wed, 07 Aug 2013 05:52:29 -0700 (PDT)
Received: by 10.70.23.225 with HTTP; Wed, 7 Aug 2013 05:52:29 -0700 (PDT)
X-Originating-IP: [24.112.236.47]
In-Reply-To: <ADE693DC-F327-4093-B06E-D89F1FFCA9DD@gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B1C41F05A@ESESSMB209.ericsson.se> <CAOPrzE37Lx-qxCCmRJ5RJX29t7EVyFZkESAEnAK5wCSySJDodw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C41F8B4@ESESSMB209.ericsson.se> <ADE693DC-F327-4093-B06E-D89F1FFCA9DD@gmail.com>
Date: Wed, 07 Aug 2013 08:52:29 -0400
Message-ID: <CAOPrzE2nvpbPmfi0BmY-+wo6vZStQKvdEz5uFqt+8vX306biZA@mail.gmail.com>
From: Brian Rosen <br@brianrosen.net>
To: James Winterbottom <a.james.winterbottom@gmail.com>
Content-Type: multipart/alternative; boundary="047d7b160515a82b3f04e35b033d"
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: Wed, 07 Aug 2013 12:52:50 -0000
There is a requirement for multiple entities to add information. I don't think there needs to be a requirement that it happen by value, but its at least desirable. James, it's perfectly clear that some blocks need to be repeated For example the block that says who provided the data. Others are more specialized. So generically, it's a requirement that at least some blocks are supplied by multiple enties. Brian On Wednesday, August 7, 2013, James Winterbottom wrote: > Actually, I think that the requirement is more whether a single entity > should be able to add multiple types if information. > > Cheers > James > > Sent from my iPhone > > On 07/08/2013, at 4:32 PM, Christer Holmberg < > christer.holmberg@ericsson.com <javascript:;>> wrote: > > > Hi Brian, > > > >> Not sure pictures in ascii art would help, but more words might. > > > > I think some ascii art, showing the calling device (user or sensor), > some intermediary ("server") and the PSAP would help. > > > >> 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. > > > > Well, that is protocol/solution talk - the question is whether there is > a REQUIREMENT that multiple entities should be able to add information :) > > > > (If so, we then have to either mandate B2BUA functionality, or use some > other mechanism. For example, data that can be defined as capabilities > could be indicated also using feature capability indicators.) > > > > Regards, > > > > Christer > > > > > > > > > > > > > > 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) > > _______________________________________________ > > Ecrit mailing list > > Ecrit@ietf.org <javascript:;> > > https://www.ietf.org/mailman/listinfo/ecrit >
- [Ecrit] draft-ietf-ecrit-additional-data-11: mult… Christer Holmberg
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Brian Rosen
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Christer Holmberg
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … James Winterbottom
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Brian Rosen
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Hannes Tschofenig
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Brian Rosen
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … James Winterbottom
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Brian Rosen
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … James Winterbottom
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Brian Rosen
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … James Winterbottom
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Brian Rosen
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … James Winterbottom
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Brian Rosen
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … James Winterbottom
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Hannes Tschofenig
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Brian Rosen
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Hannes Tschofenig
- Re: [Ecrit] draft-ietf-ecrit-additional-data-11: … Randall Gellens