Re: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice

mrex@sap.com (Martin Rex) Tue, 07 June 2016 08:40 UTC

Return-Path: <mrex@sap.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 ED44612B02F for <ietf@ietfa.amsl.com>; Tue, 7 Jun 2016 01:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.922
X-Spam-Level:
X-Spam-Status: No, score=-6.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-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 rtrTcxyDRLuJ for <ietf@ietfa.amsl.com>; Tue, 7 Jun 2016 01:40:28 -0700 (PDT)
Received: from smtpde02.smtp.sap-ag.de (smtpde02.smtp.sap-ag.de [155.56.68.140]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0064212B006 for <ietf@ietf.org>; Tue, 7 Jun 2016 01:40:27 -0700 (PDT)
Received: from mail06.wdf.sap.corp (mail06.sap.corp [194.39.131.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde02.smtp.sap-ag.de (Postfix) with ESMTPS id AFA2B442B8; Tue, 7 Jun 2016 10:40:25 +0200 (CEST)
X-purgate-ID: 152705::1465288825-0000299C-96F84358/0/0
X-purgate-size: 1009
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail06.wdf.sap.corp (Postfix) with ESMTP id 621614EABBB; Tue, 7 Jun 2016 10:40:25 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 3DE961A4DF; Tue, 7 Jun 2016 10:40:25 +0200 (CEST)
Subject: Re: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
In-Reply-To: <C44ABA4D-6247-43D6-A19B-EDA41E78E939@sn3rd.com>
To: Sean Turner <sean@sn3rd.com>
Date: Tue, 7 Jun 2016 10:40:25 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20160607084025.3DE961A4DF@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RFzB0OFtaP_pjtAUsBMG6r8erzg>
Cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: mrex@sap.com
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, 07 Jun 2016 08:40:30 -0000

Sean Turner wrote:
>
> draft-ietf-tls-tls1.3 is going to widow/orphan some registries
> and obsolete RFC 5246.

TLSv1.3 is *NOT* going to obsolete in the original/true sense of
obsoletion as it was defined and meant for RFC documents & IETF specifications.

Please remove any such bogus Obsoletion meta-data from the TLSv1.3 draft,
that is erroneously present in rfc4346 and rfc5246, and your perceived
problem vanishes completely.


>
> What I'm hoping to do is not update the references for these
> widowed/orphaned registries and include a Note in the IANA registries
> that says something along the lines of "These registries are for TLS 1.2,
> 1.1, and 1.0".
> Assuming the words in the draft-leiba-cotton-iana-5226bis allow me
> to do that I'll be happy.


Retaining the history of documents in the IANA registry (not deleting
older references to older documents) will also avoid confusion.


-Martin

PS: your MUA seems to be erroneously configured to send HTML-only EMail