Re: Status of this memo

Vittorio Bertola <vittorio.bertola@open-xchange.com> Tue, 27 April 2021 13:27 UTC

Return-Path: <vittorio.bertola@open-xchange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB583A18E9 for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 06:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 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_DNSWL_MED=-2.3, SPF_HELO_NONE=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=open-xchange.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 ccFtTYTTSLzo for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 06:26:55 -0700 (PDT)
Received: from mx3.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69BD93A18E5 for <ietf@ietf.org>; Tue, 27 Apr 2021 06:26:55 -0700 (PDT)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.20.28.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPSA id 10BCE6A0D1; Tue, 27 Apr 2021 15:26:52 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1619530012; bh=ZZcsYnDNz0NLZumTP5JVLJUZHFLZV1s1D4czYQuL3w0=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=endg+myYA/fIrUAoztV+i0MBiYyYecYDh7pqOqhNMOrD9kH7GApdZSKV9LJlViMgW xMDVZTSItdXUGziw3bQ2nXL/tRplqd9qySgXrfhaqxVOzjldpNqBpxxDZ7JAYjgOz7 AhJdkasqKYe7fBD65ARS3rEI07kzvdEROzAX9WXEuE/DPHPXx+13/XQBvj2SbemkbZ WPH+g07cRpbN7pJHxsGBV5Bx7QSTirhSF1IP77Qv3lcMFM8TWUdlRd5yTJ5jOM+GRz qJySIXsU5uR6TXcrpwIGQjW5uRDGx3nVIju9MzD6T1LI14DpvwiNav4L2QVzxcQ2GH BxY57z//cbtIA==
Received: from appsuite-gw2.open-xchange.com ([10.20.28.82]) by imap.open-xchange.com with ESMTPSA id +7IaBBwRiGC1LQAA3c6Kzw (envelope-from <vittorio.bertola@open-xchange.com>); Tue, 27 Apr 2021 15:26:52 +0200
Date: Tue, 27 Apr 2021 15:26:51 +0200
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Lars Eggert <lars@eggert.org>
Cc: IETF discussion list <ietf@ietf.org>
Message-ID: <269463648.9898.1619530011972@appsuite-gw2.open-xchange.com>
In-Reply-To: <D653D3B2-7666-409A-B856-2A4B1BA958CA@eggert.org>
References: <376f83f0-89a3-cd0e-1792-c8434bd8a5d2@gmail.com> <9ACE59FA-30B6-475A-AF6B-4B874E4A2788@eggert.org> <1804294246.5904.1619512137931@appsuite-gw2.open-xchange.com> <D653D3B2-7666-409A-B856-2A4B1BA958CA@eggert.org>
Subject: Re: Status of this memo
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.5-Rev8
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2Oc421b0-j0fhMfgyJ_rARc7wJk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 13:27:00 -0000


> Il 27/04/2021 10:41 Lars Eggert <lars@eggert.org> ha scritto:
> 
> There was a suggestion recently to not serve I-Ds from ietf.org domains until they were adopted by the IETF. Do you think serving individual drafts from another domain would help make that distinction clearer?

URIs can help, because they are posted around to refer to documents, so they can contain prominent semantic "messages", either in the hostname or in the top path element. However, I think it would be even better to do this in the filename, as the filename persists even when the file is downloaded or attached. For example, you could reverse the order of the initial elements and things would already be much clearer:

ietf-draft-<wg>-<subject>
irtf-draft-<wg>-<subject>
independent-draft-<author>-<subject>

> There was also a suggestion to add something to the boilerplate text of individual I-Ds along the lines of "anyone can submit an I-D; they have no formal standing until they are adopted by a group in the IETF or IRTF". Would that provide additional clarification?

The boilerplate is useful mostly as something that people can refer to when having a specific discussion; people that know the issue can point other participants to text in the boilerplate. However, people that just randomly find the document and are interested in the content will mostly skip the boilerplate and just read the technical spec.

So, I would add text in the boilerplate but I would also add a short, neat, isolated sentence in a much more visible position, such as a tagline above the title and below the headers, or a subtitle just under the title. Something like "Working draft of IETF group <wgname>" or "Unofficial submission", perhaps combined with something on the intended status (standard vs informational etc.).

By the way, "independent" is not immediately clear. "Personal" or "unofficial" would IMHO be better.

-- 
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy