Re: [TOOLS-DEVELOPMENT] Draft of inline-errata SoW

Eric Rescorla <> Thu, 31 January 2019 19:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ABAB8130E9A for <>; Thu, 31 Jan 2019 11:29:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PkQyIlWfNwEx for <>; Thu, 31 Jan 2019 11:29:43 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 585FB130E9C for <>; Thu, 31 Jan 2019 11:29:43 -0800 (PST)
Received: by with SMTP id c16so3210400lfj.8 for <>; Thu, 31 Jan 2019 11:29:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UEtpjRBzLe0gAvh8/ryyFLkr/FNQqj3f4gEFOILERvw=; b=FRjJ5It9HgXRZIhmFDSS9t+y+LxkN5Cs0OWngEGnYqnOSjDSDOrI0Png5D9ENDkgN/ IHq7RCPDDRsfLqofvBk7n8Kz9z6LqgLNidL+2AwVlIkn+0DaRo4O4jRM7pYCysx2JRtP dGrBykjzmV+zT4I6kUaTL5viy4csyTfzA6R4Ip55hUAsxvCkOa2MuFey6xJ0oX85FGCq DbAi4IxK8Kz7aWSeCYjt4Dg/pwUpQ9FUKv/08K95JSgCXqkZo9Sy8o6RoND9Vv7EAHkI N0R5o4rVKRB4UDs78L8eVSpicUx6rcwRODcrqiyrgBuKCAEXiCFq5gf/eofQMDgpt+Zy Um+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UEtpjRBzLe0gAvh8/ryyFLkr/FNQqj3f4gEFOILERvw=; b=TycVjTOgqnVMuAFaovEkgw8qCeDKbmg3RZQZbtkHCGpinT2QXXk8ntH5hyuhyB/TaL UBwnYc2dC0GVyG9WEGngoOLWt1iTrA+Q6GBxUgRL442eK9IhR8PaNlTwIgQ3mv0E94Sp etlVVfC0XBJsninGJt90MaUxE9ZpzRGQnRs6SmpV9X4JeVk6K+gZPgtAz6lGHD3TjO9m HsXiLOYaLyh2WJgndWjD33/3ybXvlWoL35wUa5wCxNh0tXbT0lA855evoGpHFGoPnW5g u8AR/RlfgD8n9/duOsmXCYEpy3QnZfQIzQ4c9KSKXAFbSJFxvzoxBWFz3t7rs1oi899J E1cQ==
X-Gm-Message-State: AJcUukdYye6p9TwlUbaCDpBYZqH+D+rMCAgrbj0u5MijeyHdOE/IdFVV CTCiVY0OYKYxkFFR4pULThmJj9pe77O6zgPl52mtJJQV
X-Google-Smtp-Source: ALg8bN5/iyXLG9uKMw6X7FvwtJFymaeitqqYyGSDTjLJACufW2hRyw/9WXfeQcyL5A/1JsLUkCQ34gJGDFCTBdwzaOE=
X-Received: by 2002:a19:9904:: with SMTP id b4mr28446743lfe.95.1548962981085; Thu, 31 Jan 2019 11:29:41 -0800 (PST)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: Eric Rescorla <>
Date: Thu, 31 Jan 2019 11:29:03 -0800
Message-ID: <>
To: Heather Flanagan <>
Cc: Sandy Ginoza <>, IETF Tools Development <>
Content-Type: multipart/alternative; boundary="000000000000421bcf0580c60ce9"
Archived-At: <>
Subject: Re: [TOOLS-DEVELOPMENT] Draft of inline-errata SoW
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 31 Jan 2019 19:29:47 -0000

Hmm... I'm not sure that that's quite the desirable outcome.

Let's take the example of a clear (and minor) technical error: in the body
of the text, the RFC says that we use code point X and in the IANA
considerations it says code point Y and the code point that people use is
actually "Y". So, someone files an erratum that changes the body of the
text to read Y. In this case, we absolutely do want people to think that
the annotated version is the one with normative force.


On Thu, Jan 31, 2019 at 9:28 AM Heather Flanagan <> wrote:

> Hi Sandy,
> You know I like the idea of a sandbox space - the RFC Editor needs a
> better way to explore ideas in a visible way. That said, there is concern
> about any hint of normative-ness to the annotated docs, and hosting them on
> the RFC Ed website might suggest some amount of officialness. I think we
> can potentially mitigate that by including something in the CSS that THESE
> ARE NOT NORMATIVE DOCUMENTS, but other ideas are welcome.
> -HEather
> On Jan 30, 2019, at 6:47 PM, Sandy Ginoza <> wrote:
> Hi all,
> I figured this comment/question would be more appropriate here rather than
> as feedback for the SoW.  I can’t remember if placement was decided when
> the IESG discussed this topic at the last IETF, so sorry if this is
> re-raising discussion I should already be aware of.
> The text says:
> This tool will initially be used to create pages served somewhere other
> than the RFC Editor’s website ( After gaining
> experience and community feedback, the pages might be moved to that
> website. Thus, the development of the tools should assume that the way the
> results are deployed will change over time.
> The RFC Editor has been talking about creating an experimental space on
> our site.  I think it’s worth considering having these annotated documents
> live in an experimental space on the RFC Editor site so they’re on the site
> from the beginning.  This seems like a perfect use for an experimental
> space.  Also, I believe that once these documents live somewhere, that is
> where users will look for them; if they become the de facto RFCs, I think
> we want them to be on our site.
> Thanks,
> Sandy
> On Jan 29, 2019, at 12:07 PM, Robert Sparks <> wrote:
> Adam's developed an initial draft for the inline-errata SoW. He started it
> as a google-doc and my initial set of feedback changes were easy enough to
> make there. Unless someone objects, I suggest we continue the development
> of this one using that tool. If you do object, for any reason, please let
> me know and I'll send a PDF while we adjust.
> RjS
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list