Re: [Ecrit] I-D Action: draft-ietf-ecrit-ecall-26.txt

[Randall Gellens <[e-mail]>]

At 7:54 PM +0000 2/12/17, Christer Holmberg wrote:

>  In INFO requests we will always place the stuff in a multipart. 
> But, the main reason for that was so the SIP level 
> Content-Disposition value is always 'info-package' (within the MIME 
> we then always use C-D 'by-refernce').
>
>  Regarding your question, my initial suggestion was not to remove 
> the requirement to wrap, only to remove the sentence saying that 
> the Content-ID is not defined as a SIP header field. But, when 
> thinking about it, there really is no need to require wrap in 
> non-INFO requests, so maybe we should consider removing it - unless 
> someone comes up with a reason why we should mandate it? In reality 
> I think INVITE requests will at least carry SDP too, so one will 
> anyway have to use a multipart.

As you say, in reality the initial INVITE will be multipart anyway, 
so we may as well not make the eCall draft depend on the sipcore 
draft.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Idiot:  A member of a large and powerful tribe whose influence in
human affairs has always been dominant and controlling.
                        --Ambrose Bierce, "The Devil's Dictionary"