Re: [Iasa20] WGLC: RFC 7776-bis (oops)

John C Klensin <john-ietf@jck.com> Sat, 30 March 2019 21:40 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 8D5151202D6 for <iasa20@ietfa.amsl.com>; Sat, 30 Mar 2019 14:40:25 -0700 (PDT)
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 S3EHkLmdsBnQ for <iasa20@ietfa.amsl.com>; Sat, 30 Mar 2019 14:40:23 -0700 (PDT)
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 CCB911202C9 for <iasa20@ietf.org>; Sat, 30 Mar 2019 14:40:23 -0700 (PDT)
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 1hALi7-000MaV-E1; Sat, 30 Mar 2019 17:40:19 -0400
Date: Sat, 30 Mar 2019 17:40:09 -0400
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk
cc: 'Jason Livingood' <Jason_Livingood@comcast.com>, iasa20@ietf.org
Message-ID: <572AD89CAB5AC339DE286DC0@PSB>
In-Reply-To: <118a01d4e732$34730040$9d5900c0$@olddog.co.uk>
References: <62B627AB-6DB2-4697-A049-A79C02A25A41@cable.comcast.com> <2FDAF1AD-F6FF-4D92-A094-96EB841C14D2@sn3rd.com> <EC7A0AF5-A042-4E7A-98EE-4FD6EE705822@gmail.com> <118a01d4e732$34730040$9d5900c0$@olddog.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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/gYvYoxzKRL7IhRX7ojek3HRrOIY>
Subject: Re: [Iasa20] WGLC: RFC 7776-bis (oops)
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <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, 30 Mar 2019 21:40:26 -0000


--On Saturday, March 30, 2019 19:53 +0000 Adrian Farrel
<adrian@olddog.co.uk> wrote:

> Well, we can do this.
> It is a bit ugly because 7776 updates 7437.
> So what we end up with is an I-D going into the RFC Editor
> Queue with a planned update to an I-D going into the RFC
> Editor Queue at the same time.
> 
> Just as a reminder, while 7437bis is a full replacement for
> (i.e., obsoletes) 7437, 7776bis is only a minor delta (i.e.,
> updates) 7776.
> 
> I completely understand the notion of "this document is only
> open to make the IASA2.0 changes" but maybe this could be
> cleaner?  
>...

It could indeed but I note, fwiw, that there has already been an
executive decision by the relevant AD that documents are not to
make changes that exceed the (narrowly-interpreted) scope of the
WG Charter.

I assume that ruling will not be different for different
documents, lest the WG be called upon to describe and document
the hair-splitting or to risk having several documents tied up
in appeals over the perceived inconsistency.

    john