IETF Logo Mail Archive

Re: [Iasa20] Odd deprecations in draft-ietf-iasa2-consolidated-upd-05

"Livingood, Jason" <Jason_Livingood@comcast.com> Sat, 02 March 2019 13:36 UTC

Return-Path: <Jason_Livingood@comcast.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE82130E25 for <iasa20@ietfa.amsl.com>; Sat, 2 Mar 2019 05:36:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ErQp2KNdIr5U for <iasa20@ietfa.amsl.com>; Sat, 2 Mar 2019 05:36:37 -0800 (PST)
Received: from copdcmhout02.cable.comcast.com (copdcmhout02.cable.comcast.com [96.114.158.212]) (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 6C152130E13 for <iasa20@ietf.org>; Sat, 2 Mar 2019 05:36:37 -0800 (PST)
X-AuditID: 60729ed4-2cdff700000044dc-40-5c7a86de77c5
Received: from copdcexc33.cable.comcast.com (copdcmhoutvip.cable.comcast.com [96.114.156.147]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by copdcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id 02.15.17628.ED68A7C5; Sat, 2 Mar 2019 06:36:30 -0700 (MST)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by copdcexc33.cable.comcast.com (147.191.125.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Sat, 2 Mar 2019 08:36:29 -0500
Received: from COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94]) by COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94%15]) with mapi id 15.01.1466.012; Sat, 2 Mar 2019 08:36:29 -0500
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: John C Klensin <john-ietf@jck.com>, IASA 2 WG <iasa20@ietf.org>, Russ Housley <housley@vigilsec.com>
Thread-Topic: [Iasa20] Odd deprecations in draft-ietf-iasa2-consolidated-upd-05
Thread-Index: AQHUwxDPRJS9tDrjZUeSpiGzdEBBx6Xc/bWAgAAEDYCABGF2gIAADxoAgAH3kwCAB2xFAIANnZQA
Date: Sat, 02 Mar 2019 13:36:29 +0000
Message-ID: <43379A25-D14D-413C-B940-9D135B128724@cable.comcast.com>
References: <1b58312a-ab8e-ccba-2f9b-884091e1c603@nostrum.com> <27724fb0-25ee-0226-b2ee-2b861a34cbf2@gmail.com> <CFBA6F06-E1A6-4974-9BA0-5DCC1CCCA7AE@vigilsec.com> <AF40B5B2002AE7A55B489999@PSB> <051B5D57-4B47-4D29-83CB-9AA3B3E3A6DE@vigilsec.com> <96A8294B81742974985BE7C8@PSB> <17AB2523-CEB6-4464-8BED-E6B99AFE39A5@rfc-editor.org>
In-Reply-To: <17AB2523-CEB6-4464-8BED-E6B99AFE39A5@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.15.0.190115
x-originating-ip: [96.115.73.254]
Content-Type: multipart/alternative; boundary="_000_43379A25D14D413CB9409D135B128724cablecomcastcom_"
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkleLIzCtJLcpLzFFi42JJKJozWfdeW1WMwZxVwhavXtxkt1gyfSOT ReulP2wOzB5Llvxk8ri88jWzx6o7X1gDmKPCbYpSi0uTcjNLFIpTi8oyk1NtlZITi5XsuBQw AFBpTmpicapjcklmfl6xPoYaG32YYXYJ4RmfHs1jLFiSWnHxwU7mBsaDSV2MnBwSAiYSKy4u Zu5i5OIQEtjFJNH8YzkThNPMJHF64mYWCOcUo8SkO3fZQVrYBMwk7i68wgxiiwjkSGy618gE YgsL+Emsu3aIDSIeKHF81WKgeg4gO0ri+7oMkDCLgIrEwvd3WUFsXgEXiSsTfkPNv84k0bN+ OwtIglPASeLRuolgMxkFxCS+n1oDZjMLiEvcejKfCeJsAYkle84zQ9iiEi8f/wMbKiqgL9H6 /QcrRFxR4te8K2wQvekSE5fvYINYLChxcuYTFogacYnDR3awTmAUm4VkxSwkLbOQtMwCeodZ QFNi/S59iBJFiSndD9khbA2J1jlzoWwriesf/7Ihq1nAyLGKkc/STM/Q0ETP0NRCz8jQaBMj OIHMu7KD8fJ0j0OMAhyMSjy8tXFVMUKsiWXFlbmHGCU4mJVEeHuagEK8KYmVValF+fFFpTmp xYcYpTlYlMR5Py6pjBESSE8sSc1OTS1ILYLJMnFwSjUwNsu+2vbskFBk4l45gd8rT3GkuOg5 VEnwP06PDWGQ5j97yOTPTuX2sl1SIsfPWFz0PDapcermeE4n21PSu7hLHvyRlPg+/eLjFP4a zw5PH9nvZ7u4pnhUH2pRXTFxz7E1mtY2r/seeV/f/WH5HQuLGoHkbTavgv8c0v7A9dZ1qXLq 3l18SfNWK7EUZyQaajEXFScCACUTYx0cAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/w2IOf-m5ETuUYkiv3UkZSn8RV00>
Subject: Re: [Iasa20] Odd deprecations in draft-ietf-iasa2-consolidated-upd-05
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Mar 2019 13:36:40 -0000

FYI for the WG – we conferred again with the RFC Editor and this is a rather complicated and arcane situation. She recommended we do the following, which John will be doing in his next revision. That should close this issue and we can move forward.

1 – The document should obsolete ***and*** move to historic RFC 3929 and RFC 4633.
2 – The document should include text that requests that the IAB move RFC 3716 to historic.

These actions will result (directly in the case of 3929 and 4633, and when the IAB makes their request for 3716) in the RFC Editor updating their database and the status of the documents in question.

Thanks,
Jason


From: iasa20 <iasa20-bounces@ietf.org> on behalf of "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Date: Thursday, February 21, 2019 at 11:41 AM
To: John C Klensin <john-ietf@jck.com>
Cc: IASA 2 WG <iasa20@ietf.org>, Russ Housley <housley@vigilsec.com>
Subject: Re: [Iasa20] Odd deprecations in draft-ietf-iasa2-consolidated-upd-05




On Feb 16, 2019, at 3:19 PM, John C Klensin <john-ietf@jck.com<mailto:john-ietf@jck.com>> wrote:

That is clearly a mess.   I believe it is the RFC Editor's mess
and Heather (copied) ought to be able to just figure out a way
to clean it up and get that implemented.  However I suspect that
at least one of the IESG, RSOC, or IAB would disagree and think
they needed to intervene, steer, or at least sign off (I'd be
delighted to be wrong about that).  It is rather clearly not an
IASA 2.0 mess or a WG mess except that I think the job of the WG
is to get the new system and transition documented and to do so
in a clear and orderly fashion.   I hope we can agree that
"mess" and "clear and orderly" are inconsistent.

Hi John, all,

This is a long standing mess, and one I brought up with the IESG some time ago. My preference (because I like a human-friendly information trail) is for there to be an RFC that documents (and perhaps explains) the action of moving another to Historic, and that happens sometimes. More often, especially these days, is just a database-level status change, which is considered sufficient by the IESG.

In either case, though, the information is noted on the Info page of the RFC that has been changed to Historic as well as on the RFC Status Change page (https://www.rfc-editor.org/status_changes.php).

Hope that helps,
Heather

v2.23.0 | Report a Bug | By Email