Re: IAOC Request for community feedback

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

 



Bob wrote:

> Having his position declared vacant ...

How long has it been since the last time he attended an IAOC or IETF meeting, or responded to an e-mail addressed directly to him?

We have processes that involve timers (viz. I-Ds expire after 6 months), and so I am thinking we should discuss how long an IAOC member may be MIA before his/her seat is declared vacant or  at risk of recall because of being MIA.

I also have one more question.  Have other modes of communication been attempted?  For example: registered letters (via snail-mail) or phone calls?

Regards,

Ed  J. 
 

-----Original Message-----
From: Bob Hinden <bob.hinden@xxxxxxxxx>
Sender: ietf-bounces@xxxxxxxx
Date: Tue, 23 Oct 2012 16:25:49 
To: <ietf@xxxxxxxx>
Cc: Bob Hinden<bob.hinden@xxxxxxxxx>
Subject: Re: IAOC Request for community feedback

Responding to some of the discussion, I would like to raise a few points.

I don't see how the IAOC has bypassed any rules.  We are asking the community if it is OK to declare Marshall's position vacant.  Bypassing the rules would be true if the IAOC had gone ahead unilaterally and asked the NomCom to fill the reminder of Marshall's term.  The community consensus will determine the answer to the query.  

We think the current procedures were not meant for this case and are not clear on the situation when to declare a position vacant.

BCP101 says:

  Any appointed IAOC member, including any appointed
  by the IAB, IESG, or ISOC Board of Trustees, may be recalled using
  the recall procedure defined in RFC 3777.

The use of "may" usually means do this unless there is good reason to do otherwise.  I think that is the case in this situation.

The IAOC has operational responsibilities.  Having one voting member not attending many meetings makes it harder obtaining a consensus.  Without a consensus the IAOC can not approve contracts, RFPs, etc.  

Lastly, and I think most important, the IAOC proposed this approach because we think it would cause the least amount of embarrassment to Marshall.  Marshall has been active in the IETF for many years and has made many important contributions.  We proposed this course of action in respect to Marshall.  We think it's better to not subject him to the formal RFC3777 recall process.  Having his position declared vacant is milder than having him be formally recalled.

Bob





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