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

John C Klensin <john-ietf@jck.com> Sat, 02 March 2019 17:22 UTC

Return-Path: <john-ietf@jck.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 21D94130E74 for <iasa20@ietfa.amsl.com>; Sat, 2 Mar 2019 09:22: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, 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 rpPk2duXUt5A for <iasa20@ietfa.amsl.com>; Sat, 2 Mar 2019 09:22:37 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C97E127287 for <iasa20@ietf.org>; Sat, 2 Mar 2019 09:22:36 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1h08LH-000EBN-G1; Sat, 02 Mar 2019 12:22:31 -0500
Date: Sat, 02 Mar 2019 12:22:26 -0500
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, "Livingood, Jason" <Jason_Livingood@comcast.com>
cc: IASA 2 WG <iasa20@ietf.org>, Russ Housley <housley@vigilsec.com>
Message-ID: <D110E3546D6957A6CAB14502@PSB>
In-Reply-To: <2E93E49C-E201-4EDC-91A7-544AFD40FB62@cisco.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> <43379A25-D14D-413C-B940-9D135B128724@cable.comcast.com> <2E93E49C-E201-4EDC-91A7-544AFD40FB62@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/x6IYqT5qRlXL01vKk_IO-DRZsGI>
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 17:22:39 -0000

Eliot and IAB members who are following this,

If the IAB is willing to commit to that RSN, I'll fix the
document accordingly.  I'd prefer to not hold up IESG review on
this matter or to find time to generate extra drafts so, if a
quick IAB commitment is not possible, I suggest I fix the
document as Heather and Jason have suggested but encourage the
RFC Editor to treat the comment about IAB action as if it were a
normative reference, i.e., assuming the IESG actually approves
this I-D for publication, they don't actually publish until the
IAB's preferences are clear and then, if necessary, we do a
touch-up on the document during AUTH48 with confidence that the
WG's intent is perfectly clear.

Does that work for everyone?

    john  (as editor)


--On Saturday, March 2, 2019 17:26 +0100 Eliot Lear
<lear@cisco.com> wrote:

> 
> 
>> On 2 Mar 2019, at 14:36, Livingood, Jason
>> <Jason_Livingood@comcast.com> wrote:
>> 
>> 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.
> 
> We have crossed streams before.  See RFC 7979 (Russ was a
> co-author of that document).  There was a note in that
> document that simply stated:
> 
>> 5.  IAB Note
>> 
>>    The IAB supports the response in this document.
> 
> 
> 
> I would propose that the IAB simply agree to a note as follows:
> 
> 
>> IAB Note
>> 
>> With the publication of this document, RFC 3716 is designated
>> as historic.
> 
> 
> That way you know that you have the IAB's support for such
> an action at the time the document is published, and that you
> cannot end up in a situation where this document is published
> and 3716 is not, for whatever reason, not made historic.