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

Bob Hinden <bob.hinden@gmail.com> Sun, 31 March 2019 15:15 UTC

Return-Path: <bob.hinden@gmail.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 29E831201A9 for <iasa20@ietfa.amsl.com>; Sun, 31 Mar 2019 08:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zZ5ZOTkC_Z8G for <iasa20@ietfa.amsl.com>; Sun, 31 Mar 2019 08:15:36 -0700 (PDT)
Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8589E12019E for <iasa20@ietf.org>; Sun, 31 Mar 2019 08:15:36 -0700 (PDT)
Received: by mail-wr1-x431.google.com with SMTP id w1so8618500wrp.2 for <iasa20@ietf.org>; Sun, 31 Mar 2019 08:15:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nimehX6F6J+wQE6tSyDntJDt6eLby4i9FQsuJhNT608=; b=JnIK+zjZOtFXWSeHDeQpbF7vYD6FFRX/rOxeW/uasKdoyzRq5gD+13zfS4NqQTo5vR Tb8c5lz8V5W8lX+aEro9gnYM85EseFH0XAF6bqhXDr/Gqwjzxs3gzgKjrm0cVzEK9J8T 3KIJBtuG3B0DekwKZRJwdCyDdaSg2/183Qt0C86KyWyDz8iTukfepZfOS5UYK5P92G07 M6NKyGcH5ukGby5cXUv2sCloC1v/N7ETQV+S1eS8Q1SMKbFuZ6bBX3qCLIYEdzhrUhs8 wzp9OnokDuRlrgxsf0ws8D0nZxUf1iLcQ49P6mw87VroOuIxZIr6yuGJntkVNcBCoWuS Wbzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nimehX6F6J+wQE6tSyDntJDt6eLby4i9FQsuJhNT608=; b=OFCuFQt4cQuyYGkxSaqvlBPc9ISkgh6Ye2ntpwxbOf5hlPLqlmPBAke+HtS/hiF/Va fDSTOHO4ldTqledenSHBKnfpjujGg3jnmR04Yyd5sh6FJjmOxQ+Tq+8QJYej4hy19o50 Zq6CBM1WDGZKK1HgLlf+y9+USObCLUQYtySK4yb37MHs0mOxn4kZs78PKxESp5a1F3NO tR87mHw1fqBQLTWniQyj6c3H5qI/1Ikd0ryqKY0HJzXtS5C4dPQvdDLlVb30Kk9xvsQz TdISvzEda/ayMs43m04w/e+o8UioBBJZ3TKtI62dPLjbNkcgSl7MZWyMYinDcTMjqNvs MUXg==
X-Gm-Message-State: APjAAAXAalE7VFZsrJs9zk82gwHyUD49a8DX8YQCb8VSZ6ldi234sK4d RJM6jMdoF+d0S/KQmq1ezSI=
X-Google-Smtp-Source: APXvYqxXxeOkuCocl8xST5NHI30GudleobQ/42z2P43dVbUz3ccBl/9RxGg2ZAkvsuAqb+IUBkO0TQ==
X-Received: by 2002:a5d:4492:: with SMTP id j18mr31546121wrq.212.1554045335023; Sun, 31 Mar 2019 08:15:35 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:4c91:3c6a:5f53:de92? ([2601:647:5a00:ef0b:4c91:3c6a:5f53:de92]) by smtp.gmail.com with ESMTPSA id x205sm3594497wmg.9.2019.03.31.08.15.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 31 Mar 2019 08:15:34 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <118a01d4e732$34730040$9d5900c0$@olddog.co.uk>
Date: Sun, 31 Mar 2019 08:15:30 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, Sean Turner <sean@sn3rd.com>, Jason Livingood <Jason_Livingood@comcast.com>, iasa20@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <92D5F92F-95D9-46C2-AACF-1F6B2BAE262D@gmail.com>
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>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/67bj8qAWDztWUEOkqfF4AynNZN0>
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: Sun, 31 Mar 2019 15:15:39 -0000

Adrian,

> On Mar 30, 2019, at 12:53 PM, 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.

I believe that draft-ietf-iasa2-rfc7437bis includes the Ombudsteam changes made by RFC7776.   It’s called out in the change log:

      draft-ietf-iasa2-rfc74337bis-03, 2018-October-22:

      *  Revised Section 7 to focus on repeal of the the NomCom appoint
         LLC Director positions.
      *  Added that the IETF Trust Trustees and IETF LLC Directors, each
         may appoint a liaison to the NomCom.
      *  Incorporated the update to RFC7437 done by RFC7776.
      *  Incorporated the update to RFC7437 done by [RFC8318] and
         updated it to refer to the IETF Trust and IETF LLC. instead of
         the IAOC.
      *  Editorial changes.

Specificly see Section 7.1. “Petition” and 7.1.2. "Ombudsteam Petition”

Thanks,
Bob

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