Re: [apps-discuss] Kathleen Moriarty's Discuss on draft-ietf-appsawg-json-merge-patch-06: (with DISCUSS)

James M Snell <jasnell@gmail.com> Thu, 21 August 2014 02:00 UTC

Return-Path: <jasnell@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A4941A0061; Wed, 20 Aug 2014 19:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 Bkptfhx3QFbb; Wed, 20 Aug 2014 19:00:55 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3642D1A06D8; Wed, 20 Aug 2014 19:00:55 -0700 (PDT)
Received: by mail-ie0-f174.google.com with SMTP id rp18so3793976iec.5 for <multiple recipients>; Wed, 20 Aug 2014 19:00:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gUIg5bzrMG6m9shXkEmWypf9Z1pWwLN7qnvndSJ4S3s=; b=EDUXcpflq8Nyz+iu4qtvAmriIQXPo/2Fu+tmVH0FHBavzmyZQRBO4YTMBi++qkgktG vaM1pnpPruleMTb4a8Ezf/r1Q17HCUdd88rJvsuhchwBqIUUoNnRAqCn2EmtOcOYECqr O6XUq2sjV6P/Qq08dwe3tJskJqQp4o+djG/TCtR5SQ1ZDqzCq7GqOtVB651kBXQQy0vt XFoaWrby+mQTtr2cyztYDosaclcFJAk1R4PHPMALNVxAeeDw5dI9lRozg5Zy4gJTK+9Z hIQQ8leHWcG+rZZogtk7g+TIMKsO/QDWXG8lbnLtRdwbB1JDBdR4y1w56by3HsaExDhw RcKQ==
MIME-Version: 1.0
X-Received: by 10.50.55.68 with SMTP id q4mr16656178igp.44.1408586454578; Wed, 20 Aug 2014 19:00:54 -0700 (PDT)
Received: by 10.107.131.134 with HTTP; Wed, 20 Aug 2014 19:00:53 -0700 (PDT)
Received: by 10.107.131.134 with HTTP; Wed, 20 Aug 2014 19:00:53 -0700 (PDT)
In-Reply-To: <4F7A88C1-52AA-4F5A-8D56-722911C9C187@vpnc.org>
References: <20140818205813.25342.9189.idtracker@ietfa.amsl.com> <5E1CE9A7-7425-4C77-9871-3B71A1CF4CC9@vpnc.org> <CAHbuEH6gGqF4s=ttFxmyGEz8veOn87nDfjwLOh-ZmzZoPPjfdA@mail.gmail.com> <4F7A88C1-52AA-4F5A-8D56-722911C9C187@vpnc.org>
Date: Wed, 20 Aug 2014 19:00:53 -0700
Message-ID: <CABP7Rbe2a0myYSef=7qLhVr6BevTNM7HeESGdVeoUXp5dERRKg@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary="047d7b10ce9142bdec05011a1799"
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/ukHDhfzgnSuB1XnQLa1eJ5ykM9E
Cc: draft-ietf-appsawg-json-merge-patch@tools.ietf.org, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, appsawg-chairs@tools.ietf.org, Apps Discuss <apps-discuss@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [apps-discuss] Kathleen Moriarty's Discuss on draft-ietf-appsawg-json-merge-patch-06: (with DISCUSS)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Aug 2014 02:00:57 -0000

On Aug 20, 2014 6:50 PM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:
>
[Snip]
>
> I'm not sure I can add those sentences in a useful fashion. With current
delivery mechanisms (HTTP being the most common), MIME objects don't come
with hashes for checking. So giving that advice would cause developers to
look for something that they won't have, namely hashes of the MIME object
they just got.
>

+1

> I do hope you're not asking us to change the format to include an
internal hash. That would require inventing JSON canonicalization (which
the JOSE WG has flailed miserably on) and say "canonicalize, pick a hash
function, hash, and add that to the patch object". The recipient would need
to pull the hash out before processing the patch, canonicalize the result,
and check the hash. This is conceptually possible but it seems onerous, and
has not been done in any of the earlier patch formats that have been
standardized in the IETF.
>

+1... Adding an internal hash would not work with this mechanism without
taking a major step backwards. I do not see the value.

- James

> --Paul Hoffman
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss