Re: don't overthink, was Just so I'm clear

mrex@sap.com (Martin Rex) Wed, 24 October 2012 21:41 UTC

Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42A4B21F88B9 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 14:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.21
X-Spam-Level:
X-Spam-Status: No, score=-10.21 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NAKIXP5n6rU7 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 14:41:29 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 58C7621F86B8 for <ietf@ietf.org>; Wed, 24 Oct 2012 14:41:29 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q9OLfMgR009261 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Wed, 24 Oct 2012 23:41:27 +0200 (MEST)
Subject: Re: don't overthink, was Just so I'm clear
In-Reply-To: <alpine.LRH.2.01.1210241214280.6521@egate.xpasc.com>
To: ietf@ietf.org
Date: Wed, 24 Oct 2012 23:41:22 +0200
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20121024214122.7ED0F1A2F3@ld9781.wdf.sap.corp>
From: mrex@sap.com
X-SAP: out
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 21:41:30 -0000

David Morris wrote:
> 
> John Levine wrote:
> >
> > >I agree with you that removing him would be the simplest approach, but I
> > >can see possible situations where NOT following the process could lead
> > >us into legal trouble.  
> > 
> > Anyone can sue in the US for any reason, but this is silly.
> > 
> > The IAOC made extensive attempts to contact him in many ways, with
> > zero response.  No court I know would find it unreasonable to assume
> > that he's no longer interested.
> 
> The legal issue raised by a previous reply that resonates with me is
> that someone unsatisfied with a business decision by the adjusted
> IAOC membership could sue based on documented process not being
> followed to appoint the membership.
> 
> > I certainly hope that this sort of situation does not recur, but it
> > seems perfectly reasonable in view of the facts to let the IAOC
> > proceed as though he's resigned.
> 
> Yeah, except establishing new process and applying it retroactively
> could be an issue. A new removal process could be defined and accepted
> by the IETF's normal process, but the clock would have to start with
> approval of the new process.


I believe you're blowing the (in)significance of "someone unsatisfied
with a business decision" out of proportion.


But actually, discussing the recall procedure _now_ looks like barking up
the _wrong_ tree to me.

The IAOC says it is currently understaffed to do its work.  So what
the IAOC needs quickly is another (at least temporary) _active_ membership.

Whether or not Marshall remains an (inactive) member of the IAOC 
may be academically interesting, and a topic of discussion to
augment the procedures for the future, but appears less relevant
for the IAOC in trying to get its work done.
 

Doing an extended last call to augment the IAOC membership by one
addidional _active_ seat up to the end of Marshalls term should
be possible as an ad-hoc interim measure to address a specific
current resource shortage.  Adjusting the procedures is a secondary
issue.


-Martin