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

Ivo Sedlacek <ivo.sedlacek@ericsson.com> Tue, 01 November 2016 14:01 UTC

Return-Path: <ivo.sedlacek@ericsson.com>
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 AE995129527 for <ecrit@ietfa.amsl.com>; Tue, 1 Nov 2016 07:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
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 OBwekRs6I3bX for <ecrit@ietfa.amsl.com>; Tue, 1 Nov 2016 07:01:38 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C16C712953A for <ecrit@ietf.org>; Tue, 1 Nov 2016 07:01:37 -0700 (PDT)
X-AuditID: c1b4fb25-953ff70000001e3e-4c-5818a03f3c6d
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by (Symantec Mail Security) with SMTP id 71.0D.07742.F30A8185; Tue, 1 Nov 2016 15:01:36 +0100 (CET)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.57) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 1 Nov 2016 15:01:35 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=DbBmuryi/vP8i3D9Mztm4jydVNGSF2M4QQmIMy46WfI=; b=XCikyuAspwCFymhpjKXMOw19nBdvqAn7aq4l4oy01gHibuzKxx4Vlw56yiqi+G1aUdXxptYAOC8XCMoUoVzT3Ek54yth+bHxMwXzhCeLCqZhVs4xjVG2zAapEU/oIfXVt+Ght3GNJe7Yhs2cB+YxUskUg3Rp/OIrBqJW26MhquE=
Received: from AM5PR0701MB2468.eurprd07.prod.outlook.com (10.169.153.136) by AM5PR0701MB2467.eurprd07.prod.outlook.com (10.169.153.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.707.1; Tue, 1 Nov 2016 14:01:34 +0000
Received: from AM5PR0701MB2468.eurprd07.prod.outlook.com ([10.169.153.136]) by AM5PR0701MB2468.eurprd07.prod.outlook.com ([10.169.153.136]) with mapi id 15.01.0707.004; Tue, 1 Nov 2016 14:01:33 +0000
From: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "ecrit@ietf.org" <ecrit@ietf.org>
Thread-Topic: [Ecrit] Ivo's review of draft-ietf-ecrit-ecall-15 - ISSUE 7
Thread-Index: AQHSM47BSesWv686Q3CGsB9ygk2d86DDtQ/wgABgXoCAAA4ooA==
Date: Tue, 01 Nov 2016 14:01:33 +0000
Message-ID: <AM5PR0701MB2468C337DF3F94003FB3ABCEE5A10@AM5PR0701MB2468.eurprd07.prod.outlook.com>
References: <AM5PR0701MB2468010828183D6956A82E66E5AE0@AM5PR0701MB2468.eurprd07.pro d.outlook.com> <p06240600d43d18f64b41@[99.111.97.136]> <AM5PR0701MB2468AC6B5171EC51373DF563E5A10@AM5PR0701MB2468.eurprd07.prod.outlook.com> <181874aa-8dc1-8cd5-3ced-9965ba071b82@alum.mit.edu>
In-Reply-To: <181874aa-8dc1-8cd5-3ced-9965ba071b82@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ivo.sedlacek@ericsson.com;
x-originating-ip: [193.179.210.162]
x-ms-office365-filtering-correlation-id: 1d2bb868-ef4f-474d-5c09-08d4025f96a2
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB2467; 7:KwLFBanLNhjVsgKzyGxnLD4T2nJDjJ0Tcrq5QU4071mW0NEIrPZjtb8YxCWFfsMNogyRu2soX5dH3Gzov1suOch7RaKtb1lFWrZQm72reCBNWs4YBJywGYdk9ftfCbOpe0RFCgtK/KP8DTr9rbzkAngxVljEw8pQtqf4aEj9yYhP1rmdqyxqsGreUAlsjC4jc06mcT8iR0mRIWOT7+K+lbKtKL7x2XX+1NfmcJIZvC681+ukrCwR+0QWqJTwf8z8m8fNJsYcck8sEQs+L5RxmbqCjqhffilcX4YgE8HI6+jyJXwS8KTFhFdAE/bnR582F03vkeeG6L/oeTuMxCMiE+MSK/qGbZTNnYj2VUKyfHY=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM5PR0701MB2467;
x-microsoft-antispam-prvs: <AM5PR0701MB246709349ADE73A003076FE7E5A10@AM5PR0701MB2467.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:AM5PR0701MB2467; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB2467;
x-forefront-prvs: 01136D2D90
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(24454002)(51444003)(189002)(377454003)(5403001)(13464003)(199003)(586003)(6116002)(3846002)(2906002)(5001770100001)(76176999)(54356999)(97736004)(50986999)(101416001)(107886002)(10400500002)(66066001)(189998001)(33656002)(3280700002)(3660700001)(9686002)(102836003)(8936002)(2501003)(5890100001)(68736007)(93886004)(230783001)(106116001)(87936001)(81166006)(2900100001)(76576001)(106356001)(5002640100001)(105586002)(305945005)(7736002)(7846002)(74316002)(92566002)(77096005)(15975445007)(5660300001)(8676002)(81156014)(86362001)(7696004)(122556002)(19580395003)(2950100002)(2171001)(19580405001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM5PR0701MB2467; H:AM5PR0701MB2468.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Nov 2016 14:01:33.5581 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2467
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SfyzUcRjH9/n+8mV916eLPH78ddj6gX6wpoapLV0rG7bmJpYr3yHncF8p +kctXUhhU46mCxclpovJsOWi6AeFley4mpNSTdEPUuR8tfXf63ne770/z/Psw5KSc7Qzm6BK 49UqhVLK2FFaefMOryAdyLcUPLfxO10xTvvVNNyngwjZn6kvhKyqao4IJSLt/GN5ZUI6r94c GGMX/908w6RMup/UahqYLNTkmotsWcC+0JNfR+YiO1aC6xHkGK7QYvEIgcliXC4onE9C2flu G1G5SkBR5SgjFk8QzGY3IGsYg72hsLGTtrI93g+/538wVl6LZdBt0FBifx+MzBURIu+GF3da lj0Udgfd6PBSn2U5HAPFpf5ifgkB2kELafXY4iB4Nla5zAivg5+Pby/nkNgRhi3XCHEhDFVt faTIDvBhbIEW/VGwmDdDi303aCyaWvGEQI1+gLI+BriChJamAkoUZDA0278SmgxltYWkdTjA O6H8abTob0PQ/qtkJcgV8qfFSwLWM9BW225jFSSYh+q6bCRewhlGBnNW2BXem9rpArSh9L8l RPYEXes0I/ImuHH9I2llDq+BHq2F0iHqFnIQeOFIUtw2H29enXBUEJJV3io+zYCWfkdH47zH PTTwaZcRYRZJV3EpUY5yCa1IFzKSjAhYUmrPjZWDXMLFKjIyeXXyYfVxJS8YkQtLSR257TfN ERIcp0jjE3k+hVf/UwnW1jkLaWK/XXgZZ3htCndy7EjMlEePazlfNqSr4FKEzZ4BzaGuxK9h 5rS+/lCWYybqVb7Bp6pOpD48cznMaaL1oskjz3zgTfVbz9QHPtkNwetThpr1kaqWWL73WPGr YBeyM9U0KeFqVt/9HOA2DXtH9F69ZxfKNVLlYvi7wDAGNwYclFJCvGLrRlItKP4CxEo4cxkD AAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/MUpjhcb_ZI830n_1KIcUIuBneu0>
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 14:01:41 -0000

Hello Paul,

Your interpretation of "attach X to SIP message" makes sense to me.

However, I do not see a statement "attach X to SIP message means ...." in the draft.

Kind regards

Ivo

-----Original Message-----
From: Ecrit [mailto:ecrit-bounces@ietf.org] On Behalf Of Paul Kyzivat
Sent: Tuesday, November 01, 2016 1:49 PM
To: ecrit@ietf.org
Subject: Re: [Ecrit] Ivo's review of draft-ietf-ecrit-ecall-15 - ISSUE 7

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
>

_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www.ietf.org/mailman/listinfo/ecrit