IETF Logo Mail Archive

Re: The IETF environment

worley@ariadne.com (Dale R. Worley) Fri, 25 April 2014 18:54 UTC

Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC1F1A0298 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 11:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OSFHRe_oj-BR for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 11:54:34 -0700 (PDT)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8641A031D for <ietf@ietf.org>; Fri, 25 Apr 2014 11:54:34 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta09.westchester.pa.mail.comcast.net with comcast id uHip1n00227AodY59JuUUt; Fri, 25 Apr 2014 18:54:28 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta19.westchester.pa.mail.comcast.net with comcast id uJuT1n00t1KKtkw3fJuTQJ; Fri, 25 Apr 2014 18:54:27 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s3PIsRII024162 for <ietf@ietf.org>; Fri, 25 Apr 2014 14:54:27 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s3PIsRld024161; Fri, 25 Apr 2014 14:54:27 -0400
Date: Fri, 25 Apr 2014 14:54:27 -0400
Message-Id: <201404251854.s3PIsRld024161@hobgoblin.ariadne.com>
From: worley@ariadne.com
Sender: worley@ariadne.com
To: ietf@ietf.org
In-reply-to: <054a01cf609b$7a186450$6e492cf0$@olddog.co.uk> (adrian@olddog.co.uk)
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <054a01cf609b$7a186450$6e492cf0$@olddog.co.uk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1398452068; bh=eq+HlogP24UQUfs77S8fGrg9pH276UqA/2GS5E1uYLk=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=LZyFyvLg0JJqSwdT+HB2AJ4+J5JTAKr/Bm/9fnhvgn9MuzqO3ah1Cd+DuiX24v9lq /GXJzjgfLn6Ce5AeGKG1NIf5LgJqgZrz2PsfL6PzWU1aTxkDop9yd9LFuk0A2BP42Z ZxpaJhwlvjLrcBTobniEiBpG8/9YJa1+JaVnFenZdg5hYu4kLa309RFxgcb/I77Ahb wJLhVbDCXJ3xv+B5AmIiF/As82acPkig/Y7rNm++2KKkLvtCJDi9AzXPesZ+Ix0Gn+ DFiLZyjBUxzYNnS6GI4yqJlHtYMQcaxOUMo2o+Q+ulIRLh4ijdFYIpcRs0xAPU/Kw8 H1liV/+GM+d1Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kciyhrGqrawtuoU03WXd1NTQJoo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 25 Apr 2014 18:54:36 -0000

> From: "Adrian Farrel" <adrian@olddog.co.uk>

> This is a handy thread and brings into question what the 'S' in IESG
> is supposed to mean.

As far as I can see, the IETF primarily develops protocols.  Work
which does not revolve around developing protocols does not happen in
the IETF.  Perpass is an example of this, because although it
*considers* pervasive monitoring, its *purpose* is the development of
protocols that are resistant to monitoring and creating an attitude
that monitoring must be considered in the development of other
protocols.  Perpass *exists* because a critical mass of people want to
work on such protocols.

In regard to the IESG, it "steers" by deciding whether or not to
charter working groups.  But its biggest job is reviewing standards
developed by the working groups.  It certainly does not "allocate
resources", that is, decide that some topic needs to be worked on and
recruit people to do the work.

Dale

v2.23.0 | Report a Bug | By Email