Note from the IASA2 WG regarding this document pertaining to the IETF Trust. After the Trust Update draft was through the normal document process and with the RFC Editor, the WG was finishing up other documents and determined a further change was needed on the Trust Update document. After much discussion over what change was needed, this has been reflected in the straightforward diff at https://arkko.com/ietf/iasa20/draft-ietf-iasa2-trust-update-diff-b.html. We are now working with the RFC Editor to make this change, while also advising the WG, the IESG, and the IETF via this list. The key change here is that the document will now obsolete RFC 4371 instead of merely updating it. Appendix A of the diff enumerates all changes. Thanks! Jason >> > -----Original Message----- >> > From: Jari Arkko [mailto:jari.arkko@xxxxxxxxx] >> > Sent: 05 October 2018 17:37 >> > To: adrian@xxxxxxxxxxxx >> > Cc: ietf@xxxxxxxx; iasa2-chairs@xxxxxxxx; iasa20@xxxxxxxx; draft-ietf-iasa2-trust- >> > update@xxxxxxxx >> > Subject: Re: Last Call: <draft-ietf-iasa2-trust-update-00.txt> (Update to the >> > Selection of Trustees for the IETF Trust) to Best Current Practice >> > >> > Adrian, >> > >> > Many thanks for your perceptive review. >> > >> > I have adopted your suggestions in my copy of the draft. >> > >> > One follow-up below: >> > >> > > Section 2 >> > > >> > > IETF rules regarding recalls and other NomCom-related processes >> > > continue to apply [RFC7437]. >> > > >> > > Pedantic, but you can't quite get away with this because the NomCom >> > > processes in 7437 did not apply to pure IETF Trust appointments. >> > > >> > > How about... >> > > >> > > The processes regarding NomCom appointments and recalls of Trustees >> > > for the IETF Trust follow those described in [RFC7437]. >> > >> > That’s much better, and this was an important catch. >> > >> > > Does this mean this document updates 7437? >> > >> > I think not, because this document uses 7437… would be happy to hear if people >> > think otherwise. >> > >> > Jari >> >> >>
