Re: [sipcore] AD Evaluation of draft-ietf-sipcore-content-id-05 - PULL REQUEST
"A. Jean Mahoney" <mahoney@nostrum.com> Fri, 26 May 2017 19:28 UTC
Return-Path: <mahoney@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ADBA129418; Fri, 26 May 2017 12:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 brP_3LptwE48; Fri, 26 May 2017 12:28:36 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D02D4126BFD; Fri, 26 May 2017 12:28:36 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v4QJSVJ2099939 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 26 May 2017 14:28:32 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be mutabilis-2.local
To: Ben Campbell <ben@nostrum.com>, Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "draft-ietf-sipcore-content-id.all@ietf.org" <draft-ietf-sipcore-content-id.all@ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>
References: <D54DF3B2.1D309%christer.holmberg@ericsson.com> <528630A5-051A-4116-9D5C-79755DF347B3@nostrum.com>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <645392ed-901f-e6c7-6b19-03ef31fb9865@nostrum.com>
Date: Fri, 26 May 2017 14:28:31 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <528630A5-051A-4116-9D5C-79755DF347B3@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/76SuBOalYIw5NHfI7qwfAN4_u5E>
Subject: Re: [sipcore] AD Evaluation of draft-ietf-sipcore-content-id-05 - PULL REQUEST
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2017 19:28:38 -0000
Hi Ben, On 5/26/17 11:27 AM, Ben Campbell wrote: > >> On May 26, 2017, at 6:58 AM, Christer Holmberg >> <christer.holmberg@ericsson.com> wrote: >> >> Hi Ben, >> >> I have created a pull request, based on your comments: >> >> https://github.com/cdh4u/draft-content-id/pull/6 >> >> > > The diff looks fine. We probably want to make sure the WG shares the > opinion that the Content-ID will never be referenced from outside the > SIP message. > > Jean, do you have thoughts on that from the shepherd perspective? > The WG did discuss whether the Content-ID could be used outside of the message. The takeaway was, that since a SIP header has non-MIME fields, the Content-ID can't really refer to the entire message, and thus would not be useful outside the message. Anyone have any input on the changes to the draft? Jean PS - nit: Campbell is misspelled in the "Change Log". > >> However, I wasnąt sure how to address the following comment: >> >> "1.2 and 1.3: A sentence or two that more strongly contrasts "body >> part" vs "message-body" would be helpful. I think that some people >> will think of a message-body as still a body-part.˛ >> >> I think section 1.1 describes the difference between a message-body >> and a body-part. I donąt think we should copy/paste that in >> sections 1.2 and 1.3. Or, did I misunderstand you comment? > > On reflection, I think this might be fine like it is. I know that > some people casually refer to the entire body as still a “part”, but > that doesn’t seem to be reflected in the MIME RFCs. Let’s see if > anyone comments in LC. > >> >> Regards, >> >> Christer >> >> >
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Christer Holmberg
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Ben Campbell
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Christer Holmberg
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… A. Jean Mahoney
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Ben Campbell
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Christer Holmberg
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Ben Campbell
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Paul Kyzivat
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Christer Holmberg
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Christer Holmberg
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Ben Campbell
- Re: [sipcore] AD Evaluation of draft-ietf-sipcore… Christer Holmberg