Re: [Ecrit] Content-ID: Way forward without SIPCORE impact
Christer Holmberg <christer.holmberg@ericsson.com> Sun, 09 October 2016 08:55 UTC
Return-Path: <christer.holmberg@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 85AB212943D for <ecrit@ietfa.amsl.com>; Sun, 9 Oct 2016 01:55:29 -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, 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
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 9ZuL5F7scECS for <ecrit@ietfa.amsl.com>; Sun, 9 Oct 2016 01:55:28 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 E9411129426 for <ecrit@ietf.org>; Sun, 9 Oct 2016 01:55:27 -0700 (PDT)
X-AuditID: c1b4fb3a-aa3ff7000000099a-3d-57fa05fdfbea
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by (Symantec Mail Security) with SMTP id 57.16.02458.DF50AF75; Sun, 9 Oct 2016 10:55:26 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0319.002; Sun, 9 Oct 2016 10:55:25 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Randall Gellens <rg+ietf@randy.pensive.org>, "ecrit@ietf.org" <ecrit@ietf.org>
Thread-Topic: [Ecrit] Content-ID: Way forward without SIPCORE impact
Thread-Index: AQHSH9FdW92vWNIey0OuUNcxPMNfjaCdGW0AgAK68TA=
Date: Sun, 09 Oct 2016 08:55:24 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD3C7DF@ESESSMB209.ericsson.se>
References: <D41C26AC.10977%christer.holmberg@ericsson.com> <p06240601d41d85bf71e8@[99.111.97.136]>
In-Reply-To: <p06240601d41d85bf71e8@[99.111.97.136]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHLMWRmVeSWpSXmKPExsUyM2K7k+4/1l/hBrMaJS0aFz1ltfj+vIvR gcljyZKfTB5b7zxmCWCK4rJJSc3JLEst0rdL4Mq40D6ZsaCVs+LnEs0GxpnsXYycHBICJhK7 nv5g6WLk4hASWM8osfvRdTYIZzGjxKrOhcxdjBwcbAIWEt3/tEFMEYEQiZb3XCC9wgLOEh9X 7mEGsUUEXCSe9HczQthWEhOu3mQFsVkEVCQ6tq9mArF5BXwl+lf1gcWFBFIllrXvZwGxOYFu aLq7EyzOKCAm8f3UGrB6ZgFxiVtP5jNB3CkgsWTPeWYIW1Ti5eN/rBC2ksSi25+h6nUkFuz+ xAZha0ssW/iaGWKvoMTJmU9YJjCKzEIydhaSlllIWmYhaVnAyLKKUbQ4tbg4N93ISC+1KDO5 uDg/Ty8vtWQTIzAWDm75bbWD8eBzx0OMAhyMSjy8D+78DBdiTSwrrsw9xCjBwawkwvuN6Ve4 EG9KYmVValF+fFFpTmrxIUZpDhYlcV6zlffDhQTSE0tSs1NTC1KLYLJMHJxSDYxBEW8T3xo2 1uy3yGd78kfFol9r/t/myETDOL7257cbtGR0VU9JCCmG7m5T/Prn54ZPyiYlPz5eu6Xw//39 7T9vdWqnZfz/9uGjlKoex0/5T6eq/RZcCOCQOPKm85iKgITv/1Zb64BF3ryPb0ZdfMb9bakH A88cudcLmtZMsnvEot9mHKYvdUiJpTgj0VCLuag4EQBECxkVgQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/W5NlheAYbOOYyuSDxPUJAiQzbI8>
Subject: Re: [Ecrit] Content-ID: Way forward without SIPCORE impact
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: Sun, 09 Oct 2016 08:55:29 -0000
Hi, >> One way to solve the Content-ID issue would be to ALWAYS use a >> multipart MIME, even if we only carry one body part. See example in >> section 12.2.2.3 of RFC 6086. >> >> Another advantage would be that we would always the same >> Content-Disposition header field value for the MSD/control body parts. >> Currently the value is dependent on whether there are other body parts >> in the message or not, which is a little strange. So, the >> multipart/MIME would have C-D:info-package and the MSD/control body >> part would have C-D:by-reference. > > In view of the slow progress of your draft, I think the proposal to > always use a multipart is the best option. As you say, it simplifies > the implementation because the C-D will always be "By-Reference". > > (As I recall, the same idea was floated some time back, during the > discussion about INFO.) So, unless someone objects, I suggest we move forward with such approach. Also, I'd like to see the a new version of the draft BEFORE the end of the WGLC, so that I can perform a WGLC review based on that. Regards, Christer
- [Ecrit] Content-ID: Way forward without SIPCORE i… Christer Holmberg
- Re: [Ecrit] Content-ID: Way forward without SIPCO… Paul Kyzivat
- Re: [Ecrit] Content-ID: Way forward without SIPCO… Christer Holmberg
- Re: [Ecrit] Content-ID: Way forward without SIPCO… Randall Gellens
- Re: [Ecrit] Content-ID: Way forward without SIPCO… Christer Holmberg
- Re: [Ecrit] Content-ID: Way forward without SIPCO… Randall Gellens