Re: Updating the NomCom RFC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I know Bob also gave a +1 to this note from Lucy, so let me add my +1 as well. As we worked on RFC7437bis in the IASA2 WG, and particularly within our charter’s constraints for what was updatable, it seemed clear that there were some gaps between what was documented and actual practices. In addition, with the current NomCom composition, we can see some areas where clarifications and re-assessments would be helpful. Finally, there also seemed to be a few areas where the community was interested in revising practices based on lessons learned.

 

Jason

 

From: ietf <ietf-bounces@xxxxxxxx> on behalf of Lucy Lynch <llynch@xxxxxxxxxxxxxxxx>
Date: Monday, July 8, 2019 at 12:36 PM
To: "ietf@xxxxxxxx" <ietf@xxxxxxxx>
Subject: Updating the NomCom RFC

 

All -

 

As a reminder there are substantive changes needed for cross body selection and liaison  appointments. There are also additional long standing problems that are noted here:

 

Many of these issues have been surfaced by  past NomCom Chsirs over the last 10 years.

 

The RFC changes I listed in my report were put on hold while IASA 2.0 changes moved forward but the current “running rules” are way out of whack with actual state so it’s time to address the updates along with any new ideas.

 

- Lucy


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux