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

Thanks Bob,

That is a good inclusion in 7437bis, but makes 7776bis a bit confusing.
I'll try to work something out 😊

A

-----Original Message-----
From: Bob Hinden <bob.hinden@gmail.com> 
Sent: 31 March 2019 16:16
To: adrian@olddog.co.uk
Cc: Bob Hinden <bob.hinden@gmail.com>; Sean Turner <sean@sn3rd.com>; Jason Livingood <Jason_Livingood@comcast.com>; iasa20@ietf.org
Subject: Re: [Iasa20] WGLC: RFC 7776-bis (oops)

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
> 