Re: [Ecrit] Ivo's review of draft-ietf-ecrit-ecall-15 - ISSUE 7

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 01 November 2016 12:48 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 30D2A1295A7 for <ecrit@ietfa.amsl.com>; Tue, 1 Nov 2016 05:48:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.698
X-Spam-Level:
X-Spam-Status: No, score=-5.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5SJtuyYpWddf for <ecrit@ietfa.amsl.com>; Tue, 1 Nov 2016 05:48:43 -0700 (PDT)
Received: from alum-mailsec-scanner-4.mit.edu (alum-mailsec-scanner-4.mit.edu [18.7.68.15]) by ietfa.amsl.com (Postfix) with ESMTP id A22A812945E for <ecrit@ietf.org>; Tue, 1 Nov 2016 05:48:43 -0700 (PDT)
X-AuditID: 1207440f-20bff700000009a9-4b-58188f2a9a34
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 3D.6A.02473.A2F88185; Tue, 1 Nov 2016 08:48:42 -0400 (EDT)
Received: from [192.168.1.110] (c-73-186-127-100.hsd1.ma.comcast.net [73.186.127.100]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id uA1CmfVG011611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ecrit@ietf.org>; Tue, 1 Nov 2016 08:48:42 -0400
To: ecrit@ietf.org
References: <AM5PR0701MB2468010828183D6956A82E66E5AE0@AM5PR0701MB2468.eurprd07.pro d.outlook.com> <p06240600d43d18f64b41@[99.111.97.136]> <AM5PR0701MB2468AC6B5171EC51373DF563E5A10@AM5PR0701MB2468.eurprd07.prod.outlook.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <181874aa-8dc1-8cd5-3ced-9965ba071b82@alum.mit.edu>
Date: Tue, 1 Nov 2016 08:48:41 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <AM5PR0701MB2468AC6B5171EC51373DF563E5A10@AM5PR0701MB2468.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFIsWRmVeSWpSXmKPExsUixO6iqKvVLxFhcO6JkUXjoqesDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKmHV8I1PBG/mKly1H2BsYt0h0MXJySAiYSGx6tompi5GLQ0jg MqPE6hcP2CCc10wS3ye3MYNUCQt4SLT/PssKYosICEm8u/WXBaLoEaNE66YHYAk2AS2JOYf+ AyU4OHgF7CWOPOIHCbMIqEj8vf4frERUIE1i+7rdYDN5BQQlTs58AlbOKZAo0ffACSTMLGAr cWcuRAmzgLzE9rdzmCcw8s1C0jELSdksJGULGJlXMcol5pTm6uYmZuYUpybrFicn5uWlFuma 6OVmluilppRuYoQEGf8Oxq71MocYBTgYlXh4N3iKRwixJpYVV+YeYpTkYFIS5f0aBhTiS8pP qcxILM6ILyrNSS0+xCjBwawkwsvVKxEhxJuSWFmVWpQPk5LmYFES51Vfou4nJJCeWJKanZpa kFoEk5Xh4FCS4J0B0ihYlJqeWpGWmVOCkGbi4AQZzgM0PAtseHFBYm5xZjpE/hSjopQ471qQ hABIIqM0D64XlgReMYoDvSLMa9IHVMUDTCBw3a+ABjMBDTZPAhtckoiQkmpgdHzBczU554rF Y8Ylvrv39S6d/oo3pvehzuHdHVbf7vR4ty1+fL5cwtdvyt3KumOCNz7xtLV+ZmL1yvy3Y4Gb ixBzc/XfqvOf+c7lSOVE21doPM2X4go1YJxTOnfGF8eGM/eC2Sw1Z4eLPDt59n3w0v2/DyWm Mvlbi/le+17MxJ+2K+rPqc/blViKMxINtZiLihMBu2f/Wd0CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/Ho5RUkBqpsulq75-VrA9xeIX5Hw>
Subject: Re: [Ecrit] Ivo's review of draft-ietf-ecrit-ecall-15 - ISSUE 7
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Nov 2016 12:48:45 -0000

On 11/1/16 3:05 AM, Ivo Sedlacek wrote:
> Randall,
>
> so, what does "attach" mean if it does not meant Content-Disposition: attachment?


IMO "attach X (to a sip message) means to package X as a mime body part 
and include it in the body of the message. That in turn means either:
- make it the complete body of the message if there are no other
   parts, and if it can validly be done that way;

- include it as a subordinate body part within a multipart/mixed that
   it the outer part of the body of the message.

In any case, it may then be necessary to do something more to ensure 
that the recipient will know what is the intent of the body part. In 
some cases this may be simply tagging it with appropriate content-type 
and content-disposition. In other cases it may also require including 
some sort of reference to it via a header field in the message or 
somewhere in one of the other body parts.

That is a "general" answer. It needs to be defined in detail for each case.

	Thanks,
	Paul

> Kind regards
>
> Ivo
>
> -----Original Message-----
> From: Randall Gellens [mailto:rg+ietf@randy.pensive.org]
> Sent: Monday, October 31, 2016 4:52 PM
> To: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
> Subject: RE: [Ecrit] Ivo's review of draft-ietf-ecrit-ecall-15 - ISSUE 7
>
> At 7:04 AM +0000 10/31/16, Ivo Sedlacek wrote:
>
>>  Hello,
>>
>>
>>>  >   > >>  >  ISSUE 7
>>>  >   > >>  >
>>>  >   > >>  >  section 6 - "The IVS then attaches an updated MSD to a SIP
>>>  >   > >>  >     INFO request and sends it within the dialog." -
>>> what is meant by
>>>  >   > >>  > "attaching MSD to SIP INFO request"?
>>>  >   > >>
>>>  >   > >>  I think that's made abundantly clear in the multiple earlier
>>>  >   > >> instances in the  same section that say "as a MIME body part".
>>>  >   > >
>>>  >   > >  I do not really know what "attach body to SIP request"  means.
>>>  >   > > Likely, other readers will not know it either.
>>>  >   > >
>>>  >   > >  A reference to a section defining how to "attach body to
>>> SIP request"
>>>  >   > > would help.
>>>  >   >
>>>  >   > It's the same section, just a little bit before.
>>>  >
>>>  >  I assume you refer -19 text stating: "[RFC7852] establishes a
>>> general  > mechanism for attaching blocks of
>>>  >     data to a SIP emergency call."
>>>
>>>  If you look seven paragraphs above the paragraph in question (same
>>> section),  you'll see:
>>>
>>>      A PSAP or IVS transmits a metadata/control object (see Section 9) by
>>>      encoding it per the description in this document and attaching it to
>>>      a SIP message as a MIME body part per [RFC7852].
>>>
>>>  Then, three paragraphs later (four paragraphs above the paragraph in
>>>  question) it uses "attach" again:
>>>
>>>      An In-Vehicle System (IVS) initiating an NG-eCall attaches an MSD to
>>>      the initial INVITE and optionally attaches a metadata/control object
>>>      informing the PSAP of its capabilities.
>>>
>>>  The surrounding text makes it clear that these are "attached" as
>>> body parts  in the SIP message.
>>
>>  The above still talks about "attaching"/"attaches" without explaining
>> what it means.
>>
>>  It can be easily misunderstood to refer to inclusion of a body part
>> with Content-Disposition "attachment" in a SIP message.
>
> Not so easily misunderstood, since the text repeatedly makes it very clear which Content-Disposition value to use.
>
> --
> Randall Gellens
> Opinions are personal;    facts are suspect;    I speak for myself only
> -------------- Randomly selected tag: --------------- Perhaps the real reason why we have always been able to champion free speech in this country is that we know perfectly well that hardly anybody has got anything to say, and that no one will listen to anyone
> that has.       -- Editorial, Daily Mail [British Paper, date unknown]
>
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit
>