IETF Logo Mail Archive

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

"Adrian Farrel" <adrian@olddog.co.uk> Sun, 31 March 2019 09:28 UTC

Return-Path: <adrian@olddog.co.uk>
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 34B7912015D for <iasa20@ietfa.amsl.com>; Sun, 31 Mar 2019 02:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 NJbGtc0Y_HGS for <iasa20@ietfa.amsl.com>; Sun, 31 Mar 2019 02:28:16 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 EDEF512008F for <iasa20@ietf.org>; Sun, 31 Mar 2019 02:28:15 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id x2V9S9LL032518; Sun, 31 Mar 2019 10:28:09 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D762422044; Sun, 31 Mar 2019 10:28:08 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs2.iomartmail.com (Postfix) with ESMTPS id C202522042; Sun, 31 Mar 2019 10:28:08 +0100 (BST)
Received: from LAPTOPK7AS653V (58.144-252-62.static.virginmediabusiness.co.uk [62.252.144.58] (may be forged)) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x2V9S8Qu005363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 31 Mar 2019 10:28:08 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'John C Klensin'" <john-ietf@jck.com>
Cc: "'Jason Livingood'" <Jason_Livingood@comcast.com>, <iasa20@ietf.org>
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> <572AD89CAB5AC339DE286DC0@PSB>
In-Reply-To: <572AD89CAB5AC339DE286DC0@PSB>
Date: Sun, 31 Mar 2019 10:28:07 +0100
Organization: Old Dog Consulting
Message-ID: <002901d4e7a4$0d261780$27724680$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQL8ONJunUay5avi+MspgHTZfvOxjALISYKBASWM7u4Cb3d3WgE9xi1no5n9r+A=
Content-Language: en-gb
X-Originating-IP: 62.252.144.58
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24522.006
X-TM-AS-Result: No--7.436-10.0-31-10
X-imss-scan-details: No--7.436-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24522.006
X-TMASE-Result: 10--7.436300-10.000000
X-TMASE-MatchedRID: QW5G6BKkLTrxIbpQ8BhdbOG5dRZCgxC3Ud7Bjfo+5jTCD3pwRkVmhvKs 69OK6MTszcME7C6X7cvlPWOZdnoFfJEYDbcmxNrfikAqqvL2KhXFphRdtkn03sNNczdXNJoihMj 5fcP5ZmKPXsQ0qWrGPNcVLzHneDDatcCPfkIwcq4D2WXLXdz+AQXAhAGZB7BnWltirZ/iPP5AbH GZdGfb2zYE68bps0IGgb8rCEXGA9EK+f3FjCGvN/jQkA7rdCuF7MCp9lIIoYpGpBz7/mRrt6PFj JEFr+olfeZdJ1Xsorj72mXKge0hlwtuKBGekqUpIG4YlbCDECvS3Rxy14J4N9SpLaVFjbelvsjb 2+zdVOkJ/H6Ekpb89oeMIaym5E6Q66XHIc5w+gc=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/ssOaJOLUHmhty8LwKrG-nsOQpto>
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: Sun, 31 Mar 2019 09:28:18 -0000

Understood.

My buffer contains an update accordingly to address Sean and SM's points.

A

-----Original Message-----
From: John C Klensin <john-ietf@jck.com> 
Sent: 30 March 2019 21:40
To: adrian@olddog.co.uk
Cc: 'Jason Livingood' <Jason_Livingood@comcast.com>om>; iasa20@ietf.org
Subject: Re: [Iasa20] WGLC: RFC 7776-bis (oops)



--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

v2.8.7 | Report a Bug | By Email