Re: Status of this memo

S Moonesamy <sm+ietf@elandsys.com> Thu, 29 April 2021 06:22 UTC

Return-Path: <sm@elandsys.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 19E9A3A320C for <ietf@ietfa.amsl.com>; Wed, 28 Apr 2021 23:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 PLQkgn6g6Na5 for <ietf@ietfa.amsl.com>; Wed, 28 Apr 2021 23:22:04 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 6F5F63A31E6 for <ietf@ietf.org>; Wed, 28 Apr 2021 23:22:04 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.158.82]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 13T6LhDd029239 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Apr 2021 23:21:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1619677316; x=1619763716; i=@elandsys.com; bh=S99A+wYvOOaVYcppvjsyuIkHvSzRykJQ6go/37vv/1w=; h=Date:To:From:Subject:In-Reply-To:References; b=MlERScTi5LiwERC+lHFvRG6qkNelgtS7glpGY4PirS5jUW04g+hg3LiMMMWPsTcJa PwtrWLeGa33Pc/AU35PVrANkqTJ6bZVtyPJKjROCSPGyvwqgHum11wMnz0DG7DZNvV N4r3K15ePhSC/IFtPkV88780UgLJRiSZe3Fh1kJc=
Message-Id: <6.2.5.6.2.20210428223758.0d781e18@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 28 Apr 2021 23:14:43 -0700
To: Lars Eggert <lars@eggert.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Status of this memo
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MQ9LpFPpJ7FfoKwTJ92fKDhSq9A>
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: Thu, 29 Apr 2021 06:22:09 -0000

Hi Lars,
At 01:41 AM 27-04-2021, Lars Eggert wrote:
>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?

I doubt that serving I-Ds from another site would change much [1].

>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 following thread is an illustration of the discussions which 
occur every now and then outside the IETF: 
https://mailarchive.ietf.org/arch/msg/cfrg/ved8f1t70B0M2aDuc6I0DcsDH1o/ 
The github repository [2] for the research group mentions "Standard 
Draft".  The research group is either publishing misleading 
information or not bothered by what goes into its repository.

It would be good to have the status represent the current status of 
the draft instead of a boilerplate clause which does not match reality.

Regards,
S. Moonesamy

1. All I-Ds are listed under the same domain name in the datatracker.
2. https://github.com/cfrg/draft-irtf-cfrg-bls-signature