Re: [Last-Call] New Version Notification for draft-crocker-inreply-react-07.txt

Barry Leiba <barryleiba@computer.org> Wed, 03 March 2021 21:31 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64F4B3A1B45 for <last-call@ietfa.amsl.com>; Wed, 3 Mar 2021 13:31:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level:
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 If-tng18lV-6 for <last-call@ietfa.amsl.com>; Wed, 3 Mar 2021 13:31:06 -0800 (PST)
Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) (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 2CE973A1B23 for <last-call@ietf.org>; Wed, 3 Mar 2021 13:31:06 -0800 (PST)
Received: by mail-lj1-f179.google.com with SMTP id h4so30456763ljl.0 for <last-call@ietf.org>; Wed, 03 Mar 2021 13:31:06 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=apswmEG/iEjUBv20yiH2gSLvUzuJVa8vLHnhxT0dKDA=; b=k7a41kGsDlyLETHYlWUip+yLs2myIxIchF/OjbNWnGpx6+ZsdSBNo4svZVjvnvKu2+ xgrwCl/s62cLayxMsA/rJjAkmpuydKbaIheq5TlMjBBAycN/NSYvxsC67a6cCIipLPqR Cub8xC5+/paO5vOAPXv0xXqyS2a4t3ebsNUd3qMGWvCLnmug08huPOGKKJqssp3Fzknh A4LKKvWL/94bD44SPvTxYS1uGcoW/NzUNA+toFOlXbU8B5rEbHw/Tdd2bgga4bUewMrq AloPrRcHQMJ4ln8I66crbWpHfol4AFThGK51Rxr6zAmPQkfA2DogRysWucBAN0jEK5Z9 lHOA==
X-Gm-Message-State: AOAM530ghAP3wTok7ID8JdGWHJbhqxa7ymLG+AQvDqEXn5JgLS/9MZnc SKfqaB9RKnqjgmzeqJ+m/ZHsMzi6PjFCho755aU=
X-Google-Smtp-Source: ABdhPJw1w+AbEySDIRfp4ydHEbBovG8AMM7dqWCHayBkQbH2J08wfGhEZsGsXthuI9p/Smd95js8oF6CSND0fNc4UdU=
X-Received: by 2002:a2e:864a:: with SMTP id i10mr456230ljj.467.1614807064294; Wed, 03 Mar 2021 13:31:04 -0800 (PST)
MIME-Version: 1.0
References: <20210226225413.EC3EA6EF3ACB@ary.qy> <0439c097-365a-4341-8f67-758ef5ba4556@beta.fastmail.com> <0CF8E76113EAF87238A9DFEE@LM73.int.jck.com> <2e2d8c51-687d-9dd9-ab5f-0cc451926e3b@bbiw.net> <CAC4RtVCJvUhgWRRGRAXy-PYrcM6SVEB0U37hr=cGcUdo7rinCA@mail.gmail.com> <fc47c6b0-e7f3-0ce3-deae-3cad1778420f@bbiw.net> <CAC4RtVDF4ZV7D4oq51xhMoZ68MD3epEXF44oVeBoCNvWNU8S8Q@mail.gmail.com> <FDF2E5C25ACD8A6C4343B326@LM73.int.jck.com> <CALaySJKmsF+Zr+7YEq3zS+F4=Q-Q4oA6dR2Z4bPBvNuiuxF34Q@mail.gmail.com> <12ebb344-72e9-a087-9d7c-ab3b52d2884c@bbiw.net> <F69D92EAF545445EC1ACF337@LM73.int.jck.com>
In-Reply-To: <F69D92EAF545445EC1ACF337@LM73.int.jck.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 03 Mar 2021 16:30:52 -0500
Message-ID: <CALaySJJtbnqyLc487i2ZmCUqENYRqBhfGzm6uUpLQz5ggg=LsQ@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: Dave Crocker <dcrocker@bbiw.net>, last-call@ietf.org
Content-Type: multipart/alternative; boundary="00000000000072b6d105bca891d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/QLW6VPH2VbAsuEk2RFRJ8e4QjKE>
Subject: Re: [Last-Call] New Version Notification for draft-crocker-inreply-react-07.txt
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2021 21:31:09 -0000

Just on the point at the end:

Discussion of the text of this document belongs on the last-call list.
Discussion, later, of how the experiment went and whether we should move to
Proposed Standard with a revised version doesn’t, and I think putting that
back on the rfc822 list is the right approach.  If that leads to a PS
version, we’ll either put it into a working group or point both the
community and the IESG to that list to review/participate i the discussion.

Barry

On Wed, Mar 3, 2021 at 4:23 PM John C Klensin <john-ietf@jck.com> wrote:

> --On Wednesday, 03 March, 2021 10:28 -0800 Dave Crocker
> <dcrocker@bbiw.net> wrote:
>
> >...
> > Having reflected a bit about this, this morning, I now think
> > it reasonable to add a bit more, but not really of the sort
> > that has been discussed.
>
> > Here's what I propose:
>
> >>   7. Experimental Goals
> >>
> >> The basic, email-specific mechanics for this capability are
> >> well-established and well-understood. Points of concern,
> >> therefore, are:
> >>
> >>   * Technical issues in using emojis within a message body
> >>   part
> >>   * Market interest
> >>   * Usability
>
> This is a question, not a request for change, but isn't the
> questions of whether a new Content-disposition value will be
> accepted and whether implementations will handle an unrecognized
> value in a a reasonable way an inherent part of this experiment
> and hence a point of concern?
>
> >> So the questions to answer for this Experimental
> >> specification are:
> >>
> >>   * Is there demonstrated interest by MUA developers?
> >>   * If MUA developers add this capability, is it used by
> >>      authors?
> >>   * Does the presence of the Reaction capability
> >>      create any operational problems for recipients?
> >>   * Does the presence of the Reaction capability demonstrate
> >>     additional security issues?
> >>   * What specific changes to the specification are needed?
> >>   * What other comments will aid in use of this mechanism?
>
> That formulation works for me.
>
> >> Please send comments to ietf-822@ietf.org.
>
> Up to Barry but, if this discussion is considered part of a Last
> Call and IESG review in progress, should it not remain on this
> list so that, among other things, the IESG sees it?
>
> thanks,
>    john
>
>
>
>
>
>