[sipcore] AD Evaluation of draft-ietf-sipcore-content-id-05

Ben Campbell <ben@nostrum.com> Tue, 16 May 2017 21:13 UTC

Return-Path: <ben@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 1AAF112F27B; Tue, 16 May 2017 14:13:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.821
X-Spam-Level:
X-Spam-Status: No, score=0.821 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 XMC3JquOFyeO; Tue, 16 May 2017 14:13:43 -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 2AE3412ACAF; Tue, 16 May 2017 14:09:06 -0700 (PDT)
Received: from [10.0.2.253] (ip-7-232-239-173.texas.us.northamericancoax.com [173.239.232.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v4GL94x6065665 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 16 May 2017 16:09:05 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host ip-7-232-239-173.texas.us.northamericancoax.com [173.239.232.7] claimed to be [10.0.2.253]
From: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-B821791D-CD78-49D6-9BD9-6F98B231AF1C"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Tue, 16 May 2017 17:09:04 -0400
Message-Id: <B9456A83-63CA-492C-89AB-622A024681A5@nostrum.com>
To: draft-ietf-sipcore-content-id.all@ietf.org, sipcore@ietf.org
X-Mailer: iPad Mail (14E304)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/AZYCO0LiN2z_z36zIIUAuqf_BYI>
Subject: [sipcore] AD Evaluation of draft-ietf-sipcore-content-id-05
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: Tue, 16 May 2017 21:13:46 -0000

Hi,

This is my AD evaluation of draft-ietf-sipcore-content-id-05. I have some points I would like discuss before going to IETF last call.

Note: I plan to request an Art-Art review on this draft to focus on the MIME usage aspects.

Thanks!

Ben.

Discussion Points:

- I have some difficulty seeing the difference between "the body and related metadata" and "the SIP message". I realize you have the more MIME-specific header fields in mind when you say "metadata". But any SIP header field could be considered metadata.

The main point of that question is, as used in MIME, Content-Id is intended to label a body part. Message-Id is used to label the whole message. Aren't we talking about the whole message here?

- Is there an expectation for the SIP Content-ID header field value to be referenced from outside the SIP message? If so, what are the uniqueness expectations? Note that for MIME, Content-ID is expected to be globally unique. Is that the case here?

If the Content-ID is _not_ expected to be referenced from outside of the SIP message that contains it, then we have a sort of degenerate case where it always identifies _this_ message regardless of the value. Does that value ever need to change? Does that suggest any guidance on how to construct values?

Specific comments:

1.4 and children: These examples seem like fairly weak motivation, since I assume in both cases one could still have just put a single body-part inside a multipart envelope. That seems more an "inconvenience" than a "problem". Are there any known use-cases where that would not be possible? (This is certainly not a show stopper; we are allowed to solve inconveniences. But if there are any stronger motivations that could be documented, they might save questions down the road.)

3.2, 2nd note: How has the msg-Id been simplified, and why?

3.4 and children: An example or two would be extremely helpful.


Editorial:

1.1, 3rd paragraph: Citation to RFC5621 is not a link in the PDF version.

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.

1.5, Note: Seems like the note belongs in the problem statement more than the solution.