Re: [Gendispatch] I-D Action: draft-nottingham-where-does-that-come-from-00.txt

Mark Nottingham <mnot@mnot.net> Mon, 15 March 2021 04:22 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 359DA3A12E8 for <gendispatch@ietfa.amsl.com>; Sun, 14 Mar 2021 21:22:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=f/HUEi6d; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=FwYSWaa+
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 RwD5QeswID7J for <gendispatch@ietfa.amsl.com>; Sun, 14 Mar 2021 21:22:12 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9A563A12E7 for <gendispatch@ietf.org>; Sun, 14 Mar 2021 21:22:12 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 773B62645; Mon, 15 Mar 2021 00:22:10 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 15 Mar 2021 00:22:10 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=e 8VpU3rbSTKlypkNdL3x8odZ8RvWNzBlGChMQcQW4U4=; b=f/HUEi6dKgIYauLeO oTLiv8vtehkevNH12tiUVYFcq4lRkGkUEnz8NlfwQX+v3+/Nc9EtkrDFXjK41Ne6 KBlNhgZeynCdDB5AoIW8Ev5BsTOuUBMuVmqZVKdpaaCTkcrryO270Y/+65hj48NP qj/eMNsnUog5SFA4VF9clY4rqVujv6n5lAdVq0hyca4uUe2vuTamWSMZqYVcvg7w BNQwt43JMeRXw+OXCSJ8BWgXfNRCDfSlH8vs57PgZIJzK7IKZd6+BocVL8ZSQDoV yfLTow9ZExM72gFP7l3QYXiQVVhnsCZb3ZLU3RcyrtaUh3+j/S/xE49/NbDRMhvu XWFtA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=e8VpU3rbSTKlypkNdL3x8odZ8RvWNzBlGChMQcQW4 U4=; b=FwYSWaa+cegJPAy4Ddo2H6nnRi2Ahp0bAuI+yRS2FevwP0r8YNgRYXELK 96OHG9DXQ0T+T4sfcbqQY5ZejSOL71+b1kkXXLLyw7NjBXi/mfGKhQMqf8Dfl5lN je9Svck2K+pPA6Kk9Ib2QCZoKRnQ7Y4Kj3PVyQ/bw6oQPhIJLrqW9dX9vHdcVYlg fCbEOZxxJUjs1n8pOdR107AKj2oWpo4l8Xh56ZMUHZ+9B+gA/SM3qmflXb9RL33j 2W+NaGi6wqQMPxic+PheSOfaC7yX5PkeKtkc7SoKllEWeFAKLbYMVUL7HJOOET2U 4wygSBtnPSmEDo9xq7N2hUaDoFEDA==
X-ME-Sender: <xms:8OBOYCRWgHX6orv9GR3Sp8jwgSOOMQRTNxsTYYuHFof4bybhPEImLg> <xme:8OBOYHwhLz7pkdcfQvgrfbL2t62f5WSRGf9NSEGynSdW7Cm5l_TDb0Xf_bOYpLGM- hpI_69GzPdPzR4SzA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddvkedgjedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtddvnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghmuceomhhnohhtsehm nhhothdrnhgvtheqnecuggftrfgrthhtvghrnhepteefgeefveejkeetgedvvdegffektd eiveduffdtheeiueehgeejjeejtefgudejnecuffhomhgrihhnpehrfhgtqdgvughithho rhdrohhrghdpihhnthgvrhhnvghtqdgurhgrfhhtshdrohhrghdpihgvthhfrdhorhhgpd hmnhhothdrnhgvthenucfkphepudduledrudejrdduheekrddvhedunecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnh gvth
X-ME-Proxy: <xmx:8OBOYP0B1y-YJJXcNroansJFZ5kEiIJRPtmPsoMH79MoxJfCq2Sr5g> <xmx:8OBOYOCSdAoXqzYK0ToIGdEzeP6baV3_6C-RgeAGYLZyTAydVcJVJA> <xmx:8OBOYLiNWxKz8Qv7ee2yuab-L_o4orgJbTofXTBUhpXNsMboaYnP9Q> <xmx:8uBOYOuZNbs8rQWlUHur0DXuZvnsDGe-qFE8tUX9q_gAE9L9v3rLCQ>
Received: from [192.168.7.30] (119-17-158-251.77119e.mel.static.aussiebb.net [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id DE6E124005B; Mon, 15 Mar 2021 00:22:07 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <06a5ed8c-d8fd-8dae-973f-6d869e6736d3@joelhalpern.com>
Date: Mon, 15 Mar 2021 15:22:05 +1100
Cc: gendispatch@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <99F90A14-125C-40E3-A7BD-385BF7F2885A@mnot.net>
References: <161551347322.9380.3417782072654776845@ietfa.amsl.com> <7a5f3d29-2ffe-b47e-59e9-f69eaa228f70@gmail.com> <6E90BCEE-C9B8-4D33-A218-707EC160730B@mnot.net> <06a5ed8c-d8fd-8dae-973f-6d869e6736d3@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/_KcPapopOXtg559uOnaGRMg9f3E>
Subject: Re: [Gendispatch] I-D Action: draft-nottingham-where-does-that-come-from-00.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Mar 2021 04:22:15 -0000

Hi Joel,

> On 15 Mar 2021, at 3:11 pm, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> Mark, I think the whole game with domains is a mistake.
> As others have said, the content (drafts, RFCs, ...) is mirrored in multiple places.  And we want people to do that.

I'm not proposing that we disallow people from mirroring drafts and RFCs - I see the value in mirroring, and even dabble in it myself.

What I'm proposing is that we not lend the IETF branding -- in the form of the domain name, which appears in the browser bar for tools and datatracker -- to any random draft that gets submitted. That's misleading as to its status, and is one of the reasons we see I-Ds cited as 'the IETF draft...'.


> Also, when it comes to drafts, it is actually important that individual drafts aimed at a working group be known to and easily visible by the working group.  So if folks are using things like the datatracker WG summary page, the drafts need to be there.  At which point putting them in a different domain is completely worthelss.

Nothing in the proposal prevents *linking* to drafts elsewhere on such a page.


> I don't object to putting logos on  different stream RFCs.  I don't know that it will help much.
> 
> Note that none of your changes would seem to help much with the most common consufion, namely informational or experimental IETF RFCs being treated as Standards Track RFCs by external promoters.  And no, I do not think the right answer is to remove Informational or Experimental RFCs.

That's indeed a problem, but personally I think we need to get this part of our house in order before we can tackle it.


> And we already see folks (maybe deliberately, maybe accidentally) confusing individual or WG Internet Drafts with RFCs.  Even though any form of reference is completely different.
> 
> I don't see most of this document as usefully improving much of any of the many problems I have seen.
> 
> Yours,
> Joel
> 
> PS: At least in my experience, folks don't generally conflate or misrepresent either IRTF or Independent Stream documents with IETF product.  Maybe if we could figure out why not, we could get more leverage for actually solving the problem.
> 
> PPS: My recommendation would be to not dispatch this document.
> 
> On 3/14/2021 11:58 PM, Mark Nottingham wrote:
>> Hi Brian,
>>> On 13 Mar 2021, at 7:53 am, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>> 
>>> As already  noted, this can't really be an IETF document since it purports to cover all streams.
>> Some parts will need to be initiated by other streams, but they stream managers can effectively opt into its suggestions. Also, much of it is about what it *not* associated with the IETF -- which we do control.
>>>> 2.1.3. Proposal 3: domain usage
>>> 
>>> I think this section is actively harmful. The canonical place for all RFCs is rfc-editor.org; I think that we should very likely deprecate copies in any other domains (although those domains should certainly have pointers to the canonical copies).
>>> 
>>> Really, RFCs have no place in the IETF data tracker, except as pointers.
>> If we can cure ourselves of the addition to the augmented views on tools and datatracker, I'm all for this. What we really need to encourage is augmentation of the RFC Editor view (perhaps on the metadata page, etc.).
>>>> 2.2. Internet-Drafts
>>>> 
>>>> The following recommendations apply to the publication of Internet-Drafts.
>>> 
>>> The problem here is that draft-foo-bar has no intrinsic link to any of the streams. A differentiation can only be made later, if the draft becomes draft-ietf-bar or draft-irtf-bar. So how would we algorithmically classify draft-nottingham-quic-new-idea or draft-nottingham-where-does-that-come-from?
>> As unassociated drafts on internet-drafts.org; they're not adopted on any stream.
>> Cheers,
>>> 
>>> Regards
>>>   Brian
>>> 
>>> On 12-Mar-21 14:44, internet-drafts@ietf.org wrote:
>>>> 
>>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>> 
>>>> 
>>>>        Title           : Clarifying IETF Document Status
>>>>        Author          : Mark Nottingham
>>>> 	Filename        : draft-nottingham-where-does-that-come-from-00.txt
>>>> 	Pages           : 7
>>>> 	Date            : 2021-03-11
>>>> 
>>>> Abstract:
>>>>   There is widespread confusion about the status of Internet-Drafts and
>>>>   RFCs, especially regarding their association with the IETF and other
>>>>   streams.  This document recommends several interventions to more
>>>>   closely align reader perceptions with actual document status.
>>>> 
>>>> 
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-nottingham-where-does-that-come-from/
>>>> 
>>>> There is also an HTML version available at:
>>>> https://www.ietf.org/archive/id/draft-nottingham-where-does-that-come-from-00.html
>>>> 
>>>> 
>>>> Please note that it may take a couple of minutes from the time of submission
>>>> until the htmlized version and diff are available at tools.ietf.org.
>>>> 
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>> 
>>>> 
>>>> _______________________________________________
>>>> I-D-Announce mailing list
>>>> I-D-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>> 
>>> 
>>> -- 
>>> Gendispatch mailing list
>>> Gendispatch@ietf.org
>>> https://www.ietf.org/mailman/listinfo/gendispatch
>> --
>> Mark Nottingham   https://www.mnot.net/

--
Mark Nottingham   https://www.mnot.net/