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

[Christer Holmberg <[e-mail]>]

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)