Re: [IETF] Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats

Phillip Hallam-Baker <hallam@gmail.com> Wed, 03 July 2013 19:41 UTC

Return-Path: <hallam@gmail.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 C1C8F11E820D for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2013 12:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.212
X-Spam-Level:
X-Spam-Status: No, score=-2.212 tagged_above=-999 required=5 tests=[AWL=0.387, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eun1AbMo67PZ for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2013 12:41:34 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 3455011E8202 for <ietf@ietf.org>; Wed, 3 Jul 2013 12:41:34 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id k10so5605897wiv.7 for <ietf@ietf.org>; Wed, 03 Jul 2013 12:41:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fi12SpI1LzQV0xebAJGWZs1/UM/rGdW395lsdGBPLAc=; b=OVN3XoM+bh/8uKI+nE7YxPzyKY82Td1vTE+GpnqVgw4rFmpwebAZvq183pRGMmEe/X ZwpcLAfLHmt4n0JeXKUvqsS4yWmFnPdU0TfUcM1ccWBttjbtQovnGf2u9KVcaoGa4mLV kcCaPOwRHzo8PqVPUVYgnwaRfzYyZkawi+E4FFtS4RkYzLcypjSML6Dzq1T1ei4q6V+z 5XFE1d3xx4aG9p1VHs67e+1gOlw8om1hzzUOD6S4xcSXMQH//xKXLJ6hfzHf2bxFNcjx UoR+5OTEwVpGwR3+t0a/mM/193vL9odnoLbabNOiFAkDeLRFAFximeM8juYJshLTpPmr LnVw==
MIME-Version: 1.0
X-Received: by 10.194.179.33 with SMTP id dd1mr1504132wjc.51.1372880493272; Wed, 03 Jul 2013 12:41:33 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Wed, 3 Jul 2013 12:41:33 -0700 (PDT)
In-Reply-To: <51D47C0C.3040603@qti.qualcomm.com>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com> <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net> <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com> <51D47C0C.3040603@qti.qualcomm.com>
Date: Wed, 03 Jul 2013 15:41:33 -0400
Message-ID: <CAMm+LwgpWZ6bP6Q4chfa-fOjQ3MBBfr0CW6SxzKFPnLe=cgpYA@mail.gmail.com>
Subject: Re: [IETF] Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary="089e013d0f801ee4ae04e0a0a6e1"
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 03 Jul 2013 19:41:35 -0000

+1

And don't lets forget that plenty of people have proposed schemes that WGs
have turned down and then been proven right years later.

If people are just saying what everyone else is saying here then they are
not adding any value. Rather too often WGs are started by folk seeking a
mutual appreciation society that will get through the process as quickly as
possible. They end up with a scheme that meets only the needs of the mutual
appreciation society.




On Wed, Jul 3, 2013 at 3:31 PM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> **
> On 7/3/13 1:10 PM, John C Klensin wrote:
>
> --On Wednesday, July 03, 2013 13:02 -0400 Warren Kumari<warren@kumari.net> <warren@kumari.net> wrote:
>
>
>
>  Thank you -- another worthwhile thing to do is look at who all has appealed and ask yourself "Do I really want to be part of this club?"
>
> Other than a **very** small minority of well known and well respected folk the http://www.ietf.org/iesg/appeal.html page is basically a handy kook reference.
>
>
>
> I think this is a bit overstated. There are 14 unique names of appellants
> (2 of which are groups of appellants). As I stated, 3 of those appellants
> account for 19 appeals, all denied. Perhaps you don't want to be part of
> the club with those 3 who make up 60% of the appealing, but if you simply
> remove those, you get:
>
> 13 appeals for 11 appellants (2 of them appealed twice, with years in
> between appeals)
> 1 appeal withdrawn before the IESG decided
> 6 appeals accepted
> 6 appeals denied.
>
> So the small minority are actually the repeat appealers. Of the rest, over
> half I would instantly recognize as well-known and long-time participants,
> and (without naming names) half of *those* folks were denied and half were
> accepted.
>
> So appeals that get to the level of the IESG from the group of 11 are
> accepted half of the time. That means that these folks are bringing issues
> to the IESG that, after having gone through the WG, the chairs, and the
> cognizant AD, half the time are still accepted by the IESG. That is,
> there's a 50/50 shot they've found a serious problem that the IESG agrees
> the rest of us in the IETF have missed.
>
> I'd be part of that club.
>
>
>  I am honored to be a member of that club.   Remembering that
> appeals, as others have pointed out, a mechanism for requesting
> a second look at some issue, they are an important, perhaps
> vital, part of our process.  We probably don't have enough of
> them.  Effectively telling people to not appeal because they
> will be identified as "kooks" hurts the process model by
> suppressing what might be legitimate concerns.
>
>
>
> Agreed. In any dispute process, there will be some folks who are outliers
> that make up an awful lot of the total load. But that shouldn't take away
> from those who are using it for its designed purpose.
>
>
>  In addition, it is important to note that the page does _not_
> list every appeal since 2002.  If one reads Section 6.5 of RFC
> 2026, it describes a multi-step process for appears in each of a
> collection of categories.  The web page lists only those that
> were escalated to full IESG review.
>
>
> Interestingly, 2026 6.5 only refers to things that get to the IESG, IAB,
> or ISOC BoT as "appeals". The rest of the "discussions" are simply part of
> "dispute" or "disagreement" resolution.
>
> But John's central point still stands: Most of the dispute resolution
> takes place before it ever gets to the IESG, IAB, or ISOC BoT as a formal
> appeal.
>
>
>  p.s. to any IESG members who are reading this: community
> understanding of the process might be enhanced by putting a note
> on the appeals page that is explicit about what that list
> represents, i.e., only appeals that reached full IESG review and
> not all appeals.
>
>
>
> Good idea.
>
>
> pr
>
> --
> Pete Resnick <http://www.qualcomm.com/~presnick/> <http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>


-- 
Website: http://hallambaker.com/