Re: [Webpush] Breaking Changes (was Re: Eric Rescorla's Discuss on draft-ietf-webpush-vapid-03: (with DISCUSS and COMMENT))

Martin Thomson <martin.thomson@gmail.com> Wed, 16 August 2017 06:22 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB3D2126B71; Tue, 15 Aug 2017 23:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 MavJEnbNrVtV; Tue, 15 Aug 2017 23:22:28 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 EAFE8124217; Tue, 15 Aug 2017 23:22:27 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id c74so10104174iod.4; Tue, 15 Aug 2017 23:22:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pZ1C8BdcW1+Xc4nLaz2uV9gOu9M5a8eULvS4auyyFDU=; b=XWoMZDIqi4vP8kVaI/tkbjkx97N34IGRh2apdX1mH0tCm2ZjDxPnyfZjZ9Ahyxd5iY K0A3FsbaNbg32IoxKoknHH10I/yIjks1YoO67R+M7tTTIHEehrAmKiKaLC/DBHXhq39i gTKn5rl91jTvMYe6dGUD9ACUTVO9qfABTWN+T/oxJ1Y+xGA6SiCg79ZiY+1QgOCEEEGc LLVWFBxh0aELSD5zdEyrdlV/pqmwverVcJRcslr4y7txOlin5UAXZSzYessits9RLxNm mpRbzTm4n2dSZYtK6EPt8ORPQ8k0VGM5rSJ/KGBG28o6Zd3ICkG1Bdb9ZTSQw2BR+WBj gIsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pZ1C8BdcW1+Xc4nLaz2uV9gOu9M5a8eULvS4auyyFDU=; b=lq8IABUOpYq9jCIO+IgWZKWSdm1du5e4XP1ISs48d1Mpf+pekHLhe12AZ2oUkeNfah ECbSu43I4DYHpF83jc2M+ysAqWBicOxttF+2bBVn0qqZkaj5+YgK9AYG9YN5hfC+Qha+ eIFC2G7quXIvPukd5bsPpUhtEhOrcusZxU+pdAGbMnGBgm6p9G/n1bLuwW3B6uXng1q0 Uzu5QnBSou625k5aSRkRiwNGGP+p6QceWX/m3Nw1eyTXsiHOpMQ03iPmzPInMQutO/y+ WqiW17aDtzWFQ/wVJKE3MZxLslrghopq1OPLXc6Kc6noolFryXD3i29I4fTTx1N/DYI7 Ok4w==
X-Gm-Message-State: AHYfb5gnQ/cH0d6QY68Pl8o+Ym1bdeypC1odfiyxhk6Gj4AfbnWyTPcD Z+Lvi922BKBbtG5n4roCRRDx6efslQ==
X-Received: by 10.107.46.155 with SMTP id u27mr489859iou.107.1502864547227; Tue, 15 Aug 2017 23:22:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.164.42 with HTTP; Tue, 15 Aug 2017 23:22:26 -0700 (PDT)
In-Reply-To: <972ccc4e-da47-cb56-addc-ba7b02b94e67@nostrum.com>
References: <150284054989.12518.11340069078773708886.idtracker@ietfa.amsl.com> <CABkgnnXwUpp4A=V6gNXoK+Q6LatCHFoB59+xVd0RxQ96Y5gfaQ@mail.gmail.com> <CABcZeBP1Ej2Dd7rPTn6Sq3uVLA1gPHBSRSQR2Fam_mxJqcQgig@mail.gmail.com> <4125C183-E369-47EA-999A-0080BDF01B4A@nostrum.com> <716e5820-e57f-b7c9-b3b4-3cf387409575@nostrum.com> <CABkgnnWG8dDMAZe0MdAf0D7WE1jzA+yPJEAMsH9siL56cNbz1Q@mail.gmail.com> <972ccc4e-da47-cb56-addc-ba7b02b94e67@nostrum.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 16 Aug 2017 16:22:26 +1000
Message-ID: <CABkgnnWqCct9J+SrC+_=Pyf-V0WsCyvStBmxZh3F-OV5QXwDzA@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>, draft-ietf-webpush-vapid <draft-ietf-webpush-vapid@ietf.org>, Phil Sorber <sorber@apache.org>, The IESG <iesg@ietf.org>, webpush-chairs@ietf.org, "webpush@ietf.org" <webpush@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/yCQENWI-bQnnGHJc3iIWRJ6o0Sk>
Subject: Re: [Webpush] Breaking Changes (was Re: Eric Rescorla's Discuss on draft-ietf-webpush-vapid-03: (with DISCUSS and COMMENT))
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of potential IETF work on a web push protocol <webpush.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webpush>, <mailto:webpush-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webpush/>
List-Post: <mailto:webpush@ietf.org>
List-Help: <mailto:webpush-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webpush>, <mailto:webpush-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Aug 2017 06:22:30 -0000

On 16 August 2017 at 15:41, Adam Roach <adam@nostrum.com>; wrote:
> On 8/16/17 12:09 AM, Martin Thomson wrote:
>>
>> p.s., It's been a while since I've been on the receiving end of the
>> old "your code doesn't matter, you took a risk implementing an I-D"
>> argument.  As an argument it kinda stinks.  I'm embarrassed to confess
>> that I've used it in the past, despite reminding myself not to.  I'd
>> be interested in learning whether the IESG has an opinion on the
>> subject.  A statement of policy might be valuable.
>
> Given that the alternative is effectively forbidding breaking changes after
> WG adoption -- which is clearly untenable -- I'm not sure what kind of
> policy you're looking for here. Can you clarify?

(Hmm, I got this message twice...)

The usual exchange goes a: "I have code", b: "you implemented an I-D,
that's your problem".

Some guidance about how to manage this situation would be appreciated.

I'm not looking for a prohibition on changes at any point in the
process.  That's ludicrous, after all, people do understand what it
means to implement an I-D.  But statements like "there is code" or
"there is deployed code" are valid and useful input to a discussion
and not just as proof that a given thing is possible.  That means
potentially affecting the outcome of a decision.

In this particular case, the arguments presented weren't problematic,
because the real arguments was actually "well, this change doesn't
seem that bad to me".  But it's not the first time someone has opened
with that argument and it annoyed me enough to comment.