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

"Adrian Farrel" <adrian@olddog.co.uk> Sat, 30 March 2019 19:53 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 22D4D12022D for <iasa20@ietfa.amsl.com>; Sat, 30 Mar 2019 12:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 5k6nKUpPArbg for <iasa20@ietfa.amsl.com>; Sat, 30 Mar 2019 12:53:19 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 C2D2D12021D for <iasa20@ietf.org>; Sat, 30 Mar 2019 12:53:18 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id x2UJrC0O016777; Sat, 30 Mar 2019 19:53:12 GMT
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4F52B2203A; Sat, 30 Mar 2019 19:53:12 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS id 39EED22032; Sat, 30 Mar 2019 19:53:12 +0000 (GMT)
Received: from LAPTOPK7AS653V ([87.114.144.161]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id x2UJrB0J002187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 30 Mar 2019 19:53:11 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Bob Hinden' <bob.hinden@gmail.com>, 'Sean Turner' <sean@sn3rd.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>
In-Reply-To: <EC7A0AF5-A042-4E7A-98EE-4FD6EE705822@gmail.com>
Date: Sat, 30 Mar 2019 19:53:10 -0000
Organization: Old Dog Consulting
Message-ID: <118a01d4e732$34730040$9d5900c0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQL8ONJunUay5avi+MspgHTZfvOxjALISYKBASWM7u6jtoFTAA==
X-Originating-IP: 87.114.144.161
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.002
X-TM-AS-Result: No--23.562-10.0-31-10
X-imss-scan-details: No--23.562-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24522.002
X-TMASE-Result: 10--23.561600-10.000000
X-TMASE-MatchedRID: 0dFPYP4mu5TxIbpQ8BhdbAbts0Qkqy42H5SN+D7shh+4Kkg59mswFwio blN62OEwphPmEFpbvMVpZkze5rrHsvMu4apF1ruYQ1OcCEvT+bdu/Xr6CKXiN+OxOq7LQlGLA2i H3GKyHDf1mHNhTON+rdKl+he8IswzjlL/hujrw1tjoaO27r+3fVHewY36PuY0wg96cEZFZobyrO vTiujE7DG73Ok+v2KtVwPRsVboteglMqDV8ypgcNjpv424W/L6RvFqpFrbMSc0EE1cHlv0zHWTh Xz58gza63BZ+u8CIN2J1N6/tfbp3mjh3elpvyuUKKCzdB3hgrJ7jgCP1tYUd7YMekRNgISzdzMX RBnT5T448M5jVFfC4f4eShhJIoU8sTYmRRlwUwpHFWsq1vzd1BLXa2P1m93zzO86RLKahv8nwf3 kfmsrQ68C3TTERs2RX7bicKxRIU0Es/H1wMyspv1vTGBiuZrtU2Qzq85WfnB0HSe131POnpBlLa 6MK1y4
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/9rBx__nM2yKAm_paMgIDLXoWqTM>
Subject: Re: [Iasa20] WGLC: RFC 7776-bis (oops)
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, 30 Mar 2019 19:53:22 -0000

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?
 
I will update my working copy of 7776bis to show the update to the work in progress, but if you or the WG prefer that we clean this up, I am happy to discuss doing different.

Cheers,
Adrian

PS If anyone knows how to wrangle the XML to handle this case, I'd welcome a clue. O/w I am using a note in the text.

-----Original Message-----
From: iasa20 <iasa20-bounces@ietf.org> On Behalf Of Bob Hinden
Sent: 30 March 2019 08:36
To: Sean Turner <sean@sn3rd.com>
Cc: Jason Livingood <Jason_Livingood@comcast.com>; Bob Hinden <bob.hinden@gmail.com>; iasa20@ietf.org
Subject: Re: [Iasa20] WGLC: RFC 7776-bis (oops)



> On Mar 30, 2019, at 8:40 AM, Sean Turner <sean@sn3rd.com> wrote:
> 
> References to RFC 7437 appear:
> 
>   [RFC7437]  Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection,
>              Confirmation, and Recall Process: Operation of the
>              Nominating and Recall Committees", BCP 10, RFC 7437,
>              DOI 10.17487/RFC7437, January 2015,
>              <http://www.rfc-editor.org/info/rfc7437>.
> 
> should we update them to refer to draft-ietf-iasa2-rfc7437bis?

I would think so.

Bob


> 
> spt
> 
>> On Mar 24, 2019, at 11:03, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
>> 
>> We’ve just realized that while we thought we’d issued all the WGLCs we seem to have missed one for RFC7776-bis (https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc7776bis/). I guess this is the danger of closing so many documents simultaneously. Anyway – WGLC is now open, ending 7-April-2019.
>> 
>> Thanks
>> Jason
>> _______________________________________________
>> iasa20 mailing list
>> iasa20@ietf.org
>> https://www.ietf.org/mailman/listinfo/iasa20
> 
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20

_______________________________________________
iasa20 mailing list
iasa20@ietf.org
https://www.ietf.org/mailman/listinfo/iasa20