
From mohta@necom830.hpcl.titech.ac.jp  Sat Jun  1 02:52:01 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 98BD921F8701 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 02:52:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 hmalySwLueF6 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 02:51:56 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 2B81321F86F0 for <ietf@ietf.org>; Sat,  1 Jun 2013 02:51:55 -0700 (PDT)
Received: (qmail 46553 invoked from network); 1 Jun 2013 09:48:58 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 1 Jun 2013 09:48:58 -0000
Message-ID: <51A9C40E.9010004@necom830.hpcl.titech.ac.jp>
Date: Sat, 01 Jun 2013 18:51:10 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Not Listening to the Ops Customer
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>	<44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>	<022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>	<19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>	<m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <51A98F30.3040508@dougbarton.us>
In-Reply-To: <51A98F30.3040508@dougbarton.us>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
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: Sat, 01 Jun 2013 09:52:01 -0000

Doug Barton wrote:

> Not picking on you here, in fact I'm agreeing with you regarding the 
> early days. In '94 SLAAC/RA was a good idea, and remains a good idea for 
> "dumb" devices that only need to know their network and gateway to be 
> happy.

Wrong.

Even at that time and even on small end user LANs, it is
better to let the gateway manage the address configuration
state in centralized fashion than to have, so called, SLAAC,
which is full of address configuration state, which is
maintained in fully distributed manner involving all the nodes.

						Masataka Ohta


From abdussalambaryun@gmail.com  Sat Jun  1 03:18:49 2013
Return-Path: <abdussalambaryun@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 521BA21F88A9 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 03:18:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=0.6, 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 oGXTa6Qr7Jwz for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 03:18:48 -0700 (PDT)
Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 8900321F8825 for <ietf@ietf.org>; Sat,  1 Jun 2013 03:18:48 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id wy17so3462795pbc.9 for <ietf@ietf.org>; Sat, 01 Jun 2013 03:18:48 -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=VrbCU30ULwDwOo5jDfq6ZrO45Y1tQMFAArHyWI80L5c=; b=YLtZPVrZpyZpG9J875LlfzvMIqrCkI9JQls/O6EXPEFZrYAME0GB4AAuPxQjmPrWXX eIfp3EUR/bZ1j9SlDnEHz4l8X9O4AO2RDk91WXx5SSRZCZAiUrwmCmK7V6PXoBEzed8e QMV6uqvMUUiZnMvJFpBUgj5JkK304JgdE1+srlcdkJmjFaH5hbbZV7FucBGLO+xuW/TK Ya9hRNteONf/0aHdh5noNu6C6dn+fpf7OLldc0RNgCLKIko84kCSgQ8J+m5smVc3rcBj pI2E5yi8KFW6dVHGzJGca9SuAROCCY8dDg2nOfkFTdToel31QZZdUdQSCA7OsLsq9lYz KyDA==
MIME-Version: 1.0
X-Received: by 10.68.103.194 with SMTP id fy2mr16635998pbb.158.1370081928216;  Sat, 01 Jun 2013 03:18:48 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Sat, 1 Jun 2013 03:18:47 -0700 (PDT)
In-Reply-To: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
Date: Sat, 1 Jun 2013 12:18:47 +0200
Message-ID: <CADnDZ88jz_juwjw2JezLWR7ZosY8gO51AYpsLnLF0=XMmAZ_gA@mail.gmail.com>
Subject: Re: Time in the Air
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf Discussion <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: Sat, 01 Jun 2013 10:18:49 -0000

Thanks Mark,

This is very interesting results, it is ok if not 100% correct which I
think the error can be less than 10%, but I may have different
analysis of results. You concluded that homes in Europe had better
shortest distances to IETF meetings (assuming that thoes homes have
full participation of all meeting from 2009). Always Europe gets
better results because it is the favoriate meeting-location for ALL
businesses, but hope that IETF changes most of its meetings in Europe
which will serve all. I will post in future another message of my
opinion of a best practice of meeting locations which may become a
good I-D start (but need your assistance and your data results)

My analysis will discover that the past locations of IETF meetings
(from 2009 until now) does not serve-best the majority of full
attendance-participants of IETF from all regions. Thoes past locations
serve only regional-meeting-participants.

My analysis discovers that there is not close air-time-results when
comparing between homes/regions, the results variances between home
cities are large.

Overall, I suggest to consider the number of participants that are
full time attendance in all most meetings 90% attendance (not 75%).
Also to consider the number of past attendance of meetings in Europe
and Asia (there are large differents I think). These two
considerations will show that past locations of meetings did not serve
better the IETF but served some regional-interests. IMHO, two meetings
in Europe per year is a better practice for IETF activities.

AB

On 5/31/13, Mark Nottingham <mnot@mnot.net> wrote:
> In an attempt to inject some data into the discussion, I wrote a bit of code
> that figures out how much time, given your home city, you would have spent
> in the air if you'd attended all IETF meetings since IETF74 (i.e., from 2009
> onwards).
>
> The first column is the "home" airport.
>
> The second column is the great circle time between the home airport and the
> nearest large airport to the IETF meeting, hhh:mm. This doesn't count things
> like transit time, taxiing, takeoff and landing overhead, indirect routing,
> etc. As such, this is an ideal number; the only way to achieve anything
> close to it is to have a private jet (with exceptional range).
>
> The third column is the time (hhh:mm) using the shortest-time routing on a
> travel booking engine. This is first-takeoff-to-last-landing time.
>
> Both numbers assume round trip between "home" and the IETF airports.
>
> SFO  204:10  282:04  // San Francisco
> BOS  197:42  297:38  // Boston
> ATL  205:44  297:28  // Atlanta
> ANC  197:12  345:54  // Anchorage
> LHR  198:02  249:44  // London
> FRA  202:10  255:22  // Frankfurt
> FCO  223:52  283:04  // Rome
> SVO  211:28  287:14  // Moscow
> TLV  264:12  334:22 // Israel
> DXB  293:26  344:34 // Dubai
> NRT  259:00  314:38  // Tokyo
> HKG  296:38  359:22  // Hong Kong
> BLR  332:28  448:24  // Bangalore
> MEL  450:28  556:04  // Melbourne
> AKL  442:24  569:04  // Auckland
> JNB  414:30  498:22  // Johannesburg
> EZE  411:10  522:56  // Buenos Aires
> GIG  381:56  488:32  // Rio de Janeiro
>
> Draw your own conclusions, of course.
>
> One observation is that there's a 3+ days-in-the-air per year variance if
> you're a full-time participant, depending on where you live. I.e., more than
> one day-per-meeting difference, on average. In the air alone.
>
> Another is that, perhaps surprisingly, the "closest" homes to all meetings
> are in Europe, not the US (at least by shortest-time routing).
>
> I can run other airports upon request, as well as make source available, but
> will do so conservatively, so as not to incur the ire of the services I'm
> (ab)using.
>
> Regards,
>
> P.S. The IETF airports chosen were:
>
>   IETF_airports: [
>     "ORL",
>     "ATL",
>     "YVR",
>     "CDG",
>     "TPE",
>     "YQB",
>     "PRG",
>     "PEK",
>     "AMS",
>     "LAX",
>     "HIJ",
>     "ARN",
>     "SFO"
>   ],
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>

From warren@kumari.net  Sat Jun  1 03:39:50 2013
Return-Path: <warren@kumari.net>
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 A5E5B21F8746 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 03:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
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 D654w9mpEmfG for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 03:39:44 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7CC921F8763 for <ietf@ietf.org>; Sat,  1 Jun 2013 03:39:44 -0700 (PDT)
Received: from [10.220.22.41] (mobile-198-228-225-030.mycingular.net [198.228.225.30]) by vimes.kumari.net (Postfix) with ESMTPSA id 7F0D81B401C6; Sat,  1 Jun 2013 06:39:43 -0400 (EDT)
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <51A98F30.3040508@dougbarton.us> <51A9C40E.9010004@necom830.hpcl.titech.ac.jp>
In-Reply-To: <51A9C40E.9010004@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <99661135-EE71-4E18-B33B-156A0DDA08A4@kumari.net>
X-Mailer: iPhone Mail (10B350)
From: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Re: Not Listening to the Ops Customer
Date: Sat, 1 Jun 2013 06:39:42 -0400
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: "ietf@ietf.org" <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: Sat, 01 Jun 2013 10:39:50 -0000

Warren Kumari
------
Please excuse typing, etc -- This was sent from a device with a tiny keyboar=
d.

On Jun 1, 2013, at 5:51 AM, Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>=
 wrote:

> Doug Barton wrote:
>=20
>> Not picking on you here, in fact I'm agreeing with you regarding the=20
>> early days. In '94 SLAAC/RA was a good idea, and remains a good idea for=20=

>> "dumb" devices that only need to know their network and gateway to be=20
>> happy.
>=20
> Wrong.
>=20

Thank you for so eloquently proving Doug's point.

W

> Even at that time and even on small end user LANs, it is
> better to let the gateway manage the address configuration
> state in centralized fashion than to have, so called, SLAAC,
> which is full of address configuration state, which is
> maintained in fully distributed manner involving all the nodes.
>=20
>                        Masataka Ohta
>=20

From arturo.servin@gmail.com  Sat Jun  1 06:31:03 2013
Return-Path: <arturo.servin@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 B0C9421E80E2 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 06:31:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 VgZunISC42vB for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 06:30:57 -0700 (PDT)
Received: from mail-qe0-f48.google.com (mail-qe0-f48.google.com [209.85.128.48]) by ietfa.amsl.com (Postfix) with ESMTP id D5B9821E8152 for <ietf@ietf.org>; Sat,  1 Jun 2013 06:28:45 -0700 (PDT)
Received: by mail-qe0-f48.google.com with SMTP id 9so295103qea.21 for <ietf@ietf.org>; Sat, 01 Jun 2013 06:28:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=TSRB8g07MuzisvnMJ15QnEw0BadDhMX5kF6VVtL9oJY=; b=iCvtwk9sH0Q1aOA3Bi5W+pbpLsjKn29dqE8Jb5zQd6eqsunACH1JBBYLwP+W0cnZLz 4kTJ4dO4JP8++B4wPBliba2CM90pgwwu9asRPRzf2mkuYkVkDgCzyPKXqo5o2B3UtKQ+ E7EUyQv2LBtp3RbPe7vEhJm1Fs/wXDnldZKCLOuA0f/45wLHMnIvUvnF9hsmYrdxY6ki LRTRBB20cSj/SCGZTqu+7CWXNrdwySGcz1+T3VsRNhRPgViXWx0P709ilwJoYNtOy9JZ /Wp3PJjTUR03kDICRNAYDrl0fx6TuYUa0hfa8VGUYniGTb+JUBYFUfS4lu0CjNRkKDEH bMhw==
X-Received: by 10.224.60.7 with SMTP id n7mr12045628qah.75.1370093325151; Sat, 01 Jun 2013 06:28:45 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (r186-48-198-242.dialup.adsl.anteldata.net.uy. [186.48.198.242]) by mx.google.com with ESMTPSA id w7sm47330160qej.7.2013.06.01.06.28.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 01 Jun 2013 06:28:44 -0700 (PDT)
Message-ID: <51A9F716.9070607@gmail.com>
Date: Sat, 01 Jun 2013 10:28:54 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Not Listening to the Ops Customer
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>	<44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>	<022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>	<19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>	<m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <51A98F30.3040508@dougbarton.us> <51A9C40E.9010004@necom830.hpcl.titech.ac.jp>
In-Reply-To: <51A9C40E.9010004@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: 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: Sat, 01 Jun 2013 13:31:03 -0000

Masataka,
	
On 6/1/13 6:51 AM, Masataka Ohta wrote:
> Doug Barton wrote:
> 
>> Not picking on you here, in fact I'm agreeing with you regarding the 
>> early days. In '94 SLAAC/RA was a good idea, and remains a good idea for 
>> "dumb" devices that only need to know their network and gateway to be 
>> happy.
> 
> Wrong.
> 
> Even at that time and even on small end user LANs, it is
> better to let the gateway manage the address configuration
> state in centralized fashion than to have, so called, SLAAC,
> which is full of address configuration state, which is
> maintained in fully distributed manner involving all the nodes.
> 
> 						Masataka Ohta
> 

YMMV.

	I was working on TCP/IP, Novell and AppleTalk nets in the mid 90s and
as network engineers we hated to maintain a database of static IP
addresses for users, and we loved how AT for example was totally
automatic (IPX was in the middle because we also hated the long addresses).

	But any how, I agree with Brian that it was a good idea at that time. I
was very young and naive (I am still naive) then but I remember that I
thought that it was a plus compared to v4, but probably I would the same
applauded an automatic centric IP address management (i.e. dhcp).

	In fact, as an operator I wanted a mechanism to handle IP address
easily, not to use the mac address and avoid ARP. I guess this backs
Randy's point too.

Best regards,
as

From mohta@necom830.hpcl.titech.ac.jp  Sat Jun  1 07:26:24 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 5BC7A21F9DBE for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 07:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 aNJ+-JO1NExv for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 07:26:19 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 1AD3921F9DB5 for <ietf@ietf.org>; Sat,  1 Jun 2013 07:26:18 -0700 (PDT)
Received: (qmail 52970 invoked from network); 1 Jun 2013 14:23:21 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 1 Jun 2013 14:23:21 -0000
Message-ID: <51AA0455.5060807@necom830.hpcl.titech.ac.jp>
Date: Sat, 01 Jun 2013 23:25:25 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Not Listening to the Ops Customer
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>	<44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>	<022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>	<19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>	<m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <51A98F30.3040508@dougbarton.us> <51A9C40E.9010004@necom830.hpcl.titech.ac.jp> <51A9F716.9070607@gmail.com>
In-Reply-To: <51A9F716.9070607@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: 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: Sat, 01 Jun 2013 14:26:24 -0000

Arturo Servin wrote:

>> Even at that time and even on small end user LANs, it is
>> better to let the gateway manage the address configuration
>> state in centralized fashion than to have, so called, SLAAC,
>> which is full of address configuration state, which is
>> maintained in fully distributed manner involving all the nodes.

> YMMV.
> 
> 	I was working on TCP/IP, Novell and AppleTalk nets in the mid 90s and
> as network engineers we hated to maintain a database of static IP
> addresses for users,

I think you mean "a database of static IP addresses" DNS, not HOSTS.TXT.
Then, neither Novell nor AppleTalk enables it.

Today, with DNS dynamic update, you don't have to maintain the database
manually.

The difference is that DHCP with centralized state is a lot more
good at automatic maintenance of the database than so stateful
SLAAC with fully distributed state.

> and we loved how AT for example was totally
> automatic (IPX was in the middle because we also hated the long addresses).

So is most NAT boxes behaving as a DHCP server.

> 	But any how, I agree with Brian that it was a good idea at that time.

Not at all.

It was merely that those who had little operational insight had
thought so.

Rest of the people developed DHCP and, now, you can see which is
better.

						Masataka Ohta

From arturo.servin@gmail.com  Sat Jun  1 07:57:42 2013
Return-Path: <arturo.servin@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 0214A21F9E46 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 07:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 gln3mZNEbKmS for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 07:57:41 -0700 (PDT)
Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 789DE21F9E45 for <ietf@ietf.org>; Sat,  1 Jun 2013 07:57:41 -0700 (PDT)
Received: by mail-ve0-f174.google.com with SMTP id oz10so1872619veb.5 for <ietf@ietf.org>; Sat, 01 Jun 2013 07:57:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=6uyejyQatSgWKmvfB7m1efNxx1qY7vJ0mlDnfMleKPU=; b=A9Mej01oph2sKO03OiY+A+6c/En20PsYs04x9nK7zMlonjFjAaweMBLEANpOwE4jj6 L3ZmbUA+USqKYzrPltGqJfYB3L+3j+K6ZuJd7/pADR5rOZV2TOhiBMVixalHH7Xvqtfa rhisT98vCoT13ysk2N91Xb8TzgX1c0AFnIkw3TQ/Xj1cjOTzRw8QcAYgwP7+CKuXbflz aMQF74TwJIaMu88Asxw4X8vqIIHFV+W1zJZo/6FRe0Ir6xcdHvH+wGQzqovQ/CfHD6RA oIG9YKX/9pTjE8xB6Lsovs0oEwD2vgFC9l6wfFqW+IcZsapKcYgfu6FDbmN/qPCtWnVm tnEA==
X-Received: by 10.58.173.36 with SMTP id bh4mr14714912vec.9.1370098660890; Sat, 01 Jun 2013 07:57:40 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba30:ea19:552b:732d:15e4:51e4]) by mx.google.com with ESMTPSA id sr7sm33250700vdc.2.2013.06.01.07.57.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 01 Jun 2013 07:57:39 -0700 (PDT)
Message-ID: <51AA0BEC.3010109@gmail.com>
Date: Sat, 01 Jun 2013 11:57:48 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Not Listening to the Ops Customer
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>	<44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>	<022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>	<19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>	<m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <51A98F30.3040508@dougbarton.us> <51A9C40E.9010004@necom830.hpcl.titech.ac.jp> <51A9F716.9070607@gmail.com> <51AA0455.5060807@necom830.hpcl.titech.ac.jp>
In-Reply-To: <51AA0455.5060807@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: 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: Sat, 01 Jun 2013 14:57:42 -0000

	No, I meant a table of static ip addresses (possibly it was in excel,
db2, or any other old database) for each host so we do not configured
the same IP to two or three different hosts. It was a nightmare.

	With IPX, AT address assignment was automatic. No DHCP in those old times.

.as

On 6/1/13 11:25 AM, Masataka Ohta wrote:
>> > 	I was working on TCP/IP, Novell and AppleTalk nets in the mid 90s and
>> > as network engineers we hated to maintain a database of static IP
>> > addresses for users,
> I think you mean "a database of static IP addresses" DNS, not HOSTS.TXT.
> Then, neither Novell nor AppleTalk enables it.

From arturo.servin@gmail.com  Sat Jun  1 08:02:41 2013
Return-Path: <arturo.servin@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 AFD8421F9E8A for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 08:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 QFVASB9tgkJ8 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 08:02:32 -0700 (PDT)
Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179]) by ietfa.amsl.com (Postfix) with ESMTP id 2AF5721F9E86 for <ietf@ietf.org>; Sat,  1 Jun 2013 08:02:17 -0700 (PDT)
Received: by mail-vc0-f179.google.com with SMTP id hz10so1742566vcb.38 for <ietf@ietf.org>; Sat, 01 Jun 2013 08:02:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=MKoxoEtaYQ7oF+KyMXgC5yNKGlFAW8mYcwmDR7m5IGI=; b=mutXrmMWUSJ+cWJZV4s+6E61NA7srKNGLY+CTtX9vjP2dy0IYc150tqFRVfVvQUcXY sM6UxTt1drs7Pwb4gXLui8mujFyS06SyJYpVnjkIETP74AjtGyIxNeEjgB2iVjKId1SE N/Zpm2Se+gQn8/g9sFz7DmiEFpDFa9ewaRzIBv4ZaOZBE+/WVkNedtjE563X3emMnlsy 7FoXRXjUxk46N7o+AyLBoSWyA+2KzZmrNWE+H4dKUAHi5Pz/Vg/oVSZ+q7wXl1JHmnFE bdVSkTxfl+PVXqmYMVtjIbS77kBqP7dd4eQaRHjtlRiiynrlUR08NBqsyH30ekq2x+zp Hzlg==
X-Received: by 10.220.97.69 with SMTP id k5mr10385490vcn.47.1370098937503; Sat, 01 Jun 2013 08:02:17 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba30:ea19:552b:732d:15e4:51e4]) by mx.google.com with ESMTPSA id ho10sm39276122vdb.7.2013.06.01.08.02.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 01 Jun 2013 08:02:16 -0700 (PDT)
Message-ID: <51AA0D02.9010308@gmail.com>
Date: Sat, 01 Jun 2013 12:02:26 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Not Listening to the Ops Customer
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>	<44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>	<022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>	<19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>	<m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <51A98F30.3040508@dougbarton.us> <51A9C40E.9010004@necom830.hpcl.titech.ac.jp> <51A9F716.9070607@gmail.com> <51AA0455.5060807@necom830.hpcl.titech.ac.jp>
In-Reply-To: <51AA0455.5060807@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: 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: Sat, 01 Jun 2013 15:02:41 -0000

	Kind of.

	Those were different times. At least us we were not so preoccupied by
tracking users, accounting, etc. So a central point to record IP address
was not as important as a central port to give IP address. So both
solutions would seem useful to me at that time (as I said I was young
and naive).

	Now, it is different. DHCP it is better solution to our current needs.

Regards
as

On 6/1/13 11:25 AM, Masataka Ohta wrote:
>> But any how, I agree with Brian that it was a good idea at that time.
> Not at all.
> 
> It was merely that those who had little operational insight had
> thought so.
> 
> Rest of the people developed DHCP and, now, you can see which is
> better.

From mohta@necom830.hpcl.titech.ac.jp  Sat Jun  1 08:09:26 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 7D1CC21F9A0A for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 08:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 nQqUuz+T3wB7 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 08:09:21 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 1474D21F99E6 for <ietf@ietf.org>; Sat,  1 Jun 2013 08:09:20 -0700 (PDT)
Received: (qmail 54402 invoked from network); 1 Jun 2013 15:06:25 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 1 Jun 2013 15:06:25 -0000
Message-ID: <51AA0E60.7060401@necom830.hpcl.titech.ac.jp>
Date: Sun, 02 Jun 2013 00:08:16 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Not Listening to the Ops Customer
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>	<44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>	<022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>	<19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>	<m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <51A98F30.3040508@dougbarton.us> <51A9C40E.9010004@necom830.hpcl.titech.ac.jp> <51A9F716.9070607@gmail.com> <51AA0455.5060807@necom830.hpcl.titech.ac.jp> <51AA0BEC.3010109@gmail.com>
In-Reply-To: <51AA0BEC.3010109@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: 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: Sat, 01 Jun 2013 15:09:26 -0000

Arturo Servin wrote:

> 	No, I meant a table of static ip addresses (possibly it was in excel,
> db2, or any other old database) for each host so we do not configured
> the same IP to two or three different hosts.

So, it's like HOSTS.TXT.

> It was a nightmare.

Yes, it was.

> 	With IPX, AT address assignment was automatic. No DHCP in those old times.

That something was automatic only to produce useless (to me) results
does not mean it was a good idea.

						Masataka Ohta


From randy@psg.com  Sat Jun  1 08:09:32 2013
Return-Path: <randy@psg.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 612A821F9BB0 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 08:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 wWCVvzufARJl for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 08:09:31 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id C419F21F9B9C for <ietf@ietf.org>; Sat,  1 Jun 2013 08:09:30 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UinQv-0000d8-Rg; Sat, 01 Jun 2013 15:09:29 +0000
Date: Sat, 01 Jun 2013 08:09:29 -0700
Message-ID: <m2vc5xsw9i.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Not Listening to the Ops Customer
In-Reply-To: <51A9F716.9070607@gmail.com>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <51A98F30.3040508@dougbarton.us> <51A9C40E.9010004@necom830.hpcl.titech.ac.jp> <51A9F716.9070607@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <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: Sat, 01 Jun 2013 15:09:32 -0000

> I was working on TCP/IP, Novell and AppleTalk nets in the mid 90s and
> as network engineers we hated to maintain a database of static IP
> addresses for users, and we loved how AT for example was totally
> automatic (IPX was in the middle because we also hated the long addresses).
> 
> But any how, I agree with Brian that it was a good idea at that time. I
> was very young and naive (I am still naive) then but I remember that I
> thought that it was a plus compared to v4, but probably I would the same
> applauded an automatic centric IP address management (i.e. dhcp).
> 
> In fact, as an operator I wanted a mechanism to handle IP address
> easily, not to use the mac address and avoid ARP. I guess this backs
> Randy's point too.

i do not disagree with you, but ...

actually, i was taking no position on slaac vs dhcp.  my point was that
customers did take a position for historic reasons, dhcp in enterprise
and fixed on the wan, and having a religious argument with the customer
is not a smart business or design plan.

if we cared about success and the customer, we might have followed the
principle of least astonishment (pola) and given them dhcp and also have
pointed to the availability of the new wonderful washes your car
alternative which they might like to try.

randy

From warren@kumari.net  Sat Jun  1 08:28:40 2013
Return-Path: <warren@kumari.net>
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 F13BB21F9CF0 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 08:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.064
X-Spam-Level: 
X-Spam-Status: No, score=-101.064 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_STRONG2=1.535, USER_IN_WHITELIST=-100]
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 XuRb50gYAkhh for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 08:28:35 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 067E421F9CAA for <ietf@ietf.org>; Sat,  1 Jun 2013 08:28:34 -0700 (PDT)
Received: from [172.26.8.94] (unknown [65.114.129.62]) by vimes.kumari.net (Postfix) with ESMTPSA id E2E761B401C6; Sat,  1 Jun 2013 11:28:31 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Not Listening to the Ops Customer 
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <51A97A21.2060001@gmail.com>
Date: Sat, 1 Jun 2013 11:28:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BF16A35-39A5-4C65-8A0F-0A779E202976@kumari.net>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>	<44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>	<022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>	<19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>	<m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: John C Klensin <john-ietf@jck.com>, IETF discussion 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: Sat, 01 Jun 2013 15:28:41 -0000

On Jun 1, 2013, at 12:35 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 01/06/2013 15:00, John C Klensin wrote:
>>=20
>> --On Friday, May 31, 2013 17:23 -0700 Randy Bush <randy@psg.com>
>> wrote:
>>=20
>>> < rant >
>>>=20
>>> the sad fact is that the ietf culture is often not very good at
>>> listening to the (ops) customer.  look at the cf we have made
>>> out of ipv6.  the end user, and the op, want the absolute
>>> minimal change and cost, let me get an ipv6 allocation from
>>> the integer rental monopoly, flip a switch or two, and get 96
>>> more bits no magic.  15 years later, dhcp is still a cf, i
>>> have to run a second server (why the hell does isc not merge
>>> them?), i can not use it for finding my gateway or vrrp exit,
>>> ...  at least we got rid of the tla/nla classful insanity.  but
>>> u/g?  puhleeze.
>>=20
>> Randy,
>>=20
>> I suggest that characterizing that set of issues as IETF versus
>> Ops is probably not completely right either. =20

> It was more complicated. I was actually running a team that ran site
> network ops at the time, and (since DHCP was not yet deployable),
> IPv4 was then a serious nuisance to manage, compared say to Novell
> Netware and, even, Appletalk. There were good reasons we wanted
> stateless auto-configuration and unlimited subnet size, to mention
> two IPv6 bells and whistles. If DHCP had already been deployed,
> our opinion might have been different.
>=20

Yes, it was more complicated, but the sad part is that DHCP was widely =
deployed in V4 long before V6 was a viable transport for real work on =
the Internet. Operators kept asking for DHCP and kept being slapped down =
by zealots who refused to listen to / consider why the Ops were asking =
for this.

I *really* want to make sure that my CEO always gets the same address, =
and want him to be assigned specific DNS servers and use a certain =
gateway. The folk who manage the DHCP are the "Internal Services =
Infrastructure Group"  (aka "The windows monkeys") and I'm sure as heck =
not giving them access to my router to twiddle knobs on it. =20


>> For example, with
>> IPv6, the IETF has proposed multiple transition solutions with
>> no roadmap as to which one to apply under what circumstances and
>> growing evidence that some of those solutions are unworkable in
>> practice and others are incompatible with what are claimed to be
>> fundamental and important features of the Internet. =20
>=20
> It turns out that as soon as you envisage a network in which some
> nodes only support 32 bit addresses and other nodes can't get
> a globally unique 32 bit address, you are forced into a world
> of hurt that requires some combination of NAT, tunnels and
> dual-stack. That is completely independent of the design of
> IPng, and we knew it 1994.
>=20

Yes, hindsight always makes things *much* clearer. It also provides a =
nice sandbox to stand on=85.

Anyway, I think that going down the path of "There are warts in V6, I =
want a refund!" is not helpful. What I hope we can try and focus on is =
how we can improve understanding of what the customer (operators, users) =
actually wants, how and where the protocols of the future will be used, =
how we can incorporate changes as we get feedback and understand new =
requirements, etc.

I was not intending to point fingers (although I realize I did), but =
rather to try show places where the protocol could have improved with a =
better understanding of what folk were looking for / with more operator =
input...


> So while your criticism is valid that we collectively came up
> with too many such combinations, that collective mistake was
> (IMHO) not a result of the design of IPv6 as such. It was more
> caused by the design of human beings.


I'd go further -- some of the issue is (IMO) caused by the consensus =
driven nature of how we do things. We all have different sets of =
interests and different priorities. Because of a need to achieve =
consensus, we end in something kind of like horse-trading. We add =
features to appease some set of folk, and compromise on other bits to =
appease others. I suspect that if one or two folk had designed this, =
soup-to-nuts, we'd have ended up with something cleaner.
>=20
>> It doesn't
>> take a skilled operations person to understand that is a
>> problem; someone with a pointy head and barely enough clue to
>> figure out what a "bit" is much less how many of them are in
>> various addresses can derive a "don't be the first person on the
>> block" or "don't migrate if you can figure out an alternative"
>> lesson from that. =20
>>=20
>> Similarly, various applications folks within the IETF have
>> pointed out repeatedly that any approach that assigns multiple
>> addresses, associated with different networks and different
>> policies and properties, either requires the applications to
>> understand those policies, properties, and associated routing
>> (and blows up all of the historical application-layer APIs in
>> the process) or requires request/response negotiation that TCP
>> doesn't allow for (and blows up most of the historical
>> application-layer APIs). =20
>=20
> It's true, but to avoid that, I think we'd have to abolish
> cellular telecommunications, Wi-Fi, and competition between
> providers.

Not sure I agree.
Most apps on my iPhone seem to work just fine while I wander in and out =
of my house and move from WiFi to cellular.

As for competition between providers -- folk have been doing this with =
e.g BGP for years. Most CPE lets you easily swap between providers (by =
moving a wire :-)) and some let you share multiple by NATing (yes, I =
know, I know) some sessions to one and others to the other provider...

>=20
>> One of the original promises about
>> IPv6 was no need for changes to TCP and consequent transparency
>> to most applications.  Ha!
>=20
> Right, but again - only part of that is due to the change of
> address size and socket API details. Most of it is due to
> multiple connectivity. That was going to happen anyway.
>=20
>>=20
>> I have never been convinced that "longer addresses and nothing
>> else" was the only viable solution for IPng,=20
>=20
> Don't forget, BTW, that even "just" changing address size
> from 32 to 64 would have blown up almost every app written to
> BSD sockets (since Real Programmers Don't Use Structures and
> almost everybody used to stick addresses into uint_32).
> There never was a free lunch on the table.


Yes, IP is fundamental plumbing, and folk make assumptions about how the =
plumbing works / take shortcuts.=20
Changing fundamental plumbing is hard, and requires changes to all the =
fittings, valves, etc.

W



>=20
>   Brian
>=20
>> but I don't think
>> it requires an advanced degree in economics to understand that,
>> if the incentives to do something don't exceed the costs and
>> risks of doing it, one shouldn't expect a lot of rational folks
>> to charge off and do it.  A complex system with high deployment
>> costs and risks and a dubious set of advantages is not a story
>> that is going to sell itself.  And, again, it doesn't require a
>> sophisticated operator to figure that out.
>>=20
>> None of this takes away from your rant (or Warren's).  But I
>> suggest that, on several of the dimensions you identify, the
>> operators are not being singled out for abusive treatment
>> because we don't listen to each other or elementary
>> decision-making or economic realities either... at least where
>> broad issues, rather than fine-tuning of a spec are concerned.
>>=20
>>   john
>>=20
>>=20
>>=20
>>=20
>=20

--
There were such things as dwarf gods. Dwarfs were not a naturally =
religious species, but in a world where pit props could crack without =
warning and pockets of fire damp could suddenly explode they'd seen the =
need for gods as the sort of supernatural equivalent of a hard hat. =
Besides, when you hit your thumb with an eight-pound hammer it's nice to =
be able to blaspheme. It takes a very special and straong-minded kind of =
atheist to jump up and down with their hand clasped under their other =
armpit and shout, "Oh, random-fluctuations-in-the-space-time-continuum!" =
or "Aaargh, primitive-and-outmoded-concept on a crutch!"
  -- Terry Pratchett



From john-ietf@jck.com  Sat Jun  1 11:52:28 2013
Return-Path: <john-ietf@jck.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 1D88E21F9DFE for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 11:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 NJLLYaaWg4bn for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 11:52:22 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id F368C21F9DCC for <ietf@ietf.org>; Sat,  1 Jun 2013 11:52:21 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UiquY-0008rm-Hj; Sat, 01 Jun 2013 14:52:18 -0400
Date: Sat, 01 Jun 2013 14:52:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Not Listening to the Ops Customer
Message-ID: <60DD0E53095F833E283BBA8F@JcK-HP8200.jck.com>
In-Reply-To: <51A97A21.2060001@gmail.com>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion 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: Sat, 01 Jun 2013 18:52:28 -0000

Brian,

I really need to stop posting to this thread -- I have other
things to do and I don't believe the conversation is leading to
anything actionable.  Second-guessing is fairly useless at this
point and there are at least a few things that we know in
retrospect that we couldn't have known in 1993-1995.  I continue
to believe that many of the IPv6 impediments have been economic
and deployment policy issues that we did understand in 1993 but
didn't pay enough attention to, but some of the technical stuff
was, and is, more complicated.  On the technical side, I believe
that there was a general belief in 1993 that we would be able to
map out a unified, clear, transition strategy for IPv6 and give
simple advice about it.  In retrospect, that was probably
naive... and I believe that confused messages about transition,
especially to people who won't make their deployment  decisions
based on complex and subtle technical issues, have been part of
the problem.

More inline.

--On Saturday, June 01, 2013 16:35 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
> It was more complicated. I was actually running a team that
> ran site network ops at the time, and (since DHCP was not yet
> deployable), IPv4 was then a serious nuisance to manage,
> compared say to Novell Netware and, even, Appletalk. There
> were good reasons we wanted stateless auto-configuration and
> unlimited subnet size, to mention two IPv6 bells and whistles.
> If DHCP had already been deployed, our opinion might have been
> different.

Yes, as I think Vint says, it is always more complicated.  But
translating the above into the perspective of a decision-maker
who has to decide if, when, and how to deploy IPv6, those
requirements weren't very compelling.  Some of the organizations
that had the need were already running some member of the family
of LAN protocols in which every node continually broadcast its
identity and location, or were getting by with BOOTP.  Others
just didn't perceive the problem as a need rather than, at most,
an inconvenience.  IPv6 would have made things better, but
almost no one actually was going to convert to it for that
reason given the other costs of conversion.   Then given your
explanation, IETF came along with an IPv6-killer in the form of
DHCP and reduced the motivation further.   

The standardization and deployment of DHCP was entirely
reasonable.  But we knew that DHCP was coming -- RFC 1531 was
published several months before even the IPng solicitation in
RFC 1550 and the DHC WG had been around, IIR, some time longer
-- so assuming that the configuration issues were going to be a
major driver to IPv6 doesn't speak well for the IETF's ability
to think about and understand complete systems and relationships
among protocols a decade ago (I have no reason to claim we have
gotten either better or worse -- so much for cross-area review
at the systems, rather than nits, details, and religion, levels).

> It turns out that as soon as you envisage a network in which
> some nodes only support 32 bit addresses and other nodes can't
> get a globally unique 32 bit address, you are forced into a
> world of hurt that requires some combination of NAT, tunnels
> and dual-stack. That is completely independent of the design of
> IPng, and we knew it 1994.

Sorry, Brian.  I may just be naive, but I see a difference
between the same protocol with an extended address format and a
different protocol that coexists more or less well.   They may
be formally no different, but the transition strategy
implications are, IMO, very different in part because the former
involves only a single address space with issues accessing part
of it while the latter implies everything we have seen played
out in recent years.   In particular, one protocol with an
extended address format doesn't ever require dual stack and, for
short-form addresses, it doesn't require address translation,
just packing and unpacking.

And yes, even with a different protocol, I think rejecting the
ideas Mike O'Dell and others pushed about embedding IPv4
addresses in IPv6 ones was a significant setback from a
deployment incentives and costs standpoint.

> So while your criticism is valid that we collectively came up
> with too many such combinations, that collective mistake was
> (IMHO) not a result of the design of IPv6 as such. It was more
> caused by the design of human beings.

What you see as "design of human beings" I see as either failure
to be able to get things right the first time or two or as a
different sort of failure to understand the whole system and act
on it.  In the first case, it would imply that we didn't
understand the implications of IPv6 nearly as well as we thought
we did when we started telling people to deploy it.  In the
second... well, we have extensive debates from time to time
about the problems associated with approving competing standards
to accomplish just about the same job.  Even when we do approve
competing protocols, we usually try to insist on good
explanations of applicability.  But, unless I've missed a series
of important conversations, IPv6 conversion/ transition methods
have been largely exempt from those discussions and
requirements.  

Whatever the causes, even if they are "design of humans", the
results don't do anything positive for either the deployment of
IPv6 or the credibility of the IETF.

>...
>> Similarly, various applications folks within the IETF have
>> pointed out repeatedly that any approach that assigns multiple
>> addresses, associated with different networks and different
>> policies and properties, either requires the applications to
>> understand those policies, properties, and associated routing
>> (and blows up all of the historical application-layer APIs in
>> the process) or requires request/response negotiation that TCP
>> doesn't allow for (and blows up most of the historical
>> application-layer APIs).  
> 
> It's true, but to avoid that, I think we'd have to abolish
> cellular telecommunications, Wi-Fi, and competition between
> providers.

An interesting response.  I guess I'm still naive enough to
believe in hourglasses and IP-over-<whatever> models.  Today, my
applications absolutely do not need to know anything beyond IPv4
addresses and TCP (or UDP or RTP or...) in order to use those
physical environments today.  And, as long as there are routers
in the network --routers that can be fairly straightforward for
edge networks, even multihomed ones-- the applications don't
need to know about routing and route optimization either.

>> One of the original promises about
>> IPv6 was no need for changes to TCP and consequent
>> transparency to most applications.  Ha!
> 
> Right, but again - only part of that is due to the change of
> address size and socket API details. Most of it is due to
> multiple connectivity. That was going to happen anyway.

In the last decade or so, I've set up several multiply-connected
IPv4 LANs  with load-sharing and fall over provisions for
various people/ businesses.  I may not know much (and don't),
but I know a lot more than the SOHO-provider ISPs do and are
willing to supply.  The routing setup is simple enough that even
my rather small brain (I won't even play a routing expert on TV)
could handle it and none of these sites have PI space that they
can get routed.  They do have one-one NATs facing both LANs so
the applications don't know a thing about the connectivity
setup.  The setup isn't optimal and the routing decisions aren't
either, but it works and it would take a lot to convince me that
getting from there to optimal is worth the trouble.    For IPv6,
I've either got to replicate the setup (hence one less incentive
to convert) or I've got to deal with a significantly more
complex applications setup and teach the applications to be
routing-path-sensitive (some incentives in terms of performance,
but really high cost, especially when one includes the
observation that, if something goes wrong with the connectivity
setups that are in use now, it is possible to call the relevant
ISP and whine while the more optimized setups are ones they
don't want to support except, maybe, for large customers and
specific contractual agreements.

That problem actually does scale, at least to analogues, and
turns into another example in which we have made IPv6 and IPv6
transition a much more costly undertaking than would predict to
rapid deployment without our being able to show huge advantages
to the operators (even of small edge networks) rather than
advantages to the network (some tragedy of the commons elements
there, but we knew about that problem).

>> I have never been convinced that "longer addresses and nothing
>> else" was the only viable solution for IPng, 
> 
> Don't forget, BTW, that even "just" changing address size
> from 32 to 64 would have blown up almost every app written to
> BSD sockets (since Real Programmers Don't Use Structures and
> almost everybody used to stick addresses into uint_32).
> There never was a free lunch on the table.

Absolutely.  No change involves a free lunch and any change from
something  that is perceived as working satisfactorily (or even
nearly so) is going to require either an ability to make
commandments, a way to externalize the costs, or a fairly
serious incentive structure.   That was my key point, and
Warren's, and I think Randy's.    It may be worth noting that
those conditions were very clear when IPv4 was deployed: the
advantages of moving off the NCP environment were fairly well
understood and accepted in the community, the costs for many
installations were borne by the agencies who provided
connectivity and insisted on conversion, and it was very clear
that a flag day requirement could be imposed and enforced. 

Let me stress that, unlike some others, I'm not an IPv6-hater.
I'm painfully aware that almost any engineering design could be
made to come out differently if different design constraints
were assumed or different priorities were chosen for
optimization.  I continue to hope for IPv6 deployment and try to
think about ways to help even while I'm pessimistic about the
situation we find ourselves in and the stumbling blocks we have
allowed to rest in the path (those that we have caused and those
that come from other sources).  I don't think this is "IETF
versus the Ops" either although that may be the effect:  I think
what what Randy, Warren, and others have said about those
relationship are much more about symptoms of different
interests, criteria, and cultures then they are about
intentionally bad behavior, even though getting the assumptions
and practices about those relationships wrong may aggravate the
symptoms.  

The mistake I think we made was in not adequately considering
the transition and incentive issues as a fundamental and
critical part of the design and solution space rather than,
e.g., something that could be sorted out later as long as the
protocol was ok (or nearly so).   Sadly, I'm not at all sure we
have learned that lesson.

  best,
    john


From cb.list6@gmail.com  Sat Jun  1 13:44:53 2013
Return-Path: <cb.list6@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 8ABB021F9CA4 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 13:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 vC-9dkfJvpUy for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 13:44:51 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 0068721F9C37 for <ietf@ietf.org>; Sat,  1 Jun 2013 13:44:50 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id hn14so1709136wib.2 for <ietf@ietf.org>; Sat, 01 Jun 2013 13:44:50 -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=PPy0xTiDPxgmUjv2WQhdjQH6LqTaNJOBZXmfKzitKTA=; b=q1PpadTnCQqYYdPpI8jxkPc+bHWet343MR1uPRE8+IEW/pzW6/WJXC6znkZYXHb64z RMzZZnY2A4UnjAm7T6wz2UO7/OzeV1gO/RgEAi9ZgBrMJgtcXuDHkL1NVu9dUGZC0koh Lf0pjTEAjFeS2pVPf57SudHnLegyJZP90sFz5s63RtblkfBOoesleYZsAGbz/mPRDI0/ 5VWcadEe4goaevEJMmN+Xkg7rbVtXgJ+OguMVWeCl5eupfOsY6PEgpCT9S6sny6ZXAO3 NnaYMTXyzplxowe9qv8qQ86GHPT4f2ajp0uVucsL3dTKHWa0f/LkjklKL/OB28KctDx4 GwSg==
MIME-Version: 1.0
X-Received: by 10.194.219.198 with SMTP id pq6mr13544690wjc.58.1370119489985;  Sat, 01 Jun 2013 13:44:49 -0700 (PDT)
Received: by 10.194.56.231 with HTTP; Sat, 1 Jun 2013 13:44:49 -0700 (PDT)
Received: by 10.194.56.231 with HTTP; Sat, 1 Jun 2013 13:44:49 -0700 (PDT)
In-Reply-To: <60DD0E53095F833E283BBA8F@JcK-HP8200.jck.com>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <60DD0E53095F833E283BBA8F@JcK-HP8200.jck.com>
Date: Sat, 1 Jun 2013 13:44:49 -0700
Message-ID: <CAD6AjGR9P+_2SRj+YudK2ZNVM=nSBY_HpSW6-tXCofKHOre6KA@mail.gmail.com>
Subject: Re: Not Listening to the Ops Customer
From: "cb.list6" <cb.list6@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a11c1b4f880232304de1dcd8f
Cc: IETF-Discussion <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: Sat, 01 Jun 2013 20:44:53 -0000

--001a11c1b4f880232304de1dcd8f
Content-Type: text/plain; charset=ISO-8859-1

On Jun 1, 2013 11:52 AM, "John C Klensin" <john-ietf@jck.com> wrote:
>
> Brian,
>
> I really need to stop posting to this thread -- I have other
> things to do and I don't believe the conversation is leading to
> anything actionable.  Second-guessing is fairly useless at this
> point and there are at least a few things that we know in
> retrospect that we couldn't have known in 1993-1995.  I continue
> to believe that many of the IPv6 impediments have been economic
> and deployment policy issues that we did understand in 1993 but
> didn't pay enough attention to, but some of the technical stuff
> was, and is, more complicated.  On the technical side, I believe
> that there was a general belief in 1993 that we would be able to
> map out a unified, clear, transition strategy for IPv6 and give
> simple advice about it.  In retrospect, that was probably
> naive... and I believe that confused messages about transition,
> especially to people who won't make their deployment  decisions
> based on complex and subtle technical issues, have been part of
> the problem.
>

I think there is something here that is interesting, and that is the
interplay between paper design, evolution, and ultimately the emergent
complex dynamical system we call the internet ... which is almost
completely zero compliant to the e2e principle.  Not that e2e is the wrong
principle, but ipv4 could not support it as of 10+ years ago. Hence, nearly
every internet node is behind a stateful device (cpe or cgn nat) or server
load balancer. There is also widespread disbelief in how dns operates in
the real world (not everyone gets the same answer).

Yet, corners of the ietf call this real world internet of middleboxes as
broken. As some of it is broken, so you have things like SPDY and
ICE/STUN/TURN/464XLAT/MAP/6RD to bust through it.  Mutation happens.

That said, the teaching moment here is look back and realize the internet
was not engineered, if was emerged.

Given that the internet is not engineered and that it is a greedy
collection of self optimizing nodes that mutate, how do we make it go fast,
bigger, better given the few levers we have.

CB

> More inline.
>
> --On Saturday, June 01, 2013 16:35 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>
> >...
> > It was more complicated. I was actually running a team that
> > ran site network ops at the time, and (since DHCP was not yet
> > deployable), IPv4 was then a serious nuisance to manage,
> > compared say to Novell Netware and, even, Appletalk. There
> > were good reasons we wanted stateless auto-configuration and
> > unlimited subnet size, to mention two IPv6 bells and whistles.
> > If DHCP had already been deployed, our opinion might have been
> > different.
>
> Yes, as I think Vint says, it is always more complicated.  But
> translating the above into the perspective of a decision-maker
> who has to decide if, when, and how to deploy IPv6, those
> requirements weren't very compelling.  Some of the organizations
> that had the need were already running some member of the family
> of LAN protocols in which every node continually broadcast its
> identity and location, or were getting by with BOOTP.  Others
> just didn't perceive the problem as a need rather than, at most,
> an inconvenience.  IPv6 would have made things better, but
> almost no one actually was going to convert to it for that
> reason given the other costs of conversion.   Then given your
> explanation, IETF came along with an IPv6-killer in the form of
> DHCP and reduced the motivation further.
>
> The standardization and deployment of DHCP was entirely
> reasonable.  But we knew that DHCP was coming -- RFC 1531 was
> published several months before even the IPng solicitation in
> RFC 1550 and the DHC WG had been around, IIR, some time longer
> -- so assuming that the configuration issues were going to be a
> major driver to IPv6 doesn't speak well for the IETF's ability
> to think about and understand complete systems and relationships
> among protocols a decade ago (I have no reason to claim we have
> gotten either better or worse -- so much for cross-area review
> at the systems, rather than nits, details, and religion, levels).
>
> > It turns out that as soon as you envisage a network in which
> > some nodes only support 32 bit addresses and other nodes can't
> > get a globally unique 32 bit address, you are forced into a
> > world of hurt that requires some combination of NAT, tunnels
> > and dual-stack. That is completely independent of the design of
> > IPng, and we knew it 1994.
>
> Sorry, Brian.  I may just be naive, but I see a difference
> between the same protocol with an extended address format and a
> different protocol that coexists more or less well.   They may
> be formally no different, but the transition strategy
> implications are, IMO, very different in part because the former
> involves only a single address space with issues accessing part
> of it while the latter implies everything we have seen played
> out in recent years.   In particular, one protocol with an
> extended address format doesn't ever require dual stack and, for
> short-form addresses, it doesn't require address translation,
> just packing and unpacking.
>
> And yes, even with a different protocol, I think rejecting the
> ideas Mike O'Dell and others pushed about embedding IPv4
> addresses in IPv6 ones was a significant setback from a
> deployment incentives and costs standpoint.
>
> > So while your criticism is valid that we collectively came up
> > with too many such combinations, that collective mistake was
> > (IMHO) not a result of the design of IPv6 as such. It was more
> > caused by the design of human beings.
>
> What you see as "design of human beings" I see as either failure
> to be able to get things right the first time or two or as a
> different sort of failure to understand the whole system and act
> on it.  In the first case, it would imply that we didn't
> understand the implications of IPv6 nearly as well as we thought
> we did when we started telling people to deploy it.  In the
> second... well, we have extensive debates from time to time
> about the problems associated with approving competing standards
> to accomplish just about the same job.  Even when we do approve
> competing protocols, we usually try to insist on good
> explanations of applicability.  But, unless I've missed a series
> of important conversations, IPv6 conversion/ transition methods
> have been largely exempt from those discussions and
> requirements.
>
> Whatever the causes, even if they are "design of humans", the
> results don't do anything positive for either the deployment of
> IPv6 or the credibility of the IETF.
>
> >...
> >> Similarly, various applications folks within the IETF have
> >> pointed out repeatedly that any approach that assigns multiple
> >> addresses, associated with different networks and different
> >> policies and properties, either requires the applications to
> >> understand those policies, properties, and associated routing
> >> (and blows up all of the historical application-layer APIs in
> >> the process) or requires request/response negotiation that TCP
> >> doesn't allow for (and blows up most of the historical
> >> application-layer APIs).
> >
> > It's true, but to avoid that, I think we'd have to abolish
> > cellular telecommunications, Wi-Fi, and competition between
> > providers.
>
> An interesting response.  I guess I'm still naive enough to
> believe in hourglasses and IP-over-<whatever> models.  Today, my
> applications absolutely do not need to know anything beyond IPv4
> addresses and TCP (or UDP or RTP or...) in order to use those
> physical environments today.  And, as long as there are routers
> in the network --routers that can be fairly straightforward for
> edge networks, even multihomed ones-- the applications don't
> need to know about routing and route optimization either.
>
> >> One of the original promises about
> >> IPv6 was no need for changes to TCP and consequent
> >> transparency to most applications.  Ha!
> >
> > Right, but again - only part of that is due to the change of
> > address size and socket API details. Most of it is due to
> > multiple connectivity. That was going to happen anyway.
>
> In the last decade or so, I've set up several multiply-connected
> IPv4 LANs  with load-sharing and fall over provisions for
> various people/ businesses.  I may not know much (and don't),
> but I know a lot more than the SOHO-provider ISPs do and are
> willing to supply.  The routing setup is simple enough that even
> my rather small brain (I won't even play a routing expert on TV)
> could handle it and none of these sites have PI space that they
> can get routed.  They do have one-one NATs facing both LANs so
> the applications don't know a thing about the connectivity
> setup.  The setup isn't optimal and the routing decisions aren't
> either, but it works and it would take a lot to convince me that
> getting from there to optimal is worth the trouble.    For IPv6,
> I've either got to replicate the setup (hence one less incentive
> to convert) or I've got to deal with a significantly more
> complex applications setup and teach the applications to be
> routing-path-sensitive (some incentives in terms of performance,
> but really high cost, especially when one includes the
> observation that, if something goes wrong with the connectivity
> setups that are in use now, it is possible to call the relevant
> ISP and whine while the more optimized setups are ones they
> don't want to support except, maybe, for large customers and
> specific contractual agreements.
>
> That problem actually does scale, at least to analogues, and
> turns into another example in which we have made IPv6 and IPv6
> transition a much more costly undertaking than would predict to
> rapid deployment without our being able to show huge advantages
> to the operators (even of small edge networks) rather than
> advantages to the network (some tragedy of the commons elements
> there, but we knew about that problem).
>
> >> I have never been convinced that "longer addresses and nothing
> >> else" was the only viable solution for IPng,
> >
> > Don't forget, BTW, that even "just" changing address size
> > from 32 to 64 would have blown up almost every app written to
> > BSD sockets (since Real Programmers Don't Use Structures and
> > almost everybody used to stick addresses into uint_32).
> > There never was a free lunch on the table.
>
> Absolutely.  No change involves a free lunch and any change from
> something  that is perceived as working satisfactorily (or even
> nearly so) is going to require either an ability to make
> commandments, a way to externalize the costs, or a fairly
> serious incentive structure.   That was my key point, and
> Warren's, and I think Randy's.    It may be worth noting that
> those conditions were very clear when IPv4 was deployed: the
> advantages of moving off the NCP environment were fairly well
> understood and accepted in the community, the costs for many
> installations were borne by the agencies who provided
> connectivity and insisted on conversion, and it was very clear
> that a flag day requirement could be imposed and enforced.
>
> Let me stress that, unlike some others, I'm not an IPv6-hater.
> I'm painfully aware that almost any engineering design could be
> made to come out differently if different design constraints
> were assumed or different priorities were chosen for
> optimization.  I continue to hope for IPv6 deployment and try to
> think about ways to help even while I'm pessimistic about the
> situation we find ourselves in and the stumbling blocks we have
> allowed to rest in the path (those that we have caused and those
> that come from other sources).  I don't think this is "IETF
> versus the Ops" either although that may be the effect:  I think
> what what Randy, Warren, and others have said about those
> relationship are much more about symptoms of different
> interests, criteria, and cultures then they are about
> intentionally bad behavior, even though getting the assumptions
> and practices about those relationships wrong may aggravate the
> symptoms.
>
> The mistake I think we made was in not adequately considering
> the transition and incentive issues as a fundamental and
> critical part of the design and solution space rather than,
> e.g., something that could be sorted out later as long as the
> protocol was ok (or nearly so).   Sadly, I'm not at all sure we
> have learned that lesson.
>
>   best,
>     john
>

--001a11c1b4f880232304de1dcd8f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On Jun 1, 2013 11:52 AM, &quot;John C Klensin&quot; &lt;<a href=3D"mailto:j=
ohn-ietf@jck.com">john-ietf@jck.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Brian,<br>
&gt;<br>
&gt; I really need to stop posting to this thread -- I have other<br>
&gt; things to do and I don&#39;t believe the conversation is leading to<br=
>
&gt; anything actionable. =A0Second-guessing is fairly useless at this<br>
&gt; point and there are at least a few things that we know in<br>
&gt; retrospect that we couldn&#39;t have known in 1993-1995. =A0I continue=
<br>
&gt; to believe that many of the IPv6 impediments have been economic<br>
&gt; and deployment policy issues that we did understand in 1993 but<br>
&gt; didn&#39;t pay enough attention to, but some of the technical stuff<br=
>
&gt; was, and is, more complicated. =A0On the technical side, I believe<br>
&gt; that there was a general belief in 1993 that we would be able to<br>
&gt; map out a unified, clear, transition strategy for IPv6 and give<br>
&gt; simple advice about it. =A0In retrospect, that was probably<br>
&gt; naive... and I believe that confused messages about transition,<br>
&gt; especially to people who won&#39;t make their deployment =A0decisions<=
br>
&gt; based on complex and subtle technical issues, have been part of<br>
&gt; the problem.<br>
&gt;</p>
<p dir=3D"ltr">I think there is something here that is interesting, and tha=
t is the interplay between paper design, evolution, and ultimately the emer=
gent complex dynamical system we call the internet ... which is almost comp=
letely zero compliant to the e2e principle.=A0 Not that e2e is the wrong pr=
inciple, but ipv4 could not support it as of 10+ years ago. Hence, nearly e=
very internet node is behind a stateful device (cpe or cgn nat) or server l=
oad balancer. There is also widespread disbelief in how dns operates in the=
 real world (not everyone gets the same answer).</p>

<p dir=3D"ltr">Yet, corners of the ietf call this real world internet of mi=
ddleboxes as broken. As some of it is broken, so you have things like SPDY =
and ICE/STUN/TURN/464XLAT/MAP/6RD to bust through it.=A0 Mutation happens. =
</p>

<p dir=3D"ltr">That said, the teaching moment here is look back and realize=
 the internet was not engineered, if was emerged.</p>
<p dir=3D"ltr">Given that the internet is not engineered and that it is a g=
reedy collection of self optimizing nodes that mutate, how do we make it go=
 fast, bigger, better given the few levers we have.</p>
<p dir=3D"ltr">CB</p>
<p dir=3D"ltr">&gt; More inline.<br>
&gt;<br>
&gt; --On Saturday, June 01, 2013 16:35 +1200 Brian E Carpenter<br>
&gt; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@g=
mail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt;...<br>
&gt; &gt; It was more complicated. I was actually running a team that<br>
&gt; &gt; ran site network ops at the time, and (since DHCP was not yet<br>
&gt; &gt; deployable), IPv4 was then a serious nuisance to manage,<br>
&gt; &gt; compared say to Novell Netware and, even, Appletalk. There<br>
&gt; &gt; were good reasons we wanted stateless auto-configuration and<br>
&gt; &gt; unlimited subnet size, to mention two IPv6 bells and whistles.<br=
>
&gt; &gt; If DHCP had already been deployed, our opinion might have been<br=
>
&gt; &gt; different.<br>
&gt;<br>
&gt; Yes, as I think Vint says, it is always more complicated. =A0But<br>
&gt; translating the above into the perspective of a decision-maker<br>
&gt; who has to decide if, when, and how to deploy IPv6, those<br>
&gt; requirements weren&#39;t very compelling. =A0Some of the organizations=
<br>
&gt; that had the need were already running some member of the family<br>
&gt; of LAN protocols in which every node continually broadcast its<br>
&gt; identity and location, or were getting by with BOOTP. =A0Others<br>
&gt; just didn&#39;t perceive the problem as a need rather than, at most,<b=
r>
&gt; an inconvenience. =A0IPv6 would have made things better, but<br>
&gt; almost no one actually was going to convert to it for that<br>
&gt; reason given the other costs of conversion. =A0 Then given your<br>
&gt; explanation, IETF came along with an IPv6-killer in the form of<br>
&gt; DHCP and reduced the motivation further.<br>
&gt;<br>
&gt; The standardization and deployment of DHCP was entirely<br>
&gt; reasonable. =A0But we knew that DHCP was coming -- RFC 1531 was<br>
&gt; published several months before even the IPng solicitation in<br>
&gt; RFC 1550 and the DHC WG had been around, IIR, some time longer<br>
&gt; -- so assuming that the configuration issues were going to be a<br>
&gt; major driver to IPv6 doesn&#39;t speak well for the IETF&#39;s ability=
<br>
&gt; to think about and understand complete systems and relationships<br>
&gt; among protocols a decade ago (I have no reason to claim we have<br>
&gt; gotten either better or worse -- so much for cross-area review<br>
&gt; at the systems, rather than nits, details, and religion, levels).<br>
&gt;<br>
&gt; &gt; It turns out that as soon as you envisage a network in which<br>
&gt; &gt; some nodes only support 32 bit addresses and other nodes can&#39;=
t<br>
&gt; &gt; get a globally unique 32 bit address, you are forced into a<br>
&gt; &gt; world of hurt that requires some combination of NAT, tunnels<br>
&gt; &gt; and dual-stack. That is completely independent of the design of<b=
r>
&gt; &gt; IPng, and we knew it 1994.<br>
&gt;<br>
&gt; Sorry, Brian. =A0I may just be naive, but I see a difference<br>
&gt; between the same protocol with an extended address format and a<br>
&gt; different protocol that coexists more or less well. =A0 They may<br>
&gt; be formally no different, but the transition strategy<br>
&gt; implications are, IMO, very different in part because the former<br>
&gt; involves only a single address space with issues accessing part<br>
&gt; of it while the latter implies everything we have seen played<br>
&gt; out in recent years. =A0 In particular, one protocol with an<br>
&gt; extended address format doesn&#39;t ever require dual stack and, for<b=
r>
&gt; short-form addresses, it doesn&#39;t require address translation,<br>
&gt; just packing and unpacking.<br>
&gt;<br>
&gt; And yes, even with a different protocol, I think rejecting the<br>
&gt; ideas Mike O&#39;Dell and others pushed about embedding IPv4<br>
&gt; addresses in IPv6 ones was a significant setback from a<br>
&gt; deployment incentives and costs standpoint.<br>
&gt;<br>
&gt; &gt; So while your criticism is valid that we collectively came up<br>
&gt; &gt; with too many such combinations, that collective mistake was<br>
&gt; &gt; (IMHO) not a result of the design of IPv6 as such. It was more<br=
>
&gt; &gt; caused by the design of human beings.<br>
&gt;<br>
&gt; What you see as &quot;design of human beings&quot; I see as either fai=
lure<br>
&gt; to be able to get things right the first time or two or as a<br>
&gt; different sort of failure to understand the whole system and act<br>
&gt; on it. =A0In the first case, it would imply that we didn&#39;t<br>
&gt; understand the implications of IPv6 nearly as well as we thought<br>
&gt; we did when we started telling people to deploy it. =A0In the<br>
&gt; second... well, we have extensive debates from time to time<br>
&gt; about the problems associated with approving competing standards<br>
&gt; to accomplish just about the same job. =A0Even when we do approve<br>
&gt; competing protocols, we usually try to insist on good<br>
&gt; explanations of applicability. =A0But, unless I&#39;ve missed a series=
<br>
&gt; of important conversations, IPv6 conversion/ transition methods<br>
&gt; have been largely exempt from those discussions and<br>
&gt; requirements.<br>
&gt;<br>
&gt; Whatever the causes, even if they are &quot;design of humans&quot;, th=
e<br>
&gt; results don&#39;t do anything positive for either the deployment of<br=
>
&gt; IPv6 or the credibility of the IETF.<br>
&gt;<br>
&gt; &gt;...<br>
&gt; &gt;&gt; Similarly, various applications folks within the IETF have<br=
>
&gt; &gt;&gt; pointed out repeatedly that any approach that assigns multipl=
e<br>
&gt; &gt;&gt; addresses, associated with different networks and different<b=
r>
&gt; &gt;&gt; policies and properties, either requires the applications to<=
br>
&gt; &gt;&gt; understand those policies, properties, and associated routing=
<br>
&gt; &gt;&gt; (and blows up all of the historical application-layer APIs in=
<br>
&gt; &gt;&gt; the process) or requires request/response negotiation that TC=
P<br>
&gt; &gt;&gt; doesn&#39;t allow for (and blows up most of the historical<br=
>
&gt; &gt;&gt; application-layer APIs).<br>
&gt; &gt;<br>
&gt; &gt; It&#39;s true, but to avoid that, I think we&#39;d have to abolis=
h<br>
&gt; &gt; cellular telecommunications, Wi-Fi, and competition between<br>
&gt; &gt; providers.<br>
&gt;<br>
&gt; An interesting response. =A0I guess I&#39;m still naive enough to<br>
&gt; believe in hourglasses and IP-over-&lt;whatever&gt; models. =A0Today, =
my<br>
&gt; applications absolutely do not need to know anything beyond IPv4<br>
&gt; addresses and TCP (or UDP or RTP or...) in order to use those<br>
&gt; physical environments today. =A0And, as long as there are routers<br>
&gt; in the network --routers that can be fairly straightforward for<br>
&gt; edge networks, even multihomed ones-- the applications don&#39;t<br>
&gt; need to know about routing and route optimization either.<br>
&gt;<br>
&gt; &gt;&gt; One of the original promises about<br>
&gt; &gt;&gt; IPv6 was no need for changes to TCP and consequent<br>
&gt; &gt;&gt; transparency to most applications. =A0Ha!<br>
&gt; &gt;<br>
&gt; &gt; Right, but again - only part of that is due to the change of<br>
&gt; &gt; address size and socket API details. Most of it is due to<br>
&gt; &gt; multiple connectivity. That was going to happen anyway.<br>
&gt;<br>
&gt; In the last decade or so, I&#39;ve set up several multiply-connected<b=
r>
&gt; IPv4 LANs =A0with load-sharing and fall over provisions for<br>
&gt; various people/ businesses. =A0I may not know much (and don&#39;t),<br=
>
&gt; but I know a lot more than the SOHO-provider ISPs do and are<br>
&gt; willing to supply. =A0The routing setup is simple enough that even<br>
&gt; my rather small brain (I won&#39;t even play a routing expert on TV)<b=
r>
&gt; could handle it and none of these sites have PI space that they<br>
&gt; can get routed. =A0They do have one-one NATs facing both LANs so<br>
&gt; the applications don&#39;t know a thing about the connectivity<br>
&gt; setup. =A0The setup isn&#39;t optimal and the routing decisions aren&#=
39;t<br>
&gt; either, but it works and it would take a lot to convince me that<br>
&gt; getting from there to optimal is worth the trouble. =A0 =A0For IPv6,<b=
r>
&gt; I&#39;ve either got to replicate the setup (hence one less incentive<b=
r>
&gt; to convert) or I&#39;ve got to deal with a significantly more<br>
&gt; complex applications setup and teach the applications to be<br>
&gt; routing-path-sensitive (some incentives in terms of performance,<br>
&gt; but really high cost, especially when one includes the<br>
&gt; observation that, if something goes wrong with the connectivity<br>
&gt; setups that are in use now, it is possible to call the relevant<br>
&gt; ISP and whine while the more optimized setups are ones they<br>
&gt; don&#39;t want to support except, maybe, for large customers and<br>
&gt; specific contractual agreements.<br>
&gt;<br>
&gt; That problem actually does scale, at least to analogues, and<br>
&gt; turns into another example in which we have made IPv6 and IPv6<br>
&gt; transition a much more costly undertaking than would predict to<br>
&gt; rapid deployment without our being able to show huge advantages<br>
&gt; to the operators (even of small edge networks) rather than<br>
&gt; advantages to the network (some tragedy of the commons elements<br>
&gt; there, but we knew about that problem).<br>
&gt;<br>
&gt; &gt;&gt; I have never been convinced that &quot;longer addresses and n=
othing<br>
&gt; &gt;&gt; else&quot; was the only viable solution for IPng,<br>
&gt; &gt;<br>
&gt; &gt; Don&#39;t forget, BTW, that even &quot;just&quot; changing addres=
s size<br>
&gt; &gt; from 32 to 64 would have blown up almost every app written to<br>
&gt; &gt; BSD sockets (since Real Programmers Don&#39;t Use Structures and<=
br>
&gt; &gt; almost everybody used to stick addresses into uint_32).<br>
&gt; &gt; There never was a free lunch on the table.<br>
&gt;<br>
&gt; Absolutely. =A0No change involves a free lunch and any change from<br>
&gt; something =A0that is perceived as working satisfactorily (or even<br>
&gt; nearly so) is going to require either an ability to make<br>
&gt; commandments, a way to externalize the costs, or a fairly<br>
&gt; serious incentive structure. =A0 That was my key point, and<br>
&gt; Warren&#39;s, and I think Randy&#39;s. =A0 =A0It may be worth noting t=
hat<br>
&gt; those conditions were very clear when IPv4 was deployed: the<br>
&gt; advantages of moving off the NCP environment were fairly well<br>
&gt; understood and accepted in the community, the costs for many<br>
&gt; installations were borne by the agencies who provided<br>
&gt; connectivity and insisted on conversion, and it was very clear<br>
&gt; that a flag day requirement could be imposed and enforced.<br>
&gt;<br>
&gt; Let me stress that, unlike some others, I&#39;m not an IPv6-hater.<br>
&gt; I&#39;m painfully aware that almost any engineering design could be<br=
>
&gt; made to come out differently if different design constraints<br>
&gt; were assumed or different priorities were chosen for<br>
&gt; optimization. =A0I continue to hope for IPv6 deployment and try to<br>
&gt; think about ways to help even while I&#39;m pessimistic about the<br>
&gt; situation we find ourselves in and the stumbling blocks we have<br>
&gt; allowed to rest in the path (those that we have caused and those<br>
&gt; that come from other sources). =A0I don&#39;t think this is &quot;IETF=
<br>
&gt; versus the Ops&quot; either although that may be the effect: =A0I thin=
k<br>
&gt; what what Randy, Warren, and others have said about those<br>
&gt; relationship are much more about symptoms of different<br>
&gt; interests, criteria, and cultures then they are about<br>
&gt; intentionally bad behavior, even though getting the assumptions<br>
&gt; and practices about those relationships wrong may aggravate the<br>
&gt; symptoms.<br>
&gt;<br>
&gt; The mistake I think we made was in not adequately considering<br>
&gt; the transition and incentive issues as a fundamental and<br>
&gt; critical part of the design and solution space rather than,<br>
&gt; e.g., something that could be sorted out later as long as the<br>
&gt; protocol was ok (or nearly so). =A0 Sadly, I&#39;m not at all sure we<=
br>
&gt; have learned that lesson.<br>
&gt;<br>
&gt; =A0 best,<br>
&gt; =A0 =A0 john<br>
&gt;<br>
</p>

--001a11c1b4f880232304de1dcd8f--

From mohta@necom830.hpcl.titech.ac.jp  Sat Jun  1 14:41:51 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 4034A21F9E1E for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 14:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 DUN3a3rsGI7S for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 14:41:46 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id C443821F9DD0 for <ietf@ietf.org>; Sat,  1 Jun 2013 14:41:43 -0700 (PDT)
Received: (qmail 63183 invoked from network); 1 Jun 2013 21:38:48 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 1 Jun 2013 21:38:48 -0000
Message-ID: <51AA6A7F.9090100@necom830.hpcl.titech.ac.jp>
Date: Sun, 02 Jun 2013 06:41:19 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Not Listening to the Ops Customer
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>	<44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>	<022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>	<19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>	<m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <51A98F30.3040508@dougbarton.us> <51A9C40E.9010004@necom830.hpcl.titech.ac.jp> <51A9F716.9070607@gmail.com> <51AA0455.5060807@necom830.hpcl.titech.ac.jp> <51AA0D02.9010308@gmail.com>
In-Reply-To: <51AA0D02.9010308@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: 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: Sat, 01 Jun 2013 21:41:51 -0000

Arturo Servin wrote:

> 	Those were different times. At least us we were not so preoccupied by
> tracking users, accounting, etc. So a central point to record IP address
> was not as important as a central port to give IP address.

A merit to have the central server is that you don't have to
waste time and packets to have DAD, with additional overehead
of IGMP, to confirm all the distributed nodes maintaining the
state of SLAAC consistently, that is, a new configured address
is unique.

						Masataka Ohta


From mohta@necom830.hpcl.titech.ac.jp  Sat Jun  1 15:06:38 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 C45FE21F9E23 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 15:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 vepkn85DfM3P for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 15:06:31 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 40FAA21F9E21 for <ietf@ietf.org>; Sat,  1 Jun 2013 15:06:29 -0700 (PDT)
Received: (qmail 64217 invoked from network); 1 Jun 2013 22:03:31 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 1 Jun 2013 22:03:31 -0000
Message-ID: <51AA7046.20005@necom830.hpcl.titech.ac.jp>
Date: Sun, 02 Jun 2013 07:05:58 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Not Listening to the Ops Customer
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <60DD0E53095F833E283BBA8F@JcK-HP8200.jck.com> <CAD6AjGR9P+_2SRj+YudK2ZNVM=nSBY_HpSW6-tXCofKHOre6KA@mail.gmail.com>
In-Reply-To: <CAD6AjGR9P+_2SRj+YudK2ZNVM=nSBY_HpSW6-tXCofKHOre6KA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
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: Sat, 01 Jun 2013 22:06:38 -0000

cb.list6 wrote:

> I think there is something here that is interesting, and that is the
> interplay between paper design, evolution, and ultimately the emergent
> complex dynamical system we call the internet ... which is almost
> completely zero compliant to the e2e principle.  Not that e2e is the wrong
> principle, but ipv4 could not support it as of 10+ years ago.

As long as a NAT box is directly connected to the Internet
and is UPnP capable, which is the case at my home, hosts
behind it can enjoy full end to end transparency (PORT
command of FTP works), if hosts' IP and transport stack is
modified a little.

> Hence, nearly
> every internet node is behind a stateful device (cpe or cgn nat)

That is not a problem if state of the device is known to
the end, because IP and transport stack of the end
can reverse the translation.

See draft-ohta-e2e-nat-00.txt for details.

> or server
> load balancer. There is also widespread disbelief in how dns operates in
> the real world (not everyone gets the same answer).

It has nothing to do with the end to end transparency.

If operators of the servers think any server is fine, it is not
a problem.

						Masataka Ohta
>

From abdussalambaryun@gmail.com  Sat Jun  1 21:48:31 2013
Return-Path: <abdussalambaryun@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 2227921F9B35; Sat,  1 Jun 2013 21:48:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 zJIXagBSVQ+6; Sat,  1 Jun 2013 21:48:27 -0700 (PDT)
Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.171]) by ietfa.amsl.com (Postfix) with ESMTP id E447E21F9B2B; Sat,  1 Jun 2013 21:48:26 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id z11so4152254pdj.30 for <multiple recipients>; Sat, 01 Jun 2013 21:48:26 -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=46FNUiHg6T4xnSiGfvj1M7Jg/BJEX1/VZ36WdVt3piU=; b=kItGcP9+EsBmrLKo1fTkhJ7knGG7oFgNUdCFeDXtWKkOG8619JesoiJVJJG5lsEbDk VloeDlBnD3nubzaT5iZatsZTviE8no5dIlcmej4UPKrJNSyd5/Ek80wwRcoKg7D4qjp6 zfsGdKNJmcVedX/pMUAcvHQtWhztGesVt8FQISRoFTou1yfKLHyppzG1er44ZzObin7W N8xjam1yK5lJaUCnXop+RN7aSGIjZ7HV8c6S3aeSDSKDetWUT0K/1JA/e32KKDbXjdmq l86lZMZJUwY2scfg5ma4UIUCCBT8kdisl+zP74n3rEwJzn50U0vfsWEnbmgh04tkWnsk fTFQ==
MIME-Version: 1.0
X-Received: by 10.68.125.227 with SMTP id mt3mr19618332pbb.153.1370148506592;  Sat, 01 Jun 2013 21:48:26 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Sat, 1 Jun 2013 21:48:26 -0700 (PDT)
In-Reply-To: <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com>
Date: Sun, 2 Jun 2013 06:48:26 +0200
Message-ID: <CADnDZ89BMkpQd2Z8MmCmnUdp0uD6v8Vrbq-z5JeerfiuqpPW0w@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iesg@ietf.org" <iesg@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: Sun, 02 Jun 2013 04:48:31 -0000

Continue Reply to your request dated 24/05/2013
Draft Reviewed By: Abdussalam Baryun (AB)    Dated:02/06/2013
Reviewed I-D: draft-ietf-manet-nhdp-sec-threats-03
Reviewer Comment A2: Referencing the NHDP and related to RFC6130
++++++++++++++++++++++++++++++++++++++++++++++++++

I think if we got an effort in IETF to update NHDP [RFC6130] as draft
[1] does, why this reviewed I-D of threats does not include [1] in its
references to be reviewed before reviewing this NHDP-threat I-D? I
suggest to include draft [1] in References section, IMHO, any updates
to RFC6130 should be considered by the community while reviewing this
I-D.

[1] draft-ietf-manet-nhdp-olsrv2-sec-02

AB

> On 5/24/13, The IESG <iesg-secretary@ietf.org> wrote:
>>
>> The IESG has received a request from the Mobile Ad-hoc Networks WG
>> (manet) to consider the following document:
>> - 'Security Threats for NHDP'
>>   <draft-ietf-manet-nhdp-sec-threats-03.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-06-06. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>    This document analyses common security threats of the Neighborhood
>>    Discovery Protocol (NHDP), and describes their potential impacts on
>>    MANET routing protocols using NHDP.
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>
>

From jcurran@istaff.org  Sat Jun  1 23:42:00 2013
Return-Path: <jcurran@istaff.org>
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 2D29621F9F84 for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 23:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 MT-Pjx1DfJVa for <ietf@ietfa.amsl.com>; Sat,  1 Jun 2013 23:41:54 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id F19A721F9F8C for <ietf@ietf.org>; Sat,  1 Jun 2013 23:41:50 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1Uj1zC-000ET6-BK for ietf@ietf.org; Sun, 02 Jun 2013 06:41:50 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/eI4PWMshp+6YqgMmPA7Fb
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Not Listening to the Ops Customer
From: John Curran <jcurran@istaff.org>
In-Reply-To: <60DD0E53095F833E283BBA8F@JcK-HP8200.jck.com>
Date: Sun, 2 Jun 2013 02:41:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F70579B-B91A-4CB1-B0F5-41FCD7C3F922@istaff.org>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <60DD0E53095F833E283BBA8F@JcK-HP8200.jck.com>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
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: Sun, 02 Jun 2013 06:42:00 -0000

On Jun 1, 2013, at 2:52 PM, John C Klensin <john-ietf@jck.com> wrote:
> On the technical side, I believe that there was a general belief
> in 1993 that we would be able to map out a unified, clear, transition
> strategy for IPv6 and give simple advice about it. =20

John is correct in terms of belief (but perhaps a bit early on date), as=20=

the IPng decision was specifically predicated upon us being able to =
explain=20
shortly thereafter "what mechanisms will be employed in the transition, =
how=20
the transition will work, the assumptions about infrastructure =
deployment=20
inherent in the operation of these mechanisms, and the types of =
functionality=20
that applications developers will be able to assume as the protocol mix=20=

changes over time." (RFC 1752 "The Recommendation for the IP Next =
Generation=20
Protocol", January 1995)

The fact that the fundamental architecture of IPng could be selected =
before
the transition strategy was settled is clear proof of the very point =
Randy=20
was making with respect to the IETF not listening to the operations =
customer,=20
as no one running production Internet service could have agreed to =
proceed=20
with a new _incompatible_ version of the Internet protocol absent a =
well-
documented transition/interoperability strategy.  This disconnect is not=20=

solely the fault of the IETF, it is definitely shared with the operator=20=

community who have more pressing and immediate demands on their time =
than=20
trying to cover IETF activities as risk mitigation against new =
developments=20
which aren't likely to impact their business for years to come.  (In =
fact,=20
it should probably be more surprising that there are any service =
providers=20
who attempt to stay informed about IETF efforts, given the difficulty of=20=

covering the range of IETF activities and the very long-term timeline =
for=20
any potential benefit from the investment.)

The reality is that there are not a lot of places where _one_ =
architecture
is needed; i.e. in general, it's fine to "let a hundred flowers blossom"
with a myriad of alternative working groups with vendors promoting =
various
competing drafts to solve a given problem. However, we can't lose sight =
of
the fact that there are also areas that are fundamentally architectural =
in
nature, with far-reaching and long-lasting impact on the Internet (e.g. =
the
IP protocol itself, TCP, DNS, etc.) where there truly needs to be just =
one
solution for any given problem space.  When dealing with such cases of =
the
fundamental architecture of the Internet, the IETF needs to go above and=20=

beyond in making sure its reaching out to the actual operator community=20=

and dealing with the actual problems that they face with these =
protocols.
I'd suggest seeking out operators with significant "skin in the game" =
and=20
interest in joining the effort before spinning up new working groups for=20=

protocols in these key architectural areas.  If you can't find a service=20=

provider interested enough to participate, then that is likely sign that=20=

the work may not actually be needed...

It would also help if there was a general acceptance that the IETF =
should
be far more rigorous when dealing with these core protocols, and set =
very=20
high standards before deciding to making any changes.  In the case of =
IPng,=20
we jumped on a solution that was neither fully defined nor focused on =
what
operational networks actually needed; the result has been quite painful=20=

but hopefully will not prove fatal for the Internet in the coming years.

FYI,
/John

Disclaimers:  My views alone.  As a member of the IPng directorate at =
the
time, I do share in responsibility for the recommendation of IPng as the=20=

new Internet Protocol despite its lack of focus on actual service =
provider
functionality and the transition/interoperability mechanism left as an =
open=20
work item. I believe that critical examination of the past is essential =
to=20
improvement, and in this particular case the pain involved in reflection=20=

is well worth it if the IETF gains as a result.


From l.wood@surrey.ac.uk  Sun Jun  2 00:39:34 2013
Return-Path: <l.wood@surrey.ac.uk>
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 B4D5021F9F28 for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 00:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level: 
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=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 cIqj-32v9ODV for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 00:39:30 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.105]) by ietfa.amsl.com (Postfix) with ESMTP id 956A621F9EBB for <ietf@ietf.org>; Sun,  2 Jun 2013 00:39:29 -0700 (PDT)
Received: from [193.109.255.147:28584] by server-1.bemta-14.messagelabs.com id 1B/25-06919-0B6FAA15; Sun, 02 Jun 2013 07:39:28 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-72.messagelabs.com!1370158767!8819893!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26607 invoked from network); 2 Jun 2013 07:39:27 -0000
Received: from unknown (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-6.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 2 Jun 2013 07:39:27 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Sun, 2 Jun 2013 08:39:27 +0100
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>, <mnot@mnot.net>
Date: Sun, 2 Jun 2013 08:38:29 +0100
Subject: RE: Time in the Air
Thread-Topic: Time in the Air
Thread-Index: Ac5esXuDd6qbW2tWT8KAIuNvQ1mK9wAsrGnA
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E9C@EXMB01CMS.surrey.ac.uk>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>, <CADnDZ88jz_juwjw2JezLWR7ZosY8gO51AYpsLnLF0=XMmAZ_gA@mail.gmail.com>
In-Reply-To: <CADnDZ88jz_juwjw2JezLWR7ZosY8gO51AYpsLnLF0=XMmAZ_gA@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 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: Sun, 02 Jun 2013 07:39:34 -0000

"Always Europe gets better results because it is the favoriate meeting-loca=
tion for ALL
businesses"

{{citation needed}}

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Abdussalam=
 Baryun [abdussalambaryun@gmail.com]
Sent: 01 June 2013 11:18
To: Mark Nottingham
Cc: ietf Discussion
Subject: Re: Time in the Air

Thanks Mark,

This is very interesting results, it is ok if not 100% correct which I
think the error can be less than 10%, but I may have different
analysis of results. You concluded that homes in Europe had better
shortest distances to IETF meetings (assuming that thoes homes have
full participation of all meeting from 2009). Always Europe gets
better results because it is the favoriate meeting-location for ALL
businesses, but hope that IETF changes most of its meetings in Europe
which will serve all. I will post in future another message of my
opinion of a best practice of meeting locations which may become a
good I-D start (but need your assistance and your data results)

My analysis will discover that the past locations of IETF meetings
(from 2009 until now) does not serve-best the majority of full
attendance-participants of IETF from all regions. Thoes past locations
serve only regional-meeting-participants.

My analysis discovers that there is not close air-time-results when
comparing between homes/regions, the results variances between home
cities are large.

Overall, I suggest to consider the number of participants that are
full time attendance in all most meetings 90% attendance (not 75%).
Also to consider the number of past attendance of meetings in Europe
and Asia (there are large differents I think). These two
considerations will show that past locations of meetings did not serve
better the IETF but served some regional-interests. IMHO, two meetings
in Europe per year is a better practice for IETF activities.

AB

On 5/31/13, Mark Nottingham <mnot@mnot.net> wrote:
> In an attempt to inject some data into the discussion, I wrote a bit of c=
ode
> that figures out how much time, given your home city, you would have spen=
t
> in the air if you'd attended all IETF meetings since IETF74 (i.e., from 2=
009
> onwards).
>
> The first column is the "home" airport.
>
> The second column is the great circle time between the home airport and t=
he
> nearest large airport to the IETF meeting, hhh:mm. This doesn't count thi=
ngs
> like transit time, taxiing, takeoff and landing overhead, indirect routin=
g,
> etc. As such, this is an ideal number; the only way to achieve anything
> close to it is to have a private jet (with exceptional range).
>
> The third column is the time (hhh:mm) using the shortest-time routing on =
a
> travel booking engine. This is first-takeoff-to-last-landing time.
>
> Both numbers assume round trip between "home" and the IETF airports.
>
> SFO  204:10  282:04  // San Francisco
> BOS  197:42  297:38  // Boston
> ATL  205:44  297:28  // Atlanta
> ANC  197:12  345:54  // Anchorage
> LHR  198:02  249:44  // London
> FRA  202:10  255:22  // Frankfurt
> FCO  223:52  283:04  // Rome
> SVO  211:28  287:14  // Moscow
> TLV  264:12  334:22 // Israel
> DXB  293:26  344:34 // Dubai
> NRT  259:00  314:38  // Tokyo
> HKG  296:38  359:22  // Hong Kong
> BLR  332:28  448:24  // Bangalore
> MEL  450:28  556:04  // Melbourne
> AKL  442:24  569:04  // Auckland
> JNB  414:30  498:22  // Johannesburg
> EZE  411:10  522:56  // Buenos Aires
> GIG  381:56  488:32  // Rio de Janeiro
>
> Draw your own conclusions, of course.
>
> One observation is that there's a 3+ days-in-the-air per year variance if
> you're a full-time participant, depending on where you live. I.e., more t=
han
> one day-per-meeting difference, on average. In the air alone.
>
> Another is that, perhaps surprisingly, the "closest" homes to all meeting=
s
> are in Europe, not the US (at least by shortest-time routing).
>
> I can run other airports upon request, as well as make source available, =
but
> will do so conservatively, so as not to incur the ire of the services I'm
> (ab)using.
>
> Regards,
>
> P.S. The IETF airports chosen were:
>
>   IETF_airports: [
>     "ORL",
>     "ATL",
>     "YVR",
>     "CDG",
>     "TPE",
>     "YQB",
>     "PRG",
>     "PEK",
>     "AMS",
>     "LAX",
>     "HIJ",
>     "ARN",
>     "SFO"
>   ],
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>

From ynir@checkpoint.com  Sun Jun  2 00:59:54 2013
Return-Path: <ynir@checkpoint.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 066E121F9DDC for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 00:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.299
X-Spam-Level: 
X-Spam-Status: No, score=-9.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 MXwXcU1b2ghL for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 00:59:49 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 9698821F9DD5 for <ietf@ietf.org>; Sun,  2 Jun 2013 00:59:48 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r527xj1N010275; Sun, 2 Jun 2013 10:59:45 +0300
X-CheckPoint: {51AAFB71-7-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Sun, 2 Jun 2013 10:59:45 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: Time in the Air
Thread-Topic: Time in the Air
Thread-Index: AQHOXeWWaH02T68BnEKcBCTmKrNm2ZkgdLiAgAFli4CAAAXvgA==
Date: Sun, 2 Jun 2013 07:59:43 +0000
Message-ID: <94D558CB-5948-415D-AC1D-87E755A21FF6@checkpoint.com>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>, <CADnDZ88jz_juwjw2JezLWR7ZosY8gO51AYpsLnLF0=XMmAZ_gA@mail.gmail.com> <290E20B455C66743BE178C5C84F12408223F494E9C@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E9C@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.159]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 111b9bfe4543d6964bdf3727685d8f9aa300996cf1
Content-Type: text/plain; charset="us-ascii"
Content-ID: <610EBD3848F3064FBE1CD5A6C5773A47@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<mnot@mnot.net>" <mnot@mnot.net>, "<ietf@ietf.org>" <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: Sun, 02 Jun 2013 07:59:54 -0000

On Jun 2, 2013, at 10:38 AM, l.wood@surrey.ac.uk wrote:

> "Always Europe gets better results because it is the favoriate meeting-lo=
cation for ALL
> businesses"
>=20
> {{citation needed}}

Here you go:
http://en.wikipedia.org/wiki/Edsel_Citation

(idea taken from http://what-if.xkcd.com/47/ - is this a reference or a cit=
ation?)

Yoav


From john-ietf@jck.com  Sun Jun  2 07:16:19 2013
Return-Path: <john-ietf@jck.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 90F1321F8763 for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 07:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 7vmPf3gjW3bW for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 07:16:13 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id ABF3521F86D3 for <ietf@ietf.org>; Sun,  2 Jun 2013 07:16:13 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uj94u-000AMV-0s; Sun, 02 Jun 2013 10:16:12 -0400
Date: Sun, 02 Jun 2013 10:15:56 -0400
From: John C Klensin <john-ietf@jck.com>
To: Warren Kumari <warren@kumari.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [IETF] Not Listening to the Ops Customer
Message-ID: <2C8035D3C35AD0F052F109F7@JcK-HP8200.jck.com>
In-Reply-To: <3BF16A35-39A5-4C65-8A0F-0A779E202976@kumari.net>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <3BF16A35-39A5-4C65-8A0F-0A779E202976@kumari.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: IETF discussion 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: Sun, 02 Jun 2013 14:16:19 -0000

--On Saturday, June 01, 2013 11:28 -0400 Warren Kumari
<warren@kumari.net> wrote:

>...
> I *really* want to make sure that my CEO always gets the same
> address, and want him to be assigned specific DNS servers and
> use a certain gateway. The folk who manage the DHCP are the
> "Internal Services Infrastructure Group"  (aka "The windows
> monkeys") and I'm sure as heck not giving them access to my
> router to twiddle knobs on it. =20

Warren, I sympathize.   But I also note that your comment above
can be read, in more general form, as "the folks in IT are
turkeys and therefore we need to export the issues they can't be
trusted to handle well to the Internet".  That isn't a good
model, if only because it involves moving the intelligence to
the middle of the net. =20

Assuming that you still work where I think you work, you've got
a significant advantage over most of the people in similar
circumstances: you have an Executive Chairman and a bunch of VPs
who actually do understand the problem with incompetent internal
IT departments and maybe even why they come out that way and
many of them are pretty accessible.  Identify the problem and
suggest a workable solution.

>...
>> It turns out that as soon as you envisage a network in which
>> some nodes only support 32 bit addresses and other nodes
>> can't get a globally unique 32 bit address, you are forced
>> into a world of hurt that requires some combination of NAT,
>> tunnels and dual-stack. That is completely independent of the
>> design of IPng, and we knew it 1994.
>=20
> Yes, hindsight always makes things *much* clearer. It also
> provides a nice sandbox to stand on=E2=80=A6.

But the "knew it in 1994" part means that this is _not_
hindsight.  Several of the other comments we have made aren't
either -- they were well-understood in the community in 1994 and
then rejected or ignored for one reason or another.  One can
complain about the rejection in hindsight, but not about lack of
information.

>...
>> So while your criticism is valid that we collectively came up
>> with too many such combinations, that collective mistake was
>> (IMHO) not a result of the design of IPv6 as such. It was =
more
>> caused by the design of human beings.
>=20
>=20
> I'd go further -- some of the issue is (IMO) caused by the
> consensus driven nature of how we do things. We all have
> different sets of interests and different priorities. Because
> of a need to achieve consensus, we end in something kind of
> like horse-trading. We add features to appease some set of
> folk, and compromise on other bits to appease others. I
> suspect that if one or two folk had designed this,
> soup-to-nuts, we'd have ended up with something cleaner.

See my note about the nature of standards. =20

>...

    john


From adrian@olddog.co.uk  Sun Jun  2 08:35:53 2013
Return-Path: <adrian@olddog.co.uk>
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 7B66821F8FAF for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 08:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
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 vH8wUMhAjnoK for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 08:35:49 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id B739F21F8FB6 for <ietf@ietf.org>; Sun,  2 Jun 2013 08:35:48 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r52FZjKV011811;  Sun, 2 Jun 2013 16:35:46 +0100
Received: from 950129200 ([220.109.211.58]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r52FZfoG011789 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 2 Jun 2013 16:35:44 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ogaki, Kenichi'" <ke-oogaki@kddi.com>, <ietf@ietf.org>
References: <20130525012629.27814.9963.idtracker@ietfa.amsl.com> <07b701ce5931$6c93acd0$45bb0670$@olddog.co.uk> <00cf01ce5de0$bb29f670$317de350$@kddi.com>
In-Reply-To: <00cf01ce5de0$bb29f670$317de350$@kddi.com>
Subject: RE: [Pce] Last Call: <draft-ietf-pce-gmpls-aps-req-07.txt>	(Requirements for	GMPLS applications of PCE) to Informational RFC
Date: Sun, 2 Jun 2013 16:35:37 +0100
Message-ID: <035f01ce5fa6$d6f5b5c0$84e12140$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFqCM6wK8Jj72Y/bcq1okRvzWE3YQMMXeZIArxcG72ZvPYGkA==
Content-Language: en-gb
Cc: draft-ietf-pce-gmpls-aps-req.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Sun, 02 Jun 2013 15:35:53 -0000

Kenichi-san,

This all looks good to me.

Thanks,
Adrian

> -----Original Message-----
> From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com]
> Sent: 31 May 2013 10:25
> To: adrian@olddog.co.uk; ietf@ietf.org
> Cc: draft-ietf-pce-gmpls-aps-req.all@tools.ietf.org
> Subject: RE: [Pce] Last Call: <draft-ietf-pce-gmpls-aps-req-07.txt>
(Requirements
> for GMPLS applications of PCE) to Informational RFC
> 
> Dear Adrian,
> 
> Thank you for your comments.
> 
> We will address your comments after this last call as follows.
> 
> > idnits shows a couple of issues with your references
> >
> >   == Unused Reference: 'RFC3945' is defined on line 373, but no explicit
> >      reference was found in the text
> >
> >   == Unused Reference: 'RFC4927' is defined on line 402, but no explicit
> >      reference was found in the text
> >
> > These both seem like relevant references and I suggest that you find a
> place
> > in the text to point to them.
> 
> RFC3945 shall be referred in section 1, paragraph 2, sentence 2 as follows:
> As the same case with MPLS, service providers (SPs) have also come up with
> requirements for path computation in GMPLS-controlled networks [RFC3945]
> such as wavelength, TDM-based or Ethernet-based networks as well.
> 
> RFC4927 shall be referred in section 1 paragraph 3 as follows:
> Note that the requirements for inter-layer and inter-area traffic
> engineering described in [RFC6457] and [RFC4927] are outside of the scope of
> this document.
> 
> 
> > Some work on acronyms, please.
> >
> > PCE needs to be expanded on first use in the Abstract and the main text
> > (not on the second use :-)
> >
> > OTOH, MPLS and GMPLS do not need to be expanded.
> >
> > PCC shows up in section 2.1
> > PCReq and PCRep are in 2.1 (but expanded a little later) P2MP is in
> section
> > 2.2 ERO and XRO show in section 3.1 PCEP shows in section 3.2
> 
> All acronyms indicated above shall be correctly expanded or not expanded.
> 
> 
> > Section 1 para 4 seems to say that SRLG is covered in RFC 3473. Are you
> > sure? Or do you need a different reference?
> 
> SRLG shall be moved to the previous sentence and refer RFC 4202 as follows:
> Constraint-based shortest path first (CSPF) computation within a domain or
> over domains for signaling GMPLS Label Switched Paths (LSPs) is usually more
> stringent than that of MPLS TE LSPs [RFC4216], because the additional
> constraints, e.g., interface switching capability, link encoding, link
> protection capability, SRLG (Shared Risk Link Group) [RFC4202] and so forth
> need to be considered to establish GMPLS LSPs.
> 
> 
> > In Section 3.1 reqs (1), (2) and (3) you appear to be limiting the
> supported
> > values to only those listed or those in the referenced RFCs.
> >
> > You may do better to say less. Just point at the base definition of the
> > signaling fields (in RFC 3473?) and then say "all current and future
> values".
> 
> reqs (1), (2) and (3) shall be rewritten as follows:
> (1) Switching capability/type: as defined in [RFC3471], [RFC4203] and, all
> current and future values.
> (2) Encoding type: as defined in [RFC3471], [RFC4203] and, all current and
> future values.
> (3) Signal Type: as defined in [RFC4606] and, all current and future values.
> 
> 
> > Section 6
> >
> > Julien Meuric not Meulic
> 
> Sorry Julien, we shall correct this typo.
> 
> Thanks,
> Kenichi
> 
> --
> Kenichi Ogaki
> KDDI | IP Transport Network Development Dept.
> +81-(0)80-5945-9138 | www.kddi.com
> 
> 
> > -----Original Message-----
> > From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> > Sent: Saturday, May 25, 2013 7:20 PM
> > To: ietf@ietf.org
> > Cc: draft-ietf-pce-gmpls-aps-req.all@tools.ietf.org
> > Subject: RE: [Pce] Last Call: <draft-ietf-pce-gmpls-aps-req-07.txt>
> > (Requirements for GMPLS applications of PCE) to Informational RFC
> >
> > Hi,
> >
> > Here are my review comments as responsible AD. Because they are minor
> > comments, I am entering them as part of IETF last call rather than getting
> > them fixed before last call. That should expedite the publication a
> little.
> >
> > Thanks,
> > Adrian
> >
> > ===
> >
> > idnits shows a couple of issues with your references
> >
> >   == Unused Reference: 'RFC3945' is defined on line 373, but no explicit
> >      reference was found in the text
> >
> >   == Unused Reference: 'RFC4927' is defined on line 402, but no explicit
> >      reference was found in the text
> >
> > These both seem like relevant references and I suggest that you find a
> place
> > in the text to point to them.
> >
> > ---
> >
> > Some work on acronyms, please.
> >
> > PCE needs to be expanded on first use in the Abstract and the main text
> > (not on the second use :-)
> >
> > OTOH, MPLS and GMPLS do not need to be expanded.
> >
> > PCC shows up in section 2.1
> > PCReq and PCRep are in 2.1 (but expanded a little later) P2MP is in
> section
> > 2.2 ERO and XRO show in section 3.1 PCEP shows in section 3.2
> >
> >
> > ---
> >
> > Section 1 para 4 seems to say that SRLG is covered in RFC 3473. Are you
> > sure? Or do you need a different reference?
> >
> > ---
> >
> > In Section 3.1 reqs (1), (2) and (3) you appear to be limiting the
> supported
> > values to only those listed or those in the referenced RFCs.
> >
> > You may do better to say less. Just point at the base definition of the
> > signaling fields (in RFC 3473?) and then say "all current and future
> values".
> >
> > ---
> >
> > Section 6
> >
> > Julien Meuric not Meulic
> >
> > > -----Original Message-----
> > > From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of
> > > The IESG
> > > Sent: 25 May 2013 02:26
> > > To: IETF-Announce
> > > Cc: pce@ietf.org
> > > Subject: [Pce] Last Call: <draft-ietf-pce-gmpls-aps-req-07.txt>
> > > (Requirements
> > for
> > > GMPLS applications of PCE) to Informational RFC
> > >
> > >
> > > The IESG has received a request from the Path Computation Element WG
> > > (pce) to consider the following document:
> > > - 'Requirements for GMPLS applications of PCE'
> > >   <draft-ietf-pce-gmpls-aps-req-07.txt> as Informational RFC
> > >
> > > The IESG plans to make a decision in the next few weeks, and solicits
> > > final comments on this action. Please send substantive comments to the
> > > ietf@ietf.org mailing lists by 2013-06-07. Exceptionally, comments may
> > > be sent to iesg@ietf.org instead. In either case, please retain the
> > > beginning of the Subject line to allow automated sorting.
> > >
> > > Abstract
> > >
> > >    The initial effort of the PCE WG is specifically focused on MPLS
> > >    (Multi-protocol label switching).  As a next step, this draft
> > >    describes functional requirements for GMPLS (Generalized MPLS)
> > >    application of PCE (Path computation element).
> > >
> > > The file can be obtained via
> > > http://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-aps-req/
> > >
> > > IESG discussion can be tracked via
> > > http://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-aps-req/ballot/
> > >
> > >
> > > The following IPR Declarations may be related to this I-D:
> > >
> > >    http://datatracker.ietf.org/ipr/1869/
> > > _______________________________________________
> > > Pce mailing list
> > > Pce@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pce



From adrian@olddog.co.uk  Sun Jun  2 08:52:07 2013
Return-Path: <adrian@olddog.co.uk>
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 49A8A21F8FEC; Sun,  2 Jun 2013 08:52:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
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 h6p5qJ1z+iQ1; Sun,  2 Jun 2013 08:52:01 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 044ED21F86CE; Sun,  2 Jun 2013 08:52:00 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r52FpwR0001032;  Sun, 2 Jun 2013 16:51:58 +0100
Received: from 950129200 ([220.109.211.58]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r52FpsPe001010 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 2 Jun 2013 16:51:57 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>, <ietf@ietf.org>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com>	<CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CADnDZ89BMkpQd2Z8MmCmnUdp0uD6v8Vrbq-z5JeerfiuqpPW0w@mail.gmail.com>
In-Reply-To: <CADnDZ89BMkpQd2Z8MmCmnUdp0uD6v8Vrbq-z5JeerfiuqpPW0w@mail.gmail.com>
Subject: RE: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt>	(Security Threats for NHDP) to Informational RFC
Date: Sun, 2 Jun 2013 16:51:47 +0100
Message-ID: <036b01ce5fa9$1afec8e0$50fc5aa0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIhotg4CdXjJ2V6m9iU5kaOA6mt7QNAiXCHAVU9LT6YV1zS4A==
Content-Language: en-gb
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Sun, 02 Jun 2013 15:52:07 -0000

Hi Abdussalam,

I think it is a reasonable suggestion for this I-D to make a forward reference
to draft-ietf-manet-nhdp-olsrv2-sec
Although this work is clearly scoped to NHDP (RFC 6130) as currently specified,
it is worth an informational reference to note that there is work in progress
that seeks to update NHDP to counter a number of security threats described in
this document.

I do not think, however, that this I-D should attempt to describe the situation
with NHDP after the inclusion of protocol work that has not yet been completed.
Contrary to your suggestion, I think this I-D motivates updates to 6130 and it
would be wrong to review this document in the context of changes being made to
address this document. 

Thanks,
Adrian

> I think if we got an effort in IETF to update NHDP [RFC6130] as draft
> [1] does, why this reviewed I-D of threats does not include [1] in its
> references to be reviewed before reviewing this NHDP-threat I-D? I
> suggest to include draft [1] in References section, IMHO, any updates
> to RFC6130 should be considered by the community while reviewing this
> I-D.
> 
> [1] draft-ietf-manet-nhdp-olsrv2-sec-02


From jcurran@istaff.org  Sun Jun  2 09:34:58 2013
Return-Path: <jcurran@istaff.org>
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 EB12D21F9051 for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 09:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level: 
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=0.930,  BAYES_00=-2.599]
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 9harQhBTQgam for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 09:34:54 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id CD9AC21F8FF3 for <ietf@ietf.org>; Sun,  2 Jun 2013 09:34:53 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1UjBF5-0001OD-Mt; Sun, 02 Jun 2013 16:34:51 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19xjDJPLxJEkkNgs2Gzvu3c
Subject: Re: [IETF] Not Listening to the Ops Customer (more)
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=windows-1252
From: John Curran <jcurran@istaff.org>
X-Priority: 1
In-Reply-To: <2C8035D3C35AD0F052F109F7@JcK-HP8200.jck.com>
Date: Sun, 2 Jun 2013 12:34:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CD84B996-0AF4-4145-A5F7-58A52F32CE9F@istaff.org>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com> <3BF16A35-39A5-4C65-8A0F-0A779E202976@kumari.net> <2C8035D3C35AD0F052F109F7@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1503)
Cc: IETF discussion 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: Sun, 02 Jun 2013 16:34:59 -0000

On Jun 2, 2013, at 10:15 AM, John C Klensin <john-ietf@jck.com> wrote:
> --On Saturday, June 01, 2013 11:28 -0400 Warren Kumari =
<warren@kumari.net> wrote:
>> ...
>>> It turns out that as soon as you envisage a network in which
>>> some nodes only support 32 bit addresses and other nodes
>>> can't get a globally unique 32 bit address, you are forced
>>> into a world of hurt that requires some combination of NAT,
>>> tunnels and dual-stack. That is completely independent of the
>>> design of IPng, and we knew it 1994.
>>=20
>> Yes, hindsight always makes things *much* clearer. It also
>> provides a nice sandbox to stand on=85.
>=20
> But the "knew it in 1994" part means that this is _not_
> hindsight.  Several of the other comments we have made aren't
> either -- they were well-understood in the community in 1994 and
> then rejected or ignored for one reason or another.  One can
> complain about the rejection in hindsight, but not about lack of
> information.

Indeed, it was well-understood that there needed to be some solution=20
involving NAT to provide for basic interoperability (even if no one=20
liked standardizing that aspect); specifically, "The IPng transition=20
plan must define the procedures required to successfully implement=20
the functions which vendors will be likely to include in their devices. =20=

This is the case even if there are good arguments to recommend against=20=

a particular function, header translation for example.  If products=20
will exist it is better to have them interoperate than not." [RFC 1752,
Section 16.1]

The problem was that the IETF felt enormous pressure _for its own
efficiency_ to come to a decision about IPng; i.e. we did not have=20
operators clamoring that they needed IPng to be decided ASAP (I'd
wager that most commercial service providers were far too busy trying=20
to keep up with the epic customer demand in the early 90's to pay=20
much attention to the IPv4 depletion problem which was many, many
years away...)  As you know, there were real concerns about transition
expressed by operators at the IPdecide BoF ('93 Amsterdam IETF) -=20
 =20
 "It was stated frequently and forcibly that the transition costs=20
  should be a significant factor in the selection criteria. Concerns=20
  were expressed by several service providers that the developers=20
  had little appreciation of the real-world networking complexities=20
  that transition would force people to cope with.  If the cost of=20
  transition outweighed the pain of other solutions (application=20
  gateways or address translators) customers would not deploy IPng."

[ftp://ftp.ietf.org/ietf/93jul/ipdecide-minutes-93jul.txt]
(Highly recommended reading for folks who are interested in=20
the history of IPv6)

In the end, the IETF decided it should take active steps toward making=20=

the technical decision on IPng (rather than waiting for the =
"marketplace"=20
to decide) and that IESG would form the IPng Directorate [RFC 1719] =
which=20
was to evaluate how long we had to IPv4 runout and develop the technical=20=

requirements and criteria for IPng.  Once this was completed at the end=20=

of 1994, there was enormous pressure to select a single IPng candidate=20=

protocol to work on (despite the unresolved issues regarding transition)=20=

so that the work of the IETF could be focused in a single effort going=20=

forward.  This approach might have worked out fine, but once the actual
IPng candidate decision was made, all of the prioritization on =
transition=20
requirements dissipated as the work was shuffled off to various working=20=

groups in the years that followed, with the result being that the once
mandatory IPng requirement for a straightforward transition plan from=20
IPv4 was never fulfilled. =20

I was asked to be more specific on how to avoid such issues the future,=20=

so here goes:

  If multiple solutions can readily coexist, let the market decide.

  If not, define the problem from the perspective of those who must
  deploy the solution, including their inherent need for a clear and
  functional transition mechanism.

In retrospect, it's fairly obvious that there's a huge difference =
between
problem spaces which allow for multiple solutions (e.g. interior routing=20=

protocols) versus problem spaces which the IETF is aiming for only _one_=20=

protocol in the final solution (e.g. IP, DNS); the process making that
type of architectural decision should probably be quite visible and =
rather
explicit because it comes with a huge responsibility for addressing all=20=

necessary transition aspects.  This responsibility for the transition=20
aspects should not be set aside by the IETF for convenience or due to =
the=20
level of effort that results, as it is the price to be paid when making
an architectural decision to have a single protocol solution for a given
problem space.

FYI,
/John

p.s. John - you made a comparison to electrical power standards with=20
     respect to operator & end-user participation: I guess the parallel
     would be that the electrical equipment manufacturers (along with
     engineers from electrical production and distribution companies who=20=

     have the right background) may indeed make new standards without =20=

     end-user input, but when they do so, it is done such that end-users=20=

     plugging in old equipment never results in explosion and fire... =20=

     We now have service providers running into real challenges trying=20=

     to accomplish the same logical result with IPv6, which implies that
     the electrical distribution folks pay more attention to transition=20=

     aspects of their new standards than we do, and is actually why end-
     users and even property developers in general don't worry about=20
     changes in power distribution standards. (You may have to learn=20
     about them if you want take advantage of new features, but if you=20=

     don't care, existing practices won't blow up in your face.)

Disclaimers:  My views alone.  Your mileage may vary; feel free to use,=20=

              abuse, or discard these views as you desire.


From abdussalambaryun@gmail.com  Sun Jun  2 10:35:05 2013
Return-Path: <abdussalambaryun@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 2636421F90EE; Sun,  2 Jun 2013 10:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, 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 z5Mh8iAI-98M; Sun,  2 Jun 2013 10:35:04 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 952E621F8C08; Sun,  2 Jun 2013 10:35:04 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq2so4625813pbb.33 for <multiple recipients>; Sun, 02 Jun 2013 10:35:04 -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=SkRaQCtWPzTjyZCKpDAOS6I/xr1op4q5JZrH/Vfm/Ao=; b=Ymn5xQCsju62BO2yEgSgsTKO93c1+VdZKZozo/qvHbr/GUlBn7741pBn4nroefwcOH ENnp/HZ3CyB2PvhUsVTyBRYxwLmWG0p/izp3qyDtJsXI8Xg7OquWl1bKNNo09MOPjZe+ Xmx/0nfAOxPJEpW67Skx4GXfCxjBpTx6TgEgclm8Bb+471pe92S8yPqZV/KeieN9Z84l RvRi3PUjrFf6h1+nZIP45LBIngUxQSOJVm/dhvqXZOY6whrXQ5FwZwssTvAH+UbHQxfl bm+MZDw85IF75J1n2F+5j9ehuq/nOih5O0o3aherdcHiLPSqAeytLv+szlIhnoH3Ella RMzQ==
MIME-Version: 1.0
X-Received: by 10.66.248.228 with SMTP id yp4mr21337177pac.158.1370194504256;  Sun, 02 Jun 2013 10:35:04 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Sun, 2 Jun 2013 10:35:04 -0700 (PDT)
In-Reply-To: <036b01ce5fa9$1afec8e0$50fc5aa0$@olddog.co.uk>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CADnDZ89BMkpQd2Z8MmCmnUdp0uD6v8Vrbq-z5JeerfiuqpPW0w@mail.gmail.com> <036b01ce5fa9$1afec8e0$50fc5aa0$@olddog.co.uk>
Date: Sun, 2 Jun 2013 19:35:04 +0200
Message-ID: <CADnDZ8-nOaog3iQu5T47CRejyZWPukgMkpG5B-hVn6WzZZ97kw@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: adrian@olddog.co.uk
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, iesg@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: Sun, 02 Jun 2013 17:35:05 -0000

Hi Adrian

My comments below,

On 6/2/13, Adrian Farrel <adrian@olddog.co.uk> wrote:
> Hi Abdussalam,
>
> I think it is a reasonable suggestion for this I-D to make a forward
> reference
> to draft-ietf-manet-nhdp-olsrv2-sec
> Although this work is clearly scoped to NHDP (RFC 6130) as currently
> specified,
> it is worth an informational reference to note that there is work in
> progress
> that seeks to update NHDP to counter a number of security threats described
> in
> this document.

So I understand you agree with my suggestion on this I-D to
referencing/refering to that draft [1].

>
> I do not think, however, that this I-D should attempt to describe the
> situation
> with NHDP after the inclusion of protocol work that has not yet been
> completed.

I think the work completes when the WG submits to AD, but reviews not
completed. IMHO, the draft/work [1] is completed from WGLC, and now is
at AD review.

> Contrary to your suggestion, I think this I-D motivates updates to 6130 and
> it
> would be wrong to review this document in the context of changes being made
> to
> address this document.

I suggest the I-D referencing. I do not think I suggested way of
reviews, but that other satetment was my opinion/beleive or advise to
community of such reveiw for output quality. I don't understand why
you think it was wrong way of review, after you agreed to reference
such document (usually my reviewing reviews all references as well).

Regards
AB

>
>> I think if we got an effort in IETF to update NHDP [RFC6130] as draft
>> [1] does, why this reviewed I-D of threats does not include [1] in its
>> references to be reviewed before reviewing this NHDP-threat I-D? I
>> suggest to include draft [1] in References section, IMHO, any updates
>> to RFC6130 should be considered by the community while reviewing this
>> I-D.
>>
>> [1] draft-ietf-manet-nhdp-olsrv2-sec-02
>
>

From hartmans@mit.edu  Sun Jun  2 15:34:52 2013
Return-Path: <hartmans@mit.edu>
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 8473D21F8FE8; Sun,  2 Jun 2013 15:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Nem9eKKnMZXU; Sun,  2 Jun 2013 15:34:46 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 7170221F8FA5; Sun,  2 Jun 2013 15:34:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 55F382062F; Sun,  2 Jun 2013 18:31:19 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQnEOLlxFZpC; Sun,  2 Jun 2013 18:31:17 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Sun,  2 Jun 2013 18:31:17 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 87A89440A; Sun,  2 Jun 2013 18:34:37 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
Subject: Re: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-07
References: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com>
Date: Sun, 02 Jun 2013 18:34:37 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com> (David Black's message of "Thu, 25 Apr 2013 11:21:36 -0400")
Message-ID: <tsly5asuooy.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "karp@ietf.org" <karp@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: Sun, 02 Jun 2013 22:34:52 -0000

>>>>> "David" == Black, David <david.black@emc.com> writes:

    David> Document: draft-ietf-karp-crypto-key-table-07 Reviewer: David
    David> L. Black Review Date: April 25, 2013 IETF LC End Date: April
    David> 29, 2013

    David> (Section 2)

    David> [1] LocalKeyName and PeerKeyName are strings.  What character
    David> set?  If Unicode (e.g., UTF-8?), add text on Unicode
    David> considerations (e.g., normalization).  Finding a Unicode
    David> expert will help in getting this done quickly.  I have
    David> similar concerns for other strings, and in particular, IANA
    David> should be told what a "string" is for any registry field that
    David> contains one.
Proposed fix;
The LocalKeyName field contains a string identifying the
key. It can be used to retrieve the key in the local database when
received in a packet.  As discussed in Section 4,  the protocol
defines  the form of this field. For example, many routing protocols
restrict the format of their key names to integers that can be
represented in 16 or 32 bits. Typically this field does not contain
data in human character sets requiring internationalization.
If there ever are any Protocols with key names requiring
internationalization, those specifications MUST address
issues of canonicalization and normalization so that key names can be
compared using binary comparison.

    David> [2] I'm not sure that I understand what a KDF really is from
    David> its high level description in this draft.  At the least, I'm
    David> surprised that the importance of non-invertibility of a KDF
    David> is not mentioned - beyond that, a functional description of
    David> inputs and outputs would help, including a strong
    David> recommendation to inject unpredictable nonce material.  This
    David> could be handled by referencing material on what a KDF is
    David> that exists elsewhere.
The KDF field indicates the key derivation function which is used to
generate short-lived keys from the long-lived value in the Key field.
When the long-lived value in the Key field is intended for direct use,
the KDF field is set to "none".  A key derivation function is a
one-way function that provides cryptographic separation of key
material.  The KDF MAY use inputs from the row in the key table and
the packet being sent or received but MUST NOT depend on other
configuration state.

    David> (Section 4)

    David> [3] It's important that this section cover all the fields
    David> involved in the database lookups in Section 3 whose format
    David> may be protocol-specific (the Direction and various time
    David> fields aren't).  Protocol should be covered by the IANA
    David> registry, peers and key names are covered here, but interface
    David> appears to be missing - item (9) covers presence vs.  absence
    David> of interface information, but not its format.
The form of the interfaces field is not protocol-specific but instead
is shared among all protocols on an implementation.  If a protocol
needs to distinguish instances running over the same interface, this
is included in the specification of peers.  Generally it is desirable
to define the specification of peers so that an operator can use the
interfaces field to refer to all instances of a protocol on a link
without having to specify both generic interfaces information and
protocol-specific peer information.

    David> --- Lots of issues with the IANA Considerations (Section 8)

I could really use some help from one of the other authors resolving the
IANA issues.
I've made the trivial fix of getting info vs values consistent.

    David> [7] Should some sort of formats for Peers and Interfaces be
    David> included in registering a Protocol?  If not, the lookups in
    David> section 3 may be implementation-dependent (strings that work
    David> w/one implementation may not work w/other implementations of
    David> the same protocol).  The specification reference may suffice
    David> based on the requirements in section 4 for what has to be in
    David> each referenced specification.

I think section 4 should  handle this.
We could add a bit of text reminding people that the specification needs
to address the issues brought up in section 4.


    David> [9] I suggest Expert Review for these registries, not just
    David> First Come First Served, so that someone with a security
    David> "clue" can check that the proposed registrations are
    David> reasonable.

I don't think I've seen support for this on the WG list.

    David> Minor issues:


I don't think it does even conceptually.
It's much closer to the SPD.
However there are no plans I'm aware of to use this to configure IPsec
and I think several of us might push back against that.

    David> [B] (Section 2) Where is key size recorded?  Is that an
    David> implicit attribute of Key?

yes.

    David> [C] (Section 3) Where does key selection occur?  I would
    David> suggest that the database return all possible keys and let
    David> the protocol figure out what to use.  This is particularly
    David> important for inbound traffic for obvious reasons.

No, the hope is that the key selection can be shared among protocols;
that's one of the main things that you get out of something like this.
The intent is that the protocol passes the things described in section 3
into the key table which pops out the right row.

We think this is solid for received packets; if you think we've missed
something please let us know: much easier to fix now!

From brian.e.carpenter@gmail.com  Sun Jun  2 16:27:07 2013
Return-Path: <brian.e.carpenter@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 779C721F8F29 for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 16:27:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Foi1b2nTzy2C for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 16:27:06 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2150121F8F6E for <ietf@ietf.org>; Sun,  2 Jun 2013 16:27:06 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id 10so7035974ied.28 for <ietf@ietf.org>; Sun, 02 Jun 2013 16:27:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=WCQal8ogm7C8VYk/NNDGDx+e8m/VyYmp1xi0M/w76Zw=; b=iJWoxtuCqf0Dj9I62OqG+IR36HzceDNDnCJKWkh+smlWJ3aY5PLXjU6d0WTOeVL68e mTPCPqJWWL51Y+J0+2BPx7sq2ApQ5xyl+55kytSRvPcCsxqLtVewcSj1yuH7q9GSqubV lQPPzucstaeRTpAQfzOQUbZGHWuefDoBETRTGWsXN2xsVxwpeOiG8/U/u3PNkSM4mqyY ZJFB75eZCNqZhY54NO3F3Je7jjDralPfxEtt2W7C6CZrnRsi8w8GLU8+Bbqp+V0/Dp7W ru496pfZ2uH66GwAPZgJuVwMWlAZ58DFi18JEJltiZFDlWiSkipRSKDceWcNnPWJMhh2 xf4g==
X-Received: by 10.50.103.98 with SMTP id fv2mr6445468igb.68.1370215625774; Sun, 02 Jun 2013 16:27:05 -0700 (PDT)
Received: from [192.168.1.2] (224.171.252.27.dyn.cust.vf.net.nz. [27.252.171.224]) by mx.google.com with ESMTPSA id ot10sm10205884igb.9.2013.06.02.16.27.02 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Jun 2013 16:27:04 -0700 (PDT)
Message-ID: <51ABD4C4.7070403@gmail.com>
Date: Mon, 03 Jun 2013 11:27:00 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-crocker-id-adoption-02.txt
References: <20130528082744.6677.288.idtracker@ietfa.amsl.com>
In-Reply-To: <20130528082744.6677.288.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Sun, 02 Jun 2013 23:27:07 -0000

Hi,

My main positive comment is that it's a good idea to document guidelines
in this area, and that (viewed as guidelines) I largely agree with
the draft.

My main negative comment is that although the draft says it's not a
formal process document, its language in many places belies that.
For example:

> 2. Adoption Process
> 
> 
> 2.1. Formal Steps
> 
> 
>    To adopt a new working group document, the chairs need to:

would be better phrased as:

 2. Adoption Guidelines

 2.1. Typical Steps

    To adopt a new working group document, the chairs often:

I'd suggest a careful pass through the text, removing instances
of words like "process", "formal" and "need", and emphasising words
like "guideline" and "typical" and "might".

Now some minor comments:

>    The convention for
>    identifying an I-D formally under the ownership of a working group is
>    by the inclusion of "ietf" in the second field of the I-D filename
>    and the working group name in the third field,

It's a useful convention but *not* a requirement afaik.

>    Note
>    that from time to time a working group will form a design team to
>    produce the first version of a working group draft.

I think that's slightly wrong. A design team draft is *not*
automatically a WG draft. I think this is more accurate:

   Note
   that from time to time a working group will form a design team to
   produce the first version of a document that may be adopted as
   a working group draft.

That's an important difference - we've seen cases where design teams
falsely believed that they had been delegated authority by the WG.

>      *  Is there strong working group support for the draft?

I think that's going a bit far. Actually a WG might adopt
a draft because there is support for the *topic* but not for
the details of the draft as it stands. Indeed, one objective of
adopting a draft is so that the WG as a whole obtains control
of the contents - so that they can change it.

>       *  What is the position of the working group chairs, concerning
>          the draft?
> 
>             [[editor note: I am not sure this is relevant.  Indeed is
>             might be specifically not relevant.  /a]]

Actually I'd go the other way: the WG chairs' job at that point is to
judge the WG's opinion of the draft, not their own opinion. (At least
once, as a WG chair, I had to declare adoption of a draft to which
both I and my co-chair were strongly opposed.)

> 5.1. Individual I-Ds Under WG Care
...

OK, but there are in fact four possible outcomes for such a draft

1. As you describe;
2. The document proceeds as an individual submission to the IESG
   without continued WG discussion;
3. The document proceeds as an Independent Submission to the RFC Editor;
4. The document is abandoned.

Regards
   Brian

From l.wood@surrey.ac.uk  Sun Jun  2 18:55:09 2013
Return-Path: <l.wood@surrey.ac.uk>
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 9583721F8B07 for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 18:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=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 XU4pVU-n541i for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 18:55:04 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.115]) by ietfa.amsl.com (Postfix) with ESMTP id 69E3221F86CB for <ietf@ietf.org>; Sun,  2 Jun 2013 18:55:03 -0700 (PDT)
Received: from [193.109.255.147:19693] by server-11.bemta-14.messagelabs.com id 82/D3-09099-677FBA15; Mon, 03 Jun 2013 01:55:02 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-72.messagelabs.com!1370224502!13536322!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 4871 invoked from network); 3 Jun 2013 01:55:02 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-14.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 3 Jun 2013 01:55:02 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Mon, 3 Jun 2013 02:55:01 +0100
From: <l.wood@surrey.ac.uk>
To: <brian.e.carpenter@gmail.com>, <ietf@ietf.org>
Date: Mon, 3 Jun 2013 02:52:17 +0100
Subject: RE: I-D Action: draft-crocker-id-adoption-02.txt
Thread-Topic: I-D Action: draft-crocker-id-adoption-02.txt
Thread-Index: Ac5f6MQ338eCyrdVQOWF8++QbK1mWAAFDZap
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E9D@EXMB01CMS.surrey.ac.uk>
References: <20130528082744.6677.288.idtracker@ietfa.amsl.com>, <51ABD4C4.7070403@gmail.com>
In-Reply-To: <51ABD4C4.7070403@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Mon, 03 Jun 2013 01:55:09 -0000

I'd argue that the draft also needs to discuss IRTF processes, such as they=
 are.

though the IRTF groups are sufficiently similar to IETF WGs that you might =
think
the same processes apply, having a draft being adopted by an IRTF group mea=
ns
far less, for example, and there appear to be other differences.

At the very least, a 'this doesn't cover IRTF research groups, where practi=
ces
very widely' is needed.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Brian E Ca=
rpenter [brian.e.carpenter@gmail.com]
Sent: 03 June 2013 00:27
To: IETF discussion list
Subject: Re: I-D Action: draft-crocker-id-adoption-02.txt

Hi,

My main positive comment is that it's a good idea to document guidelines
in this area, and that (viewed as guidelines) I largely agree with
the draft.

My main negative comment is that although the draft says it's not a
formal process document, its language in many places belies that.
For example:

> 2. Adoption Process
>
>
> 2.1. Formal Steps
>
>
>    To adopt a new working group document, the chairs need to:

would be better phrased as:

 2. Adoption Guidelines

 2.1. Typical Steps

    To adopt a new working group document, the chairs often:

I'd suggest a careful pass through the text, removing instances
of words like "process", "formal" and "need", and emphasising words
like "guideline" and "typical" and "might".

Now some minor comments:

>    The convention for
>    identifying an I-D formally under the ownership of a working group is
>    by the inclusion of "ietf" in the second field of the I-D filename
>    and the working group name in the third field,

It's a useful convention but *not* a requirement afaik.

>    Note
>    that from time to time a working group will form a design team to
>    produce the first version of a working group draft.

I think that's slightly wrong. A design team draft is *not*
automatically a WG draft. I think this is more accurate:

   Note
   that from time to time a working group will form a design team to
   produce the first version of a document that may be adopted as
   a working group draft.

That's an important difference - we've seen cases where design teams
falsely believed that they had been delegated authority by the WG.

>      *  Is there strong working group support for the draft?

I think that's going a bit far. Actually a WG might adopt
a draft because there is support for the *topic* but not for
the details of the draft as it stands. Indeed, one objective of
adopting a draft is so that the WG as a whole obtains control
of the contents - so that they can change it.

>       *  What is the position of the working group chairs, concerning
>          the draft?
>
>             [[editor note: I am not sure this is relevant.  Indeed is
>             might be specifically not relevant.  /a]]

Actually I'd go the other way: the WG chairs' job at that point is to
judge the WG's opinion of the draft, not their own opinion. (At least
once, as a WG chair, I had to declare adoption of a draft to which
both I and my co-chair were strongly opposed.)

> 5.1. Individual I-Ds Under WG Care
...

OK, but there are in fact four possible outcomes for such a draft

1. As you describe;
2. The document proceeds as an individual submission to the IESG
   without continued WG discussion;
3. The document proceeds as an Independent Submission to the RFC Editor;
4. The document is abandoned.

Regards
   Brian

From ulrich@herberg.name  Sun Jun  2 22:36:03 2013
Return-Path: <ulrich@herberg.name>
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 940B121F928C for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 22:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 EWqj6o-TX4hp for <ietf@ietfa.amsl.com>; Sun,  2 Jun 2013 22:35:59 -0700 (PDT)
Received: from mail-vc0-f170.google.com (mail-vc0-f170.google.com [209.85.220.170]) by ietfa.amsl.com (Postfix) with ESMTP id B5F0B21F89A6 for <ietf@ietf.org>; Sun,  2 Jun 2013 22:35:58 -0700 (PDT)
Received: by mail-vc0-f170.google.com with SMTP id hf12so904444vcb.1 for <ietf@ietf.org>; Sun, 02 Jun 2013 22:35:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Zi+IYJgPOHmi4i7SMwEjN+7sl5TX897iRxxedc0SEyk=; b=sMPNaINM9eM54auOJcsWxbdrklqY52R+tMP4ffuVAYCoKgqcb7bJlNG9kmDtl3BZUc 7g3BrWpW+CUndohDQolwIZityRFZ5ip/M1fTFWEXOAfoIsC62Bv8M/Jd9Fhs0zfW7IF2 pL46Kb0ggoXkWuv0h4oRc84mSdYP9bggVvrZQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=Zi+IYJgPOHmi4i7SMwEjN+7sl5TX897iRxxedc0SEyk=; b=SrHcjC5vBXo+qG3wuzU1x909Wxc06Ric5y4ouHhe0nnXYcSkfOG94+Ec52FpaI/5oV K4rDBZIf8Hb5CwGXaOWAqVnhLA5Qor5Pdoc4Y1yj/H7TeNz4+68u5r3n9oR3EyFOBKU2 xjfCj66COK9i2yrIbkonyUI6lK4dXvKCxgYC+XggZZLr9JzZGkajuhmiEX4H69IG0OwH 1092fQ5f9zR/WN103DEOaTdrpiA6B4t0HdlEGMxMceNitghUIS/DyeNspDa0abgkPrA1 NbjIzNmWs2zMnLl5INgYFS5DKcQih4XzaNH0BFuAOyBHmiMM71HVvix7Lovc6fpcS+8D PK3Q==
MIME-Version: 1.0
X-Received: by 10.52.69.40 with SMTP id b8mr13692173vdu.130.1370237757547; Sun, 02 Jun 2013 22:35:57 -0700 (PDT)
Received: by 10.220.29.7 with HTTP; Sun, 2 Jun 2013 22:35:57 -0700 (PDT)
In-Reply-To: <036b01ce5fa9$1afec8e0$50fc5aa0$@olddog.co.uk>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CADnDZ89BMkpQd2Z8MmCmnUdp0uD6v8Vrbq-z5JeerfiuqpPW0w@mail.gmail.com> <036b01ce5fa9$1afec8e0$50fc5aa0$@olddog.co.uk>
Date: Sun, 2 Jun 2013 22:35:57 -0700
Message-ID: <CAK=bVC-pDxG0F-kQaPaTw0hY3f9b5=c9nxkCwqdVSw0rmVUDhg@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Ulrich Herberg <ulrich@herberg.name>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=20cf3071ca32cc028304de3956ae
X-Gm-Message-State: ALoCoQkO49OaG4l6P4E6IZqu+GPZ9WQ/kGnrYgejffvJr4YDsDzceViEYEeIWHUFCvRxH6Gi6nzK
Cc: "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <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: Mon, 03 Jun 2013 05:36:03 -0000

--20cf3071ca32cc028304de3956ae
Content-Type: text/plain; charset=ISO-8859-1

Hi Adrian,

I personally agree that adding an informational ref to
draft-ietf-manet-nhdp-olsrv2-sec is a good idea. I will discuss with my
co-authors.

Thanks
Ulrich

On Sunday, June 2, 2013, Adrian Farrel wrote:

> Hi Abdussalam,
>
> I think it is a reasonable suggestion for this I-D to make a forward
> reference
> to draft-ietf-manet-nhdp-olsrv2-sec
> Although this work is clearly scoped to NHDP (RFC 6130) as currently
> specified,
> it is worth an informational reference to note that there is work in
> progress
> that seeks to update NHDP to counter a number of security threats
> described in
> this document.
>
> I do not think, however, that this I-D should attempt to describe the
> situation
> with NHDP after the inclusion of protocol work that has not yet been
> completed.
> Contrary to your suggestion, I think this I-D motivates updates to 6130
> and it
> would be wrong to review this document in the context of changes being
> made to
> address this document.
>
> Thanks,
> Adrian
>
> > I think if we got an effort in IETF to update NHDP [RFC6130] as draft
> > [1] does, why this reviewed I-D of threats does not include [1] in its
> > references to be reviewed before reviewing this NHDP-threat I-D? I
> > suggest to include draft [1] in References section, IMHO, any updates
> > to RFC6130 should be considered by the community while reviewing this
> > I-D.
> >
> > [1] draft-ietf-manet-nhdp-olsrv2-sec-02
>
>

--20cf3071ca32cc028304de3956ae
Content-Type: text/html; charset=ISO-8859-1

Hi Adrian,<div><br></div>I personally agree that adding an informational ref to draft-ietf-manet-nhdp-olsrv2-sec is a good idea. I will discuss with my co-authors.<div><br></div><div>Thanks</div><div>Ulrich<span></span><br>
<div><br>On Sunday, June 2, 2013, Adrian Farrel  wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Abdussalam,<br>
<br>
I think it is a reasonable suggestion for this I-D to make a forward reference<br>
to draft-ietf-manet-nhdp-olsrv2-sec<br>
Although this work is clearly scoped to NHDP (RFC 6130) as currently specified,<br>
it is worth an informational reference to note that there is work in progress<br>
that seeks to update NHDP to counter a number of security threats described in<br>
this document.<br>
<br>
I do not think, however, that this I-D should attempt to describe the situation<br>
with NHDP after the inclusion of protocol work that has not yet been completed.<br>
Contrary to your suggestion, I think this I-D motivates updates to 6130 and it<br>
would be wrong to review this document in the context of changes being made to<br>
address this document.<br>
<br>
Thanks,<br>
Adrian<br>
<br>
&gt; I think if we got an effort in IETF to update NHDP [RFC6130] as draft<br>
&gt; [1] does, why this reviewed I-D of threats does not include [1] in its<br>
&gt; references to be reviewed before reviewing this NHDP-threat I-D? I<br>
&gt; suggest to include draft [1] in References section, IMHO, any updates<br>
&gt; to RFC6130 should be considered by the community while reviewing this<br>
&gt; I-D.<br>
&gt;<br>
&gt; [1] draft-ietf-manet-nhdp-olsrv2-sec-02<br>
<br>
</blockquote></div></div>

--20cf3071ca32cc028304de3956ae--

From adrian@olddog.co.uk  Mon Jun  3 02:09:33 2013
Return-Path: <adrian@olddog.co.uk>
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 27C5421F942B for <ietf@ietfa.amsl.com>; Mon,  3 Jun 2013 02:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.605
X-Spam-Level: 
X-Spam-Status: No, score=-1.605 tagged_above=-999 required=5 tests=[AWL=0.375,  BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
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 SXIIRByzT7Cw for <ietf@ietfa.amsl.com>; Mon,  3 Jun 2013 02:09:19 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 27F7921F93F8 for <ietf@ietf.org>; Mon,  3 Jun 2013 02:08:56 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5397mfg030714;  Mon, 3 Jun 2013 10:07:48 +0100
Received: from 950129200 ([220.109.211.58]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5397i2A030625 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 3 Jun 2013 10:07:46 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l.wood@surrey.ac.uk>, <brian.e.carpenter@gmail.com>, <ietf@ietf.org>
References: <20130528082744.6677.288.idtracker@ietfa.amsl.com>, <51ABD4C4.7070403@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E9D@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E9D@EXMB01CMS.surrey.ac.uk>
Subject: RE: I-D Action: draft-crocker-id-adoption-02.txt
Date: Mon, 3 Jun 2013 10:07:38 +0100
Message-ID: <040d01ce6039$ce571920$6b054b60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKYVSo77dnlPuq6cHIlzZmuHo1uiwIccD/TAiM8InyXbct/0A==
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Mon, 03 Jun 2013 09:09:35 -0000

Thanks Lloyd,

I doubt that we should make commentary on IRTF practices, but you are right that
it would help to clarify "This document applies to the IETF stream only (i.e.,
not the IAB, IRTF, or Independent streams)"

Thanks,
Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> l.wood@surrey.ac.uk
> Sent: 03 June 2013 02:52
> To: brian.e.carpenter@gmail.com; ietf@ietf.org
> Subject: RE: I-D Action: draft-crocker-id-adoption-02.txt
> 
> I'd argue that the draft also needs to discuss IRTF processes, such as they
are.
> 
> though the IRTF groups are sufficiently similar to IETF WGs that you might
think
> the same processes apply, having a draft being adopted by an IRTF group means
> far less, for example, and there appear to be other differences.
> 
> At the very least, a 'this doesn't cover IRTF research groups, where practices
> very widely' is needed. 
> 
> Lloyd Wood
> http://sat-net.com/L.Wood/
> 
> 
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Brian E
> Carpenter [brian.e.carpenter@gmail.com]
> Sent: 03 June 2013 00:27
> To: IETF discussion list
> Subject: Re: I-D Action: draft-crocker-id-adoption-02.txt
> 
> Hi,
> 
> My main positive comment is that it's a good idea to document guidelines
> in this area, and that (viewed as guidelines) I largely agree with
> the draft.
> 
> My main negative comment is that although the draft says it's not a
> formal process document, its language in many places belies that.
> For example:
> 
> > 2. Adoption Process
> >
> >
> > 2.1. Formal Steps
> >
> >
> >    To adopt a new working group document, the chairs need to:
> 
> would be better phrased as:
> 
>  2. Adoption Guidelines
> 
>  2.1. Typical Steps
> 
>     To adopt a new working group document, the chairs often:
> 
> I'd suggest a careful pass through the text, removing instances
> of words like "process", "formal" and "need", and emphasising words
> like "guideline" and "typical" and "might".
> 
> Now some minor comments:
> 
> >    The convention for
> >    identifying an I-D formally under the ownership of a working group is
> >    by the inclusion of "ietf" in the second field of the I-D filename
> >    and the working group name in the third field,
> 
> It's a useful convention but *not* a requirement afaik.
> 
> >    Note
> >    that from time to time a working group will form a design team to
> >    produce the first version of a working group draft.
> 
> I think that's slightly wrong. A design team draft is *not*
> automatically a WG draft. I think this is more accurate:
> 
>    Note
>    that from time to time a working group will form a design team to
>    produce the first version of a document that may be adopted as
>    a working group draft.
> 
> That's an important difference - we've seen cases where design teams
> falsely believed that they had been delegated authority by the WG.
> 
> >      *  Is there strong working group support for the draft?
> 
> I think that's going a bit far. Actually a WG might adopt
> a draft because there is support for the *topic* but not for
> the details of the draft as it stands. Indeed, one objective of
> adopting a draft is so that the WG as a whole obtains control
> of the contents - so that they can change it.
> 
> >       *  What is the position of the working group chairs, concerning
> >          the draft?
> >
> >             [[editor note: I am not sure this is relevant.  Indeed is
> >             might be specifically not relevant.  /a]]
> 
> Actually I'd go the other way: the WG chairs' job at that point is to
> judge the WG's opinion of the draft, not their own opinion. (At least
> once, as a WG chair, I had to declare adoption of a draft to which
> both I and my co-chair were strongly opposed.)
> 
> > 5.1. Individual I-Ds Under WG Care
> ...
> 
> OK, but there are in fact four possible outcomes for such a draft
> 
> 1. As you describe;
> 2. The document proceeds as an individual submission to the IESG
>    without continued WG discussion;
> 3. The document proceeds as an Independent Submission to the RFC Editor;
> 4. The document is abandoned.
> 
> Regards
>    Brian


From jari.arkko@piuha.net  Mon Jun  3 02:32:29 2013
Return-Path: <jari.arkko@piuha.net>
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 0B26921F8F0C for <ietf@ietfa.amsl.com>; Mon,  3 Jun 2013 02:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 I3xrFQ3Dz5x0 for <ietf@ietfa.amsl.com>; Mon,  3 Jun 2013 02:32:21 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id EA58721F904B for <ietf@ietf.org>; Mon,  3 Jun 2013 02:32:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 716B22CC48; Mon,  3 Jun 2013 12:32:18 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJ0BVxcjPJf8; Mon,  3 Jun 2013 12:32:17 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B7D9E2CC3C; Mon,  3 Jun 2013 12:32:17 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Issues in wider geographic participation
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <m2ehcmvs7a.wl%randy@psg.com>
Date: Mon, 3 Jun 2013 12:32:17 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC765610-0B13-457E-A84B-4EA4C2239BC6@piuha.net>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <11B378FD-CADE-49CA-BAC5-814B6E2E07C7@kumari.net> <m2ehcmvs7a.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1503)
Cc: IETF Disgust <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: Mon, 03 Jun 2013 09:32:29 -0000

Randy, Warren,

>> One (IMO) good idea that was mentioned recently (sorry, I cannot
>> remember by whom, may have been Jim Martin) was for someone from the
>> IETF to present a short summary of interesting work at NOG meetings.
>=20
> this has been done many times.  imiho, it has not stirred up much =
useful
> interaction unless the ietfer says something really st00pid.  then it
> gets amusing.

I have found that generic "this is happening" informational is usually =
not so interesting. Whereas discussion on specific topics has been far =
more interesting=85 sessions that talk about some IETF WG technology, =
operator's problems in that area, and someone's experience in deploying =
the stuff are very interesting IMO.

Jari


From rwfranks@gmail.com  Fri May 31 14:02:43 2013
Return-Path: <rwfranks@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 DC1B121F8FF8 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 14:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 9cdIa9rg9mRT for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 14:02:43 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 657F321F8FE8 for <ietf@ietf.org>; Fri, 31 May 2013 14:02:43 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id u16so2745006iet.36 for <ietf@ietf.org>; Fri, 31 May 2013 14:02:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=UL2NFQTZnBBeAJEaHWNqQaoYiSI8qfOB4OJuW44bgFw=; b=PSqaRQ52W6fKFDWFfIY4ukXLKWzMRFtHEanJfjGl9cufUiLWcNEf541UGWJvigD2Rx RvSgGNk9KF4YQzAtRHSyq9cx7WsizCTbr209okaiRQLmm+29IfC1oAMun54LJT385G47 Zmd0GRKjBozQEnBWfyveJ3Xpic1M9fwBXUK7XIJvVU4sfSyYadXvsHxKnaDDYJYiJ/cl r3//vYm3mO44YEmwAVOhKE2pp0l62QEQ8LCPwDHXOB7EmEyWwvNWF/4mZIN7cc0yI9/Q vbsupJsBL2kzs4xdNXZzS1htOgJSSbi/EWAtrXChq46AamazazrEabE10BWZQu3vv/Wr RESg==
X-Received: by 10.50.1.70 with SMTP id 6mr2488093igk.54.1370034162995; Fri, 31 May 2013 14:02:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.252.131 with HTTP; Fri, 31 May 2013 14:02:22 -0700 (PDT)
In-Reply-To: <51A90081.4070804@gmail.com>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net> <51A8E847.9020804@gmail.com> <EF3FB01A-FBEC-4B24-AD7E-9F62B710D709@gmail.com> <51A90081.4070804@gmail.com>
From: Dick Franks <rwfranks@gmail.com>
Date: Fri, 31 May 2013 22:02:22 +0100
Message-ID: <CAKW6Ri5byrr+9a_tcLvgx6bjRGqmbBw30jMabA5a6BasihmGeQ@mail.gmail.com>
Subject: Re: [IETF] RE: Time in the Air
To: carlos@lacnic.net
Content-Type: multipart/alternative; boundary=047d7bd6c7309d9bd004de09ef40
X-Mailman-Approved-At: Mon, 03 Jun 2013 06:35:10 -0700
Cc: "mnot@mnot.net" <mnot@mnot.net>, "ietf@ietf.org" <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: Fri, 31 May 2013 21:02:44 -0000

--047d7bd6c7309d9bd004de09ef40
Content-Type: text/plain; charset=UTF-8

On 31 May 2013 20:56, Carlos M. Martinez <carlosm3011@gmail.com> wrote:

> You are right, Wellington is almost 7 degrees south of Montevideo,
> although I hope it's better served by airlines :D
>

also nearer the equator than most of Europe; a geographical fact of life
that has been conveniently ignored in the discussion thus far!
(with the conspicuous exception of Mark Nottingham's numerical attack on
the topic).

--047d7bd6c7309d9bd004de09ef40
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div><div dir=3D"ltr"><br></div></div>
<div class=3D"gmail_quote">On 31 May 2013 20:56, Carlos M. Martinez <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:carlosm3011@gmail.com" target=3D"_blank">c=
arlosm3011@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">

You are right, Wellington is almost 7 degrees south of Montevideo,<br>
although I hope it&#39;s better served by airlines :D<br></blockquote><br><=
/div>also nearer the equator than most of Europe; a geographical fact of li=
fe that has been conveniently ignored in the discussion thus far!<br>(with =
the conspicuous exception of Mark Nottingham&#39;s numerical attack on the =
topic).<br>

<br><br>

--047d7bd6c7309d9bd004de09ef40--

From yi.jiazi@gmail.com  Mon Jun  3 02:09:04 2013
Return-Path: <yi.jiazi@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 350F721F9420; Mon,  3 Jun 2013 02:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 3MHD7AMuo2cL; Mon,  3 Jun 2013 02:09:01 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5491821F941D; Mon,  3 Jun 2013 02:08:40 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w57so1479491wes.1 for <multiple recipients>; Mon, 03 Jun 2013 02:08:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=1duOUOCk03q6q3LifSq36CejteokCasRVyHyY16hHL4=; b=wgk6rKcq9duNwAzEpdUWbsDfbfBfav1JKqhHCX10cLgq3GEg2sxnJH+L4o88SIZL8J Re0QAroIFPByU4STQUUxOlhVKz1a2MA5Y259DLcwvGE+5zV3HuhqyVTUen1xaIYhMyPe xRrAP8oM3EuMiGfl7uGejYS9imK++O3PSdKCF1D5XxOTMvr5elQLz6vo07Y+SpFD3kR9 c4nS/Z3NfnGOf7jdGZM/50un1PUsaRdi73p2IY1SNs5Vrknx9C9id5hXUiCLRCJKJJXI FZ4yo4kH8MJqDUvz9xpF4BTxx/3CMpPOnVXJBZJderXVglVS0mL9k2ltzwDdGMIWxOpt TuWg==
X-Received: by 10.180.9.195 with SMTP id c3mr11503068wib.61.1370250502077; Mon, 03 Jun 2013 02:08:22 -0700 (PDT)
Received: from 193.55.177-98.saclay.inria.fr ([193.55.177.98]) by mx.google.com with ESMTPSA id e5sm21970622wiy.5.2013.06.03.02.08.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Jun 2013 02:08:21 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Jiazi Yi <yi.jiazi@gmail.com>
In-Reply-To: <CAK=bVC-pDxG0F-kQaPaTw0hY3f9b5=c9nxkCwqdVSw0rmVUDhg@mail.gmail.com>
Date: Mon, 3 Jun 2013 11:08:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3680105-26C7-48B0-B0CE-2D0A3A1BEDDE@gmail.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CADnDZ89BMkpQd2Z8MmCmnUdp0uD6v8Vrbq-z5JeerfiuqpPW0w@mail.gmail.com> <036b01ce5fa9$1afec8e0$50fc5aa0$@olddog.co.uk> <CAK=bVC-pDxG0F-kQaPaTw0hY3f9b5=c9nxkCwqdVSw0rmVUDhg@mail.gmail.com>
To: Ulrich Herberg <ulrich@herberg.name>
X-Mailer: Apple Mail (2.1503)
X-Mailman-Approved-At: Mon, 03 Jun 2013 06:35:23 -0700
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <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: Mon, 03 Jun 2013 09:09:06 -0000

Hi,=20

I think it's OK to add an informative reference to =
draft-ietf-nhdp-olsrv2-sec, which serves as a pointer to the related =
work going on, and possible countermeasures to the threats.=20

best

Jiazi

On Jun 3, 2013, at 07:35 , Ulrich Herberg <ulrich@herberg.name> wrote:

> Hi Adrian,
>=20
> I personally agree that adding an informational ref to =
draft-ietf-manet-nhdp-olsrv2-sec is a good idea. I will discuss with my =
co-authors.
>=20
> Thanks
> Ulrich
>=20
> On Sunday, June 2, 2013, Adrian Farrel wrote:
> Hi Abdussalam,
>=20
> I think it is a reasonable suggestion for this I-D to make a forward =
reference
> to draft-ietf-manet-nhdp-olsrv2-sec
> Although this work is clearly scoped to NHDP (RFC 6130) as currently =
specified,
> it is worth an informational reference to note that there is work in =
progress
> that seeks to update NHDP to counter a number of security threats =
described in
> this document.
>=20
> I do not think, however, that this I-D should attempt to describe the =
situation
> with NHDP after the inclusion of protocol work that has not yet been =
completed.
> Contrary to your suggestion, I think this I-D motivates updates to =
6130 and it
> would be wrong to review this document in the context of changes being =
made to
> address this document.
>=20
> Thanks,
> Adrian
>=20
> > I think if we got an effort in IETF to update NHDP [RFC6130] as =
draft
> > [1] does, why this reviewed I-D of threats does not include [1] in =
its
> > references to be reviewed before reviewing this NHDP-threat I-D? I
> > suggest to include draft [1] in References section, IMHO, any =
updates
> > to RFC6130 should be considered by the community while reviewing =
this
> > I-D.
> >
> > [1] draft-ietf-manet-nhdp-olsrv2-sec-02
>=20


From dhc@dcrocker.net  Mon Jun  3 07:04:38 2013
Return-Path: <dhc@dcrocker.net>
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 8DB9A21E8050 for <ietf@ietfa.amsl.com>; Mon,  3 Jun 2013 07:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 K3wmWO5yXnVi for <ietf@ietfa.amsl.com>; Mon,  3 Jun 2013 07:04:34 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 07FDE21E808B for <ietf@ietf.org>; Mon,  3 Jun 2013 07:04:15 -0700 (PDT)
Received: from [173.255.178.130] (130.178.255.173.client.dyn.strong-mf8.as54203.net [173.255.178.130]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r53E47WD005702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 3 Jun 2013 07:04:13 -0700
Message-ID: <51ACA253.3030304@dcrocker.net>
Date: Mon, 03 Jun 2013 16:04:03 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-crocker-id-adoption-02.txt
References: <20130528082744.6677.288.idtracker@ietfa.amsl.com> <51ABD4C4.7070403@gmail.com>
In-Reply-To: <51ABD4C4.7070403@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 03 Jun 2013 07:04:14 -0700 (PDT)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Mon, 03 Jun 2013 14:04:38 -0000

On 6/3/2013 1:27 AM, Brian E Carpenter wrote:
> My main negative comment is that although the draft says it's not a
> formal process document, its language in many places belies that.
> For example:
...
> I'd suggest a careful pass through the text, removing instances
> of words like "process", "formal" and "need", and emphasising words
> like "guideline" and "typical" and "might".

ack.


> Now some minor comments:
>
>>     The convention for
>>     identifying an I-D formally under the ownership of a working group is
>>     by the inclusion of "ietf" in the second field of the I-D filename
>>     and the working group name in the third field,
>
> It's a useful convention but *not* a requirement afaik.

Times change.  It's now a requirement:

    "If the document is accepted as a working
    group document, then it will have the draft-ietf-<wg acronym> I-D
    filename and will be announced on the working group mailing list by
    the IETF Secretariat. "

         --  http://www.ietf.org/ietf-ftp/1id-guidelines.txt


>>     Note
>>     that from time to time a working group will form a design team to
>>     produce the first version of a working group draft.
>
> I think that's slightly wrong. A design team draft is *not*
> automatically a WG draft. I think this is more accurate:
>
>     Note
>     that from time to time a working group will form a design team to
>     produce the first version of a document that may be adopted as
>     a working group draft.
>
> That's an important difference - we've seen cases where design teams
> falsely believed that they had been delegated authority by the WG.

I think what I wrote doesn't mean what you took from it, but of course 
it's worth rewording, to avoid that possibility.

And to broaden its scope a bit, perhaps:

    Note that one way of formulating the first version of a working 
group draft is for the group to commission a design team, or even for 
the design team to self-organize and offer its output for working group 
consideration.


>>       *  Is there strong working group support for the draft?
>
> I think that's going a bit far. Actually a WG might adopt
> a draft because there is support for the *topic* but not for
> the details of the draft as it stands. Indeed, one objective of
> adopting a draft is so that the WG as a whole obtains control
> of the contents - so that they can change it.

Yeah.  Wording is off.  Meant what you suggest, not literally what was 
written.  Will modify accordingly.


>>        *  What is the position of the working group chairs, concerning
>>           the draft?
>>
>>              [[editor note: I am not sure this is relevant.  Indeed is
>>              might be specifically not relevant.  /a]]
>
> Actually I'd go the other way: the WG chairs' job at that point is to
> judge the WG's opinion of the draft, not their own opinion. (At least
> once, as a WG chair, I had to declare adoption of a draft to which
> both I and my co-chair were strongly opposed.)

moved to the next list, of stuff that's inappropriate...


>
>> 5.1. Individual I-Ds Under WG Care
> ...
>
> OK, but there are in fact four possible outcomes for such a draft
>
> 1. As you describe;
> 2. The document proceeds as an individual submission to the IESG
>     without continued WG discussion;
> 3. The document proceeds as an Independent Submission to the RFC Editor;
> 4. The document is abandoned.


mumble. yeah.

but i hope we don't spend too much energy on this topic, given how rare 
it is.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From chris.dearlove@baesystems.com  Mon Jun  3 08:38:27 2013
Return-Path: <chris.dearlove@baesystems.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 2E33911E80D3 for <ietf@ietfa.amsl.com>; Mon,  3 Jun 2013 08:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.74
X-Spam-Level: 
X-Spam-Status: No, score=-8.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_HI=-8]
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 ZdA5XRZHQfki for <ietf@ietfa.amsl.com>; Mon,  3 Jun 2013 08:38:22 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 9AF6D11E80D5 for <ietf@ietf.org>; Mon,  3 Jun 2013 08:38:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,793,1363132800"; d="scan'208";a="290223547"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 03 Jun 2013 16:38:21 +0100
X-IronPort-AV: E=Sophos;i="4.87,793,1363132800"; d="scan'208";a="17406222"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasodc005.greenlnk.net with ESMTP; 03 Jun 2013 16:38:21 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.244]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.02.0328.009; Mon, 3 Jun 2013 16:38:21 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Time in the Air
Thread-Topic: Time in the Air
Thread-Index: AQHOXeWT8kT0pdg1tEqSfDTZAbrq4JkfQqOAgATh9xA=
Date: Mon, 3 Jun 2013 15:38:20 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25079AF1@GLKXM0002V.GREENLNK.net>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
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: Mon, 03 Jun 2013 15:38:27 -0000

Lloyd Wood
> quiet time on a plane can be productive time.

Economy class or something better?

-- =

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From jnc@mercury.lcs.mit.edu  Mon Jun  3 08:56:49 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
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 2B93B21F9774 for <ietf@ietfa.amsl.com>; Mon,  3 Jun 2013 08:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 W5dz2TIkN09u for <ietf@ietfa.amsl.com>; Mon,  3 Jun 2013 08:56:44 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id F16D721F9732 for <ietf@ietf.org>; Mon,  3 Jun 2013 08:56:43 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id E6AE118C0F8; Mon,  3 Jun 2013 11:56:42 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Not Listening to the Ops Customer
Message-Id: <20130603155642.E6AE118C0F8@mercury.lcs.mit.edu>
Date: Mon,  3 Jun 2013 11:56:42 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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: Mon, 03 Jun 2013 15:56:49 -0000

    > From: "cb.list6" <cb.list6@gmail.com>

    > the emergent complex dynamical system we call the internet ... which is
    > almost completely zero compliant to the e2e principle. Not that e2e is
    > the wrong principle, but ipv4 could not support it as of 10+ years ago.
    > Hence, nearly every internet node is behind a stateful device
    > ...
    > Yet, corners of the ietf call this real world internet of middleboxes
    > as broken. As some of it is broken, so you have things ... to bust
    > through it. Mutation happens.
    > That said, the teaching moment here is look back and realize the
    > internet was not engineered, if was emerged.
    > Given that the internet is not engineered ... how do we make it go
    > fast, bigger, better given the few levers we have.

Exactly. The Internet is evolving, and can we push it in a better direction,
and if so, how?

In all of this, the bottom line, to me, is that we have to be aware of the
limits of our power. Mandating forklift replaces is just a non-starter. By
and large, new stuff has to interoperate to the maximum extent possible with
unmodified 'stuff'; an approach that don't require _any_ host modifications
is almost a sine qua non.

And it was long (and remains) a truism of system design that security can't
be added at the last stages - it has to be 'baked in' all the way through the
design process. The same is true, now, of deployment and interoperability.


I persist in thinking that those 32-bit names are continuing their evolution
into local-scope names, with translation at naming region boundaries. How can
we improve that - reduce the brittleness of the middleboxes you refer to, by
making their data more visible (and thus replicable, etc)?

And we still need global namespaces. DNS names are slowly becoming more key
(the Web now makes them a key namespace at the protocol level, not just the
content), but what else? At one point the IETF considered trying to craft a
new endpoint namespace (through the NSRG, if I have remembered the name
correctly), but I think in retrospect that's a non-starter - changing TCP
(which is what that would require) is not really an option (see point 1).

Within that 'deployable' envelope, I am now back to where I was almost 30
years ago, which is that _probably_ the thing to deploy is a new location
namespace, for use by the path-selection (since only _some_ routers have to
know about that). That's not a namespace the Internet has now, and so we'd be
less constrained in doing so, and it's one the Internet really needs.

	Noel

From abdussalambaryun@gmail.com  Mon Jun  3 09:10:30 2013
Return-Path: <abdussalambaryun@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 7CE4A21F8D90; Mon,  3 Jun 2013 09:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.150,  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 iYV+ETGb8nQJ; Mon,  3 Jun 2013 09:10:29 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id CBDFC21F86D3; Mon,  3 Jun 2013 09:10:29 -0700 (PDT)
Received: by mail-pa0-f43.google.com with SMTP id hz10so963072pad.30 for <multiple recipients>; Mon, 03 Jun 2013 09:10:29 -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=XN5rXln/2H9HkpT0vbgkUze6JAog0Nx5gvSR1XsB8XQ=; b=fcO7Nerva5eZmAZypDQ8LdaIbkCv53FlnMHdnMKnztWuOyaS3lXYK4EqhPYUTjGjCn UOg3topegfIedqvMMpU5j9MToD/S/QE0tR+ienVfsPLhPtw005hAQ4N/5eDvmUKL+Wne t2ymZ72CZaVbpDKWWDcudz9UXs1DZtCwmxLzsBJDdwpgLbbmUu0GFs5vwAG75eefBPUA UQbX2hOgdsrlxK3el7aSRk+UZhb0WRYZbYwk+gP3d/uDfoZ70JnnO+3LcDreWpoQFafT cB+kQYfrulrlQULM/15UIj4V1+II2xr1zO87Y5jMv/0lUqyfNM3/TdJvZe1uc3kJw+If p9ig==
MIME-Version: 1.0
X-Received: by 10.68.176.197 with SMTP id ck5mr23806308pbc.165.1370275829571;  Mon, 03 Jun 2013 09:10:29 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Mon, 3 Jun 2013 09:10:29 -0700 (PDT)
In-Reply-To: <CAK=bVC-pDxG0F-kQaPaTw0hY3f9b5=c9nxkCwqdVSw0rmVUDhg@mail.gmail.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CADnDZ89BMkpQd2Z8MmCmnUdp0uD6v8Vrbq-z5JeerfiuqpPW0w@mail.gmail.com> <036b01ce5fa9$1afec8e0$50fc5aa0$@olddog.co.uk> <CAK=bVC-pDxG0F-kQaPaTw0hY3f9b5=c9nxkCwqdVSw0rmVUDhg@mail.gmail.com>
Date: Mon, 3 Jun 2013 17:10:29 +0100
Message-ID: <CADnDZ89nH3+REiN27Wci5aSX=JZqyFv9aRWpbOef2qKTi80Q_w@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bd75b0010e79504de4234f6
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "iesg@ietf.org" <iesg@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: Mon, 03 Jun 2013 16:10:30 -0000

--047d7bd75b0010e79504de4234f6
Content-Type: text/plain; charset=ISO-8859-1

I would hope that IETF add my name in the acknowledgement section of the
I-D. I complained to AD about that my efforts in WGLC was not acknowledged
by editors even after my request, however, I did not stop reviewing (trying
not be discouraged) which I will complete on 6 June with the final
comments. Therefore, this message (can be added as a comment on the I-D) is
an objection to section 8 that ignores acknowledge input/review effort
related to the I-D.

AB


On Mon, Jun 3, 2013 at 6:35 AM, Ulrich Herberg <ulrich@herberg.name> wrote:

> Hi Adrian,
>
> I personally agree that adding an informational ref to
> draft-ietf-manet-nhdp-olsrv2-sec is a good idea. I will discuss with my
> co-authors.
>
> Thanks
> Ulrich
>
>
> On Sunday, June 2, 2013, Adrian Farrel wrote:
>
>> Hi Abdussalam,
>>
>> I think it is a reasonable suggestion for this I-D to make a forward
>> reference
>> to draft-ietf-manet-nhdp-olsrv2-sec
>> Although this work is clearly scoped to NHDP (RFC 6130) as currently
>> specified,
>> it is worth an informational reference to note that there is work in
>> progress
>> that seeks to update NHDP to counter a number of security threats
>> described in
>> this document.
>>
>> I do not think, however, that this I-D should attempt to describe the
>> situation
>> with NHDP after the inclusion of protocol work that has not yet been
>> completed.
>> Contrary to your suggestion, I think this I-D motivates updates to 6130
>> and it
>> would be wrong to review this document in the context of changes being
>> made to
>> address this document.
>>
>> Thanks,
>> Adrian
>>
>> > I think if we got an effort in IETF to update NHDP [RFC6130] as draft
>> > [1] does, why this reviewed I-D of threats does not include [1] in its
>> > references to be reviewed before reviewing this NHDP-threat I-D? I
>> > suggest to include draft [1] in References section, IMHO, any updates
>> > to RFC6130 should be considered by the community while reviewing this
>> > I-D.
>> >
>> > [1] draft-ietf-manet-nhdp-olsrv2-sec-02
>>
>>

--047d7bd75b0010e79504de4234f6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I would hope that IETF add my name in the acknowledge=
ment section of the I-D. I complained to AD about that my efforts in WGLC w=
as not acknowledged by editors even after=A0my request, however, I did not =
stop reviewing (trying not be discouraged) which I=A0will complete on 6 Jun=
e with the final comments. Therefore, this message (can be added as a comme=
nt on the I-D)=A0is an objection to=A0section 8 that ignores acknowledge=A0=
input/review effort related to the I-D.</div>
<div>=A0</div><div>AB</div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Mon, Jun 3, 2013 at 6:35 AM, Ulrich Herberg <span dir=3D"l=
tr">&lt;<a href=3D"mailto:ulrich@herberg.name" target=3D"_blank">ulrich@her=
berg.name</a>&gt;</span> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">Hi Adrian,<div><br></div>I personally agree that adding an=
 informational ref to draft-ietf-manet-nhdp-olsrv2-sec is a good idea. I wi=
ll discuss with my co-authors.<div>
<br></div><div>Thanks</div><div><span class=3D"HOEnZb"><font color=3D"#8888=
88">Ulrich</font></span><div><div class=3D"h5"><span></span><br>
<div><br>On Sunday, June 2, 2013, Adrian Farrel  wrote:<br><blockquote styl=
e=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,20=
4,204);border-left-width:1px;border-left-style:solid" class=3D"gmail_quote"=
>
Hi Abdussalam,<br>
<br>
I think it is a reasonable suggestion for this I-D to make a forward refere=
nce<br>
to draft-ietf-manet-nhdp-olsrv2-sec<br>
Although this work is clearly scoped to NHDP (RFC 6130) as currently specif=
ied,<br>
it is worth an informational reference to note that there is work in progre=
ss<br>
that seeks to update NHDP to counter a number of security threats described=
 in<br>
this document.<br>
<br>
I do not think, however, that this I-D should attempt to describe the situa=
tion<br>
with NHDP after the inclusion of protocol work that has not yet been comple=
ted.<br>
Contrary to your suggestion, I think this I-D motivates updates to 6130 and=
 it<br>
would be wrong to review this document in the context of changes being made=
 to<br>
address this document.<br>
<br>
Thanks,<br>
Adrian<br>
<br>
&gt; I think if we got an effort in IETF to update NHDP [RFC6130] as draft<=
br>
&gt; [1] does, why this reviewed I-D of threats does not include [1] in its=
<br>
&gt; references to be reviewed before reviewing this NHDP-threat I-D? I<br>
&gt; suggest to include draft [1] in References section, IMHO, any updates<=
br>
&gt; to RFC6130 should be considered by the community while reviewing this<=
br>
&gt; I-D.<br>
&gt;<br>
&gt; [1] draft-ietf-manet-nhdp-olsrv2-sec-02<br>
<br>
</blockquote></div></div></div></div>
</blockquote></div><br></div></div>

--047d7bd75b0010e79504de4234f6--

From ron.even.tlv@gmail.com  Mon Jun  3 16:36:45 2013
Return-Path: <ron.even.tlv@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 95F4121E80BC; Mon,  3 Jun 2013 16:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=0.374,  BAYES_00=-2.599, HTML_MESSAGE=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 xDDCUOeFSCk9; Mon,  3 Jun 2013 16:36:31 -0700 (PDT)
Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id E3D3B21E8084; Mon,  3 Jun 2013 16:27:21 -0700 (PDT)
Received: by mail-ea0-f171.google.com with SMTP id m14so1357626eaj.2 for <multiple recipients>; Mon, 03 Jun 2013 16:27:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=+dw+/0rEAOgmZOjiNqe9xKF7OccO5uSxv9hXkYO+wPw=; b=TrElih34RBk9LJj58N+1Ml8+606WQDTUZLLtjhbEV1hADfuVpxhJLpwbknmF0wDcBh CT+F1jZjhGjAqmzM1hUX3sZdpaaPBZFD81odTis6S/pYljWquhiBxhF2cX27YBYW7AE/ l56gOSYj4xX4PFU5c7jU62RgDFaOBmJoEQ8ep/X++tbG0zhhF6eqPM9lbE78w5g0sctb 30DzKZQC82DyLglEEbUkLWwnoftRi8ZA/ZbM/aWrcKrJzpZ72lkA91ZCYpfFtRzheGOf 3d2gvO3l3ZoZZiQpJL6B2ORIHxQl0j7s2woBQqk4VSnWknfSqxagkIWtATqXfy05EDah 1JSA==
X-Received: by 10.14.179.68 with SMTP id g44mr24650241eem.18.1370302040836; Mon, 03 Jun 2013 16:27:20 -0700 (PDT)
Received: from RoniE ([109.64.225.31]) by mx.google.com with ESMTPSA id c5sm72183724eeu.8.2013.06.03.16.27.18 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 03 Jun 2013 16:27:20 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <Simo.Veikkolainen@nokia.com>, <draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org>
References: <000301ce5c98$278d0220$76a70660$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com>
In-Reply-To: <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com>
Subject: RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
Date: Tue, 4 Jun 2013 02:26:05 +0300
Message-ID: <027001ce60b1$ba2ecbf0$2e8c63d0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0271_01CE60CA.DF7D1560"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQD2ctd9kjZ9dlpMJt4mULENla+sLwGDWn0omshh2mA=
Content-Language: en-us
Cc: gen-art@ietf.org, 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: Mon, 03 Jun 2013 23:36:45 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0271_01CE60CA.DF7D1560
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Simo,

For the PSTN case the document explain how to construct the m-line PSTN is
used based on the ccap using port 9. This is not specified for the ATM case.
So if it is not mentioned it should be clear that using  ccap for ATM is not
specified and need another document

Roni

 

From: Simo.Veikkolainen@nokia.com [mailto:Simo.Veikkolainen@nokia.com] 
Sent: 31 May, 2013 1:14 PM
To: ron.even.tlv@gmail.com;
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of
draft-ietf-mmusic-sdp-miscellaneous-caps-05

 

Hello Roni,

Please see my answer below prefixed with [SV].

 

From: ext Roni Even [mailto:ron.even.tlv@gmail.com] 
Sent: 29. toukokuuta 2013 21:13
To: draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05

 

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-mmusic-sdp-miscellaneous-caps-05

Reviewer: Roni Even

Review Date:2013-5-29

IETF LC End Date: 2013-6-4

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as Standard track RFC.

 

 

Major issues:

 

Minor issues:

1.       I can understand from the draft that when you have IP and PSTN
nettype it is requires that the ccap will be for the PSTN. What happens if
you want to have the ccap nettype as ATM to be used with IP in the c=

 

[SV] If either endpoint does not support ATM, the "c=" line with the ATM
address would not get used (either it is not offered, or the Answerer
removes that from the SDP configurations). In case both endpoints actually
support and want to use ATM as alternative to IP based bearer, the
conventions in RFC3108 would need to be followed when crafting the SDP
configurations. That said, I haven't taken a detailed look at RFC3108 to see
if the ATM based media can be negotiated using the SDP Capability
Negotiation framework and its current extensions.

 

Simo

 

Nits/editorial comments:

 


------=_NextPart_000_0271_01CE60CA.DF7D1560
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1745645097;
	mso-list-type:hybrid;
	mso-list-template-ids:-1464020766 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Simo,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>For the PSTN case the =
document explain how to construct the m-line PSTN is used based on the =
ccap using port 9. This is not specified for the ATM case. So if it is =
not mentioned it should be clear that using &nbsp;ccap for ATM is not =
specified and need another document<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Simo.Veikkolainen@nokia.com [mailto:Simo.Veikkolainen@nokia.com] =
<br><b>Sent:</b> 31 May, 2013 1:14 PM<br><b>To:</b> =
ron.even.tlv@gmail.com; =
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org<br><b>Cc:</b>=
 ietf@ietf.org; gen-art@ietf.org<br><b>Subject:</b> RE: Gen-ART LC =
review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05<o:p></o:p></span></p></div></=
div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hello Roni,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Please see my answer =
below prefixed with [SV].<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><a =
name=3D"_____replyseparator"></a><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ext Roni Even [<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Sent:</b> 29. toukokuuta 2013 21:13<br><b>To:</b> <a =
href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.or=
g">draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br><b>=
Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
Gen-ART LC review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05<o:p></o:p></span></p></div></=
div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-mmusic-sdp-miscellaneous-caps-05</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;5&#8211;29<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-6&#8211;4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as Standard track =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I can =
understand from the draft that when you have IP and PSTN nettype it is =
requires that the ccap will be for the PSTN. What happens if you want to =
have the ccap nettype as ATM to be used with IP in the =
c=3D<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[SV] If either endpoint does not support ATM, the &#8220;c=3D&#8221; =
line with the ATM address would not get used (either it is not offered, =
or the Answerer removes that from the SDP configurations). In case both =
endpoints actually support and want to use ATM as alternative to IP =
based bearer, the conventions in RFC3108 would need to be followed when =
crafting the SDP configurations. That said, I haven&#8217;t taken a =
detailed look at RFC3108 to see if the ATM based media can be negotiated =
using the SDP Capability Negotiation framework and its current =
extensions.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Simo<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_0271_01CE60CA.DF7D1560--


From chris.dearlove@baesystems.com  Tue Jun  4 03:06:59 2013
Return-Path: <chris.dearlove@baesystems.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 D429021F9B4E for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 03:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.669
X-Spam-Level: 
X-Spam-Status: No, score=-9.669 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 RTfXNt7ezWl7 for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 03:06:46 -0700 (PDT)
Received: from ukmta2.baesystems.com (ukmta2.baesystems.com [20.133.0.56]) by ietfa.amsl.com (Postfix) with ESMTP id 836FB21F9A16 for <ietf@ietf.org>; Tue,  4 Jun 2013 02:04:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,798,1363132800"; d="scan'208";a="11987986"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds004ir.sharelnk.net with ESMTP; 04 Jun 2013 10:04:03 +0100
X-IronPort-AV: E=Sophos;i="4.87,798,1363132800"; d="scan'208";a="17755096"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasmds017.greenlnk.net with ESMTP; 04 Jun 2013 10:04:02 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.244]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.02.0328.009; Tue, 4 Jun 2013 10:04:03 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Randy Bush <randy@psg.com>
Subject: RE: Time in the Air
Thread-Topic: Time in the Air
Thread-Index: AQHOXeWT8kT0pdg1tEqSfDTZAbrq4JkfQqOAgACzFwCAAAGIgIAAGHkAgAU4isA=
Date: Tue, 4 Jun 2013 09:04:02 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25079C9A@GLKXM0002V.GREENLNK.net>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <8C48B86A895913448548E6D15DA7553B900110@xmb-rcd-x09.cisco.com> <m2obbqu02e.wl%randy@psg.com> <8D23D4052ABE7A4490E77B1A012B6307751BFDA8@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751BFDA8@mbx-01.win.nominum.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: IETF Disgust <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: Tue, 04 Jun 2013 10:06:59 -0000

If always meeting in one place, we should obviously consult the work on whe=
re is central, which shows London at the top of the list. Twice.

(Yes, I do know where I've made a deliberate error in reaching that conclus=
ion.)

-- =

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ted=
 Lemon
Sent: 01 June 2013 03:17
To: Randy Bush
Cc: IETF Disgust
Subject: Re: Time in the Air

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

On May 31, 2013, at 8:49 PM, Randy Bush <randy@psg.com> wrote:
> i too, but tokyo.  induce.  answer, remote participation.  i hope that a
> decade from now many of us will not need to fly.

We could just always meet in Tokyo.   I'd be down with that...

:)


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From dhc@dcrocker.net  Tue Jun  4 03:47:54 2013
Return-Path: <dhc@dcrocker.net>
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 6A6C021F9C1A; Tue,  4 Jun 2013 03:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
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 eONWySXKKy8k; Tue,  4 Jun 2013 03:47:40 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B238521F96E8; Tue,  4 Jun 2013 02:44:27 -0700 (PDT)
Received: from [172.16.16.101] (62-50-200-178.client.stsn.net [62.50.200.178]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r549iAMx028051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 4 Jun 2013 02:44:15 -0700
Message-ID: <51ADB6E6.5030300@dcrocker.net>
Date: Tue, 04 Jun 2013 11:44:06 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Douglas Otis <doug.mtview@gmail.com>
Subject: Re: Review of: draft-otis-dkim-harmful
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com>
In-Reply-To: <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 04 Jun 2013 02:44:18 -0700 (PDT)
Cc: "Murray S. Kucherawy" <msk@blackops.org>, Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Dave Rand <dave_rand@trendmicro.com>, dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Tue, 04 Jun 2013 10:47:54 -0000

The problems with this draft persist...



> Organizations such as M3AAWG hope to use DKIM will be able as a required
>    acceptance requirement to offer better ensure a domain identity to provide offers a
>

I happen to be sitting in a M3AAWG meeting as I write this note and it 
happens that I just came out of a session in which someone tried to 
assert the use of DKIM (or SPF) as a 'requirement' and the group was 
very clear that no such 'requirement' exists or is a goal.

of coure, this is quite different from seeking to promote "greater use" 
of such authentication, but the word 'required', above, is wrong.  This 
is worth noting since the premise of the I-D concerns problematic 
policies and practices.

Certainly some individuals advocate such a requirement, but that's 
different from saying that a primary anti-abuse organization advocates it.


> There are
>    proposals within the IETF aimed at establishing DKIM as a basis for
>    reputation schemes in the Repute WG (i.e. section 3.2 of
>    [I-D.ietf-repute-email-identifiers] which introduces DKIM domains
>    being used along with SMTP client IP addresses and rfc5321.helo also
>    identifying the SMTP client.  Identifying the SMTP client encompasses
>    both "Who Initiated" and "To Whom" message elements to support fair
>    negative assertions.  However, DKIM does not encompass this essential
>    information.

The repute drafts specify a query mechanisms; they don't "establish" use 
of the information being queried.  DKIM is already used for reputation.

Worse, the draft here seems to conflate address-based reputation and 
role-based reputation with dkim-based reputation.  That's probably 
because any handling agent can add a dkim signature to a message, 
including an "SMTP client".

However DKIM does not specify the role of the signing agent and doesn't 
care.  Consequently the concern apparently being raised here seems to be 
fundamentally confused about what DKIM is doing.



> Simply publishing this draft
>    appears to have already increase the level of multiple FROM header
>    field abuse seen where it is now at 21% of signed DKIM messages.

Sounds pretty scary.  No doubt the assertion is publicly verifiable, 
including the basis for asserting that it is causing problem?


>  DKIM signs only fragments of an email message, so it is more proper
>    to refer to "DKIM Signed Fragments", and not "DKIM Signed Messages".
>    Normal DKIM signature validation offers a simple PASS/FAIL
>    associating it with a specific domain.  When a recipient receives a
>    PASS status, only the last FROM header field message fragment is
>    ensured to have been included in the DKIM signature process.

This continues the draft's fundamental failure in understanding what 
DKIM does.  DKIM does not validate the message; it uses crypto-signing 
methodology to "affix" a domain name to the message.  In other words, it 
validates the attached domain name, not the message.

As such, the choice of what message parts to include in the signing hash 
is more like deciding how strong the glue on the stamp should be, than 
deciding how to prove the message is valid.


> DKIM's trust related role is to better ensure message delivery to a
>    user's in-box.  Unless DKIM ensures this trust is not used to
>    perpetrate deception, no positive assertions regarding a DKIM domain
>    is safe.  As a result, DKIM can not be used with either positive or
>    negative reputation assertions in its current form.

As logic sequences go, this paragraph is difficult reading.  At least 
one of it's key errors is in claiming that a validation technique has a 
responsibility for how the validated information is used.  DKIM has a 
responsibility for provide a validated domain name.  It does that.

Policies and practices for the /use/ of that domain name are outside of 
the scope of the DKIM signing specification.

When you show your drivers license to validate your identity, it does 
not mean you are a good credit risk.  Nor does it mean that the 
Department of Motor Vehicles has a responsibility to ensure that you are.


> The FROM header field is the Author identifier in section 11.1 of
>    [I-D.kucherawy-dmarc-base].  The DMARC specification offers normative
>    language that a message SHOULD be rejected when multiple FROM header
>    fields are detected.  This requirement would not be necessary or
>    impose protocol layer violations if DKIM did not offer valid
>    signature results when repeated header fields violate [RFC5322].

It's good to see this text refer to a layer violation, since the text is 
one.

Discussion of DMARC is entirely outside of the scope of DKIM, unless use 
of DMARC uncovers some technical flaw in DKIM.  It hasn't done that so 
far and the text in the draft doesn't offer any.

At the least, the draft appears to be claiming that DKIM validates the 
author (rfc5322.From) field.  It doesn't do that validation and it 
doesn't purport to.

It appears the authors have some concerns about the way DMARC uses DKIM. 
  That well might be a worthy discussion... about DMARC.  It actually 
has nothing to do with the DKIM signing specification.


> Trust established by a signing domain is being exploited to mislead
>    recipients about who authored a message.

The draft continues to make broad, onerous claims like this, but 
provides no documentation to indicate that the DKIM signing 
specification is flawed in the function it is performing:  attaching a 
validated domain name to a message.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From doug.mtview@gmail.com  Tue Jun  4 05:33:11 2013
Return-Path: <doug.mtview@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 5220821F9C87; Tue,  4 Jun 2013 05:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_14=0.6]
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 LtHerNk3rzzc; Tue,  4 Jun 2013 05:33:01 -0700 (PDT)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id B7B4D21F9CD0; Tue,  4 Jun 2013 04:08:45 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 17so164017iea.3 for <multiple recipients>; Tue, 04 Jun 2013 04:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=KNXgsMssfxZkmUkZ+rNIlThb+SWGrbWUi1kCvizYpJ8=; b=engJGoudpODM9+2hDfHI6D8okDte5XFWRaICbbY476rGAkfXclEiX2bxgCbvmX95Mg h/ED5kIL9Q3t2Jr9Ycw+NbPPUkHf1oEmN73nFhNW56/V+W3KZi2E8dpn+TcFcuVmDF5h hLszlVsT+uTO/GbpFnA9NcMsCPbE6+MHJHs6YlNHxUtndc7BQ0wOFSamOgYdj1NZ74qH H2t1bUonqF84lpt8yfYJChJHE/kQgShAXwl5gTdHthr35urwqzG3HUBt1wZSAKY4Wh7y LTT7FBWeqhnwnffv4BLgeYtHd7x9mJ3aksGiaHFB5/TvIzAi3WVkTbxlcTQk40thzAQS 8kzA==
X-Received: by 10.50.111.233 with SMTP id il9mr423922igb.103.1370344125312; Tue, 04 Jun 2013 04:08:45 -0700 (PDT)
Received: from [10.12.1.50] ([82.112.204.69]) by mx.google.com with ESMTPSA id r20sm1247071ign.8.2013.06.04.04.08.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Jun 2013 04:08:44 -0700 (PDT)
Subject: Re: Review of: draft-otis-dkim-harmful
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <51ADB6E6.5030300@dcrocker.net>
Date: Tue, 4 Jun 2013 13:08:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com>
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1503)
Cc: "Murray S. Kucherawy" <msk@blackops.org>, Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Dave Rand <dave_rand@trendmicro.com>
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: Tue, 04 Jun 2013 12:33:11 -0000

Dear Dave,

On Jun 4, 2013, at 11:44 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> The problems with this draft persist...
>=20
>> Organizations such as M3AAWG hope to use DKIM will be able as a =
required
>>   acceptance requirement to offer better ensure a domain identity to =
provide offers a
>=20
> I happen to be sitting in a M3AAWG meeting as I write this note and it =
happens that I just came out of a session in which someone tried to =
assert the use of DKIM (or SPF) as a 'requirement' and the group was =
very clear that no such 'requirement' exists or is a goal.
>=20
> of coure, this is quite different from seeking to promote "greater =
use" of such authentication, but the word 'required', above, is wrong.  =
This is worth noting since the premise of the I-D concerns problematic =
policies and practices.
>=20
> Certainly some individuals advocate such a requirement, but that's =
different from saying that a primary anti-abuse organization advocates =
it.

"Hope to use", rather than advocates.  We stand by the assertion, but we =
can further modify this statement.
>=20
>=20
>> There are
>>   proposals within the IETF aimed at establishing DKIM as a basis for
>>   reputation schemes in the Repute WG (i.e. section 3.2 of
>>   [I-D.ietf-repute-email-identifiers] which introduces DKIM domains
>>   being used along with SMTP client IP addresses and rfc5321.helo =
also
>>   identifying the SMTP client.  Identifying the SMTP client =
encompasses
>>   both "Who Initiated" and "To Whom" message elements to support fair
>>   negative assertions.  However, DKIM does not encompass this =
essential
>>   information.
>=20
> The repute drafts specify a query mechanisms; they don't "establish" =
use of the information being queried.  DKIM is already used for =
reputation.
>=20
> Worse, the draft here seems to conflate address-based reputation and =
role-based reputation with dkim-based reputation.  That's probably =
because any handling agent can add a dkim signature to a message, =
including an "SMTP client".
>=20
> However DKIM does not specify the role of the signing agent and =
doesn't care.  Consequently the concern apparently being raised here =
seems to be fundamentally confused about what DKIM is doing.

The combination of an assertion a message fragment is "authenticated" =
and conflation of that assertion is happening today.  More on this in a =
bit.  The authors are in no way confused.

>> Simply publishing this draft
>>   appears to have already increase the level of multiple FROM header
>>   field abuse seen where it is now at 21% of signed DKIM messages.
>=20
> Sounds pretty scary.  No doubt the assertion is publicly verifiable, =
including the basis for asserting that it is causing problem?

Sure.  Simply observe the increasing signed DKIM messages that have =
multiple From:'s.

>> DKIM signs only fragments of an email message, so it is more proper
>>   to refer to "DKIM Signed Fragments", and not "DKIM Signed =
Messages".
>>   Normal DKIM signature validation offers a simple PASS/FAIL
>>   associating it with a specific domain.  When a recipient receives a
>>   PASS status, only the last FROM header field message fragment is
>>   ensured to have been included in the DKIM signature process.
>=20
> This continues the draft's fundamental failure in understanding what =
DKIM does.  DKIM does not validate the message; it uses crypto-signing =
methodology to "affix" a domain name to the message.  In other words, it =
validates the attached domain name, not the message.
>=20
> As such, the choice of what message parts to include in the signing =
hash is more like deciding how strong the glue on the stamp should be, =
than deciding how to prove the message is valid.

Unfortunately, affixation of the domain name to the message is the root =
of the issue.   More on this in a bit.

>> DKIM's trust related role is to better ensure message delivery to a
>>   user's in-box.  Unless DKIM ensures this trust is not used to
>>   perpetrate deception, no positive assertions regarding a DKIM =
domain
>>   is safe.  As a result, DKIM can not be used with either positive or
>>   negative reputation assertions in its current form.
>=20
> As logic sequences go, this paragraph is difficult reading.  At least =
one of it's key errors is in claiming that a validation technique has a =
responsibility for how the validated information is used.  DKIM has a =
responsibility for provide a validated domain name.  It does that.
>=20
> Policies and practices for the /use/ of that domain name are outside =
of the scope of the DKIM signing specification.
>=20
> When you show your drivers license to validate your identity, it does =
not mean you are a good credit risk.  Nor does it mean that the =
Department of Motor Vehicles has a responsibility to ensure that you =
are.

There's quite a difference between the use of a Department of Motor =
Vehicles driver's license to validate your identity, and using a [insert =
theme park of your choice] driver's license to validate your identity.  =
In one, significant thought has gone into the  process, including =
several field verifiable methods to ensure that the license itself is =
valid.  In the other, you can simply write your name on the top of the =
license, and it becomes valid.

Again; we are objecting to the absolute ease of forgery facilitated by =
DKIM. =20

>> The FROM header field is the Author identifier in section 11.1 of
>>   [I-D.kucherawy-dmarc-base].  The DMARC specification offers =
normative
>>   language that a message SHOULD be rejected when multiple FROM =
header
>>   fields are detected.  This requirement would not be necessary or
>>   impose protocol layer violations if DKIM did not offer valid
>>   signature results when repeated header fields violate [RFC5322].
>=20
> It's good to see this text refer to a layer violation, since the text =
is one.
>=20
> Discussion of DMARC is entirely outside of the scope of DKIM, unless =
use of DMARC uncovers some technical flaw in DKIM.  It hasn't done that =
so far and the text in the draft doesn't offer any.
>=20
> At the least, the draft appears to be claiming that DKIM validates the =
author (rfc5322.From) field.  It doesn't do that validation and it =
doesn't purport to.
>=20
> It appears the authors have some concerns about the way DMARC uses =
DKIM.  That well might be a worthy discussion... about DMARC.  It =
actually has nothing to do with the DKIM signing specification.

This assertion is simply wrong. =20

>> Trust established by a signing domain is being exploited to mislead
>>   recipients about who authored a message.
>=20
> The draft continues to make broad, onerous claims like this, but =
provides no documentation to indicate that the DKIM signing =
specification is flawed in the function it is performing:  attaching a =
validated domain name to a message.

DKIM does not, in its current form, attach a validated domain name to a =
message.  By adding one line "MUST NOT validate a message with multiple =
From:'s", DKIM will attach a validated domain name to a message.

In its current form, DKIM simply attaches a domain name in an unseen =
message fragment, not a message.  The ease in which the only assured =
visible fragment of the message signed by the domain being forged makes =
it impossible for appropriate handling to be applied or likely harm =
prevented.

Thank you for your review.  We'll take your input and review how this =
draft can be better clarified.

Regards,
Douglas Otis=

From barryleiba@gmail.com  Tue Jun  4 07:55:28 2013
Return-Path: <barryleiba@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 C611821F9ADC; Tue,  4 Jun 2013 07:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.933
X-Spam-Level: 
X-Spam-Status: No, score=-101.933 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 PbkQ8Vxcvngq; Tue,  4 Jun 2013 07:55:18 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id DE90F11E80FA; Tue,  4 Jun 2013 06:08:09 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id m16so106231qcq.33 for <multiple recipients>; Tue, 04 Jun 2013 06:08:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=gz5A/5lxnJ8IbFhjrgqPUxqwA/x7IvoDb0uNeorvHUY=; b=hpHZ5DXWMdpKdDXYW6KZyVyWzu3lKtbeeuqYi2psw27RjHa0B3uwWJs4cPaQ/+C9eZ mBrCmlniLqt8hSuR75+UYe4dEF4WqyPpsxSUCzHnSDwhEzV8S9fcNtixEd5mIy/cIGLj uS4LnUc8aklcr2PDcRjNTIwEJ4qwP+dUqCNWKWUDkVIYIfXiBJ+CqY5zKT+vHmuqeNbR SbY7LPKIojhs4mqQ1SWwCrra3XjbkeStXPKyGLYtp6aqzKRnCduQq3UZZg1g6CmZdzqC MMvDYJkzEFSjICU+X2PHhFCiPYav2IWfUbkhL1Rk2fqqkhjj+zecaxlloPLjXSK8o1/X c9vQ==
MIME-Version: 1.0
X-Received: by 10.49.73.202 with SMTP id n10mr26258330qev.55.1370351289287; Tue, 04 Jun 2013 06:08:09 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.0.139 with HTTP; Tue, 4 Jun 2013 06:08:09 -0700 (PDT)
In-Reply-To: <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com>
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net> <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com>
Date: Tue, 4 Jun 2013 09:08:09 -0400
X-Google-Sender-Auth: xQ-wonO8S3z9uoOH_uJf2ALjg3Q
Message-ID: <CALaySJJiEY4OB8+L8fEWvrL4C7tojU_tLMmrYCbdHt6tM8SDDw@mail.gmail.com>
Subject: Review of: draft-otis-dkim-harmful
From: Barry Leiba <barryleiba@computer.org>
To: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bb03ccad0f19304de53c530
Cc: "Murray S. Kucherawy" <msk@blackops.org>, Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Dave Rand <dave_rand@trendmicro.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
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: Tue, 04 Jun 2013 14:55:28 -0000

--047d7bb03ccad0f19304de53c530
Content-Type: text/plain; charset=ISO-8859-1

>
> > The draft continues to make broad, onerous claims like this, but
> provides no documentation to indicate that the DKIM signing specification
> is flawed in the function it is performing:  attaching a validated domain
> name to a message.
>
> DKIM does not, in its current form, attach a validated domain name to a
> message.  By adding one line "MUST NOT validate a message with multiple
> From:'s", DKIM will attach a validated domain name to a message.


Here's the part of this I don't understand:
A DKIM signature does two things.  It *does* attach a validated domain name
(the domain in the d= tag).  And it tells the verifier what parts of the
message are covered by the signature (h= and l= tags).  There is no claim
in DKIM that the d= domain has any relation to the RFC 5322 From.  But the
h= tag does tell you how many From header fields are covered by te
signature.

Any verifier that wants to consider a message suspicious if the message
contains more From fields than are covered by the signature can do so, and
the DKIM spec does describe this situation.

You would like the spec to REQUIRE that a message be considered suspicious
under those circumstances.  You made your case for this at least twice to
the working group and at least once more to the IETF community during Last
Call of the draft that became RFC 6376.  Your opinion wasn't agreed with:
you were "in the rough".  You're now bringing it up a fourth time (at
least), and you still appear to be in the rough.   The decision was to
allow the verifier to decide how to handle this.

Being in the rough doesn't make you wrong.  But DKIM isn't wrong either,
and at some point you have to accept that you're standing alone, and accept
the consensus.

Barry

--047d7bb03ccad0f19304de53c530
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">&gt; The draft continues to make broad, oner=
ous claims like this, but provides no documentation to indicate that the DK=
IM signing specification is flawed in the function it is performing: =A0att=
aching a validated domain name to a message.<br>


<br>
DKIM does not, in its current form, attach a validated domain name to a mes=
sage. =A0By adding one line &quot;MUST NOT validate a message with multiple=
 From:&#39;s&quot;, DKIM will attach a validated domain name to a message.<=
/blockquote>

<div><br></div><div>Here&#39;s the part of this I don&#39;t understand:</di=
v><div>A DKIM signature does two things. =A0It=A0*does* attach a validated =
domain name (the domain in the d=3D tag). =A0And it tells the verifier what=
 parts of the message are covered by the signature (h=3D and l=3D tags). =
=A0There is no claim in DKIM that the d=3D domain has any relation to the R=
FC 5322 From. =A0But the h=3D tag does tell you how many From header fields=
 are covered by te signature.</div>

<div><br></div><div>Any verifier that wants to consider a message suspiciou=
s if the message contains more From fields than are covered by the signatur=
e can do so, and the DKIM spec does describe this situation.</div><div>

<br></div><div>You would like the spec to REQUIRE that a message be conside=
red suspicious under those circumstances. =A0You made your case for this at=
 least twice to the working group and at least once more to the IETF commun=
ity during Last Call of the draft that became RFC 6376. =A0Your opinion was=
n&#39;t agreed with: you were &quot;in the rough&quot;. =A0You&#39;re now b=
ringing it up a fourth time (at least), and you still appear to be in the r=
ough.=A0 =A0The decision was to allow the verifier to decide how to handle =
this.<span></span></div>
<div><br></div><div>Being in the rough doesn&#39;t make you wrong. =A0But D=
KIM isn&#39;t wrong either, and at some point you have to accept that you&#=
39;re standing alone, and accept the consensus.</div><div><br></div><div>
Barry</div>

--047d7bb03ccad0f19304de53c530--

From mohta@necom830.hpcl.titech.ac.jp  Tue Jun  4 08:07:18 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 C3E9121F9936 for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 08:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 svLlQlo7orDV for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 08:07:04 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id E0B8421F9A33 for <ietf@ietf.org>; Tue,  4 Jun 2013 06:16:20 -0700 (PDT)
Received: (qmail 41509 invoked from network); 4 Jun 2013 13:13:16 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 4 Jun 2013 13:13:16 -0000
Message-ID: <51ADE888.6020505@necom830.hpcl.titech.ac.jp>
Date: Tue, 04 Jun 2013 22:15:52 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Not Listening to the Ops Customer
References: <20130603155642.E6AE118C0F8@mercury.lcs.mit.edu>
In-Reply-To: <20130603155642.E6AE118C0F8@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
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: Tue, 04 Jun 2013 15:07:18 -0000

Noel Chiappa wrote:

> I persist in thinking that those 32-bit names are continuing their evolution
> into local-scope names, with translation at naming region boundaries. How can
> we improve that - reduce the brittleness of the middleboxes you refer to, by
> making their data more visible (and thus replicable, etc)?

Just say, A+P, except that the original proposal of A+P has
wrongly assumed that a NAT box is required inside a site.

Still, surely, port numbers are local-scope names.

However, if the 16bit port numbers are combined with 32bit IP
addresses, they are the globally scoped names with 48 bit
length, which is a lot more than enough to make the Internet
fully end to end transparent even at the current global scale.

> but I think in retrospect that's a non-starter - changing TCP
> (which is what that would require) is not really an option (see point 1).

Changing TCP is required not for address space extension but
for better handling of multiple addresses for better routing
table aggregation.


						Masataka Ohta

From dhc@dcrocker.net  Tue Jun  4 08:47:52 2013
Return-Path: <dhc@dcrocker.net>
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 C4E8121F9E07; Tue,  4 Jun 2013 08:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
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 bSffiT-28o1s; Tue,  4 Jun 2013 08:47:36 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C47E621F9E24; Tue,  4 Jun 2013 06:49:00 -0700 (PDT)
Received: from [172.16.22.72] (62-50-200-178.client.stsn.net [62.50.200.178]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r54DmkxO004072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 4 Jun 2013 06:48:51 -0700
Message-ID: <51ADF03A.8060501@dcrocker.net>
Date: Tue, 04 Jun 2013 15:48:42 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Douglas Otis <doug.mtview@gmail.com>
Subject: Re: Review of: draft-otis-dkim-harmful
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net> <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com>
In-Reply-To: <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 04 Jun 2013 06:48:53 -0700 (PDT)
Cc: "Murray S. Kucherawy" <msk@blackops.org>, Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Dave Rand <dave_rand@trendmicro.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Tue, 04 Jun 2013 15:47:52 -0000

On 6/4/2013 1:08 PM, Douglas Otis wrote:
> Dear Dave,
>
> On Jun 4, 2013, at 11:44 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>> I happen to be sitting in a M3AAWG meeting as I write this note
>> and it happens that I just came out of a session in which someone
>> tried to assert the use of DKIM (or SPF) as a 'requirement' and the
>> group was very clear that no such 'requirement' exists or is a
>> goal.
...
> "Hope to use", rather than advocates.  We stand by the assertion,
> but we can further modify this statement.

You can invent any sort of claim you want.  What you can't do is
substantiate it, because it has no objective basis.

I made a point of citing minutes-old group discussion that I had
first-person knowledge of and that was explicitly contrary to your claim.


>> However DKIM does not specify the role of the signing agent and
>> doesn't care.  Consequently the concern apparently being raised
>> here seems to be fundamentally confused about what DKIM is doing.
>
> The combination of an assertion a message fragment is
> "authenticated" and conflation of that assertion is happening today.
> More on this in a bit.  The authors are in no way confused.

People mis-use specifications all the time.

The issue here is what the spec says and does, not how people some stray
folk somewhere choose to mis-use it.

DKIM makes no 'assertion a message fragment is "authenticated"'.

Period.


>>> Simply publishing this draft appears to have already increase
>>> the level of multiple FROM header field abuse seen where it is
>>> now at 21% of signed DKIM messages.
>>
>> Sounds pretty scary.  No doubt the assertion is publicly
>> verifiable, including the basis for asserting that it is causing
>> problem?
>
> Sure.  Simply observe the increasing signed DKIM messages that have
> multiple From:'s.

The challenge I placed was on documenting the claim.  The point is to
permit community assessment of the claim.



> DKIM does not, in its current form, attach a validated domain name
> to a message.  By adding one line "MUST NOT validate a message with
> multiple From:'s", DKIM will attach a validated domain name to a
> message.

One of the hallmarks of serious participation in IETF processes is
respect for the outcome of a legitimate discussion that happen to go
against one's preference.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From doug.mtview@gmail.com  Tue Jun  4 10:06:54 2013
Return-Path: <doug.mtview@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 A2F6A21F9B82; Tue,  4 Jun 2013 10:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_44=0.6]
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 iS3ladGAfCb1; Tue,  4 Jun 2013 10:06:25 -0700 (PDT)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id CB1F121F9DE5; Tue,  4 Jun 2013 07:52:19 -0700 (PDT)
Received: by mail-ie0-f179.google.com with SMTP id c13so618461ieb.24 for <multiple recipients>; Tue, 04 Jun 2013 07:52:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=iDsGMebYR7hajx07ocAKXXIVDkOwDqK/jNNWheU+OtY=; b=BDxeDHc2oou+zEPm9o8IBTLzQ4htPT88tZNRVe5YsFvDjXjDgK463X69TM/aU7JOVD xGyGoeE3SGCsrKtq+e93aEfO0AeRTWXc7Y6OGy3N/aPDJFraAsYJurnJI5KwqM1oQd5H 7xjglyl0Yu3u1DhfKXO22ncmlk3pVoBbrN/cXUnqT/Fou9xFO7V0k2PXtpSrT7VDHbU1 C7MfDLL94P+DP13aLYSd4ZgS8YxlRgrA7hvyFJ54Eh8PZE5UVrJtec4/CnbreAxx3KRM vtbleoOF5Bs+qoFq+o0WGXBnZDqFTlCEIB1y0HUnKX4MI86SncRxtc0L0HyBpI5S8Xs7 2ZbA==
X-Received: by 10.50.67.10 with SMTP id j10mr1004495igt.70.1370357539382; Tue, 04 Jun 2013 07:52:19 -0700 (PDT)
Received: from [10.12.1.50] ([82.112.204.69]) by mx.google.com with ESMTPSA id it3sm2212219igb.0.2013.06.04.07.52.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Jun 2013 07:52:18 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_D86C7A61-A49B-49A2-A470-46075A67135B"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Review of: draft-otis-dkim-harmful
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <CALaySJJiEY4OB8+L8fEWvrL4C7tojU_tLMmrYCbdHt6tM8SDDw@mail.gmail.com>
Date: Tue, 4 Jun 2013 16:51:54 +0200
Message-Id: <9408F2D5-133F-45B4-8E56-62C595D47E11@gmail.com>
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net> <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com> <CALaySJJiEY4OB8+L8fEWvrL4C7tojU_tLMmrYCbdHt6tM8SDDw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1503)
Cc: "Murray S. Kucherawy" <msk@blackops.org>, Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Dave Rand <dave_rand@trendmicro.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
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: Tue, 04 Jun 2013 17:06:58 -0000

--Apple-Mail=_D86C7A61-A49B-49A2-A470-46075A67135B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Jun 4, 2013, at 3:08 PM, Barry Leiba <barryleiba@computer.org> wrote:

> > The draft continues to make broad, onerous claims like this, but =
provides no documentation to indicate that the DKIM signing =
specification is flawed in the function it is performing:  attaching a =
validated domain name to a message.
>=20
> DKIM does not, in its current form, attach a validated domain name to =
a message.  By adding one line "MUST NOT validate a message with =
multiple From:'s", DKIM will attach a validated domain name to a =
message.

Dear Barry,

Thank you for your response.

> Here's the part of this I don't understand:
> A DKIM signature does two things.  It *does* attach a validated domain =
name (the domain in the d=3D tag).  And it tells the verifier what parts =
of the message are covered by the signature (h=3D and l=3D tags).  There =
is no claim in DKIM that the d=3D domain has any relation to the RFC =
5322 From.  But the h=3D tag does tell you how many =46rom header fields =
are covered by te signature.

Of course it is incorrect for a DKIM signature to be valid when a =
message has multiple =46rom header fields.  DKIM requires AT LEAST the =
=46rom header field to be the minimal portion of the message signed.  =
Every other part of the message is optional.

DKIM was intended not to require ANY change of other mail components.  =
None. =20

When the DKIM signature is trusted and changes how the message is =
handled, it would be wrong to suggest special consideration is then =
given other message fragments.  In addition, recipients will not see the =
signature header field nor should they be expected to understand what it =
contains.  They will see and understand the =46rom header field however.=20=


Of course dkim=3Dpass is placed in an Authentication-Results header =
where many suggest this indicates the message has been "authenticated"!

> Any verifier that wants to consider a message suspicious if the =
message contains more =46rom fields than are covered by the signature =
can do so, and the DKIM spec does describe this situation.

DKIM does NOT score messages.  Either the signature is valid or not.  =
The spec wrongly justifies allowing invalid repeated headers to result =
in a DKIM signature verified as valid.=20

> You would like the spec to REQUIRE that a message be considered =
suspicious under those circumstances.

No. Just indicate the signature is NOT valid.  This is the only sure way =
to ensure trust is not misapplied and cause harm.

>  You made your case for this at least twice to the working group and =
at least once more to the IETF community during Last Call of the draft =
that became RFC 6376.  Your opinion wasn't agreed with: you were "in the =
rough".  You're now bringing it up a fourth time (at least), and you =
still appear to be in the rough.   The decision was to allow the =
verifier to decide how to handle this.

You and Dave Crocker made assurances this issue would not be abused.  It =
is being abused and NO other protocol layer ensures message structures =
are valid. None.  It was negligent for DKIM to ignore occurrences of =
highly deceptive invalidly repeated header fields as it walks up and =
down the header field stack.  It is also wrong to suggest some other =
protocol layer handles this checking.  Such suggestion represents a =
waste of resources as ONLY DKIM should determine signature validity =
which MUST consider invalidly repeated header fields.  It also appears =
most even expect DKIM signature validation checks message structure, but =
this ONLY happens by double listing singleton header fields in the =
signed header list.  MOST domains don't bother with this ugly hack, =
especially larger domains where checking message structure is critical.=20=


> Being in the rough doesn't make you wrong.  But DKIM isn't wrong =
either, and at some point you have to accept that you're standing alone, =
and accept the consensus.

Putting people at risk in some race to obtain Standard status can not be =
justified.  Getting this right is far far more important.  Allowing this =
to become a standard will make specification modification even more =
difficult.

Regards,
Douglas Otis

 =20=

--Apple-Mail=_D86C7A61-A49B-49A2-A470-46075A67135B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jun 4, 2013, at 3:08 PM, Barry Leiba &lt;<a =
href=3D"mailto:barryleiba@computer.org">barryleiba@computer.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px =
0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, =
204); border-left-style: solid; padding-left: 1ex; position: static; =
z-index: auto; ">&gt; The draft continues to make broad, onerous claims =
like this, but provides no documentation to indicate that the DKIM =
signing specification is flawed in the function it is performing: =
&nbsp;attaching a validated domain name to a message.<br>


<br>
DKIM does not, in its current form, attach a validated domain name to a =
message. &nbsp;By adding one line "MUST NOT validate a message with =
multiple From:'s", DKIM will attach a validated domain name to a =
message.</blockquote></blockquote><div><br></div><div>Dear =
Barry,</div><div><br></div><div>Thank you for your =
response.</div><br><blockquote type=3D"cite"><div>Here's the part of =
this I don't understand:</div><div>A DKIM signature does two things. =
&nbsp;It&nbsp;*does* attach a validated domain name (the domain in the =
d=3D tag). &nbsp;And it tells the verifier what parts of the message are =
covered by the signature (h=3D and l=3D tags). &nbsp;There is no claim =
in DKIM that the d=3D domain has any relation to the RFC 5322 From. =
&nbsp;But the h=3D tag does tell you how many =46rom header fields are =
covered by te signature.</div></blockquote><div><br></div><div>Of course =
it is incorrect for a DKIM signature to be valid when a message has =
multiple =46rom header fields. &nbsp;DKIM requires AT LEAST the =46rom =
header field to be the minimal portion of the message signed. =
&nbsp;Every other part of the message is =
optional.</div><div><br></div><div>DKIM was intended not to require ANY =
change of other mail components. &nbsp;None. =
&nbsp;</div><div><br></div><div>When the DKIM signature is trusted and =
changes how the message is handled, it would be wrong to suggest special =
consideration is then given other message fragments. &nbsp;In addition, =
recipients will not see the signature header field nor should they be =
expected to understand what it contains. &nbsp;They will see and =
understand the =46rom header field =
however.&nbsp;</div><div><br></div><div>Of course dkim=3Dpass is placed =
in an Authentication-Results header where many suggest this indicates =
the message has been "authenticated"!</div><div><br></div><blockquote =
type=3D"cite">

<div>Any verifier that wants to consider a message suspicious if the =
message contains more =46rom fields than are covered by the signature =
can do so, and the DKIM spec does describe this =
situation.</div></blockquote><div><br></div><div>DKIM does NOT score =
messages. &nbsp;Either the signature is valid or not. &nbsp;The spec =
wrongly justifies allowing invalid repeated headers to result in a DKIM =
signature verified as valid.&nbsp;</div><br><blockquote =
type=3D"cite"><div>You would like the spec to REQUIRE that a message be =
considered suspicious under those circumstances. =
</div></blockquote><div><br></div><div>No. Just indicate the signature =
is NOT valid. &nbsp;This is the only sure way to ensure trust is not =
misapplied and cause harm.</div><br><blockquote =
type=3D"cite"><div>&nbsp;You made your case for this at least twice to =
the working group and at least once more to the IETF community during =
Last Call of the draft that became RFC 6376. &nbsp;Your opinion wasn't =
agreed with: you were "in the rough". &nbsp;You're now bringing it up a =
fourth time (at least), and you still appear to be in the rough.&nbsp; =
&nbsp;The decision was to allow the verifier to decide how to handle =
this.</div></blockquote><div><br></div><div>You and Dave Crocker made =
assurances this issue would not be abused. &nbsp;It is being abused and =
NO other protocol layer ensures message structures are valid. None. =
&nbsp;It was negligent for DKIM to ignore occurrences of highly =
deceptive invalidly repeated header fields as it walks up and down the =
header field stack. &nbsp;It is also wrong to suggest some other =
protocol layer handles this checking. &nbsp;Such suggestion represents a =
waste of resources as ONLY DKIM should determine signature validity =
which MUST consider invalidly repeated header fields. &nbsp;It also =
appears most even expect DKIM signature validation checks message =
structure, but this ONLY happens by double listing singleton header =
fields in the signed header list. &nbsp;MOST domains don't bother with =
this ugly hack, especially larger domains where checking message =
structure is critical.&nbsp;</div><br><blockquote =
type=3D"cite"><div><span></span></div>
<div>Being in the rough doesn't make you wrong. &nbsp;But DKIM isn't =
wrong either, and at some point you have to accept that you're standing =
alone, and accept the =
consensus.</div></blockquote><div><br></div><div>Putting people at risk =
in some race to obtain Standard status can not be justified. =
&nbsp;Getting this right is far far more important. &nbsp;Allowing this =
to become a standard will make specification modification even more =
difficult.</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div><div>&nbsp;&nbsp;</div></div></body></html>=

--Apple-Mail=_D86C7A61-A49B-49A2-A470-46075A67135B--

From barryleiba@gmail.com  Tue Jun  4 10:17:01 2013
Return-Path: <barryleiba@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 D3DF421F9C7B; Tue,  4 Jun 2013 10:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.941
X-Spam-Level: 
X-Spam-Status: No, score=-101.941 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 5FKdIGB1Rnms; Tue,  4 Jun 2013 10:17:01 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 9F99321F9CCF; Tue,  4 Jun 2013 08:20:02 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id m16so214856qcq.5 for <multiple recipients>; Tue, 04 Jun 2013 08:20:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=XBm3xEuvSnSgbRs+SoULR2thWiUlXLE7ZEbTLcNh764=; b=ttTZxPrkWMUv29juUUBPYmmFShNxiQUrmKpvsGQrzst4xnIJ17ycFEfTaq8MuU7mtb uUIBViKZOaAraWKc9B6nECs/uAQaOG/Q1eDFI8iIp2UY8FuRhp5aN0bwYGIqDuE+8toz h2f9YZRGR7UAlUGbyNqvKYwPV7DJbFkvfxcCDeLyfAzxqVqavKoMPQW4iOXhMZ0W7ezb O6Utv7n6Kz4NraQ4xcElkH5QzCZSEKsY4xqPV8Bt4A2Lk0DgcJsaJKc5j4aF4HxVuoYF 1inaZgzoOUTtJ6Xg7S+PuB3dmqU+S6HElk8xUCt8uGOfgluPQBSOPLa09aiLYAssvyFQ JIXQ==
MIME-Version: 1.0
X-Received: by 10.224.47.6 with SMTP id l6mr24075123qaf.9.1370359202013; Tue, 04 Jun 2013 08:20:02 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.0.139 with HTTP; Tue, 4 Jun 2013 08:20:01 -0700 (PDT)
In-Reply-To: <9408F2D5-133F-45B4-8E56-62C595D47E11@gmail.com>
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net> <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com> <CALaySJJiEY4OB8+L8fEWvrL4C7tojU_tLMmrYCbdHt6tM8SDDw@mail.gmail.com> <9408F2D5-133F-45B4-8E56-62C595D47E11@gmail.com>
Date: Tue, 4 Jun 2013 11:20:01 -0400
X-Google-Sender-Auth: Mn6ee1NqbRdMmsm1q5K3E5JDFpY
Message-ID: <CALaySJLBaf6Ox2TAW3k+9Rdzq9mLhSiHMi8pVaX+ra=Xgj3dvg@mail.gmail.com>
Subject: Re: Review of: draft-otis-dkim-harmful
From: Barry Leiba <barryleiba@computer.org>
To: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2c7e4736da004de559dcb
Cc: "Murray S. Kucherawy" <msk@blackops.org>, Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, Barry Leiba <barryleiba@computer.org>, Dave Rand <dave_rand@trendmicro.com>, iesg <iesg@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: Tue, 04 Jun 2013 17:17:02 -0000

--001a11c2c7e4736da004de559dcb
Content-Type: text/plain; charset=ISO-8859-1

>
> Of course it is incorrect for a DKIM signature to be valid when a message
> has multiple From header fields.  DKIM requires AT LEAST the From header
> field to be the minimal portion of the message signed.  Every other part of
> the message is optional.
>

In retrospect, I think that requirement was a mistake, because it
encourages misunderstandings such as yours.  Whether or not a header field
is signed has nothing whatever to do with the validity of the signature or
the fact that the signature attaches the d= domain to the message.

Having an (extra) unsigned From should no more invalidate the signature
than having an unsigned Subject should.

But the information that there's a valid signature and an unsigned
<whatever> header field can certainly be two pieces of information that are
passed to an evaluator, which decides what to do with the message.


> DKIM does NOT score messages.  Either the signature is valid or not.  The
> spec wrongly justifies allowing invalid repeated headers to result in a
> DKIM signature verified as valid.
>

Indeed; the signature is valid.  That and the list of what bits are covered
by the signature are the two things that DKIM provides.  An evaluator built
on top of DKIM can use that information in any way it likes, including
throwing away the DKIM validation if certain header fields weren't covered.
 That was the working group's decision, which you don't seem to accept.  As
I said, you're in the rough on that.

You and Dave Crocker made assurances this issue would not be abused.
>

That's not an accurate characterization.  No one made any "assurances";
certainly I didn't, as chair.
The working group understood the potential for abuse.  The working group
decided that the risk of abuse and damage from that abuse was less than the
problems that would be cause by the proposed fixes.  The text that's in the
document was put there to explain the problem, and to allow implementors to
address it if they want to (or think they need to).


> Putting people at risk in some race to obtain Standard status can not be
> justified.  Getting this right is far far more important.
>

Getting it right is, indeed, important, and the working group does think it
got it right.  The rest of that is hyperbole, as best I can tell.I see no
evidence that has been presented that shows me how this puts people at
risk.  (And remember that DKIM provides a relatively low level of security,
and is meant to be used as one piece of information that forms a *part* of
an overall system.)

Barry

--001a11c2c7e4736da004de559dcb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><di=
v>Of course it is incorrect for a DKIM signature to be valid when a message=
 has multiple From header fields. =A0DKIM requires AT LEAST the From header=
 field to be the minimal portion of the message signed. =A0Every other part=
 of the message is optional.</div>
</div></div></blockquote><div><br></div><div>In retrospect, I think that re=
quirement was a mistake, because it encourages misunderstandings such as yo=
urs. =A0Whether or not a header field is signed has nothing whatever to do =
with the validity of the signature or the fact that the signature attaches =
the d=3D domain to the message.</div>
<div><br></div><div>Having an (extra) unsigned From should no more invalida=
te the signature than having an unsigned Subject should.</div><div><br></di=
v><div>But the information that there&#39;s a valid signature and an unsign=
ed &lt;whatever&gt; header field can certainly be two pieces of information=
 that are passed to an evaluator, which decides what to do with the message=
.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-=
word"><div><div>DKIM does NOT score messages. =A0Either the signature is va=
lid or not. =A0The spec wrongly justifies allowing invalid repeated headers=
 to result in a DKIM signature verified as valid.</div>
</div></div></blockquote><div><br></div><div>Indeed; the signature is valid=
. =A0That and the list of what bits are covered by the signature are the tw=
o things that DKIM provides. =A0An evaluator built on top of DKIM can use t=
hat information in any way it likes, including throwing away the DKIM valid=
ation if certain header fields weren&#39;t covered. =A0That was the working=
 group&#39;s decision, which you don&#39;t seem to accept. =A0As I said, yo=
u&#39;re in the=A0rough on that.</div>
<div><br></div><div></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word=
-wrap:break-word"><div><div>You and Dave Crocker made assurances this issue=
 would not be abused.</div>
<div></div></div></div></blockquote><div><br></div><div>That&#39;s not an a=
ccurate characterization. =A0No one made any &quot;assurances&quot;; certai=
nly I didn&#39;t, as chair.</div><div>The working group understood the pote=
ntial for abuse. =A0The working group decided that the risk of abuse and da=
mage from that abuse was less than the problems that would be cause by the =
proposed fixes. =A0The text that&#39;s in the document was put there to exp=
lain the problem, and to allow implementors to address it if they want to (=
or think they need to).</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-=
word"><div>Putting people at risk in some race to obtain Standard status ca=
n not be justified. =A0Getting this right is far far more important.</div>
</div></blockquote><div><br></div><div>Getting it right is, indeed, importa=
nt, and the working group does think it got it right. =A0The rest of that i=
s hyperbole, as best I can tell.I see no evidence that has been presented t=
hat shows me how this puts people at risk. =A0(And remember that DKIM provi=
des=A0a relatively low level of security, and is meant to be used as one pi=
ece of information that forms a *part* of an overall system.)<span></span><=
/div>
<div><br></div><div>Barry=A0=A0</div>

--001a11c2c7e4736da004de559dcb--

From dhc@dcrocker.net  Tue Jun  4 10:25:59 2013
Return-Path: <dhc@dcrocker.net>
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 95B4E21F9814; Tue,  4 Jun 2013 10:25:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_MED=-4]
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 UQQ8ODgaN9i5; Tue,  4 Jun 2013 10:25:51 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4478021F9AD1; Tue,  4 Jun 2013 08:46:05 -0700 (PDT)
Received: from [192.168.1.7] (chello080108132236.14.wu-wien.teleweb.at [80.108.132.236] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r54FjjnY007224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 4 Jun 2013 08:45:51 -0700
Message-ID: <51AE0BA4.8030605@dcrocker.net>
Date: Tue, 04 Jun 2013 17:45:40 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Douglas Otis <doug.mtview@gmail.com>
Subject: Re: Review of: draft-otis-dkim-harmful
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net> <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com> <CALaySJJiEY4OB8+L8fEWvrL4C7tojU_tLMmrYCbdHt6tM8SDDw@mail.gmail.com> <9408F2D5-133F-45B4-8E56-62C595D47E11@gmail.com>
In-Reply-To: <9408F2D5-133F-45B4-8E56-62C595D47E11@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 04 Jun 2013 08:45:53 -0700 (PDT)
Cc: "Murray S. Kucherawy" <msk@blackops.org>, Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Barry Leiba <barryleiba@computer.org>, Dave Rand <dave_rand@trendmicro.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Tue, 04 Jun 2013 17:25:59 -0000

On 6/4/2013 4:51 PM, Douglas Otis wrote:
> Of course it is incorrect for a DKIM signature to be valid when a
> message has multiple From header fields.

You lost that debate in the working group.  Multiple times.

Saying "of course" at the beginning of your claim does not make you win 
the argument.


> DKIM was intended not to require ANY change of other mail components.
>   None.

It doesn't.


> When the DKIM signature is trusted and changes how the message is
> handled, it would be wrong to suggest special consideration is then
> given other message fragments.

So it's a good thing the DKIM spec doesn't do that.


>  In addition, recipients will not see the
> signature header field nor should they be expected to understand what it
> contains.  They will see and understand the From header field however.

Quite possibly.

And it's why the DKIM signing specification says:

    3.8.  Input Requirements

    A message that is not compliant with [RFC5322], [RFC2045], and
    [RFC2047] can be subject to attempts by intermediaries to correct or
    interpret such content.  See Section 8 of [RFC4409] for examples of
    changes that are commonly made.  Such "corrections" may invalidate
    DKIM signatures or have other undesirable effects, including some
    that involve changes to the way a message is presented to an end
    user.

    Accordingly, DKIM's design is predicated on valid input.


> Of course dkim=pass is placed in an Authentication-Results header where
> many suggest this indicates the message has been "authenticated"!

So, you are criticizing the DKIM Signature specification for wording in 
a separate specification that was developed independently?


>>  You made your case for this at least twice to the working group and
>> at least once more to the IETF community during Last Call of the draft
>> that became RFC 6376.  Your opinion wasn't agreed with: you were "in
>> the rough".  You're now bringing it up a fourth time (at least), and
>> you still appear to be in the rough.   The decision was to allow the
>> verifier to decide how to handle this.
>
> You and Dave Crocker made assurances this issue would not be abused.

Please document that claim.


>  It
> is being abused

Please document that claim, and more importantly please substantiate the 
implication that it is causing a problem in the operation of Internet mail.


> and NO other protocol layer ensures message structures
> are valid.

Perhaps you have heard of RFC5322 and MIME?  Those are the 
specifications that define valid message formats.  Software that 
implements those specs ensures message structure validity.

Your issue is with software that enforces those standards -- or doesn't 
--  rather than a separate specification that calls on them.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From superuser@gmail.com  Tue Jun  4 10:34:58 2013
Return-Path: <superuser@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 6120F21F9B2C; Tue,  4 Jun 2013 10:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 6F8jAYrhpr0D; Tue,  4 Jun 2013 10:34:57 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2FDAB21F9CA0; Tue,  4 Jun 2013 09:05:50 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id q58so384985wes.19 for <multiple recipients>; Tue, 04 Jun 2013 09:05:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=U+fBDxcAFapQtZyLJFqWXyWLLIvR72X5w5OAb/HKKUA=; b=Ns6yVO1B3TBjbAu6LM2Km47GnXghkI1ScakF6fPgRpW59FCBQu+XHjE7XrhhJspNuR UPhy0pvd6v4+odF9MmWDXyblwZ5C07dp2spQ2zyC5MkqKysDV67jH4ob7KyUka0/SYdq YvGNiUOpzOeJEkrjk8xVtO54oGHMl0gU8A3O+SMQKd1v4p6Jw3X92qLZ0tBWRI7lZ46Y 2LBmOWhVg0PsuEOuU87tv8LwqGOAs8bEhN2DyRztKKsEDexHKnGW1Np0bQC8AVt0lPit zWAxtA5ybchDMfBU4Cl1EAboId8Td0/gPOA39OmLhCU1F8zBezNbczbBvN9FcalXRer6 o/Ng==
MIME-Version: 1.0
X-Received: by 10.194.158.194 with SMTP id ww2mr24668197wjb.3.1370361946078; Tue, 04 Jun 2013 09:05:46 -0700 (PDT)
Sender: superuser@gmail.com
Received: by 10.180.74.203 with HTTP; Tue, 4 Jun 2013 09:05:45 -0700 (PDT)
In-Reply-To: <51ADF03A.8060501@dcrocker.net>
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net> <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com> <51ADF03A.8060501@dcrocker.net>
Date: Tue, 4 Jun 2013 09:05:45 -0700
X-Google-Sender-Auth: xdXRItPApkcpQdmjMYGmeTI201U
Message-ID: <CAL0qLwb7ybEwB+yc0X=LxWAXTG-cmbDpf006DhcjxYXcVE4HEg@mail.gmail.com>
Subject: Re: Review of: draft-otis-dkim-harmful
From: "Murray S. Kucherawy" <msk@blackops.org>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=089e013c64de0287e304de5641d3
Cc: Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Dave Rand <dave_rand@trendmicro.com>
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: Tue, 04 Jun 2013 17:34:58 -0000

--089e013c64de0287e304de5641d3
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 4, 2013 at 6:48 AM, Dave Crocker <dhc@dcrocker.net> wrote:

>
>  Simply publishing this draft appears to have already increase
>>>> the level of multiple FROM header field abuse seen where it is
>>>> now at 21% of signed DKIM messages.
>>>>
>>>
>>> Sounds pretty scary.  No doubt the assertion is publicly
>>> verifiable, including the basis for asserting that it is causing
>>> problem?
>>>
>>
>> Sure.  Simply observe the increasing signed DKIM messages that have
>> multiple From:'s.
>>
>
> The challenge I placed was on documenting the claim.  The point is to
> permit community assessment of the claim.


As another data point, when Doug's claim of increased appearance of
multi-From messages surfaced, I instrumented my own MTAs to detect the same
sort of thing to see if he's right.  My data don't concur with the claim;
it's still nearly zero.  I will release the source code for this in an
update to OpenDKIM soon, so others can collect their own data.

-MSK

--089e013c64de0287e304de5641d3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jun 4, 2013 at 6:48 AM, Dave Crocker <span dir=3D"=
ltr">&lt;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker=
.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmai=
l_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
<div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Simply publishing this draft appears to have already increase<br>
the level of multiple FROM header field abuse seen where it is<br>
now at 21% of signed DKIM messages.<br>
</blockquote>
<br>
Sounds pretty scary. =A0No doubt the assertion is publicly<br>
verifiable, including the basis for asserting that it is causing<br>
problem?<br>
</blockquote>
<br>
Sure. =A0Simply observe the increasing signed DKIM messages that have<br>
multiple From:&#39;s.<br>
</blockquote>
<br></div>
The challenge I placed was on documenting the claim. =A0The point is to<br>
permit community assessment of the claim.</blockquote><div><br></div><div>A=
s another data point, when Doug&#39;s claim of increased appearance of mult=
i-From messages surfaced, I instrumented my own MTAs to detect the same sor=
t of thing to see if he&#39;s right.=A0 My data don&#39;t concur with the c=
laim; it&#39;s still nearly zero.=A0 I will release the source code for thi=
s in an update to OpenDKIM soon, so others can collect their own data.<br>
<br></div><div>-MSK<br></div></div></div></div>

--089e013c64de0287e304de5641d3--

From superuser@gmail.com  Tue Jun  4 10:38:29 2013
Return-Path: <superuser@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 A381321F94BA; Tue,  4 Jun 2013 10:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 xhlrigvy47LP; Tue,  4 Jun 2013 10:38:29 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id C304421F99BE; Tue,  4 Jun 2013 09:13:11 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hj6so382425wib.17 for <multiple recipients>; Tue, 04 Jun 2013 09:13:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=c74+yofDspeC2VKAbDH/XtSPhQJ7aEysXPNC86LSOFQ=; b=c9KvrzCuM7FVldOoQr7BgfOn4E/NaTIEu3Utk8PX0Q3HCuXJNnwDRyc0G3GYANEzfq ULbFPD83KVw5j3ntq0JpaYQy9rcEGI3gtgblZCJUibR9J4xNBuhBvU+AU2wKhpUCB1A3 r0fXTDanfo1JQ5PzzM8HPBLARRjDOjRicKpm0aK6x52SViMruf8bJw28BQRWGNMe7Lm3 3Vg54YvSkhcCAnbrvlSy6wm4RFLqxmn7DAHiH81K1awsh37sGssVRboIUWvdQAY+DvM9 FaD1EhNgA7KtR2jkaKt+cmJrypY+KYEKtZtASoE7Xh7P9FfF4Cfk2sN9grKcqTvetsWh bIYw==
MIME-Version: 1.0
X-Received: by 10.180.208.81 with SMTP id mc17mr2264591wic.35.1370362390816; Tue, 04 Jun 2013 09:13:10 -0700 (PDT)
Sender: superuser@gmail.com
Received: by 10.180.74.203 with HTTP; Tue, 4 Jun 2013 09:13:10 -0700 (PDT)
In-Reply-To: <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com>
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net> <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com>
Date: Tue, 4 Jun 2013 09:13:10 -0700
X-Google-Sender-Auth: 5u-XBD0Ou_EiBXt-EwC4INltCkE
Message-ID: <CAL0qLwZ6t7TNvowfQwC53a8nZMtb-06B4zwB3=rWJW+EEpAKzg@mail.gmail.com>
Subject: Re: Review of: draft-otis-dkim-harmful
From: "Murray S. Kucherawy" <msk@blackops.org>
To: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c33bb084af6004de565ba3
Cc: Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Dave Rand <dave_rand@trendmicro.com>, Dave Crocker <dcrocker@bbiw.net>
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: Tue, 04 Jun 2013 17:38:29 -0000

--001a11c33bb084af6004de565ba3
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 4, 2013 at 4:08 AM, Douglas Otis <doug.mtview@gmail.com> wrote:

> In its current form, DKIM simply attaches a domain name in an unseen
> message fragment, not a message.  The ease in which the only assured
> visible fragment of the message signed by the domain being forged makes it
> impossible for appropriate handling to be applied or likely harm prevented.
>
>
There are existence proofs that contradict this claim.  They have been
brought to your attention in the past.

It appears you're continuing to assign semantics to DKIM signatures that
simply aren't there.  I don't know what else can be done to clarify this.

Procedurally speaking, what path do you anticipate your draft following?

-MSK

--001a11c33bb084af6004de565ba3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jun 4, 2013 at 4:08 AM, Douglas Otis <span dir=3D"=
ltr">&lt;<a href=3D"mailto:doug.mtview@gmail.com" target=3D"_blank">doug.mt=
view@gmail.com</a>&gt;</span> wrote: <br><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">In its current form, DKIM =
simply attaches a domain name in an unseen message fragment, not a message.=
 =A0The ease in which the only assured visible fragment of the message sign=
ed by the domain being forged makes it impossible for appropriate handling =
to be applied or likely harm prevented.<br>
</div>
<br></blockquote></div><br></div><div class=3D"gmail_extra">There are exist=
ence proofs that contradict this claim.=A0 They have been brought to your a=
ttention in the past.<br><br></div><div class=3D"gmail_extra">It appears yo=
u&#39;re continuing to assign semantics to DKIM signatures that simply aren=
&#39;t there.=A0 I don&#39;t know what else can be done to clarify this.<br=
>
<br>Procedurally speaking, what path do you anticipate your draft following=
?<br><br></div><div class=3D"gmail_extra">-MSK<br></div></div>

--001a11c33bb084af6004de565ba3--

From touch@isi.edu  Tue Jun  4 10:53:56 2013
Return-Path: <touch@isi.edu>
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 CF4B521F9D07 for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 10:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.162
X-Spam-Level: 
X-Spam-Status: No, score=-105.162 tagged_above=-999 required=5 tests=[AWL=1.438, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 FaYqATcvkpAz for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 10:53:49 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id D7FD621E80FF for <ietf@ietf.org>; Tue,  4 Jun 2013 10:05:28 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r54H3uu9025820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 4 Jun 2013 10:03:56 -0700 (PDT)
Message-ID: <51AE1DF6.50106@isi.edu>
Date: Tue, 04 Jun 2013 10:03:50 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk> <FD94EB85-010E-4295-8500-75108F93C4C3@vpnc.org>
In-Reply-To: <FD94EB85-010E-4295-8500-75108F93C4C3@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: adrian@olddog.co.uk, "ietf@ietf.org 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: Tue, 04 Jun 2013 17:53:56 -0000

On 5/30/2013 7:59 AM, Paul Hoffman wrote:
> On May 29, 2013, at 11:53 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>
>> I can also see potential for adding some info to the Tao, but the danger there is that document becomes too big and too detailed to be of use.
>
> Many would claim it already is. We discussed that here a few years ago, and informally decided "too long" was better than "too short and with a lot of pointers to other documents that needed to be read".
>
>> Is this a tutorial?
>
> Mainly. To quote...
>
>       NOTE:    This draft is intentionally non-normative.  It is meant as a
>       guide to common practice, rather than as a formal definition of
>       what is permissible.
>
> Proposal: maybe don't do this as an Internet Draft, but do it as a tutorial.

Or in the TAO, which is fairly clearly non-normative even when issued as 
an RFC.

:-)

Joe

From Simo.Veikkolainen@nokia.com  Tue Jun  4 00:43:11 2013
Return-Path: <Simo.Veikkolainen@nokia.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 DD60621F9B37; Tue,  4 Jun 2013 00:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 bXTjU8Hhed4g; Tue,  4 Jun 2013 00:42:56 -0700 (PDT)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 2351D11E80E7; Mon,  3 Jun 2013 23:47:19 -0700 (PDT)
Received: from vaebh101.NOE.Nokia.com (in-mx.nokia.com [10.160.244.22]) by mgw-sa02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r546lE4A008845; Tue, 4 Jun 2013 09:47:14 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.26]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 4 Jun 2013 09:47:27 +0300
Received: from 008-AM1MPN1-025.mgdnok.nokia.com ([169.254.5.171]) by 008-AM1MMR1-010.mgdnok.nokia.com ([65.54.30.26]) with mapi id 14.02.0328.011; Tue, 4 Jun 2013 06:48:24 +0000
From: <Simo.Veikkolainen@nokia.com>
To: <ron.even.tlv@gmail.com>, <draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org>
Subject: RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
Thread-Topic: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
Thread-Index: Ac5cmCWECo5bIU14RKqGyok1y70zYABS86TwALNw8IAAD1Rg4A==
Date: Tue, 4 Jun 2013 06:48:24 +0000
Message-ID: <D09DAE6B636851459F7575D146EFB54B2406EA58@008-AM1MPN1-025.mgdnok.nokia.com>
References: <000301ce5c98$278d0220$76a70660$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com> <027001ce60b1$ba2ecbf0$2e8c63d0$@gmail.com>
In-Reply-To: <027001ce60b1$ba2ecbf0$2e8c63d0$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-version: 3.5.9.3
x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Nokia Internal Use Only;Project=None;
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IieUVVR+P20VDCzpg3HHXu3iIt34TClchC1lFMW65RFpQIjYqffJgrmfD1cpNgGbjtK8fB7f+0feePD/3lFuEnnkEez1dWv4zZaxFseCBqz9vmPplcQguUY4aymB6E2FlXKMnVmqGMRGGOklYWAKTXB+mqjHKxFjyTSbRvCSq9ZSlLCqmfs3bpHtpJ6E8hoghaVDC0dozB9AWOU7rGBrPnu/tUoAuQ7hJg97r0tWFsJFeIUou2s76WJFRrdIzzPW2JgXZ1J8xbVDQ7xySsJFM8s=
x-originating-ip: [172.21.81.94]
Content-Type: multipart/alternative; boundary="_000_D09DAE6B636851459F7575D146EFB54B2406EA58008AM1MPN1025mg_"
MIME-Version: 1.0
X-OriginalArrivalTime: 04 Jun 2013 06:47:27.0982 (UTC) FILETIME=[60EB80E0:01CE60EF]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Tue, 04 Jun 2013 11:34:00 -0700
Cc: gen-art@ietf.org, 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: Tue, 04 Jun 2013 07:43:11 -0000

--_000_D09DAE6B636851459F7575D146EFB54B2406EA58008AM1MPN1025mg_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Would adding a statement like this at the end of 3.1.2 address your concern=
:
                Exceptions for other network types, such as for  the "ATM" =
network type defined in [RFC3108], require additional specifications.
Regards,
Simo

From: ext Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: 4. kes=E4kuuta 2013 2:26
To: Veikkolainen Simo (Nokia-CTO/Espoo); draft-ietf-mmusic-sdp-miscellaneou=
s-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-=
05

Hi Simo,
For the PSTN case the document explain how to construct the m-line PSTN is =
used based on the ccap using port 9. This is not specified for the ATM case=
. So if it is not mentioned it should be clear that using  ccap for ATM is =
not specified and need another document
Roni

From: Simo.Veikkolainen@nokia.com<mailto:Simo.Veikkolainen@nokia.com> [mail=
to:Simo.Veikkolainen@nokia.com]
Sent: 31 May, 2013 1:14 PM
To: ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>; draft-ietf-mmusi=
c-sdp-miscellaneous-caps.all@tools.ietf.org<mailto:draft-ietf-mmusic-sdp-mi=
scellaneous-caps.all@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@ie=
tf.org>
Subject: RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-=
05

Hello Roni,
Please see my answer below prefixed with [SV].

From: ext Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: 29. toukokuuta 2013 21:13
To: draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org<mailto:draf=
t-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@ie=
tf.org>
Subject: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.
Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-mmusic-sdp-miscellaneous-caps-05

Reviewer: Roni Even

Review Date:2013-5-29

IETF LC End Date: 2013-6-4

IESG Telechat date:



Summary: This draft is almost ready for publication as Standard track RFC.





Major issues:



Minor issues:

1.       I can understand from the draft that when you have IP and PSTN net=
type it is requires that the ccap will be for the PSTN. What happens if you=
 want to have the ccap nettype as ATM to be used with IP in the c=3D



[SV] If either endpoint does not support ATM, the "c=3D" line with the ATM =
address would not get used (either it is not offered, or the Answerer remov=
es that from the SDP configurations). In case both endpoints actually suppo=
rt and want to use ATM as alternative to IP based bearer, the conventions i=
n RFC3108 would need to be followed when crafting the SDP configurations. T=
hat said, I haven't taken a detailed look at RFC3108 to see if the ATM base=
d media can be negotiated using the SDP Capability Negotiation framework an=
d its current extensions.



Simo


Nits/editorial comments:


--_000_D09DAE6B636851459F7575D146EFB54B2406EA58008AM1MPN1025mg_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1745645097;
	mso-list-type:hybrid;
	mso-list-template-ids:-1464020766 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Would adding a stateme=
nt like this at the end of 3.1.2 address your concern:<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Except=
ions for other network types, such as for &nbsp;the &quot;ATM&quot; network=
 type defined in [RFC3108], require additional specifications.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Simo<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<a name=3D"_____replyseparator"></a><b><span style=3D"font-size:10.0pt;font=
-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span st=
yle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quo=
t;"> ext Roni Even [mailto:ron.even.tlv@gmail.com]
<br>
<b>Sent:</b> 4. kes=E4kuuta 2013 2:26<br>
<b>To:</b> Veikkolainen Simo (Nokia-CTO/Espoo); draft-ietf-mmusic-sdp-misce=
llaneous-caps.all@tools.ietf.org<br>
<b>Cc:</b> ietf@ietf.org; gen-art@ietf.org<br>
<b>Subject:</b> RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneou=
s-caps-05<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Simo,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">For the PSTN case the =
document explain how to construct the m-line PSTN is used based on the ccap=
 using port 9. This is not specified for the ATM case. So if it is not ment=
ioned it should be clear that using
 &nbsp;ccap for ATM is not specified and need another document<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Roni<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;font-family:=
&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:Simo.Veikkolainen@nokia.com">Simo.Veikkolainen@nokia.com<=
/a> [<a href=3D"mailto:Simo.Veikkolainen@nokia.com">mailto:Simo.Veikkolaine=
n@nokia.com</a>]
<br>
<b>Sent:</b> 31 May, 2013 1:14 PM<br>
<b>To:</b> <a href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com=
</a>; <a href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.=
ietf.org">
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a href=3D"m=
ailto:gen-art@ietf.org">
gen-art@ietf.org</a><br>
<b>Subject:</b> RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneou=
s-caps-05<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hello Roni,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please see my answer b=
elow prefixed with [SV].<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;font-family:=
&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ext Roni Even [<a href=3D"mailt=
o:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]
<br>
<b>Sent:</b> 29. toukokuuta 2013 21:13<br>
<b>To:</b> <a href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@t=
ools.ietf.org">
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a href=3D"m=
ailto:gen-art@ietf.org">
gen-art@ietf.org</a><br>
<b>Subject:</b> Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-ca=
ps-05<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>=
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Document:
</span><span style=3D"font-family:&quot;Courier New&quot;">draft-ietf-mmusi=
c-sdp-miscellaneous-caps-05</span><span style=3D"font-size:11.0pt;font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Reviewer: Roni Even<o:p></o:p></span=
></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Review Date:2013&#8211;5&#8211;29<o:=
p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">IETF LC End Date: 2013-6&#8211;4<o:p=
></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">IESG Telechat date:
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Summary: This draft is almost ready =
for publication as Standard track RFC.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Major issues:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Minor issues:<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">1.<span s=
tyle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;">I can understand from the draft=
 that when you have IP and PSTN nettype it is requires that the ccap will b=
e for the PSTN. What happens if you want to have the ccap
 nettype as ATM to be used with IP in the c=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[SV] If either endpoin=
t does not support ATM, the &#8220;c=3D&#8221; line with the ATM address wo=
uld not get used (either it is not offered, or the Answerer removes that
 from the SDP configurations). In case both endpoints actually support and =
want to use ATM as alternative to IP based bearer, the conventions in RFC31=
08 would need to be followed when crafting the SDP configurations. That sai=
d, I haven&#8217;t taken a detailed look
 at RFC3108 to see if the ATM based media can be negotiated using the SDP C=
apability Negotiation framework and its current extensions.<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Simo<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_D09DAE6B636851459F7575D146EFB54B2406EA58008AM1MPN1025mg_--

From paul@cypherpunks.ca  Tue Jun  4 15:33:11 2013
Return-Path: <paul@cypherpunks.ca>
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 32C2321F99C2 for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 15:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
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 BCbdwdEWzWM7 for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 15:33:06 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id 4F3E221F944C for <ietf@ietf.org>; Tue,  4 Jun 2013 15:33:04 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3bQ7F66cljz78g for <ietf@ietf.org>; Tue,  4 Jun 2013 18:32:58 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id Vg9VBXbVzWyk for <ietf@ietf.org>; Tue,  4 Jun 2013 18:32:57 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP for <ietf@ietf.org>; Tue,  4 Jun 2013 18:32:56 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id C3B4B82C55; Tue,  4 Jun 2013 18:32:56 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id B4E9782C54 for <ietf@ietf.org>; Tue,  4 Jun 2013 18:32:56 -0400 (EDT)
Date: Tue, 4 Jun 2013 18:32:56 -0400 (EDT)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: ietf@ietf.org
Subject: Hugh Daniel has passed away
Message-ID: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
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: Tue, 04 Jun 2013 22:33:11 -0000

Hugh Daniel passed away on June 3rd after what appears to have been a heart attack.

https://nohats.ca/hugh-of-borg.jpg


Those who met him, know him. Principled to the core, and very present in
any room, he compelled people to listen to him - both by what he said,
and how loud he said it.

He has made many contributions during the early days of IPsec and
DNSSEC. He was a manager of the FreeS/WAN Project for many years and
co-founder of The Openswan Project and recently The Libreswan Project,
although his health prevented him from being as active and he wanted to
be in the last two years.

I met him for the first time at the CCC summer conference in 1999. Our
car had broken down, and everyone around me suggested to find Hugh Daniel
for help. He shone his freeswan photon light under the car, diagnosed
the problem, and put in a quick fix we could carefully drive to a repair
shop at 5km/h where we could tell the mechanic what to fix. We started
talking about Linux, crypto and he recruited me for the FreeS/WAN and
the goal to make the default mode of the internet encrypted. It is what
started me on IPsec, Opportunistic Encryption and DNS(SEC). In 2003,
he brought me to my first IETF in Vienna.

Hugh, you are still causing a difference and we will raise a non-aloholic
drink in your honour when we have reached the universal deployment
of encrypted communication for everything.



 	"When you're NAT on the net, you're NOT on the net"  -- Hugh Daniel


From cos@mip.polyamory.org  Tue Jun  4 16:04:25 2013
Return-Path: <cos@mip.polyamory.org>
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 4314A21F9992 for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 16:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
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 MfRmIbBEV-wG for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 16:04:20 -0700 (PDT)
Received: from mip.polyamory.org (mip.aaaaa.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id 1832B21F9991 for <ietf@ietf.org>; Tue,  4 Jun 2013 16:04:19 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id 3903810760; Tue,  4 Jun 2013 19:04:15 -0400 (EDT)
Date: Tue, 4 Jun 2013 19:04:15 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: Paul Wouters <paul@cypherpunks.ca>
Subject: Re: Hugh Daniel has passed away
Message-ID: <20130604230415.GY8399@mip.aaaaa.org>
References: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca>
User-Agent: Mutt/1.4.2.3i
Organization: American Association Against Acronym Abuse
Cc: 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: Tue, 04 Jun 2013 23:04:25 -0000

Paul Wouters <paul@cypherpunks.ca> wrote:
> Hugh Daniel passed away on June 3rd after what appears to have been
> a heart attack.

Whoah.  I had completely lost track of him in the past decade, but he
was one of the most memorable people I ever met through the IETF.  We
met first at IETF 37 I think, in San Jose, and kept reconnecting at
meetings for the next few years, and sharing music and book
recommendations in between.  At IETF 40 he joined me and a few friends
on a trip out of town to a concert.  I wish I remembered more of the
stories he told - I remember re-telling them to other people often,
back in the 1990s, but only remember a few now.

If I recall correctly, in addition to his leadership in promoting
encryption on the Internet, he also had a mission to make Internet
access available all over the western US, and started a number of
local and regional ISPs in the 90s in pursuit of this goal.
  -- Cos

From paf@frobbit.se  Tue Jun  4 16:39:46 2013
Return-Path: <paf@frobbit.se>
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 DC12821F8ECB for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 16:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 hKI77e7r7pIm for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 16:39:45 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id E86B121F8EC6 for <ietf@ietf.org>; Tue,  4 Jun 2013 16:39:44 -0700 (PDT)
Received: from [192.168.49.35] (unknown [87.213.29.58]) by mail.frobbit.se (Postfix) with ESMTPSA id D105B21A1C; Wed,  5 Jun 2013 01:39:43 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Hugh Daniel has passed away
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca>
Date: Wed, 5 Jun 2013 01:39:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B95823D9-7998-46ED-86D6-E7FF05FBCD72@frobbit.se>
References: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca>
To: Paul Wouters <paul@cypherpunks.ca>
X-Mailer: Apple Mail (2.1503)
Cc: 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: Tue, 04 Jun 2013 23:39:47 -0000

Oh.......

What to say, what to add?

  Patrik -- sad

On 5 jun 2013, at 00:32, Paul Wouters <paul@cypherpunks.ca> wrote:

>=20
> Hugh Daniel passed away on June 3rd after what appears to have been a =
heart attack.
>=20
> https://nohats.ca/hugh-of-borg.jpg
>=20
>=20
> Those who met him, know him. Principled to the core, and very present =
in
> any room, he compelled people to listen to him - both by what he said,
> and how loud he said it.
>=20
> He has made many contributions during the early days of IPsec and
> DNSSEC. He was a manager of the FreeS/WAN Project for many years and
> co-founder of The Openswan Project and recently The Libreswan Project,
> although his health prevented him from being as active and he wanted =
to
> be in the last two years.
>=20
> I met him for the first time at the CCC summer conference in 1999. Our
> car had broken down, and everyone around me suggested to find Hugh =
Daniel
> for help. He shone his freeswan photon light under the car, diagnosed
> the problem, and put in a quick fix we could carefully drive to a =
repair
> shop at 5km/h where we could tell the mechanic what to fix. We started
> talking about Linux, crypto and he recruited me for the FreeS/WAN and
> the goal to make the default mode of the internet encrypted. It is =
what
> started me on IPsec, Opportunistic Encryption and DNS(SEC). In 2003,
> he brought me to my first IETF in Vienna.
>=20
> Hugh, you are still causing a difference and we will raise a =
non-aloholic
> drink in your honour when we have reached the universal deployment
> of encrypted communication for everything.
>=20
>=20
>=20
> 	"When you're NAT on the net, you're NOT on the net"  -- Hugh =
Daniel
>=20


From aeopare@gmail.com  Tue Jun  4 17:06:16 2013
Return-Path: <aeopare@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 F04E021F9A1E for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 17:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.149
X-Spam-Level: 
X-Spam-Status: No, score=-1.149 tagged_above=-999 required=5 tests=[AWL=1.150,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 2fjwOmLLsjTB for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 17:06:15 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id C9ABE21F9A10 for <ietf@ietf.org>; Tue,  4 Jun 2013 17:06:14 -0700 (PDT)
Received: by mail-ob0-f179.google.com with SMTP id xk17so1524863obc.24 for <ietf@ietf.org>; Tue, 04 Jun 2013 17:06:08 -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=NdEap3mn9Lt/DWAk6jhwMlId9fFW4wCkHG4NWNJ5OFU=; b=IEwTdGln4DLAqX/m3Y6sqxaMZTGkRmj6ZJN5CAfUJt/BfALQaxVGg+NQkCA0zsHZXv wUVaWTNmTmkPVv6TKKkF06+akDrSCFKyrgwbkoayUX5SP81BrAncEHG4vgct4saPwzIn RKSSOOy6Q+FPwcbslySkhnctDtDU5LPG/10ZUDGeJJD9JxvpvUO1mNOpJ5V5q0Z+Vnz4 tnC36iKsTJDRl+Wc1x2iv32yo7+YzeBa6b0BZMzjuMnjJVx6KhPZnfVhbj8diixQYMPl 6v/RgEao4wDZYK1rOy6G9X8TPrOjHWXIu7VtERj9/7PRNJV2PrGOtYj3zn3rkAP3++eH dc9g==
MIME-Version: 1.0
X-Received: by 10.60.54.194 with SMTP id l2mr3462900oep.52.1370390768739; Tue, 04 Jun 2013 17:06:08 -0700 (PDT)
Received: by 10.60.144.7 with HTTP; Tue, 4 Jun 2013 17:06:08 -0700 (PDT)
In-Reply-To: <B95823D9-7998-46ED-86D6-E7FF05FBCD72@frobbit.se>
References: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca> <B95823D9-7998-46ED-86D6-E7FF05FBCD72@frobbit.se>
Date: Wed, 5 Jun 2013 00:06:08 +0000
Message-ID: <CANeGSFkqv6jLFVk-oetDUhGkvV1mXA3FZ6dkbuzduJtXRe=LVw@mail.gmail.com>
Subject: Re: Hugh Daniel has passed away
From: "Edwin A. Opare" <aeopare@gmail.com>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=089e011841c8f9be6604de5cf6fc
Cc: 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, 05 Jun 2013 00:06:16 -0000

--089e011841c8f9be6604de5cf6fc
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Sounds like a great guy.'

Too bad I never met him.

R.I.P Hugh Daniel.

Edwin (sob sob)


On Tue, Jun 4, 2013 at 11:39 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrot=
e:

> Oh.......
>
> What to say, what to add?
>
>   Patrik -- sad
>
> On 5 jun 2013, at 00:32, Paul Wouters <paul@cypherpunks.ca> wrote:
>
> >
> > Hugh Daniel passed away on June 3rd after what appears to have been a
> heart attack.
> >
> > https://nohats.ca/hugh-of-borg.jpg
> >
> >
> > Those who met him, know him. Principled to the core, and very present i=
n
> > any room, he compelled people to listen to him - both by what he said,
> > and how loud he said it.
> >
> > He has made many contributions during the early days of IPsec and
> > DNSSEC. He was a manager of the FreeS/WAN Project for many years and
> > co-founder of The Openswan Project and recently The Libreswan Project,
> > although his health prevented him from being as active and he wanted to
> > be in the last two years.
> >
> > I met him for the first time at the CCC summer conference in 1999. Our
> > car had broken down, and everyone around me suggested to find Hugh Dani=
el
> > for help. He shone his freeswan photon light under the car, diagnosed
> > the problem, and put in a quick fix we could carefully drive to a repai=
r
> > shop at 5km/h where we could tell the mechanic what to fix. We started
> > talking about Linux, crypto and he recruited me for the FreeS/WAN and
> > the goal to make the default mode of the internet encrypted. It is what
> > started me on IPsec, Opportunistic Encryption and DNS(SEC). In 2003,
> > he brought me to my first IETF in Vienna.
> >
> > Hugh, you are still causing a difference and we will raise a non-alohol=
ic
> > drink in your honour when we have reached the universal deployment
> > of encrypted communication for everything.
> >
> >
> >
> >       "When you're NAT on the net, you're NOT on the net"  -- Hugh Dani=
el
> >
>
>

--089e011841c8f9be6604de5cf6fc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">Sounds like a great guy.&#39;</=
div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Too bad=
 I never met him.=A0</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">
R.I.P Hugh Daniel.</div><div class=3D"gmail_extra"><br></div><div class=3D"=
gmail_extra">Edwin (sob sob)<br>
<br><br><div class=3D"gmail_quote">On Tue, Jun 4, 2013 at 11:39 PM, Patrik =
F=E4ltstr=F6m <span dir=3D"ltr">&lt;<a href=3D"mailto:paf@frobbit.se" targe=
t=3D"_blank">paf@frobbit.se</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
Oh.......<br>
<br>
What to say, what to add?<br>
<br>
=A0 Patrik -- sad<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On 5 jun 2013, at 00:32, Paul Wouters &lt;<a href=3D"mailto:paul@cypherpunk=
s.ca">paul@cypherpunks.ca</a>&gt; wrote:<br>
<br>
&gt;<br>
&gt; Hugh Daniel passed away on June 3rd after what appears to have been a =
heart attack.<br>
&gt;<br>
&gt; <a href=3D"https://nohats.ca/hugh-of-borg.jpg" target=3D"_blank">https=
://nohats.ca/hugh-of-borg.jpg</a><br>
&gt;<br>
&gt;<br>
&gt; Those who met him, know him. Principled to the core, and very present =
in<br>
&gt; any room, he compelled people to listen to him - both by what he said,=
<br>
&gt; and how loud he said it.<br>
&gt;<br>
&gt; He has made many contributions during the early days of IPsec and<br>
&gt; DNSSEC. He was a manager of the FreeS/WAN Project for many years and<b=
r>
&gt; co-founder of The Openswan Project and recently The Libreswan Project,=
<br>
&gt; although his health prevented him from being as active and he wanted t=
o<br>
&gt; be in the last two years.<br>
&gt;<br>
&gt; I met him for the first time at the CCC summer conference in 1999. Our=
<br>
&gt; car had broken down, and everyone around me suggested to find Hugh Dan=
iel<br>
&gt; for help. He shone his freeswan photon light under the car, diagnosed<=
br>
&gt; the problem, and put in a quick fix we could carefully drive to a repa=
ir<br>
&gt; shop at 5km/h where we could tell the mechanic what to fix. We started=
<br>
&gt; talking about Linux, crypto and he recruited me for the FreeS/WAN and<=
br>
&gt; the goal to make the default mode of the internet encrypted. It is wha=
t<br>
&gt; started me on IPsec, Opportunistic Encryption and DNS(SEC). In 2003,<b=
r>
&gt; he brought me to my first IETF in Vienna.<br>
&gt;<br>
&gt; Hugh, you are still causing a difference and we will raise a non-aloho=
lic<br>
&gt; drink in your honour when we have reached the universal deployment<br>
&gt; of encrypted communication for everything.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 &quot;When you&#39;re NAT on the net, you&#39;re NOT on th=
e net&quot; =A0-- Hugh Daniel<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div></div>

--089e011841c8f9be6604de5cf6fc--

From marka@isc.org  Tue Jun  4 17:08:35 2013
Return-Path: <marka@isc.org>
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 E4E3421F9A26 for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 17:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 ODewjUun60k7 for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 17:08:34 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id AF00B21F9A34 for <ietf@ietf.org>; Tue,  4 Jun 2013 17:08:31 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 5A6335F9904; Wed,  5 Jun 2013 00:08:20 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1370390910; bh=3juBUSkkkjaI/mxxjegG6B8HW4bw3iSsoBVVJtkbe/I=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=EasSRCP2ij6eE6H/HcpuYaLllVJv0M98hJ12JvJCQXCBybTO2IwuQFpgAS0MeQPJb RZvTLrkA9ge5XhkjUNR9TMaut4TQky4ffs2F3GFNOjEkC7VY73aIePVxA3izvNmjRp kXqlpSzUf4vK9mbjX7luqkDqFauw/cBV1fEkKpBE=
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id EC57F216C40; Wed,  5 Jun 2013 00:08:16 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 8B8733565A7D; Wed,  5 Jun 2013 10:08:12 +1000 (EST)
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
From: Mark Andrews <marka@isc.org>
References: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca> <B95823D9-7998-46ED-86D6-E7FF05FBCD72@frobbit.se>
Subject: Re: Hugh Daniel has passed away
In-reply-to: Your message of "Wed, 05 Jun 2013 01:39:43 +0200." <B95823D9-7998-46ED-86D6-E7FF05FBCD72@frobbit.se>
Date: Wed, 05 Jun 2013 10:08:12 +1000
Message-Id: <20130605000812.8B8733565A7D@drugs.dv.isc.org>
Cc: 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, 05 Jun 2013 00:08:35 -0000

In message <B95823D9-7998-46ED-86D6-E7FF05FBCD72@frobbit.se>, =?iso-8859-1?Q?Pa
trik_F=E4ltstr=F6m?= writes:
> Oh.......
> 
> What to say, what to add?
> 
>   Patrik -- sad

Sad indeed.  Just used one of those key chain lights the other day.

Mark
 
> On 5 jun 2013, at 00:32, Paul Wouters <paul@cypherpunks.ca> wrote:
> 
> >=20
> > Hugh Daniel passed away on June 3rd after what appears to have been a =
> heart attack.
> >=20
> > https://nohats.ca/hugh-of-borg.jpg
> >=20
> >=20
> > Those who met him, know him. Principled to the core, and very present =
> in
> > any room, he compelled people to listen to him - both by what he said,
> > and how loud he said it.
> >=20
> > He has made many contributions during the early days of IPsec and
> > DNSSEC. He was a manager of the FreeS/WAN Project for many years and
> > co-founder of The Openswan Project and recently The Libreswan Project,
> > although his health prevented him from being as active and he wanted =
> to
> > be in the last two years.
> >=20
> > I met him for the first time at the CCC summer conference in 1999. Our
> > car had broken down, and everyone around me suggested to find Hugh =
> Daniel
> > for help. He shone his freeswan photon light under the car, diagnosed
> > the problem, and put in a quick fix we could carefully drive to a =
> repair
> > shop at 5km/h where we could tell the mechanic what to fix. We started
> > talking about Linux, crypto and he recruited me for the FreeS/WAN and
> > the goal to make the default mode of the internet encrypted. It is =
> what
> > started me on IPsec, Opportunistic Encryption and DNS(SEC). In 2003,
> > he brought me to my first IETF in Vienna.
> >=20
> > Hugh, you are still causing a difference and we will raise a =
> non-aloholic
> > drink in your honour when we have reached the universal deployment
> > of encrypted communication for everything.
> >=20
> >=20
> >=20
> > 	"When you're NAT on the net, you're NOT on the net"  -- Hugh =
> Daniel
> >=20
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From ietf@cdl.asgaard.org  Tue Jun  4 18:03:52 2013
Return-Path: <ietf@cdl.asgaard.org>
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 8BB9621F9A4E for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 18:03:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 YWxXJj0Ze9Ta for <ietf@ietfa.amsl.com>; Tue,  4 Jun 2013 18:03:48 -0700 (PDT)
Received: from smtp1.emailarray.com (smtp1.emailarray.com [65.39.216.14]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC2421F9A4D for <ietf@ietf.org>; Tue,  4 Jun 2013 18:03:47 -0700 (PDT)
Received: (qmail 2708 invoked by uid 89); 5 Jun 2013 01:03:46 -0000
Received: from unknown (HELO ?204.29.150.161?) (Y2RsQGFzZ2FhcmQub3JnQDUwLjc2LjM0LjE4NQ==) (POLARISLOCAL)  by smtp1.emailarray.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 5 Jun 2013 01:03:46 -0000
From: "Christopher LILJENSTOLPE" <ietf@cdl.asgaard.org>
To: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
Subject: Re: Hugh Daniel has passed away
Date: Tue, 04 Jun 2013 18:03:44 -0700
Message-ID: <C8728364-3040-40D4-B3BF-29EF2FA91C37@cdl.asgaard.org>
In-Reply-To: <B95823D9-7998-46ED-86D6-E7FF05FBCD72@frobbit.se>
References: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca> <B95823D9-7998-46ED-86D6-E7FF05FBCD72@frobbit.se>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_7C870838-FA01-416D-BC39-5F59FB8933F1_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (1.5.4r3438)
X-PolarisMail-Flags: x
Cc: 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, 05 Jun 2013 01:03:53 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_7C870838-FA01-416D-BC39-5F59FB8933F1_=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4 Jun 2013, at 16:39, Patrik F=C3=A4ltstr=C3=B6m wrote:

> Oh.......
>
> What to say, what to add?

The world is, unfortunately, a tad bit quieter now.

Quite sad, and quite unexpected.

	Christopher

>
> Patrik -- sad
>
> On 5 jun 2013, at 00:32, Paul Wouters <paul@cypherpunks.ca> wrote:
>
>>
>> Hugh Daniel passed away on June 3rd after what appears to have been a =
heart attack.
>>
>> https://nohats.ca/hugh-of-borg.jpg
>>
>>
>> Those who met him, know him. Principled to the core, and very present =
in
>> any room, he compelled people to listen to him - both by what he said,=

>> and how loud he said it.
>>
>> He has made many contributions during the early days of IPsec and
>> DNSSEC. He was a manager of the FreeS/WAN Project for many years and
>> co-founder of The Openswan Project and recently The Libreswan Project,=

>> although his health prevented him from being as active and he wanted t=
o
>> be in the last two years.
>>
>> I met him for the first time at the CCC summer conference in 1999. Our=

>> car had broken down, and everyone around me suggested to find Hugh Dan=
iel
>> for help. He shone his freeswan photon light under the car, diagnosed
>> the problem, and put in a quick fix we could carefully drive to a repa=
ir
>> shop at 5km/h where we could tell the mechanic what to fix. We started=

>> talking about Linux, crypto and he recruited me for the FreeS/WAN and
>> the goal to make the default mode of the internet encrypted. It is wha=
t
>> started me on IPsec, Opportunistic Encryption and DNS(SEC). In 2003,
>> he brought me to my first IETF in Vienna.
>>
>> Hugh, you are still causing a difference and we will raise a non-aloho=
lic
>> drink in your honour when we have reached the universal deployment
>> of encrypted communication for everything.
>>
>>
>>
>> 	"When you're NAT on the net, you're NOT on the net"  -- Hugh Daniel
>>


--
=E6=9D=8E=E6=9F=AF=E7=9D=BF
Check my PGP key here: http://www.asgaard.org/cdl/cdl.asc
Current vCard here: http://www.asgaard.org/cdl/cdl.vcf
--=_MailMate_7C870838-FA01-416D-BC39-5F59FB8933F1_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJRro5wAAoJEGmx2Mt/+Iw/8tQH/jeXVoELpf20SVvy+gOCnnmv
xt6/Aock2Kwrssj2yvJN2C/R7NC0/WdFGwINjwvPZSHEK8O8lRHjIwDorXwsiV6/
4V8fsN6wxkGS05v6i5g1DgoI6bUkvQsZc9fHVp5plvqd7abuq1cO1GJpw8LYiXjg
a75s20Zor3ooiKNATKcxZaVlxsLWlnb90IrnaMo2mp635SMA3Vg8mfOZ0Kx9hca4
ELx7CMJ+bOiccT1OwuR1FLzSta4kD5sQLn8Rn5/l3Be2XkSxNsStVWAzqxzTRpD1
nM3yIwfB12YQdaJACK3T9kPPEjomo2wtUPmZfKL7qMZoXr41Qh+30vqsBcsuuxE=
=aYPv
-----END PGP SIGNATURE-----

--=_MailMate_7C870838-FA01-416D-BC39-5F59FB8933F1_=--

From hartmans@mit.edu  Tue Jun  4 19:17:52 2013
Return-Path: <hartmans@mit.edu>
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 D293A21F9AFD; Tue,  4 Jun 2013 19:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 BwXvF009Fvk1; Tue,  4 Jun 2013 19:17:45 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id CC0A721F9943; Tue,  4 Jun 2013 19:17:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 71A6120629; Tue,  4 Jun 2013 22:13:10 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tE2pW_s_6mdK; Tue,  4 Jun 2013 22:13:08 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue,  4 Jun 2013 22:13:08 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3608F4498; Tue,  4 Jun 2013 22:16:37 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Douglas Otis <doug.mtview@gmail.com>, "Murray S. Kucherawy" <msk@blackops.org>, Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Dave Rand <dave_rand@trendmicro.com>
Subject: Re: Review of: draft-otis-dkim-harmful
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net>
Date: Tue, 04 Jun 2013 22:16:37 -0400
In-Reply-To: <51ADB6E6.5030300@dcrocker.net> (Dave Crocker's message of "Tue,  04 Jun 2013 11:44:06 +0200")
Message-ID: <tslfvwxjo8q.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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, 05 Jun 2013 02:17:52 -0000

I'm jumping into this particular branch of the conversation late.  I've
followed Doug's concerns against DKIM somewhat over the years.

It seems fairly clear that Doug has a long-standing concern regarding
DKIM and how it interacts with e-mail.
It seems fairly clear he's in the rough within the IETF.

If Doug is asking the IETF to get consensus behind his draft, that seems
like it will be a hard sell.

However, I strongly support writing down Doug's argument in a draft and
assuming it is sufficiently coherent publishing it somewhere.  I tend to
think the ISR process of the RFC editor would do a good job evaluating
the question of coherency and that the independent stream of the RFC
series is a great place to publish the opinion of someone who has been
involved in the process for a long time and still believes we've made a
mistake.

Sure, lots of people in the IETF will disagree with doug; that's what
makes Doug in the rough.

Interestingly, reading Dave's review and criticism of Doug's draft
increases my confidence that there's something in what Doug has been
thinking worth writing down and publishing.
I think it's fine if Dave wants to write up his own draft about why Doug
is wrong.

So, I'd like to encourage Doug to refine his work, fix errors of
precision, but to say I think this is worth writing down.

--Sam

From ron.even.tlv@gmail.com  Tue Jun  4 21:57:35 2013
Return-Path: <ron.even.tlv@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 AD4D121F9371; Tue,  4 Jun 2013 21:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HTML_MESSAGE=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 BzZM1h2j0c2L; Tue,  4 Jun 2013 21:57:33 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id BFEF721F93F8; Tue,  4 Jun 2013 21:57:32 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id hn14so4419258wib.2 for <multiple recipients>; Tue, 04 Jun 2013 21:57:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=DN7HQiaS+cJ6gFfXZNjWwjPAjjmZKuDdC//HQjp+Fjg=; b=Ct+90WIIhjARVq40FyI97CIL5kg7bAWd0bekEBRik57qJhrDNyLUsrXnlzmABNgBWo Qh1rjdHJRJCaQ21dfV19DqkyOUSH1E4YWls0tLgvwytXimHqcUJj/SK4VkPAYHUfjVMN M5iPJDdBknWkrDo9Y7w1+3ZRvYUVlYgfc2f2J8pQtHDLdDwSXbVvFEudPuuXhh1R6b2I a5e0yzTKnwDsypulokWGDIChEjyGtJkGkByjZoMR0TM46t1iOeVKw0NSDiHNdkXstdVa 9NySu7tRk8V+sPwT0tHpz0JwEdtGj90l3eKNpfAZiAnGaCg/0PCOjSc+v2hkUPopL7pc TiCQ==
X-Received: by 10.180.198.140 with SMTP id jc12mr4468790wic.53.1370408251521;  Tue, 04 Jun 2013 21:57:31 -0700 (PDT)
Received: from RoniE ([109.64.225.31]) by mx.google.com with ESMTPSA id b11sm7447741wiv.10.2013.06.04.21.57.29 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 04 Jun 2013 21:57:30 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <Simo.Veikkolainen@nokia.com>, <draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org>
References: <000301ce5c98$278d0220$76a70660$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com> <027001ce60b1$ba2ecbf0$2e8c63d0$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2406EA58@008-AM1MPN1-025.mgdnok.nokia.com>
In-Reply-To: <D09DAE6B636851459F7575D146EFB54B2406EA58@008-AM1MPN1-025.mgdnok.nokia.com>
Subject: RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
Date: Wed, 5 Jun 2013 07:56:16 +0300
Message-ID: <031901ce61a9$04af7ce0$0e0e76a0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_031A_01CE61C2.29FE1470"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQD2ctd9kjZ9dlpMJt4mULENla+sLwGDWn0oAPcibgECiupmU5quQQiQ
Content-Language: en-us
Cc: gen-art@ietf.org, 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, 05 Jun 2013 04:57:35 -0000

This is a multipart message in MIME format.

------=_NextPart_000_031A_01CE61C2.29FE1470
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Simo,

This will be OK

Roni

=20

From: Simo.Veikkolainen@nokia.com [mailto:Simo.Veikkolainen@nokia.com]=20
Sent: 04 June, 2013 9:48 AM
To: ron.even.tlv@gmail.com;
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of
draft-ietf-mmusic-sdp-miscellaneous-caps-05

=20

Would adding a statement like this at the end of 3.1.2 address your =
concern:

                Exceptions for other network types, such as for  the =
"ATM"
network type defined in [RFC3108], require additional specifications.

Regards,

Simo

=20

From: ext Roni Even [mailto:ron.even.tlv@gmail.com]=20
Sent: 4. kes=E4kuuta 2013 2:26
To: Veikkolainen Simo (Nokia-CTO/Espoo);
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of
draft-ietf-mmusic-sdp-miscellaneous-caps-05

=20

Hi Simo,

For the PSTN case the document explain how to construct the m-line PSTN =
is
used based on the ccap using port 9. This is not specified for the ATM =
case.
So if it is not mentioned it should be clear that using  ccap for ATM is =
not
specified and need another document

Roni

=20

From: Simo.Veikkolainen@nokia.com [mailto:Simo.Veikkolainen@nokia.com]=20
Sent: 31 May, 2013 1:14 PM
To: ron.even.tlv@gmail.com;
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of
draft-ietf-mmusic-sdp-miscellaneous-caps-05

=20

Hello Roni,

Please see my answer below prefixed with [SV].

=20

From: ext Roni Even [mailto:ron.even.tlv@gmail.com]=20
Sent: 29. toukokuuta 2013 21:13
To: draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: Gen-ART LC review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05

=20

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments =
you
may receive.

Document: draft-ietf-mmusic-sdp-miscellaneous-caps-05

Reviewer: Roni Even

Review Date:2013=965=9629

IETF LC End Date: 2013-6=964

IESG Telechat date:=20

=20

Summary: This draft is almost ready for publication as Standard track =
RFC.

=20

=20

Major issues:

=20

Minor issues:

1.  I can understand from the draft that when you have IP and PSTN =
nettype
it is requires that the ccap will be for the PSTN. What happens if you =
want
to have the ccap nettype as ATM to be used with IP in the c=3D

=20

[SV] If either endpoint does not support ATM, the =93c=3D=94 line with =
the ATM
address would not get used (either it is not offered, or the Answerer
removes that from the SDP configurations). In case both endpoints =
actually
support and want to use ATM as alternative to IP based bearer, the
conventions in RFC3108 would need to be followed when crafting the SDP
configurations. That said, I haven=92t taken a detailed look at RFC3108 =
to see
if the ATM based media can be negotiated using the SDP Capability
Negotiation framework and its current extensions.

=20

Simo

=20

Nits/editorial comments:

=20


------=_NextPart_000_031A_01CE61C2.29FE1470
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1745645097;
	mso-list-type:hybrid;
	mso-list-template-ids:-1464020766 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Simo,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>This will be =
OK<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Simo.Veikkolainen@nokia.com [mailto:Simo.Veikkolainen@nokia.com] =
<br><b>Sent:</b> 04 June, 2013 9:48 AM<br><b>To:</b> =
ron.even.tlv@gmail.com; =
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org<br><b>Cc:</b>=
 ietf@ietf.org; gen-art@ietf.org<br><b>Subject:</b> RE: Gen-ART LC =
review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05<o:p></o:p></span></p></div></=
div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Would adding a statement like this at the end of =
3.1.2 address your concern:</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Exceptions for other network =
types, such as for &nbsp;the &quot;ATM&quot; network type defined in =
[RFC3108], require additional specifications.</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Regards,</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Simo</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><a =
name=3D"_____replyseparator"></a><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ext Roni Even [<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Sent:</b> 4. kes=E4kuuta 2013 2:26<br><b>To:</b> Veikkolainen =
Simo (Nokia-CTO/Espoo); <a =
href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.or=
g">draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br><b>=
Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
RE: Gen-ART LC review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05</span><o:p></o:p></p></div></=
div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Simo,</span><o:p></o:p></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>For the PSTN case the =
document explain how to construct the m-line PSTN is used based on the =
ccap using port 9. This is not specified for the ATM case. So if it is =
not mentioned it should be clear that using &nbsp;ccap for ATM is not =
specified and need another document</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a =
href=3D"mailto:Simo.Veikkolainen@nokia.com">Simo.Veikkolainen@nokia.com</=
a> [<a =
href=3D"mailto:Simo.Veikkolainen@nokia.com">mailto:Simo.Veikkolainen@noki=
a.com</a>] <br><b>Sent:</b> 31 May, 2013 1:14 PM<br><b>To:</b> <a =
href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>; <a =
href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.or=
g">draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br><b>=
Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
RE: Gen-ART LC review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05</span><o:p></o:p></p></div></=
div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hello Roni,</span><o:p></o:p></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Please see my answer =
below prefixed with [SV].</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ext Roni Even [<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Sent:</b> 29. toukokuuta 2013 21:13<br><b>To:</b> <a =
href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.or=
g">draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br><b>=
Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
Gen-ART LC review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05</span><o:p></o:p></p></div></=
div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-mmusic-sdp-miscellaneous-caps-05</span><o:p></o:p></p><p=
 class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;5&#8211;29</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-6&#8211;4</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: </span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as Standard track =
RFC.</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I can =
understand from the draft that when you have IP and PSTN nettype it is =
requires that the ccap will be for the PSTN. What happens if you want to =
have the ccap nettype as ATM to be used with IP in the =
c=3D</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[SV] If either endpoint does not support ATM, the &#8220;c=3D&#8221; =
line with the ATM address would not get used (either it is not offered, =
or the Answerer removes that from the SDP configurations). In case both =
endpoints actually support and want to use ATM as alternative to IP =
based bearer, the conventions in RFC3108 would need to be followed when =
crafting the SDP configurations. That said, I haven&#8217;t taken a =
detailed look at RFC3108 to see if the ATM based media can be negotiated =
using the SDP Capability Negotiation framework and its current =
extensions.</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Simo</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div></div></body></html>
------=_NextPart_000_031A_01CE61C2.29FE1470--


From nsclick@gmx.de  Wed Jun  5 04:40:05 2013
Return-Path: <nsclick@gmx.de>
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 BFC5021F85BF for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 04:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 kuYLhSq56ljU for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 04:40:00 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id AA8F021F854E for <ietf@ietf.org>; Wed,  5 Jun 2013 04:39:59 -0700 (PDT)
Received: from 3capp-gmx-bs19.server.lan ([172.19.170.71]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0Leg4G-1U2sRa2oCU-00qRw7 for <ietf@ietf.org>; Wed, 05 Jun 2013 13:39:52 +0200
Received: from [141.7.28.126] by 3capp-gmx-bs19.server.lan with HTTP; Wed Jun 05 13:39:52 CEST 2013
MIME-Version: 1.0
Message-ID: <trinity-eaf9eee4-0692-4534-9e59-393702af96ba-1370432392554@3capp-gmx-bs19>
From: "Thomas Meier" <nsclick@gmx.de>
To: ietf@ietf.org
Subject: Forwarding AODV messages over a tunnel
Content-Type: text/plain; charset=UTF-8
Date: Wed, 5 Jun 2013 13:39:52 +0200 (CEST)
Importance: normal
Sensitivity: Normal
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-Provags-ID: V03:K0:shU2DleTFkOLTdO/a+IOPiGmauc0XiqK5PIWUkgFgnU pgBIrqMUZOnbgH1nvFBTsSpiSbYAqZlz8Nve85MSMJiP0hTl1z h52Yr2AlMPTWKRjWJKDf0Vycwg4ZNb5c0ADnmLjq5QFxBllHs+ eW/g8JWEKJNc/TSElp2ER7JPxdce/Um+4Q7jsiv/aaeRfrdwoP aEGf7iPD/QfDEty2FjvNdt5PFdjeoabWFSoDXCDWGUUvnzgog5 m+s6Xfd6Wse9qzfOpu+25day8XhteFbBk0OjdzQoRf5V6b3vBI zyei9E=
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, 05 Jun 2013 12:02:21 -0000

Hello,
=C2=A0
I want to forward AODV messages over a tunnel (don't worry, =
it's not for a wormhole attack).
In the RFC3561 I can't find information ab=
out how to deal with the packet at the tunnel endpoint. Should I increment =
the hopcount of a RREQ by one or by the number of hops the tunnel has? Furt=
hermore I'm wondering about which address to use for the previous node at t=
he tunnel endpoint. Should this be the entrance of the tunnel or the "real"=
 previous node?
If the tunnel entrance is used as previous node and the hop=
count is only incremented by one, the tunnel would be prefered compared to =
a connection without a tunnel (like in wormhole attacks).
Is there some inf=
ormation on how to deal with a tunnel?
=C2=A0
Thanks,
=C2=A0
Thomas

From ybmcu@panix.com  Wed Jun  5 05:42:59 2013
Return-Path: <ybmcu@panix.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 713B221F9A01 for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 05:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.249
X-Spam-Level: 
X-Spam-Status: No, score=-1.249 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FB_GET_MEDS=2.75, RCVD_IN_DNSWL_MED=-4]
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 AcG22NQcRkqy for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 05:42:54 -0700 (PDT)
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by ietfa.amsl.com (Postfix) with ESMTP id 32F0D21F96ED for <ietf@ietf.org>; Wed,  5 Jun 2013 05:42:54 -0700 (PDT)
Received: from Desktop6.panix.com (167-19.nyc.dsl.access.net [166.84.167.19]) by mailbackend.panix.com (Postfix) with ESMTP id 599E128653 for <ietf@ietf.org>; Wed,  5 Jun 2013 08:42:53 -0400 (EDT)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 05 Jun 2013 08:42:58 -0400
To: ietf@ietf.org
From: Ben Yalow <ybmcu@panix.com>
Subject: Re: Hugh Daniel has passed away
In-Reply-To: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca>
References: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20130605124253.599E128653@mailbackend.panix.com>
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, 05 Jun 2013 12:42:59 -0000

At 06:32 PM 6/4/2013 -0400, Paul Wouters wrote:

>Hugh Daniel passed away on June 3rd after what appears to have been 
>a heart attack.
>
>https://nohats.ca/hugh-of-borg.jpg


   <snip>

Since he was also very well known in the science fiction community, I 
thought I would pass along details from an SF list that had them 
(with permission from the poster on that list, Tony Cratz).

- - -


         I have talked with Mel (Hugh's roommate) and got a bit more
         information then I had earlier tonight.

         I have known Hugh for a number of years (about the time he first
         moved out to the Bay Area in the early '80s). And we have
         maintain a close contact. Under normal conditions I would talk
         with Hugh at least once a month. Often times more often.

         In the 2011-2012 time frame he spent almost a year back in the
         DC area doing work for a friend. He he came back he developed
         an inner ear condition which earlier this year caused him to
         almost be blind. He did get some meds for the condition at the
         time but it was not until last month when he found the correct
         me (or at least one which seemed to be working better). Of late
         he has been able to see mostly normal (not his extra normal
         vision which he had but closer to a standard 20/20 vision).

         I last talked to Hugh about a week+ ago. At that time he was
         on a good day after having had a few bad days and being almost
         full bed ridden.

         About half an hour ago (2:15 AM 6/4) I was able to talk with
         Mel. Hugh had picked Mel up from the airport and seemed his
         normal self (or at least his present condition self). Monday
         morning Mel had walked around the apartment and knew that Hugh
         had been up and not in his bedroom. Then at 2:30 PDT Mel went
         to a movie. He found Hugh on the floor in the bathroom with the
         water running (which was not running before the movie). Which
         means the TOD was between 2:30-4:30 PDT. Mel did overhear one
         of the EMTs say that Hugh's body temp (at that time) was at
         72F.

         Mel has confirmed that both Hugh's mother and sister has been
         notified and he has talked with both of them.

         At present we are not sure of cause of death but it would seem
         to be heart attack or stroke related.

         I for one will miss Hugh. He has been a good friend and help
         me a number of times. When I had a tech question I wanted
         answered, Hugh was the person I turned to in most cases.

         I have enjoyed our late night chats on the phone during the last
         few years. There has been times when he wanted someone to talk
         to about technical issues, or about what was happening in the
         world (such as the flooding and nuclear building collapse).
         Or talking about how he was solving a human rights abuse issue
         by being able to read 8 inch floppies which had been stored
         away (this even made Frontline, Hugh was never mention as the
         person, but he was doing the main technical work.) Hugh even
         gave me a VoIP call while he was there. Or how he was
         testing metal detectors in bath of dry ice, so Landon Noll
         could used them for Antarctic meteorites.

         I will miss my good friend.


                                                         Tony

- - -

Ben

-----
Ben Yalow                                    ybmcu@panix.com  


From sm@resistor.net  Wed Jun  5 10:04:05 2013
Return-Path: <sm@resistor.net>
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 D707421F9C32 for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 10:04:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 BbJGaVGxg6iQ for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 10:04:05 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F4A421F9C2F for <ietf@ietf.org>; Wed,  5 Jun 2013 10:04:04 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r55H3wYo002851 for <ietf@ietf.org>; Wed, 5 Jun 2013 10:04:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1370451843; bh=ZwJpUtBYET9jNe10BnZWnqSA0WzAc3D4NRnjAC2GSk8=; h=Date:To:From:Subject:In-Reply-To:References; b=psXLHzckBcdcszwPN80ue4ME4s80jdI7tvrjBEmuu1Kvifx0sgwC80VYKqe1vi3xX RMet5lYVBx3xni/UWEi/GiM8SOMbZD1PfLKS5Zq2KN5qr8AimPNC+2/IGncgM9kyV3 ksOrWzJ1JoQXUYmdP6yD5wOKIPOJ4NsB9bccXaeM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1370451843; i=@resistor.net; bh=ZwJpUtBYET9jNe10BnZWnqSA0WzAc3D4NRnjAC2GSk8=; h=Date:To:From:Subject:In-Reply-To:References; b=FUKcbWKnuEnjJSSb9tlT1u7DG4Lgghm+bpJ6zB92ilIOFLUeCsPXgCfIy9F+H85/1 DNXeVRJU0HTjc4luCToX4Kn05ytLRnW4cUu3fRmaImzx+nYvzb3ZFYcxXuBgE5KV4T tkOfmHZD2IkvtK3iRF2cDPcgjTesCeILMI1smGjE=
Message-Id: <6.2.5.6.2.20130605072309.0be62c30@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 05 Jun 2013 09:12:30 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-thornburgh-adobe-rtmfp-07.txt> (Adobe's Secure Real-Time Media Flow Protocol) to Informational RFC
In-Reply-To: <20130528161229.25215.37302.idtracker@ietfa.amsl.com>
References: <20130528161229.25215.37302.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 05 Jun 2013 17:04:06 -0000

At 09:12 28-05-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Adobe's Secure Real-Time Media Flow Protocol'
>   <draft-thornburgh-adobe-rtmfp-07.txt> as Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-06-25. Exceptionally, comments may be

The write-up mentions that:

   "As a private protocol, no technical changes were performed on the
    protocol itself, but the authors disclosed more details in
    response to the WG discussions."

I don't see why this specification requires IETF consensus as it is 
not possible to suggest any major changes.  The explanation given for 
the intended status is that the aspects of the protocol protected by 
IPR were not reviewed externally.

The summary is that there is a memo which is not a WG memo, which is 
supposed to have gained WG consensus, where some group is supposed to 
consider the IPR disclosure, and which is being Last-Called as an 
Individual Submission.  I would like to be considered as not part of 
the consensus.

Nits:

   "At the time of writing, the Adobe Flash Player runtime is
    installed on more than one billion end-user desktop computers."

Shouldn't the memo be about the protocol?

Regards,
-sm 


From iab-chair@iab.org  Wed Jun  5 11:50:24 2013
Return-Path: <iab-chair@iab.org>
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 AA28C21F8F4D; Wed,  5 Jun 2013 11:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 XDgsRewHI6aw; Wed,  5 Jun 2013 11:50:24 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 867E721F8F5C; Wed,  5 Jun 2013 11:50:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 76C2612462A; Wed,  5 Jun 2013 11:50:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jte1v8EUBaNr; Wed,  5 Jun 2013 11:50:23 -0700 (PDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) by c8a.amsl.com (Postfix) with ESMTPSA id 09165124627; Wed,  5 Jun 2013 11:50:22 -0700 (PDT)
From: IAB Chair <iab-chair@iab.org>
Content-Type: multipart/alternative; boundary=Apple-Mail-424--838486026
Subject: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 / IETF Relationship"
Date: Wed, 5 Jun 2013 14:50:21 -0400
Message-Id: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <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, 05 Jun 2013 18:50:24 -0000

--Apple-Mail-424--838486026
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

This is a call for review of "The IEEE 802 / IETF Relationship"
prior to potential approval as an IAB stream RFC.

The document is available for inspection here:
https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/

The Call for Review will last until 20 June 2013.
Please send comments to iab@iab.org. 

On behalf of the IAB,
  Russ Housley
  IAB Chair


--Apple-Mail-424--838486026
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">This is a call for review of "The IEEE 802 / IETF Relationship"<div>prior to potential approval as an IAB stream RFC.<br><br>The document is available for inspection here:<br><a href="https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/">https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/</a><br>

<br>The Call for Review will last until 20 June 2013.<div>Please send comments to <a href="mailto:iab@iab.org">iab@iab.org</a>. <br>
</div></div><div><br></div><div>On behalf of the IAB,</div><div>&nbsp; Russ Housley</div><div>&nbsp; IAB Chair</div><div><br></div></body></html>
--Apple-Mail-424--838486026--

From rjsparks@nostrum.com  Wed Jun  5 14:56:26 2013
Return-Path: <rjsparks@nostrum.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 00DBC21F9193; Wed,  5 Jun 2013 14:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 0c5i+IL92bII; Wed,  5 Jun 2013 14:56:24 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4170021F8B35; Wed,  5 Jun 2013 14:56:24 -0700 (PDT)
Received: from unnumerable.local (mobile-166-147-071-187.mycingular.net [166.147.71.187]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r55LuLOW065539 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Wed, 5 Jun 2013 16:56:22 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <51AFB3FF.7000009@nostrum.com>
Date: Wed, 05 Jun 2013 16:56:15 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, mmusic@ietf.org, draft-ietf-mmusic-rfc2326bis@tools.ietf.org
Subject: Gen-art last call review: draft-ietf-mmusic-rfc2326bis-34
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (shaman.nostrum.com: 166.147.71.187 is authenticated by a trusted mechanism)
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, 05 Jun 2013 21:56:26 -0000

I am the assigned Gen-ART reviewer for this draft. For background on 
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments 
you may receive.

Document: draft-ietf-mmusic-rfc2326bis-34
Reviewer: Robert Sparks
Review Date: 05-Jun-2013
IETF LC End Date: 04-Jun-2013
IESG Telechat date: not yet on a telechat

Summary: This draft is on the right track but has open issues, described 
in the review.

I have not reviewed this document at the level of detail I prefer for 
Gen-art reviews, but have tried to be thorough in the sections I have 
reviewed.

In particular,
I didn't verify the tables and the text agree
I didn't carefully check the ABNF
I haven't thought about possible edge cases and race conditions as much 
as I would have liked
I didn't closely review the security mechanisms in section 19 or the 
specialized MIKEY keying mechanism in the appendix - both need careful 
review from security experts.

One observation I would like to make before calling out issues and nits:

The document is very long, and the structure is unusual - much of the 
definition of the protocol itself is in the appendices. You are missing 
an opportunity to make this document much shorter (thereby likely 
increasing its effectiveness). Much of the jump in from RFC2326 was 
importing the description of headers and responses from HTTP, tailoring 
them to RTSP. That was a good exercise in that it highlights some issues 
that would otherwise be non-obvious (and raises a few questions below). 
But you followed the style from HTTP perhaps too closely - much shorter 
descriptions without examples might have done the job better. Overall, 
separating exposition and examples from the protocol definition would 
make it much easier for an implementer to find the definition of the 
protocol, and use the document as a reference when diagnosing a failure 
to interoperate.

Major Issues

I'm not seeing what instructs an RTSP element on how to find the server 
it would try to open a connection to given an rtsp or rtsps URI? Are you 
assuming it would be doing A or AAAA DNS lookups? Should this protocol 
use NAPTR/SRV? The document should be explicit. On a related note, (and 
maybe I missed this), but where do you talk about what an element should 
check in the server's certificate when connecting over TLS? Are you 
assuming a common name match? Or are you expecting some SubjectAltName 
processing?

The document should say more about when connection reuse is appropriate, 
particularly when the connections happened because of an rtsps uri. Two 
different names might resolve to the same IP address - reusing a 
connection formed when looking at the first name (and verifying the 
server's cert) is dangerous. A new connection needs to be formed (and 
verified) instead.

The text talks about the option to queue S->C requests if there isn't a 
connection to the client available. Ostensibly, this means the request 
can go down some future connection. It's not clear how the server can 
tell the right client connected. In particular, when using rtsps, how do 
you prevent a malicious client from getting such a queued message that 
wasn't meant for him?

Given that the text talks about queuing S-C requests, it should 
explicitly call out whether a server can queue a response if the 
connection the associated request arrived on is no longer available. I 
think what you want to say is that such a response must not be queued, 
and must be dropped.

There are several places in the text that talk about using a 503 
response with a Retry-After header to push back on traffic from an 
element (the first is section 10.7).
* It's not clear what the subject of a 503 is. Is it intended to be 
scoped to requests to the resource in the RURI of the associated 
request? Is it intended to be scoped to the domain in that resource? Or 
is it, like in SIP, intended to be scoped to the server issuing the 
response, independent of what the RURI contained?
* If the intent is that the 503 talks about the server, then you should 
clarify that a proxy doesn't simply forward 503 responses (after 
rewriting CSeqs), and should probably have a response of its own. 
Otherwise, clients that might be talking to two different servers 
through one proxy would lose access to both of them when one of the 
servers 503ed.

Section 4.9.1 lists values the Seek-Style header can take, but 18.45 
lists a completely different set (which most of the rest of the document 
uses). Should 4.9.1 be changed to use the values in 18.45? Are the right 
strings being used in sections 13.4.4 through 13.4.6? Those appear to be 
using strings from 4.9.1.

The document will not stand if you delete some of the appendices. They 
aren't supplementary material. Please consider restructuring the 
normative sections back into the main document, or clearly identifying 
which ones define protocol and which are background information.

Section 15 talks about a "transparent' proxy, but there is no 
description in this document of what protocol such a thing should 
follow. What bad thing happens if you remove all mention of 
"transparent" proxies from the document? As far as I can tell, that 
won't affect the protocol definition at all.

The list of steps for establishing an SRTP cryptographic context in 
C.1.4.1 says "This specification does not specify an explicit method for 
indicating this SRTP cryptographic context establishment method, but 
future specifications may." in the context of looking at the SDP. SDP 
_has_ methods of indicating what keying mechanism is used with SRTP - 
are you talking about something different? Why doesn't this section say 
something like "the use of SRTP with RTSP is only defined with MIKEY 
with keys established as defined in this section. Future documents may 
talk about how an RTSP implementation might treat SDP that indicates 
some other key mechanism be used"? Could you provide an example in the 
document of an RTSP message carrying SDP reflecting the use of SRTP as 
defined in this document?


Minor Issues

The document uses the notion of a "control connection" (it appears first 
in section 2.5) without defining what that is, or what kind of 
connections you might have that aren't control connections.

The update to the registration of the rtsp and rtsps schema call out 
that there are changes that can result in interoperability issues. It 
doesn't say what the issues are, or who might encounter them. I can 
infer that the point is that there might be problems if a URI following 
this updated registration were to be processed by an RTSP 1.0 
implementation (or any other application that relied on the previous 
definition). It would be better to say that explicitly, and talk about 
how a previous implementation is likely to act when presented with a URI 
that exercised these new changes. (It's not clear to me that all of the 
thread at www.ietf.org—msg01567.html 
<http://www.ietf.org/mail-archive/web/uri-review/current/msg01567.html> 
concluded - I see how the fragments question ended, but what about 
things like the addition of IPV6 literals? In particular, I'm not 
finding a response where Ted Hardie agreed that the potential for 
interoperability failure had been adequately addressed).


I think you've said something different than you mean in 5.4 item 1. I 
think you mean to say that an RTSP implementation would ignore any body 
that happened to come in message that MUST NOT contain one. What you've 
said is that the part of the parser that's doing framing has to stop 
framing at the end of the headers, and that such an errant body would be 
parsed as a separate message. As written this would keep someone from 
using an Internet Message Format parser since it would have to ignore 
any Content-Length that might have appeared, even though it wasn't 
supposed to.

In section 10.4, it looks like a server can keep an RTSP transaction 
pending forever if it sends 100 responses often enough. I assume the 
client's recourse if it doesn't want to remain involved is to close the 
connection. If that's right, it's worth calling it out explicitly in 
this section.

Somewhere, probably in section 15.2, you should be explicit that a proxy 
that is multiplexing requests MUST keep the requests in the same order 
as they are folded together. You can infer that, or things simply break, 
but saying it explicitly would be better.

Both GET_PARAMETER and SET_PARAMETER are listed as keep-alive methods in 
10.5, but the note in section 13 on table 7 only uses that as a reason 
for requiring SET_PARAMETER. Why doesn't it also apply to GET_PARAMETER? 
And why is this only required at servers? "Required" in this section 
means Mandatory to Implement, I think. If that's right, it should be 
made explicit. If that's not right, what does it mean?

Section 13.8 makes a good argument for always putting parameters to be 
retrieved in a body. Why are you keeping the complexity of also allowing 
them in headers?

Section 13.10: "That should not provide any benefit." is not clear - can 
you expand it a little?

In Section 13.10 you talk about clients _sending_ media (search for 
"send or receive media"). Do you mean anything more than possibly RTCP? 
Can you make that clear in the section?

Section 15.2's second paragraph appears to be the only place the proxy 
rewriting of CSeq in order to multiplex requests is defined, and it is 
very loose. It would be easy for a reader to fail to recognize this as 
an interoperability requirement. Please consider expanding how this is 
specified when addressing the comment about above about keeping requests 
in relative order when multiplexing.

You follow the principle of saying a client should treat a response with 
an unknown response code, the same as it would treat the x00 of that 
class (e.g. 400 for an unknown 4xx). However, you do not define what a 
response code of 300 means. How is a client supposed to handle an 
unknown 3xx response?

As written, a client and server can use HTTP Basic authentication over 
TCP that is not protected with TLS. Consider restricting it's use to TLS 
only. Are you sure you don't need to say anything RTSP specific about 
DIGEST computations (I don't think you need to go as far as SIP did 
talking about DIGEST, but I'm surprised you haven't run into issues 
relying only on 2617 literally.


How does 411 Length Required for this protocol make sense? Given that 
you've restricted the protocol to TCP and require the Content-Length 
header to be present if there is a body, in what circumstance would a 
server need to send a 411?


Section 18.19 requires senders to increment CSeq by 1. We have a 
reliable transport with no request retransmission, so there should never 
be gaps at the receiver. Should the receiver check and react some way if 
there are gaps? I think you should explicitly tell them not to even 
look. If you agree, why is incrementing by one important as long as you 
are always strictly increasing?

You call out several places where RTCP is essential to allow RTSP using 
RTP to work correctly, yet section C.1.2 sets up conditions where RTCP 
MUST NOT be sent. Why are you allowing those instead of treating the 
conditions you describe as errors?


Nits


The definition of Message still talks about connectionless transports

22.14 says "These URI schemes are defined in existing registries which 
are not created by RTSP." Should it say that they are _registered_ 
rather than defined, and "not created by this document" instead of by 
RTSP? In section 4.2 in the paragraph discussing ports 554 and 322, why 
is the language different for rtsp and rtsps? "MUST be used" vs "is 
registered and MUST be assumed"?

Consider a reference in 4.4 to where SMPTE 30 drop is defined, 
particularly for where the 1/100th frame measurement comes from.

Section 4.5 introduces NPT as indicating "the absolute position" and 
then defines something that can carry a point or a range. I suggest 
adjusting the first sentence to allow for a range.

Section 4.9.1's description of Conditional Random Access contains some 
ambiguity. It would help be more explicit. I think it's trying to say 
"would move the client's play point further away from the requested play 
point than it's play point currently is."?

Section 5 : what do you mean by "tricky" switching?

Section 7: consider octets instead of bytes

Section 10.3: what is "take appropriate action" trying to say?

The document mixes using "3rr" and "3xx" to talk about redirect 
responses. Why are there two ways to say the same thing?

(Total nit, but) The examples show dates in 1997, when there could be no 
RTSP/2.0. Are there other aspects of the examples that might not have 
been updated?

Is "will need to use" at the bottom of page 85 in section 13.5.2 trying 
to say something that should be said with 2119?

Consider saying that a client must not put a Terminate-Reason in a C->S 
Teardown request, or tweak the definition of Terminate-Reason to discuss 
client use and the possibility of C->S specific values.

These two sentences in 13.7.1 are particularly hard to parse together: 
"The time period is considered extended when it is 10 times the Session 
Timeout period. Consideration of the application of the server and its 
content should be performed when configuring what is considered as 
extended period of time." I suspect they were not written at the same 
time? Can you simplify what they are trying to say, noting that the 
suggested "10 times" is a default, and that if you want to change that 
default, you need to consider the context?

Section 14: "Interleaved binary data SHOULD only be used if RTSP is 
carried over TCP". Is this leftover from when UDP was an option?

(small nit) Section 14, you mention an ASCII dollar sign - maybe you 
should just say an octet with value 0x24?

It's not clear how far up to go with "upper-layer protocol headers" in 
section 14, given that you are trying to speak generally about carrying 
things in interleaved data. Your example for RTP may cover the only case 
that matters. Consider speaking more normatively (instead of with an 
example) for RTP and provide some guidelines about where to cut the 
prefixes for other things you might want to carry (lest you end up with 
the v6 headers too when tunneling some new foo protocol?)

In section 17, you say "Status codes that have the same meaning are not 
repeated here." But you did repeat them (see 200 OK). Should that 
sentence be deleted?

304 (section 17.3.4) probably should have been a different class 
response, maybe even a 2xx. The text does call it out as "unusual" for 
the 3xx, but it would be better to say why this ended up in this 
response class.

I might be confused, but I'm not sure the redirection semantics defined 
in this document lead to the "black hole" case discussed in 17.4.14. If 
I'm confused, could you send me an example of such a redirection black 
hole happening?

Section 18.11 first paragraph should be split into two sentences.

Is "MUST be transported over TCP" in C.2.1 stale now that no 
connectionless transport is defined?

The end of Appendix G still implies that CSeq was primarily for 
unreliable transports. There are other places that out and point to 
proxy multiplexing. All of them should acknowledge that CSeq is 
necessary for associating responses with requests.


From d3e3e3@gmail.com  Wed Jun  5 15:25:22 2013
Return-Path: <d3e3e3@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 6B08221F853A; Wed,  5 Jun 2013 15:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 2Edrwoalnjn9; Wed,  5 Jun 2013 15:25:21 -0700 (PDT)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id DE67921F842E; Wed,  5 Jun 2013 15:25:20 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id n12so1640009oag.3 for <multiple recipients>; Wed, 05 Jun 2013 15:24:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=fFcsCiyEWhgEBu8lyqjT6GbmlMMw0PoUVwa0WIWBeLU=; b=r0zgyulHGu2/cWQL2Ay1se2v4Yhi0DLC/siSE/99tEf3Smmv3dnfv8rxt69Gd+dDfI Ue3/JZC+rtXWN1j74F8MmenpnZm0vhAQ3dLgsRTncALsOVJfM1aijfUfksDft27/CPHn 0XVLmAQL+WIE/PGDyYQOatP++FJvhxjD6vE1nvZkfIgfBTgM/K+45SwxVI5zDi3DCiK1 iPiSb44z9WGtcodUOOXxscYNwUhQVqW5dRNsEZHacbep7GS5q1OwDDk/JC5R1uLwY4Iy qa1XW63Hkk+pMrF4ZELOuxeiODeeTscV4i4SfiojKgCSfQu7bfsiqkvfJ9INRPHt9n6G MVdw==
X-Received: by 10.60.79.68 with SMTP id h4mr16895188oex.39.1370471096719; Wed, 05 Jun 2013 15:24:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.12.65 with HTTP; Wed, 5 Jun 2013 15:24:36 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 5 Jun 2013 18:24:36 -0400
Message-ID: <CAF4+nEESGzBW51ARg-YbZ1ZZ8q5KXtj55Cx-musdkwrG+zOJWA@mail.gmail.com>
Subject: Re: Gen-ART review of draft-eastlake-rfc5342bis-02
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: General Area Review Team <gen-art@ietf.org>, "joe.abley@icann.org" <joe.abley@icann.org>, "ietf@ietf.org" <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, 05 Jun 2013 22:25:22 -0000

Hi David,

Thanks for this review. See below:

On Wed, Jun 5, 2013 at 6:13 PM, Black, David <david.black@emc.com> wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-eastlake-rfc5342bis-02
> Reviewer: David L. Black
> Review Date: June 5, 2013
> IETF LC End Date: June 4, 2013
>
> Summary:
> This draft is on the right track but has open issues, described in the review.
>
> This draft updates the IANA registered Ethernet parameters for IETF use,
> including recording values assigned for documentation.  It also makes some
> minor changes to IANA procedures.
>
> IANA should review this entire draft, not just its IANA Considerations section;
> Pearl Liang appears to have done that comprehensive review for IANA.

Right, I'm working on a response to Pearl.

> Major issues: None
>
> Minor issues: One, the IANA review also found this issue.
>
> Section 3.2 states:
>
>         IANA will assign "00-00-0E-00-42" as the protocol number under the
>         IANA OUI to be used for documentation purposes.
>
> IANA has not made this assignment, but this assignment request is not
> recorded in the IANA Considerations section where IANA actions are
> requested and recorded by IANA after they have been performed.  This
> assignment needs to be added to the IANA Considerations section;
> see item 5 in the IANA review.

OK.

> Nits/editorial comments:
>
> Section 1: This document uses an "IESG Ratification" process for some
> assignments.  This is not the same process as the "IESG Approval" process
> defined in RFC 5226.  As those names could be confused by a casual reader
> who is not strongly familiar with IANA processes, I suggest adding a
> statement that the "IESG Ratification" process is defined in this document
> and is not the same as the "IESG Approval" process in RFC 5226.  This could
> be added after the sentence that cites RFC 5226.

OK.

> Section 1.4: It would be helpful to point out that there is no OUI assigned
> for documentation purposes, but there are identifiers based on the IANA OUI
> that have been assigned for documentation purposes.

OK.

> In general, the use of the acronym IAB for Individual Address Block is
> unfortunate, but unavoidable, and this is clearly pointed out in the
> definition of the IAB acronym in section 1.2.  Nothing can or should be
> done about this.
>
> idnits 2.12.17 did not find any nits.

I think your suggestions are all good.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------

From sm@resistor.net  Wed Jun  5 18:08:11 2013
Return-Path: <sm@resistor.net>
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 EC0CB21F9632; Wed,  5 Jun 2013 18:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
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 By569cxsBdET; Wed,  5 Jun 2013 18:08:11 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BF3F721F9631; Wed,  5 Jun 2013 18:08:10 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r56183QC005609; Wed, 5 Jun 2013 18:08:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1370480888; bh=uvTn/wX3MYWR35LNrP/gG4AmqLP93LJ/2MIu/MQv8hE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=a7VWdpRx94xt9flAt/1Aj3LmhnZMuG++w5ZCYX52SMV7oyW0o3w8a6sFd61iOfgWZ 6ErbxE8y2UOlBL0SF3T+uU/SJAqIdxXe79gkl7bTBjwt6AOU/QcvQOzTA2H4S2EmFT 7CrOuGxeFMjdxvH2zXwuM0U7CzyLZ9NyytdkBd0U=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1370480888; i=@resistor.net; bh=uvTn/wX3MYWR35LNrP/gG4AmqLP93LJ/2MIu/MQv8hE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pks7z4VMNOelD5JvJkOK/EeDmKSLAmb4nHHqqGVjNrDLlazb7FU/zlThaD4IPjr3Z 4csKxcZIWBO23tY/Jf4q3UOgVP08ilxzXhIAAERihMzb6G9veG5yOdQyHd1cIN5xVF RhHEHaKDCsp1FNKwgfm87KDcRCx1Pr3QQxG6gMsU=
Message-Id: <6.2.5.6.2.20130605173623.0d4a9790@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 05 Jun 2013 18:07:27 -0700
To: iab@iab.org
From: SM <sm@resistor.net>
Subject: Re: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 / IETF Relationship"
In-Reply-To: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Thu, 06 Jun 2013 01:08:12 -0000

At 11:50 05-06-2013, IAB Chair wrote:
>This is a call for review of "The IEEE 802 / IETF Relationship"
>prior to potential approval as an IAB stream RFC.

In Section 1:

   "This document contains a set of principles and guidelines that serves
    as the basis for establishing collaboration between Project 802 of
    the Institute of Electrical and Electronics Engineers (IEEE 802) and
    the Internet Engineering Task Force (IETF) of the Internet Society
    (ISOC)"

Is the IETF a task force of the Internet Society?

In Section 3.1.2:

   "4.  Appointment of RFC Series and Internet Assigned Number Authority
       (IANA) roles"

What is the meaning of IANA roles in the above?

In Section 3.1.4

   "Voting:   Both organizations use voting as a decision-making tool,
              but IEEE 802 uses voting within working groups, while IETF
              working groups do not use voting.  Working group chairs may
              ask for a "show of hands" or "take a hum" to judge backing
              for a proposal, but this is not considered to be "voting" -
              The IESG does ballot documents when considering them for
              publication.  This balloting is a final approval for
              publication."

The first part of the text says that the IETF uses voting whereas the 
"hum" is not considered as "voting".  "Decision-making" might be a 
better label.

Regards,
-sm


From abdussalambaryun@gmail.com  Wed Jun  5 18:28:50 2013
Return-Path: <abdussalambaryun@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 F2F7321F944C for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 18:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[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 KiYTs5dArQBT for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 18:28:49 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 8820021F9362 for <ietf@ietf.org>; Wed,  5 Jun 2013 18:28:49 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa11so1361445pad.5 for <ietf@ietf.org>; Wed, 05 Jun 2013 18:28:49 -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=39y2hUDisCtTACPMaZzxDpkKDanpjXWfJ83sMyzvQEE=; b=d27AQGMrbiCOAirlOr6GIuZbofvp7Kfvy95jAxofUcbPikcwbVyJfwsq+/OWBZVEef x22N+0y58+Cb2C/9f5KAf2/JlNBB/TCM6OutUborrXm3iLbfu9SlRS6hwcmJtZjiw59q Z38N7IXTcwHJjiVuEo9/0dk1Ju8Ww3/N1nFvJV9V35Qthtaf0WnTLKDzArJJGdGc/W5m lzbEBb/l/YZUM4cBcBp4aHm3O5MPT2vbQMmxKXeW17P/crGa/kBp5z4LoljfpdbLcw3G 9jFUfL05dirvJFMCXRZySf47LqiqoHiy02vqr5hsnkbp225Mn2k7yJuLE8JwRsLQeYeb rwdA==
MIME-Version: 1.0
X-Received: by 10.68.113.101 with SMTP id ix5mr36410837pbb.142.1370482129192;  Wed, 05 Jun 2013 18:28:49 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Wed, 5 Jun 2013 18:28:49 -0700 (PDT)
In-Reply-To: <trinity-eaf9eee4-0692-4534-9e59-393702af96ba-1370432392554@3capp-gmx-bs19>
References: <trinity-eaf9eee4-0692-4534-9e59-393702af96ba-1370432392554@3capp-gmx-bs19>
Date: Thu, 6 Jun 2013 03:28:49 +0200
Message-ID: <CADnDZ8-bKDfGuuhFXTgPHD6dQy2yyRr8npKzBJxsEFPFCH7Yhw@mail.gmail.com>
Subject: Re: Forwarding AODV messages over a tunnel
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Thomas Meier <nsclick@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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: Thu, 06 Jun 2013 01:28:50 -0000

On 6/5/13, Thomas Meier <nsclick@gmx.de> wrote:
>
> Hello,
>
> I want to forward AODV messages over a tunnel (don't worry, it's not for a
> wormhole attack).

its ok, but if it was my AODV network I will be worried. Tunneling is
not understood only if I know what network are you tunneling through!!

> In the RFC3561 I can't find information about how to deal with the packet at
> the tunnel endpoint.

IMHO, normal ways of packet tunnel

> Should I increment the hopcount of a RREQ by one or by
> the number of hops the tunnel has?

RREQ is not a packet, your question was on packets, that increment of
RREQ is done by AODV node received. So I think only once, because one
tunnel and between two aodv-nodes only.

> Furthermore I'm wondering about which
> address to use for the previous node at the tunnel endpoint. Should this be
> the entrance of the tunnel or the "real" previous node?

nothing is real when you are tunneling, so use the node address of
tunnel start. Overall I think the routing performance will not be good
only if the network elements of the tunnel is not mobile.

> If the tunnel entrance is used as previous node and the hopcount is only
> incremented by one, the tunnel would be prefered compared to a connection
> without a tunnel (like in wormhole attacks).

Not correct, you don't say your reason, so I don't know how to respond.

> Is there some information on how to deal with a tunnel?
>
In MANET documents I don't think there is importance of using
tunneling, I think it is not prefered. If used it will be an attack so
I am worried about what are you doing  :-)

AB

From abdussalambaryun@gmail.com  Wed Jun  5 19:14:13 2013
Return-Path: <abdussalambaryun@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 6A92821F93F8 for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 19:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[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 X8dA3dhwKyhC for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 19:14:12 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id C8F9221F93D4 for <ietf@ietf.org>; Wed,  5 Jun 2013 19:14:12 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so2602375pbb.20 for <ietf@ietf.org>; Wed, 05 Jun 2013 19:14:07 -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=jrC/zQq9Z8uTUi3GhM1UoGiNlCeYtQd6E3PfSxQ6uKw=; b=CPVQX8ErN6tZ7HRRUZBoRElPHkoKVgu7XytJKWQ/ACJuzFbw5FsKtHMHbMv4ryt3uR LwE0v7ptCMKcYsnTJXEjiy8NECtO6XdFu5W3clh2pLuWsc56XyRMIEhHpgdiGZBULFXI m22JDAaKCIcV5ObYHwc5s3UALrPomOPpHvwuWsMhbZBpBzy4BXsvDVy+u1PLfINZDCk5 VEdrpENEmQuo2lIat/+/LxgmBbSU7HDBAXgWOFC0uD7+xP6ALkA11o0LgGVy5mPHVk8D tID9tSrmJ/Ug+Q2xvBvptX3oTcbASi0iX9FinHaumWcWMKhnDJlrPOaj6X+dEtsu2EZY UU6A==
MIME-Version: 1.0
X-Received: by 10.66.122.8 with SMTP id lo8mr35843297pab.165.1370484847770; Wed, 05 Jun 2013 19:14:07 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Wed, 5 Jun 2013 19:14:07 -0700 (PDT)
In-Reply-To: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
Date: Thu, 6 Jun 2013 04:14:07 +0200
Message-ID: <CADnDZ8-AhTZHwJ2uL4M8G_98g+WLvOEWPTmS8PxytJJnefSGvQ@mail.gmail.com>
Subject: Re: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 / IETF Relationship"
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: IAB <iab@iab.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: Thu, 06 Jun 2013 02:14:13 -0000

Reply to your request dated 05.06.2013

Reviewer: Abdussalam Baryun
Dated 06.06.2013
The I-D: draft-iab-rfc4441rev-04
A1 Comments: Overall

Overall, why does the document start with IEEE before IETF. If this is
a document produced by us as IETF, we need to focus on the
relationship of OUR organisation first with others. So IMHO, it should
say in the title: The IETF/ IEEE 802 Relationship. Within all the
document I recommend we follow that focus on the relationship between
the IETF and IEEE 802. In the sections I recommend to start with IETF
not IEEE802. Furthermore, the title just says relationship, it is not
enough title, what kind of relationship you are doing? The word
relationship is not mentioned in the Abstract at all which I expected
that.

AB>change> please amend the title to : The IETF and IEEE 802
Collaboration Relationship.

Why the I-D does not reference a normative reference from IEEE that
also states the relationship between IEEE802 / IETF, or is there no
document procedure for the other party?

Each IETF and IEEE802 should have their own terminology in this I-D,
there is some mixing which confuses, example ballot used in IEEE802
but the I-D uses it for IETF as well (please change). Are we ignoring
our other terminologies of IETF procedure.

Section 3.1.4 Cultural differences

AB> there is missing culture issue which is the opennes, is the IEEE
802 open for access. Culture does not mean only how and when making
decisions, the culture is about interacting with the COMMUNITY. I am
not sure about the domain of the IEEE802 community, but know the IETF
community.

AB> ADD> please describe in this section the communities and access
policy to each organisation body (WG, Working task, etc).

Best Regards
AB

+++++++++++++++++++++++++++++++++
On 6/5/13, IAB Chair <iab-chair@iab.org> wrote:
> This is a call for review of "The IEEE 802 / IETF Relationship"
> prior to potential approval as an IAB stream RFC.
>
> The document is available for inspection here:
> https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/
>
> The Call for Review will last until 20 June 2013.
> Please send comments to iab@iab.org.
>
> On behalf of the IAB,
>   Russ Housley
>   IAB Chair
>
>

From abdussalambaryun@gmail.com  Wed Jun  5 20:02:00 2013
Return-Path: <abdussalambaryun@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 8258C21F8464 for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 20:01:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[AWL=-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 wVf1VfY5U9+W for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 20:01:55 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id EA1C221F8B90 for <ietf@ietf.org>; Wed,  5 Jun 2013 20:01:53 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id g10so2695759pdj.41 for <ietf@ietf.org>; Wed, 05 Jun 2013 20:01:53 -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=YoBUVboBj7sOshj4o+ZVXtNob8BHGC0hgSYhP10LxZo=; b=QAKvXTSG5tg++xURtY0a+6+N+3Q8D0U6Q+SsZA7fpmAzYP6MyH5mPrUZBnKUu8WCmx imi6MoqKd1NZy7bRwwXnd/SQMPjYs8jH+FT3pp63jL58kYeKoHGf0bFh7XRAtM8fIBGS BuSMxVVsnw7zPxDXnxAa59HTeGETirNQT6QUqTNylLcwKwcaPdMN6wXuitFmYUHJz6YW EWxhHsaScdl0yQfTNIc5VnrDnKLsE3wxTguufZKQhTwfj32dBeThHd8D5e2D832gP9EQ ss2NPMknMEU9pmt7O0vQuBEjBM+EddzJp29dkKAhDgMtit0ykugOvH05QVUI1AJDCHcP WReQ==
MIME-Version: 1.0
X-Received: by 10.68.113.101 with SMTP id ix5mr36697089pbb.142.1370487713647;  Wed, 05 Jun 2013 20:01:53 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Wed, 5 Jun 2013 20:01:53 -0700 (PDT)
In-Reply-To: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
Date: Thu, 6 Jun 2013 05:01:53 +0200
Message-ID: <CADnDZ8_UWTPYd7GX2irqi7uG_WEpSS0uUCbLLfygaWQ7t96M=g@mail.gmail.com>
Subject: Re: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 / IETF Relationship"
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: IAB <iab@iab.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: Thu, 06 Jun 2013 03:02:00 -0000

I want to discuss this issue of collaboration if I get a
response/permission. How can the IETF participant collaborate with
IEEE 802 memebr/participant? From the I-D I see that the IETF
participant NEEDs the IETF WG chair to do that, but the IEEE 802
participant does not need any chair.

 Are we collaborating at all levels as management and participants, or
are we collaborating at management only from one organisation and at
other levels at the other organisation (no equal opportunities)?

I RECOMMEND that this I-D reconsiders the collaboration and leave it
between managements of both organisations, as long as one of the
organisation is collaborating mostly at management.

If we don't discuss and only review, there may be a misunderstandning
between community and the author.

Regards
AB

On 6/5/13, IAB Chair <iab-chair@iab.org> wrote:
> This is a call for review of "The IEEE 802 / IETF Relationship"
> prior to potential approval as an IAB stream RFC.
>
> The document is available for inspection here:
> https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/
>
> The Call for Review will last until 20 June 2013.
> Please send comments to iab@iab.org.
>
> On behalf of the IAB,
>   Russ Housley
>   IAB Chair
>
>

From l.wood@surrey.ac.uk  Wed Jun  5 20:03:26 2013
Return-Path: <l.wood@surrey.ac.uk>
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 0618D21F9273 for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 20:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[UNPARSEABLE_RELAY=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 AM-w32uSqEBD for <ietf@ietfa.amsl.com>; Wed,  5 Jun 2013 20:03:21 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.150]) by ietfa.amsl.com (Postfix) with ESMTP id A873D21F8D90 for <ietf@ietf.org>; Wed,  5 Jun 2013 20:03:17 -0700 (PDT)
Received: from [195.245.231.67:10867] by server-14.bemta-5.messagelabs.com id 48/CE-25870-3FBFFA15; Thu, 06 Jun 2013 03:03:15 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-82.messagelabs.com!1370487794!28395237!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1576 invoked from network); 6 Jun 2013 03:03:14 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-9.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 6 Jun 2013 03:03:14 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Thu, 6 Jun 2013 04:03:14 +0100
From: <l.wood@surrey.ac.uk>
To: <sm@resistor.net>, <iab@iab.org>
Date: Thu, 6 Jun 2013 04:01:08 +0100
Subject: RE: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE	802 / IETF Relationship"
Thread-Topic: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE	802 / IETF Relationship"
Thread-Index: Ac5iUoc4EckjoBj1Qm+nsskGt2+FywAD5B0N
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EA0@EXMB01CMS.surrey.ac.uk>
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>, <6.2.5.6.2.20130605173623.0d4a9790@resistor.net>
In-Reply-To: <6.2.5.6.2.20130605173623.0d4a9790@resistor.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 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: Thu, 06 Jun 2013 03:03:26 -0000

> Is the IETF a task force of the Internet Society?

RFC2031 documented the takeover. Snuck through on informational...

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of SM [sm@res=
istor.net]
Sent: 06 June 2013 02:07
To: iab@iab.org
Cc: ietf@ietf.org
Subject: Re: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE  802=
 / IETF Relationship"

At 11:50 05-06-2013, IAB Chair wrote:
>This is a call for review of "The IEEE 802 / IETF Relationship"
>prior to potential approval as an IAB stream RFC.

In Section 1:

   "This document contains a set of principles and guidelines that serves
    as the basis for establishing collaboration between Project 802 of
    the Institute of Electrical and Electronics Engineers (IEEE 802) and
    the Internet Engineering Task Force (IETF) of the Internet Society
    (ISOC)"

Is the IETF a task force of the Internet Society?

In Section 3.1.2:

   "4.  Appointment of RFC Series and Internet Assigned Number Authority
       (IANA) roles"

What is the meaning of IANA roles in the above?

In Section 3.1.4

   "Voting:   Both organizations use voting as a decision-making tool,
              but IEEE 802 uses voting within working groups, while IETF
              working groups do not use voting.  Working group chairs may
              ask for a "show of hands" or "take a hum" to judge backing
              for a proposal, but this is not considered to be "voting" -
              The IESG does ballot documents when considering them for
              publication.  This balloting is a final approval for
              publication."

The first part of the text says that the IETF uses voting whereas the
"hum" is not considered as "voting".  "Decision-making" might be a
better label.

Regards,
-sm


From abdussalambaryun@gmail.com  Thu Jun  6 03:15:28 2013
Return-Path: <abdussalambaryun@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 1FD1B21F92E7; Thu,  6 Jun 2013 03:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[AWL=1.299, BAYES_00=-2.599]
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 ldBzzB9XIgNQ; Thu,  6 Jun 2013 03:15:24 -0700 (PDT)
Received: from mail-pd0-f179.google.com (mail-pd0-f179.google.com [209.85.192.179]) by ietfa.amsl.com (Postfix) with ESMTP id D409721F921F; Thu,  6 Jun 2013 03:15:23 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id q11so3138596pdj.38 for <multiple recipients>; Thu, 06 Jun 2013 03:15:20 -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=UzmbndkKjIU1oQDCy5twj3ynC4pxiNOub82+G4AD95Q=; b=V0L6L4Nzpe9Fy2gAa62M8MvLHdW03qpe2IZ/OldRXDsIhNI96pQsaD7Eev96eLY1ep 2R8UlEDTGa54UaMXBkVJczLtOLd4SM5Qd3pBYaCa37CULi09cKfCVh+GJdn8NYpLuIIk Xd/ZfzoJGorDHRySZOWu5RGM9rmU38qjgMfoF8GwOAaOkglfNGaVUQMgVrmPnu4Wlubw BxXhcpDeNPOzTsFn1FFaE7kDWyG0D/mSvzikI3gE9iU9sFKW+88MPMISYDPCr6CThugH oUgf4Ug9QXFqw/mtUtQv91tgyjnQjZ1oTGUFcccEN7nr8FGjoky1INZ0pSSWZqIBQTpf 4eNw==
MIME-Version: 1.0
X-Received: by 10.68.176.197 with SMTP id ck5mr36797529pbc.165.1370513720720;  Thu, 06 Jun 2013 03:15:20 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Thu, 6 Jun 2013 03:15:20 -0700 (PDT)
In-Reply-To: <20130605150955.25672.65454.idtracker@ietfa.amsl.com>
References: <20130605150955.25672.65454.idtracker@ietfa.amsl.com>
Date: Thu, 6 Jun 2013 12:15:20 +0200
Message-ID: <CADnDZ8-JoLv4drWwx1DmU9Bgeo1ts7_h=WtNUwripmTYB3EZ9w@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-ospf-manet-single-hop-mdr-03.txt> (Use of OSPF-MDR in Single-Hop Broadcast Networks) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: "draft-ietf-ospf-manet-single-hop-mdr@tools.ietf.org" <draft-ietf-ospf-manet-single-hop-mdr@tools.ietf.org>, "iesg@ietf.org" <iesg@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: Thu, 06 Jun 2013 10:15:28 -0000

I send my request to the editors including questions but no reply from
them to me. The thread [1] raised some issues, which is not mentioned
in the I-D. The message [2] was ignored not answered (this is last
reminder). The message [3] proposes using RFC5444 into this I-D, or
raise the question of why not using MANET packet format within MANET
domains (I need an answer).

[1] http://www.ietf.org/mail-archive/web/manet/current/msg15400.html
[2] http://www.ietf.org/mail-archive/web/manet/current/msg15412.html
[3] http://www.ietf.org/mail-archive/web/manet/current/msg15418.html

The I-D SHOULD not go forward if it still ignores the IETF community questions.

Regards
AB

On 6/5/13, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Open Shortest Path First IGP WG
> (ospf) to consider the following document:
> - 'Use of OSPF-MDR in Single-Hop Broadcast Networks'
>   <draft-ietf-ospf-manet-single-hop-mdr-03.txt> as Experimental RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-19. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
> RFC 5614 (OSPF-MDR) extends OSPF to support mobile ad hoc networks
> (MANETs) by specifying its operation on the new OSPF interface of type
> MANET.  This document describes the use of OSPF-MDR in a single-hop
> broadcast network, which is a special case of a MANET in which each
> router is a (one-hop) neighbor of each other router.  Unlike an OSPF
> broadcast interface, such an interface can have a different cost
> associated with each neighbor.  The document includes configuration
> recommendations and simplified mechanisms that can be used in single-hop
> broadcast networks.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

From jari.arkko@piuha.net  Thu Jun  6 04:49:03 2013
Return-Path: <jari.arkko@piuha.net>
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 EED8621F99DD for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 04:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.25
X-Spam-Level: 
X-Spam-Status: No, score=-102.25 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 xogrFgWGs5i9 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 04:48:57 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 3410921F99AB for <ietf@ietf.org>; Thu,  6 Jun 2013 04:48:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8204C2CC48; Thu,  6 Jun 2013 14:48:52 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTxJVi88j27C; Thu,  6 Jun 2013 14:48:51 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 8110E2CC3C; Thu,  6 Jun 2013 14:48:51 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Hugh Daniel has passed away
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20130605000812.8B8733565A7D@drugs.dv.isc.org>
Date: Thu, 6 Jun 2013 07:48:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A5D349E-8699-47AD-8A78-FB2FF2A2BD1C@piuha.net>
References: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca> <B95823D9-7998-46ED-86D6-E7FF05FBCD72@frobbit.se> <20130605000812.8B8733565A7D@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1503)
Cc: 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: Thu, 06 Jun 2013 11:49:03 -0000

I am sad to hear about this. I remember Hugh from various IPsec test =
events. And the lights=85 I still remember the lights.

Jari
=20=

From stephen.farrell@cs.tcd.ie  Thu Jun  6 06:13:32 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
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 4240021F99C4 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 06:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2+HnRBFCR+D7 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 06:13:27 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 748DC21F99C9 for <ietf@ietf.org>; Thu,  6 Jun 2013 06:13:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D3546BEA1; Thu,  6 Jun 2013 14:13:03 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b31A6yOf24BE; Thu,  6 Jun 2013 14:12:59 +0100 (IST)
Received: from [10.87.48.12] (unknown [86.41.56.142]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E5D76BE87; Thu,  6 Jun 2013 14:12:58 +0100 (IST)
Message-ID: <51B08AD0.2070908@cs.tcd.ie>
Date: Thu, 06 Jun 2013 14:12:48 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: IAB Chair <iab-chair@iab.org>
Subject: Re: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 / IETF Relationship"
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
In-Reply-To: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IAB <iab@iab.org>, IETF <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: Thu, 06 Jun 2013 13:13:32 -0000

A couple of minor comments:

- For some unfathomable reason IEEE people seem to call mailing
lists "reflectors" - that might be worth a mention. Section 4
otherwise seems repetitive.

-  3.3.1.4 says: Since it is
   possible to participate in IETF without attending meetings, or even
   joining a mailing list, IETF WG chairs will provide the information
   to anyone who requests it.  However, since IEEE 802 work-in-progress
   is copyrighted, incorporating material into IETF documents or posting
   the username/password on mailing lists or websites is not permitted.

That's a pretty bogus setup. I would think that if IEEE do want to
share some or all drafts with us they could much more easily create
a web page when those drafts are available without access control.
Or we could if they didn't mind. (Or I could do it if there's no "we"
that wants to:-) Asking IETF WG chairs to deal with passwords is a
bit silly. I'm not objecting to this, but am suggesting someone ask
IEEE if they'd like to consider the silliness here and fix it.

S.


On 06/05/2013 07:50 PM, IAB Chair wrote:
> This is a call for review of "The IEEE 802 / IETF Relationship"
> prior to potential approval as an IAB stream RFC.
> 
> The document is available for inspection here:
> https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/
> 
> The Call for Review will last until 20 June 2013.
> Please send comments to iab@iab.org. 
> 
> On behalf of the IAB,
>   Russ Housley
>   IAB Chair
> 
> 

From wjhns1@hardakers.net  Thu Jun  6 07:07:01 2013
Return-Path: <wjhns1@hardakers.net>
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 4CE2021F9052 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 07:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 JB2SjpZbYUnk for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 07:06:56 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id 1FDB721F8EC3 for <ietf@ietf.org>; Thu,  6 Jun 2013 07:06:56 -0700 (PDT)
Received: from localhost (unknown [IPv6:2001:470:1f00:187:211f:1683:e2b8:8b09]) by mail.hardakers.net (Postfix) with ESMTPSA id 2D51F28F97; Thu,  6 Jun 2013 07:06:53 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Paul Wouters <paul@cypherpunks.ca>
Subject: Re: Hugh Daniel has passed away
References: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca>
Date: Thu, 06 Jun 2013 07:06:53 -0700
In-Reply-To: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca> (Paul Wouters's message of "Tue, 4 Jun 2013 18:32:56 -0400 (EDT)")
Message-ID: <0ld2rzs58i.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: 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: Thu, 06 Jun 2013 14:07:01 -0000

Paul Wouters <paul@cypherpunks.ca> writes:

> Hugh Daniel passed away on June 3rd after what appears to have been a
> heart attack.

I remember many interesting moments and conversations within the 
times that I talked with him.  He was a very memorable person.

But certainly the one that stands out in my mind the most was our first
encounter.  He wrote me over email as we were arranging a time and place
to meet and ended it with "I'll be wearing a red shirt; you won't miss
me".  I thought at the time that was quite a declaration.  And indeed I
did not miss him that day.  I do now, however.

-- 
Wes Hardaker
Parsons

From l.wood@surrey.ac.uk  Thu Jun  6 07:21:33 2013
Return-Path: <l.wood@surrey.ac.uk>
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 358AF21F90CD for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 07:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, UNPARSEABLE_RELAY=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 iO0lYVximVdy for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 07:21:28 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.147]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0CB21F93C4 for <ietf@ietf.org>; Thu,  6 Jun 2013 07:21:27 -0700 (PDT)
Received: from [195.245.231.67:28733] by server-11.bemta-5.messagelabs.com id 50/91-26693-5EA90B15; Thu, 06 Jun 2013 14:21:25 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-82.messagelabs.com!1370528485!30829885!2
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29770 invoked from network); 6 Jun 2013 14:21:25 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-2.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 6 Jun 2013 14:21:25 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Thu, 6 Jun 2013 15:21:25 +0100
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <iab-chair@iab.org>
Date: Thu, 6 Jun 2013 15:20:12 +0100
Subject: RE: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802	/ IETF Relationship"
Thread-Topic: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 / IETF Relationship"
Thread-Index: Ac5it8LHzdODfUi0RRukqSO6MPnyawACTIob
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EA2@EXMB01CMS.surrey.ac.uk>
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>, <51B08AD0.2070908@cs.tcd.ie>
In-Reply-To: <51B08AD0.2070908@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: iab@iab.org, 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: Thu, 06 Jun 2013 14:21:33 -0000

> Asking IETF WG chairs to deal with passwords is a bit silly.

Maybe they could be emailed a monthly reminder of their personal subscripti=
on password on the first of each month.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Stephen Fa=
rrell [stephen.farrell@cs.tcd.ie]
Sent: 06 June 2013 14:12
To: IAB Chair
Cc: IAB; IETF
Subject: Re: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 =
     / IETF Relationship"

A couple of minor comments:

- For some unfathomable reason IEEE people seem to call mailing
lists "reflectors" - that might be worth a mention. Section 4
otherwise seems repetitive.

-  3.3.1.4 says: Since it is
   possible to participate in IETF without attending meetings, or even
   joining a mailing list, IETF WG chairs will provide the information
   to anyone who requests it.  However, since IEEE 802 work-in-progress
   is copyrighted, incorporating material into IETF documents or posting
   the username/password on mailing lists or websites is not permitted.

That's a pretty bogus setup. I would think that if IEEE do want to
share some or all drafts with us they could much more easily create
a web page when those drafts are available without access control.
Or we could if they didn't mind. (Or I could do it if there's no "we"
that wants to:-) Asking IETF WG chairs to deal with passwords is a
bit silly. I'm not objecting to this, but am suggesting someone ask
IEEE if they'd like to consider the silliness here and fix it.

S.


On 06/05/2013 07:50 PM, IAB Chair wrote:
> This is a call for review of "The IEEE 802 / IETF Relationship"
> prior to potential approval as an IAB stream RFC.
>
> The document is available for inspection here:
> https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/
>
> The Call for Review will last until 20 June 2013.
> Please send comments to iab@iab.org.
>
> On behalf of the IAB,
>   Russ Housley
>   IAB Chair
>
>

From touch@isi.edu  Thu Jun  6 10:13:44 2013
Return-Path: <touch@isi.edu>
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 8F8ED21F9A3C for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 10:13:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 wb0wc6YCAsp0 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 10:13:38 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id B6B0A21F99BA for <ietf@ietf.org>; Thu,  6 Jun 2013 10:13:38 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r56HDKXa022443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 6 Jun 2013 10:13:20 -0700 (PDT)
Message-ID: <51B0C328.3060105@isi.edu>
Date: Thu, 06 Jun 2013 10:13:12 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Hugh Daniel has passed away
References: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca> <0ld2rzs58i.fsf@wjh.hardakers.net>
In-Reply-To: <0ld2rzs58i.fsf@wjh.hardakers.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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: Thu, 06 Jun 2013 17:13:44 -0000

Paul Wouters <paul@cypherpunks.ca> writes:
>
> Hugh Daniel passed away on June 3rd after what appears to have been a
> heart attack.

I met Hugh many years ago when we were working on our overlay system, 
and had problems integrating it with FreeS/WAN's IPsec implementation.

And yes, I too remember the LED lights. He correlated wavelength with 
"clue" - the shorter the wavelength, the higher you stood in his view, 
AFAIR.

--

He visited my office about 12 years ago - unannounced, as was more 
typical than not. After talking at length, he invited me to dinner with 
a group of his friends in a nearby town. I mentioned that I was 
'closing' on a house in that same town, and would show him after dinner.

He rolled up just under a large tree and parked on the street. I asked 
him why he picked that location, and he said it was because his friend 
was three lots up the street, and this was the closest vacant spot.

He had parked directly at my new house.

Through him I met a very interesting sci-fi writer, Renfair frequenter, 
and food historian that evening, among others, at a restaurant I walk 
past nearly every day.

His contributions to my six degrees was sincerely appreciated and will 
be missed.

Joe

From adrian@olddog.co.uk  Thu Jun  6 10:30:13 2013
Return-Path: <adrian@olddog.co.uk>
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 07F6C21F9A82; Thu,  6 Jun 2013 10:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, HTML_MESSAGE=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 MM4cxe66nocg; Thu,  6 Jun 2013 10:30:07 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC7421F9A81; Thu,  6 Jun 2013 10:30:06 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r56HU3CB013690;  Thu, 6 Jun 2013 18:30:03 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r56HU2WE013678 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Jun 2013 18:30:02 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'ietf'" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
Date: Thu, 6 Jun 2013 18:29:57 +0100
Message-ID: <09b601ce62db$77adc5c0$67095140$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_09B7_01CE62E3.D9769A90"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5i22UgBxQKv2PhTiW4S3Ku8O2C3Q==
Content-Language: en-gb
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Thu, 06 Jun 2013 17:30:13 -0000

This is a multipart message in MIME format.

------=_NextPart_000_09B7_01CE62E3.D9769A90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,
 
It falls to me to make a call on this issue before the document moves on.
 
Abdussalam has complained that he has not been acknowledged and has objected to
the current text in section 8.
The authors have responded on the MANET list
 
> We believe that only comments that lead to significant improvements of
> the draft deserve a listing in the acknowledgment section, and we have
> therefore not modified the section.
 
I have reviewed the email threads on the MANET mailing list and do not consider
that Abdussalam made contributions to the text of the document. I also believe
that the comments he made did not advance the content of the document.
Furthermore, per multiple references (such as RFC 2026) the Acknowledgements
section is used to "properly acknowledge major contributors." Normal IETF
business is to discuss not seek acknowledgement.
 
I do not propose to do an explicit consensus call on whether Abdussalam should
be named in this draft. 
 
The authors have posted a revised I-D handling other IETF last call issues, and
I will advance that to IESG evaluation.
 
Thanks,
Adrian
 
From: Abdussalam Baryun [mailto:abdussalambaryun@gmail.com] 
Sent: 03 June 2013 17:10
To: ietf
Cc: adrian@olddog.co.uk; iesg@ietf.org
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt>
(Security Threats for NHDP) to Informational RFC
 
I would hope that IETF add my name in the acknowledgement section of the I-D. I
complained to AD about that my efforts in WGLC was not acknowledged by editors
even after my request, however, I did not stop reviewing (trying not be
discouraged) which I will complete on 6 June with the final comments. Therefore,
this message (can be added as a comment on the I-D) is an objection to section 8
that ignores acknowledge input/review effort related to the I-D.
 
AB
 
On Mon, Jun 3, 2013 at 6:35 AM, Ulrich Herberg <ulrich@herberg.name> wrote:
Hi Adrian,
 
I personally agree that adding an informational ref to
draft-ietf-manet-nhdp-olsrv2-sec is a good idea. I will discuss with my
co-authors.
 
Thanks
Ulrich
 

On Sunday, June 2, 2013, Adrian Farrel wrote:
Hi Abdussalam,

I think it is a reasonable suggestion for this I-D to make a forward reference
to draft-ietf-manet-nhdp-olsrv2-sec
Although this work is clearly scoped to NHDP (RFC 6130) as currently specified,
it is worth an informational reference to note that there is work in progress
that seeks to update NHDP to counter a number of security threats described in
this document.

I do not think, however, that this I-D should attempt to describe the situation
with NHDP after the inclusion of protocol work that has not yet been completed.
Contrary to your suggestion, I think this I-D motivates updates to 6130 and it
would be wrong to review this document in the context of changes being made to
address this document.

Thanks,
Adrian

> I think if we got an effort in IETF to update NHDP [RFC6130] as draft
> [1] does, why this reviewed I-D of threats does not include [1] in its
> references to be reviewed before reviewing this NHDP-threat I-D? I
> suggest to include draft [1] in References section, IMHO, any updates
> to RFC6130 should be considered by the community while reviewing this
> I-D.
>
> [1] draft-ietf-manet-nhdp-olsrv2-sec-02
 

------=_NextPart_000_09B7_01CE62E3.D9769A90
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CE62E3.CA430090"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.hoenzb
	{mso-style-name:hoenzb;
	mso-style-unhide:no;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Hi,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>It falls to me to make a call =
on this issue before the document moves on.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Abdussalam has complained that =
he has not been acknowledged and has objected to the current text in =
section 8.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>The authors have responded on =
the MANET list<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>&gt; We believe that only =
comments that lead to significant improvements =
of<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>&gt; the draft deserve a =
listing in the acknowledgment section, and we =
have<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>&gt; therefore not modified =
the section.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>I have reviewed the email =
threads on the MANET mailing list and do not consider that Abdussalam =
made contributions to the text of the document. I also believe that the =
comments he made did not advance the content of the document. =
Furthermore, per multiple references (such as RFC 2026) the =
Acknowledgements section is used to &quot;properly acknowledge major =
contributors.&quot; Normal IETF business is to discuss not seek =
acknowledgement.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>I do not propose to do an =
explicit consensus call on whether Abdussalam should be named in this =
draft. <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>The authors have posted a =
revised I-D handling other IETF last call issues, and I will advance =
that to IESG evaluation.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> Abdussalam Baryun =
[mailto:abdussalambaryun@gmail.com] <br><b>Sent:</b> 03 June 2013 =
17:10<br><b>To:</b> ietf<br><b>Cc:</b> adrian@olddog.co.uk; =
iesg@ietf.org<br><b>Subject:</b> Re: [manet] Last Call: =
&lt;draft-ietf-manet-nhdp-sec-threats-03.txt&gt; (Security Threats for =
NHDP) to Informational RFC<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>I =
would hope that IETF add my name in the acknowledgement section of the =
I-D. I complained to AD about that my efforts in WGLC was not =
acknowledged by editors even after&nbsp;my request, however, I did not =
stop reviewing (trying not be discouraged) which I&nbsp;will complete on =
6 June with the final comments. Therefore, this message (can be added as =
a comment on the I-D)&nbsp;is an objection to&nbsp;section 8 that =
ignores acknowledge&nbsp;input/review effort related to the =
I-D.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>AB<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Mon, Jun 3, 2013 at 6:35 AM, Ulrich Herberg &lt;<a =
href=3D"mailto:ulrich@herberg.name" =
target=3D"_blank">ulrich@herberg.name</a>&gt; wrote:<o:p></o:p></p><p =
class=3DMsoNormal>Hi Adrian,<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>I =
personally agree that adding an informational ref to =
draft-ietf-manet-nhdp-olsrv2-sec is a good idea. I will discuss with my =
co-authors.<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Thanks<o:p></o:p></p></div><div><p =
class=3DMsoNormal><span class=3Dhoenzb><span =
style=3D'color:#888888'>Ulrich</span></span><o:p></o:p></p><div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><br>On =
Sunday, June 2, 2013, Adrian Farrel wrote:<o:p></o:p></p><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Hi Abdussalam,<br><br>I =
think it is a reasonable suggestion for this I-D to make a forward =
reference<br>to draft-ietf-manet-nhdp-olsrv2-sec<br>Although this work =
is clearly scoped to NHDP (RFC 6130) as currently specified,<br>it is =
worth an informational reference to note that there is work in =
progress<br>that seeks to update NHDP to counter a number of security =
threats described in<br>this document.<br><br>I do not think, however, =
that this I-D should attempt to describe the situation<br>with NHDP =
after the inclusion of protocol work that has not yet been =
completed.<br>Contrary to your suggestion, I think this I-D motivates =
updates to 6130 and it<br>would be wrong to review this document in the =
context of changes being made to<br>address this =
document.<br><br>Thanks,<br>Adrian<br><br>&gt; I think if we got an =
effort in IETF to update NHDP [RFC6130] as draft<br>&gt; [1] does, why =
this reviewed I-D of threats does not include [1] in its<br>&gt; =
references to be reviewed before reviewing this NHDP-threat I-D? =
I<br>&gt; suggest to include draft [1] in References section, IMHO, any =
updates<br>&gt; to RFC6130 should be considered by the community while =
reviewing this<br>&gt; I-D.<br>&gt;<br>&gt; [1] =
draft-ietf-manet-nhdp-olsrv2-sec-02<o:p></o:p></p></div></div></div></div=
></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div></body></h=
tml>
------=_NextPart_000_09B7_01CE62E3.D9769A90--


From sm@resistor.net  Thu Jun  6 10:57:33 2013
Return-Path: <sm@resistor.net>
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 3326321E8085; Thu,  6 Jun 2013 10:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 iO-riY6FP27j; Thu,  6 Jun 2013 10:57:31 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB5721F8470; Thu,  6 Jun 2013 10:57:12 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r56Hv6pg023711; Thu, 6 Jun 2013 10:57:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1370541431; bh=ILRqLAiUVGR+7ADiIF9JfiW9QDX9lue0um4xkBn0xic=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=DLdpWOEuYFE9uw3TIqQv7Eorn68UNtQlTLwttYxx8fjpFBCjL91FYhYas6L+qYn7o xRurV8PYm/SXur67VtLP38o9ZqlqlokbOUEcX4M/LoMCyvkSt33zy7UfX8VvZL5gkC pRb01Ba+ouvGPtgujIdH06/IVO/KleYKb7UkaMhM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1370541431; i=@resistor.net; bh=ILRqLAiUVGR+7ADiIF9JfiW9QDX9lue0um4xkBn0xic=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=W0A9PYBXsE0zixXH5fR7brPoG/XmhL1V66+ZDZd5ljQnTmbEW1rtaP6jF6eULPUlI G4xmgnfNfGRlE3w4m1oaU8qiYV1aakCIHjeW9Bc9PqAYozb1+ihsdLT5rUjmdcO4pj DRAuin1HDrTEyrKhFQn0MexJx0FSrvYDhsINFNjc=
Message-Id: <6.2.5.6.2.20130606082015.08aa2150@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 06 Jun 2013 10:09:10 -0700
To: iab@iab.org
From: SM <sm@resistor.net>
Subject: RE: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE	802 / IETF Relationship"
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EA0@EXMB01CMS.surre y.ac.uk>
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org> <6.2.5.6.2.20130605173623.0d4a9790@resistor.net> <290E20B455C66743BE178C5C84F12408223F494EA0@EXMB01CMS.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Thu, 06 Jun 2013 17:57:33 -0000

At 20:01 05-06-2013, l.wood@surrey.ac.uk wrote:
>RFC2031 documented the takeover. Snuck through on informational...

It's part of the poorly documented historical facts which happened 
after some IETF financial woes.

I read draft-iab-rfc4441rev-04 again.  Section 1 mentions that:

   "This version of the document responds to comments received during IAB
    Last Call."

I would have expected the IAB to catch issues which are related to the IETF.

Section 3.1.4 lists "Balance between mailing lists and meetings" as a 
cultural difference.  The last sentence in the paragraph:

   "Attendance at meetings is critical to influencing decisions
    and to maintaining membership voting rights."

sums up a major difference.  It could be said that a standard setting 
organization is dominated by interest groups (see RFC 6852) which can 
afford the air travel if major decisions are made during a plenary or 
interim meetings.

In Section 3.3.1.4:

   "However, since IEEE 802 work-in-progress is copyrighted, incorporating
    material into IETF documents or posting"

The above does not describe correctly why it is not possible to 
incorporate the material.  It could mention that due to copyright 
restrictions, incorporating materials into IETF documents or postings 
is not allowed.

In Section 3.3.1.5:

   "IEEE 802 standards, once approved, are published and made available
    for sale."

This could be a cultural difference.  RFC 6852 glosses over that (see 
"Standards specifications are made accessible to all for 
implementation and deployment.")

BTW, the draft could be made shorter by incorporating the relevant 
topics by reference instead of describing them in the draft.  RFC 
6756 has a better layout in my opinion.  RFC 4441 describes the 
policies and procedures that have developed in order to coordinate 
between the IETF and IEEE 802.  draft-iab-rfc4441rev-04 mentions that 
it describes the standardization collaboration between the IETF and 
IEEE 802.  The result looks like a "Taoesque" mix of IETF and IEEE 
802 material.

   Why is it important to explain the IAB responsibilities?

   Why is it important to explain IESG and IAB member appointments?

   What does cross-referencing documents have to do with the relationship?

I suggest looking at the draft while taking the above 
(non-exhaustive) list of questions into consideration.  The details 
of the collaboration, e.g. how to get a password, can be documented 
through a Wiki.  The IEEE does a decent job of documenting its 
standards document lifecycle; it's less convoluted than the 
IETF.  The relevant URL is not mentioned in the draft.  The draft 
lists analogies between the IETF and IEEE 802 whereas the reality is 
that the two organizations operate differently.  The details of that 
is written as politically appropriate version of reality.

Regards,
-sm 


From peter@akayla.com  Thu Jun  6 11:09:35 2013
Return-Path: <peter@akayla.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 7EB5D11E80EC for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 11:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 sKs2WZfdkI+h for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 11:09:30 -0700 (PDT)
Received: from p3plsmtpa07-03.prod.phx3.secureserver.net (p3plsmtpa07-03.prod.phx3.secureserver.net [173.201.192.232]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF4111E80D5 for <ietf@ietf.org>; Thu,  6 Jun 2013 11:09:30 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-03.prod.phx3.secureserver.net with  id l69U1l0081huGat0169Uj4; Thu, 06 Jun 2013 11:09:29 -0700
From: "Peter Yee" <peter@akayla.com>
To: "'SM'" <sm@resistor.net>, <iab@iab.org>
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>	<6.2.5.6.2.20130605173623.0d4a9790@resistor.net>	<290E20B455C66743BE178C5C84F12408223F494EA0@EXMB01CMS.surrey.ac.uk> <6.2.5.6.2.20130606082015.08aa2150@resistor.net>
In-Reply-To: <6.2.5.6.2.20130606082015.08aa2150@resistor.net>
Subject: RE: Call for Review of draft-iab-rfc4441rev-04.txt, "The	IEEE	802 / IETF Relationship"
Date: Thu, 6 Jun 2013 11:09:45 -0700
Message-ID: <009801ce62e1$07391c30$15ab5490$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGUqyFYe+EEfht0u/twcB9M9pCvEAIIJuNOAiaEDgACSrNT/plonzTA
Content-Language: en-us
Cc: 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: Thu, 06 Jun 2013 18:09:35 -0000

>In Section 3.3.1.5:
>
>   "IEEE 802 standards, once approved, are published and made available
>    for sale."
>
>This could be a cultural difference.  RFC 6852 glosses over that (see
"Standards specifications are made accessible to all for implementation and
deployment.")

IEEE 802 standards are made more-or-less freely available (you have to agree
to terms of use online) after a period of 6 months from publication.
Details are here: http://standards.ieee.org/about/get/.

		-Peter




From spencerdawkins.ietf@gmail.com  Thu Jun  6 11:30:10 2013
Return-Path: <spencerdawkins.ietf@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 7718421F88FB for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 11:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.216
X-Spam-Level: 
X-Spam-Status: No, score=-2.216 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599]
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 hvPq-uJcnnP7 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 11:30:10 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 92FA821F89EB for <ietf@ietf.org>; Thu,  6 Jun 2013 11:30:09 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id 16so5211974obc.26 for <ietf@ietf.org>; Thu, 06 Jun 2013 11:30:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ely+jy9sH7Lmx2eNBNRop1B+z6EuIANPmTj7IqtXoEg=; b=piIWqtF/sIkeeOPSq0QfTj03yHot58LlhJUdpYuY4qrqs7JCevQSGDF+8e9A47mLbQ pW0QK/ICLMVPPvuaPQx5xk8UGqpTQYBDULVPBgQZuLWAQ7XRhlJSPa53IAHAoo21HuKJ mk4d4f0LJG/ZNgpYxJGduy9AMBfv0rxH6mIXUF5pdslHNNLvAPO6j6bo83nOaujkAvXt VbuxHXs2v8amRsDkZpw5Js3v57uuOkOYbzPh52oziivYCanWZWhJ7nU39L3m6NNlV4l/ NBmn1bjbIGVtCo4wcbjN6EX8/CTHZZ6AE9MRQMsRlKhspvkCRlQ16jrmO91IF4Xr3XwW C3mQ==
X-Received: by 10.182.80.5 with SMTP id n5mr18865546obx.88.1370543409053; Thu, 06 Jun 2013 11:30:09 -0700 (PDT)
Received: from [192.168.1.77] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net. [99.108.174.213]) by mx.google.com with ESMTPSA id wz1sm45843676obc.3.2013.06.06.11.30.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Jun 2013 11:30:07 -0700 (PDT)
Message-ID: <51B0D4FB.4090702@gmail.com>
Date: Thu, 06 Jun 2013 13:29:15 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 / IETF Relationship"
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org> <51B08AD0.2070908@cs.tcd.ie>
In-Reply-To: <51B08AD0.2070908@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IAB Chair <iab-chair@iab.org>, IAB <iab@iab.org>, IETF <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: Thu, 06 Jun 2013 18:30:10 -0000

On 6/6/2013 8:12 AM, Stephen Farrell wrote:
> -  3.3.1.4 says: Since it is
>     possible to participate in IETF without attending meetings, or even
>     joining a mailing list, IETF WG chairs will provide the information
>     to anyone who requests it.  However, since IEEE 802 work-in-progress
>     is copyrighted, incorporating material into IETF documents or posting
>     the username/password on mailing lists or websites is not permitted.
>
> That's a pretty bogus setup. I would think that if IEEE do want to
> share some or all drafts with us they could much more easily create
> a web page when those drafts are available without access control.
> Or we could if they didn't mind. (Or I could do it if there's no "we"
> that wants to:-) Asking IETF WG chairs to deal with passwords is a
> bit silly. I'm not objecting to this, but am suggesting someone ask
> IEEE if they'd like to consider the silliness here and fix it.

Hi, Stephen,

It's probably worth pointing out to the community that both IETF and 
IEEE 802 leadership have been looking at previous revisions and asking 
"if they do that, should we do the same?"

The most recent case I can think of was that IETF published a list of 
its liaison managers, while IEEE 802 did not - but review discussions 
prompted iEEE 802 to start publishing a list of its liaison managers as 
well. There have been others.

I'd be pleasantly surprised if either organization has run out of 
bogosity to fix, of course ;-)

Spencer

From david.black@emc.com  Wed Jun  5 15:14:04 2013
Return-Path: <david.black@emc.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 6E19B21F9651; Wed,  5 Jun 2013 15:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 WwFJsEJoAZ2l; Wed,  5 Jun 2013 15:13:59 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2D421F9649; Wed,  5 Jun 2013 15:13:59 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r55MDRjB001272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jun 2013 18:13:30 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Wed, 5 Jun 2013 18:13:08 -0400
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.222.70.203]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r55MD7QM029499; Wed, 5 Jun 2013 18:13:07 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub06.corp.emc.com ([128.222.70.203]) with mapi; Wed, 5 Jun 2013 18:13:06 -0400
From: "Black, David" <david.black@emc.com>
To: "d3e3e3@gmail.com" <d3e3e3@gmail.com>, "joe.abley@icann.org" <joe.abley@icann.org>, General Area Review Team <gen-art@ietf.org>
Date: Wed, 5 Jun 2013 18:13:06 -0400
Subject: Gen-ART review of draft-eastlake-rfc5342bis-02
Thread-Topic: Gen-ART review of draft-eastlake-rfc5342bis-02
Thread-Index: Ac5iOdqxPgeHIMhASdCnl829MYVBxw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 06 Jun 2013 11:32:59 -0700
Cc: "Black, David" <david.black@emc.com>, "ietf@ietf.org" <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, 05 Jun 2013 22:14:04 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-eastlake-rfc5342bis-02
Reviewer: David L. Black
Review Date: June 5, 2013
IETF LC End Date: June 4, 2013

Summary:
This draft is on the right track but has open issues, described in the revi=
ew.

This draft updates the IANA registered Ethernet parameters for IETF use,
including recording values assigned for documentation.  It also makes some
minor changes to IANA procedures.

IANA should review this entire draft, not just its IANA Considerations sect=
ion;
Pearl Liang appears to have done that comprehensive review for IANA.

Major issues: None

Minor issues: One, the IANA review also found this issue.

Section 3.2 states:

	IANA will assign "00-00-0E-00-42" as the protocol number under the=09
	IANA OUI to be used for documentation purposes.

IANA has not made this assignment, but this assignment request is not
recorded in the IANA Considerations section where IANA actions are
requested and recorded by IANA after they have been performed.  This
assignment needs to be added to the IANA Considerations section;
see item 5 in the IANA review.

Nits/editorial comments:

Section 1: This document uses an "IESG Ratification" process for some
assignments.  This is not the same process as the "IESG Approval" process
defined in RFC 5226.  As those names could be confused by a casual reader
who is not strongly familiar with IANA processes, I suggest adding a
statement that the "IESG Ratification" process is defined in this document
and is not the same as the "IESG Approval" process in RFC 5226.  This could
be added after the sentence that cites RFC 5226.

Section 1.4: It would be helpful to point out that there is no OUI assigned
for documentation purposes, but there are identifiers based on the IANA OUI
that have been assigned for documentation purposes.

In general, the use of the acronym IAB for Individual Address Block is
unfortunate, but unavoidable, and this is clearly pointed out in the
definition of the IAB acronym in section 1.2.  Nothing can or should be
done about this.

idnits 2.12.17 did not find any nits.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From elwynd@folly.org.uk  Wed Jun  5 17:12:18 2013
Return-Path: <elwynd@folly.org.uk>
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 033E211E80D1; Wed,  5 Jun 2013 17:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[AWL=-0.900, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6]
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 B1POAFCwdXkF; Wed,  5 Jun 2013 17:12:13 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 2FB4521F9690; Wed,  5 Jun 2013 17:12:13 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1UkNo5-0004Jw-Vf; Thu, 06 Jun 2013 01:11:59 +0100
Subject: Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
From: Elwyn Davies <elwynd@folly.org.uk>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Organization: Folly Consulting
Date: Thu, 06 Jun 2013 01:11:53 +0100
Message-Id: <1370477514.4596.9052.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-ACL-Warn: Blacklisted URL in message. (ietf.org) in. See http://lookup.uribl.com.
X-Mailman-Approved-At: Thu, 06 Jun 2013 11:32:59 -0700
Cc: draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, IETF discussion <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: Thu, 06 Jun 2013 00:12:18 -0000

I am an additional Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-mmusic-rfc2326bis
Reviewer: Elwyn Davies
Review Date: 5 June 2013
IETF LC End Date: 5 JUne 2013
IESG Telechat date: (if known) -

Summary:
Almost ready.  Generally this is an excellent and well written document,
particularly given its size.  There are a few minor issues to sort out
mainly at the nit level and some consistency issues to fix up.  The two
issues that I have brought out below are really at what the IESG would
call 'DISCUSS-DISCUSS' level.  The issue of URI scheme redefinition may
well have already been cleared by the URI expert - the draft does not do
itself any favours here by failing to explain what the syntax changes
are in s4.2; this raises immediate red flags that only start to fade a
couple of hundred pages later. The rudimentary nature of the pipeline
mechanism is carried over from RTSP 1.0.  I'd like to be sure that this
has been properly discussed in the WG as it looks pretty flaky to an
outsider.  There are several inconsistencies between various lists of
headers that need sorting out and there is no definition of
Proxy-Authorization in the ABNF.

There are also a fairly large number of editorial nits but these are all
localized and trivial to fix.  Finally I have't had time to review the
appendices (maybe there will be a follow up).

Robert Sparks is the main gen-art reviewer for the document; he asked
for additional eyes on the document given the size and his RAI
background.  Having (just) seen his review, I think we have both picked
up on the URI scheme and pipeline issues.  I am not sure that I concur
with his view that there is significant normative material in the
appendices - AFAICS the main protocol definition *is* in the main body
of the document and the bits especiially in Appendices B and C are not
the core of the protocol.  However this is based on a very cursory
glance through something like 75 pages of the document.  However, I do
concur with Robert's view that it needs a security expert to check the
security stories.

Major(ish) issues:
s4.2: This section (re-)defines the URI schemes "rtsp" and "rtsps". The 
last sentence of para 1 states that the 'details of the syntax' of the 
URIs 'have been changed'.  Is this a reasonable thing to do? Has this 
been cleared with the URI expert reviewer?  I am not entirely clear what 
the change involves and the draft doesn't explain exactly how the syntax 
has been altered  and its consequences (if any) in s4.2.  Some details
are finally given in s22.14.


Minor issues:
s11, para 3: I guess that the WG decided that sticking with the RTSP 1.0
model of sending requests and worrying about success of prior prior
pipelined requests was the right answer.  I would have thought that it
might have been helpful to provide qualifiers on the Pipelined-Requests
header that allowed subsequent requests to be suppressed unless the
previous command resulted in one of a given set of status codes with a
'reset' option to 'restart' the pipeline.  It strikes me that this would
avoid some irritating need to work out how to recover from arbitrary
failures in a command chain in a client.

Nits/editorial comments:

General: s/i.e./i.e.,/; s/e.g./e.g.,/

General:  Consistent usage of octet vs. byte (octet preferred).

General: Consistent use of '(session) keep alive' vs. '(session) keep-alive'

General: Consistent use of Base64 vs BASE64.

s1, para 2, last sentence: s/delivered as a time-synchronized 
streams/delivered as time-synchronized streams/

s1. last para: s/used terms/terms used/

s1, last para: Need to expand SDP acronym.

s2, para 1: s/considered use cases/use cases considered/

s2.1, para 1: s/completely out of bands/completely out of band/

s2.1, next to last para: It would be useful to  provide a pointer to 
where the  two URI schemes are defined (s4.2?) so it is clear these are 
internally defined and one needn't go looking for another doc.

s2.2, para 5: s/uses client-selected identifier/uses a client-selected 
identifier/

s2.2, para 5: For  consistency there should be a reference for s18.32 
with Pipelined-Requests.

s2.2, last para: For  consistency there should be a reference for s18.29 
with Media-Range.

s2.3, para 1: Expand SMPTE acronym.

s2.3, para 3: Reference s13.5 for PLAY_NOTIFY

s2.3, para 5:
> The server should also regularly send every 5
>     minutes the current media range in a PLAY_NOTIFY request.
Shouldn't this be configurable?

s2.3, last para:
> If the client waits too long
>     before resuming the pause point, the content may no longer be
>     available.  In this case the pause point will be adjusted to the end
>     of the available media.
I know this is a subjective choice, but I would have thought adjusting 
to the beginning of the available media would be what the user expects.
Later: Having read s13.4.1, I think this conflicts with (or is unclear) 
compared with s13.4.1, para 2 which states that the pause point will be
the oldest retained time - that is what I would have expected.

s2.4, para 1: For  consistency there should be a references for 
s22.11/s22.9 with RTP-Info and Range.

s2.4, para 2: s/that can be used/can be used/

s2.5.1, paras 2/3:  Should have references to ss18.48/18.44 for Scale/Speed.

s2.5.1, para 6:
OLD:
These media manipulation and when they are needed are highly media-type 
dependent.
NEW:
The nature of these media manipulations and when they are needed is 
highly media-type dependent.
--or--
The nature of this media manipulation and when it is needed is highly 
media-type dependent.

s2.5.1, para 9: s/and the currently used scale factor
    exist./and the scale factor currently in use, exists./
OLD:
    a mechanism for
    updating the media properties and the currently used scale factor
    exist.
NEW:
    a mechanism exists for
    updating the media properties and the scale factor currently in use.

s2.6, bullet 1: Need to expand RTCP acronym (RTP is 'well-known' but not 
so RTCP apparently).

s2.6, para 5: Reference s13.7 for TEARDOWN.

s2.6, para 7: s/10*times/ten times/

s2.6, last para: Reference s13.10 for REDIRECT

s2.6, last para: Reference s22.10 for Terminate-Reason

s2.7, para 2: Reference s18.41 for Require

s2.7, para 2: The reference for s18.35 for Proxy-Require should be moved 
from bullet 2.

s2.7, para 3: s/in order of the magnitude/in increasing order of the 
magnitude/

s2.7, bullet 3: s/standard/standards/

s3.1, para 3:  Clearly there won't be any smaller type paras in the 
ASCII version.. is there a PDF version that actually has smaller type?  
The one I get from the repository doesn't seem to have any smaller type 
paras.

s4.2, para 2, last sentence:
OLD:
This way RTSP 2.0 URIs for request
    can be produced from an RTSP IRI.
NEW:
This allows a URI that matches the RTSP 2.0 specification, and so is 
suitable for use in a request, to be created from an RTSP IRI.

s4.4: An external reference to the relevant Society of Motion Picture 
and Television Engineers standard (probably SMPTE 12M) ought to be 
included to define things like "SMPTE 30 drop".  [Aside: 29.97 frames 
per second?? Must be something to do with Never Twice the Same Color.  
Oh, well,  a little research job for whan I am really bored.]

s4.5: The NTP reference is interesting but gratuitous.

s4.6:  It would be useful to add the "clock=19961108T143720.25Z-" form for 
consistency with s4.4 and s4.5 as well as the 'free-standing' absolute
time which is used in Media-Properties etc.

s4.8, para 1: A more precise reference for HTTP ETag would be helpful.

s4.9, para 1: s/the below listed media properties/the media properties 
listed below/

s4.9.1: There seems to be some confusion in this section between the
values from the Seek-Style header and the values from the
Media-Properties random access property.  The section says the values
are from Seek-Style but they are actually from the random access
property.  Presumably there was some intention to interelate the media
capabilities and the play event policies?  Further this section has
Random Access, Conditional Random Access, Return to Start and No
Seeking.  This doesn't match exactly with either Seek-Style (RAP, CoRAP,
First-Prior and Next) or Media-Properties (Random-Access, Beginning-Only
and No-Seeking).

s4.9.2, "Time Limited": s/before given wallclock time/before the given 
wallclock time/

s4.9.3, para 1: s/during time/over time/

s4.9.x: It would be desirable to use the parameter names in the same 
form as they appear in s18 (e.g., Random-Access instead of Random 
Access, No-Seeking instead of No seeking) both in the definitions 
(s4.9.1 - s4.9.4) and the mapping (s4.9.5).


ss4.4/4.5/4.6: If I read the ABNF in s20.2.1 correctly, the unqualified 
values "smpte", "npt" and "clock" are valid  in the Range parameter.  
What is the meaning of such an unqualified value?

s5:  It would be sensible to note that the ABNF fragments in s5 and the 
following sections match with the full syntax productions in s20.

Table 3:  Proxy-Authorization (Section 18.34) doesn't appear in any of 
the various header categorization tables [I must have better things to 
do than checking they were all there :-( ].  I think it belongs here.

s5.3: For consistency with s9.2, this section should also say that a 
message with a body MUST contain a Content-Type header also.

s5.3, para 1:
> An example of a message body is the Session Description
>     Protocol (SDP).
Er, perhaps not the *whole* protocol?  Maybe an SDP message??

s7.2, para 1 and Table 3:  Perhaps the headers that can also be in 
Response messages could be marked?  I believe these are Range, Scale, 
Session, Supported and Transport.

s8.1.1: Should clarify that a separate registry is being defined so the
story about importing HTTP codes doesn't have any impact on the HTTP
registry.  I initially read this as if it did.

s8.1.1, para 5:  Is there some deep reason for labelling this 3rr rather 
than 3xx? (and throughout the document).  Sort of understandable but a 
bit odd.

s8.1.1, code 505:  HTTP code 505 is explicitly '*HTTP* version not 
supported' - should there really be a separate code for 'RTSP version 
not supported'?

s8.1.1, code 551: s/Support/Supported/

Table 5: Alphabetic sort on Server and Session is incorrect.

s8.2, last para: s/recognize them to be response-header/recognize them 
to be a response-header/

s9, para 1:  Should the cross-reference be to s5.3 (message body) rather 
than 5.2?

s9: Is it deliberately left vague as to whether other message types 
might have message bodies?

s10.2, para 6 and following note:  I can't see that the note following 
para 6 can be justified: since the restriction on multiple connections 
from a client to a server is only a SHOULD, an interoperable server MUST 
be capable of handling multiple connections from a client unless the 
server can explicitly send back a TOO MANY CONNECTIONS status.

s10.2, para 10: s/due to the response is caught in the queue behind a 
number of request that/due to the response being caught in the queue 
behind a number of requests that/

s10.3, para 4, "on the flip side":  Slang.  Maybe "Contrariwise" or 
something less archaic.

s10.4, para 4: Expand RTT acronym (its apparently not well-known).

s10.5, para 1: s/ To show liveness between RTSP request issued/ To show 
liveness between RTSP requests being issued/

s10.5, RTCP para: s/it MUST also work as keep alive/it will necessarily 
also function as a keep alive/; s/statistical guarantees to reach the 
server/statistical guarantees of reaching the server/

s10.5, RTCP para:
OLD:
         That client has, for a network with 5
         % packet loss, the probability to fail showing liveness sign in
         that session within the timeout interval of 2.4*E-16.  Sessions
         with shorter timeouts, or much higher packet loss, or small
         RTCP bandwidths SHOULD also use any of the mechanisms below.
NEW:
         That client has, for a network with 5% 
         packet loss, a probability of failing to confirm liveness 
         within the timeout interval for that session  of 2.4*E-16.  
         Sessions with shorter timeouts, or much higher packet loss, 
         or small RTCP bandwidths SHOULD also implement one or more 
         of the mechanisms below.

s10.5, RTCP para: expand SSRC acronym.

s10.5, SET PARAMETER para: s/keep-alive/keep alive/

s10.5, last para: Should clarify that the 'timeout parameter' is a 
qualifier on the Session parameter - 'timeout parameter' appeared to 
indicate that it was a separate protocol parameter and sent me searching.

s10.6: RFC 3986 has capability for dealing with IP versions beyond 6... 
should these be carried over into RTSP?  The IANA registry says they are.

s10.7, para 3: s/and in dependency of its current load situation/and 
bearing in mind its current load situation/; s/to  increase the length 
proportional with the load of the server/to increase the timeout period 
in proportion to the current load on the server/

s10.7, para 3: Anti-synchronization measures such as are RECOMMENDED 
here are usually MANDATORY. (Also applies to wait timer in last para of 
this section).

s10.7, para 4: s/Another issue are load balancing RTSP proxies/A more 
complex case may arise when a load balancing RTSP proxy is in use/

s10.7, last para: Should the doubling of the wait timer have an upper limit?

s11, para 4: s/Feature-Tag/Feature-tag/

s11, para 4: According to s22.1.3, play.basic, play.scale and play.speed
are 'defined' in this draft.  The nearest thing to a definition of
play.basic that I can find is the last sentence of para 4 in this
section.  I am not convinced that I could produce an interoperable
implementation of a server with this feature-tag with the one sentence
'definition'.  References to where play.xxx are defined would be useful
(play.scale in s18.44, play.speed in s18.48).

s11, Supported (and Proxy-Supported) bullets: 
OLD:
         This results in the
         receiver is learning the requester's feature support.
NEW:
         This results in the
         receiver learning the requester's feature support 
         relevant to the specified resource.
[Note: I added 'specified resource' here and then thought about whether
this made any sense.  It probably needs to be clearer what set of
features are included in the Supported list for both requester and
responder.  Are they restricted to those relevant to the specified
resource that might of course be the whole server, proxy - or client?? -
in which case there isn't an issue, but it might be a specific
presentation - what happens then?  Affects s13.1, para 3 also.]

s11, Proxy-Supported bullet: To emphasise the 'intersection of features'
mechanism used for Proxy-Supported (s18.36), it might be good to 
s/a view of what functionality the proxy chain/a view of the common
functionality supported by all members of the proxy chain/

s12, para 2: Might be better with:
s/allow all requests to setup and initiate media delivery/allow all
requests involved in setting up and initiating media delivery/

s12, para 2, last sentence: s/with at least one RTT/by at least one RTT/

Table 7: The 'Server req' and 'Client req' columns are not described.

s13.1, para 1: s/a client request it to a server/a client can send the
request to a server/

s13.1, para 1:
OLD:
   The client, server or proxy MAY also
   implement the converse of their required capability, but still retain
   the prior mentioned about what is a "MUST implement".
NEW:
   In addition to this "MUST implement" functionality, clients, servers 
   and proxies MAY provide support both for sending OPTIONS requests and 
   generating responses to the requests. 

s13.1, para 3: s/Regardless of scope of the request/Regardless of the
scope of the request/

s13.1, para 4: s/ID/identity/

s13.1, last para: s/fictional/fictitious/

s13.2, example S->C: Is Mark Handley cool with using his name? Might be
better to use the traditional 'another' (A.N.Other).

s13.3, para 1:  It would be helpful to copy the list of (3) states from
Appendix B somewhere around here and mention that the protocol drives a
state machine.

s13.4.1, para 2:
> Upon receipt of the PLAY request, the server MUST position the normal
>    play time to the beginning of the range specified in the received
>    Range header 

Should this mention the caveat that (if I understood earlier statements
correctly) the server may not be able to deliver exactly on this MUST
and then sets it the nearest it can manage? This is borne out by the
example later in this section where the server sets the start point back
10ms (and says so), etc.  Seek-Style affects the interpreation of MUST!

s13.4.1, page 72:
OLD:
   i.e.
   being handled the same as the request was received in Ready state.
   In the case the range in Range header has an implicit start time
   (-endtime),
NEW:
   i.e.
   being handled in the same way as if as the request was received in Ready state.
   In the case that the range in Range header has an implicit start time
   ("-endtime"),

s13.4.3, para 2: s/will take action/will take effect/

s13.4.3, page 76: s/entering or leaving from fast forward or fast
rewind./entering or leaving fast forward or fast rewind mode./

s13.4.4/.5/.7/.8: In these sections the Media-Property random access
property is stated as being required to be Random-Access.  Is
Conditional Random Access a possible value for this property? The
confusion in s4.9.1 does not allow me to conclude that this shouldn't be
a value for the property (sorry for the double negative but this looks a
bit confused).

s13.5.1:  Apologies if this question is stupid - I am not a media stream
wxpert.  Suppose we have an aggregated stream with (say) a number of
recorded media items making up the aggregate.  The client sets it on to
play to the end.  What happens if not all the streams end at the same
time?  Do we get PLAY_NOTIFY End-of-Stream notifications for each
individual stream as it ends or just one when the complete aggregate
ends?

s13.5.2, para 2:
> that changes the basis for making
>    estimates on how the media range progress. 
I can't parse the last part of this and I am not sure what it should be.

s13.5.3, first sentence: 'change the rate' of what? media delivery
presumably.

s13.5.3, para 2: s/adjust the used Scale value/adjust the Scale value
used/

s13.5.3, para 2: s/where the change took effect/when the change took
effect/; s/ID/identity/

s13.6, para after 1st example:s/ resume from the pause/resumes from the
pause/

s13.7.1, para 3:
OLD:
   This may result in
   that a session returns to non-aggregated control, due to that it only
   contains a single media after the requests completion.
NEW:
   This may result in
   a session returning to non-aggregated control, because it only
   contains a single media after the request's completion.

s13.8, para after bullets: s/request parameters/requests parameters/; 
s/Due to this reason/For this reason/

s13.9, para 2: s/In the case a parameter/When a parameter/

s13.10, 3rd para after numbered bullets, page 93: s/"time" parameter are
included/"time" parameter is included/

s13.10, page 94, para next but 1 before example:
OLD:
   However, the
   usage of conditional SETUP using MTag identifiers are RECOMMENDED to
   verify the assumption.
NEW:
   However, the
   usage of conditional SETUP using MTag identifiers is RECOMMENDED as
   a means to verify the assumption.

s14, para 2: s/integer/unsigned integer/ (I assume)

s14: What happens if the upper layer PDU is longer than (2^16 - 1)?

s14, figure: Binary header should have a figure number and title.

s14, figure: 'Length number of bytes of binary data' is confusing.
Maybe 'Binary data (length as in Length field)'

s17.3:  Uses 3xx in the title and 3rr in the body. See previous comment
about 3rr.

s17.4.32: s/next hops/next hop's/ (I think).

s17.5.6: See previous comment about overloading the 505 error code.

s18, Table 8 caption: 
OLD:
Note: It is allowed for all error messages 4xx and 5xx to
                                have a body
NEW:
Note: All error messages for statuses 4xx and 5xx are allowed to
                                carry a body.

s18, para after Table 8: s/[HX.Y] to informational refer to Section
X.Y/[HX.Y] to reference Section X.Y/

s18.2, para 2: s/This as/This is because/

s18.2, para 2: Expand DER avronym.

s18.2, para 3: s/replacement algorithm exist./replacement algorithm
exists./

s18.5, para 1: s/formats it support to receive/formats are acceptable
when received/

s18.6 para 1: s/to strictly inform the recipient of valid methods/to
inform the receipient of the complete set of valid methods/

s18.6, para 2: s/Allow/Allow message-header/; s/is different than/is
different from/

s18.8, para 2: s/due to that/because the/; s/what is reasonable/what is
a reasonable/

s18.10, para 3: s/govern only/govern just/; s/Below is the
description/Below are the descriptions/

s18.10: The various descriptions talk about 'media stream'.  Presumably
this should include media streams and RTSP responses.

s18.10, no-cache para: 
OLD:
Note, there is no security function enforcing that the content can't be
cached.
NEW:
Note, there is no security function preventing the caching of content.

s18.10, private para:  Is there any way in RTSP for the cache to know
whether this is a private cache for the user that should cache this
content?
s18.10, last para:  I am not absolutely certain, but I think this para
is specific to the max-age cache type rather than being generic as
implied by the indentation. [If so use the <vspace blankLines=1/> trick
to provide a pseudo-paragraph break]

s18.11, para 5: s/therefore see/therefore sees/

s18.12, para 1: s/of any next hop that need to be approved/for any next
hop that needs to be approved

s18.12: Figure needs a number and a caption.

s18.14: Consider adding the 'identity' value explicitly to the ABNF.

s18.17, para 6: s/relative URI/relative URI(s)/

s18.10, last para: Should have a reference to RFC 1123 for the date format.

s18.28, para 1: s/properties take effect/properties taking effect/

s18.29, para 2: Are (or should there be) constraints on the ordering of
media ranges for a non-continuous media stream?  It would probably make
the client's job easier if they were in incresing order. 

s18.32, para 3: s/or request of any type/or requests of any type/

s18.32, para 4: s/to a session context exist/to a session context
exists/

s18.39, para 2: Strictly 'fragment' should be 'fragment identifier'.

s18.40, para 1: s/that takes time/that take time/; s/such a/such as/

s18.41, para 1: s/the Supported/the Supported message-header/

s18.41: It appears from a literal interpretation (the third sentence is
an unqualified MUST) that the responder has to respond with error code
551 and an (empty?) list of Unsupported features if it actually does
support all the features.  I suspect this is not what is wanted.

s18.43, para 2: s/result in that a client needs/result in a client
needing/; s/Also functionality as informing/Also functionality that
informs/

s18.43, para 3: s/also the Range header MUST be included/the Range
header MUST also be included/

s18.43, para 9: It might be wise to explicitly expand the NTP acronym
even though it is well-known - its a long distance since the doc told us
not to confuse NPT and NTP.

s18.45, para 4: Harummph! Political Correctness strikes again.  Every
protocol should (and probably does) have a CRAP policy. ;-)

s18.50, Session-Timeout para: s/is kept alive/has been kept alive/

s18.50, time para: s/will stop provide/will stop providing/ 

s18.52, 1st 'No dest_addr' para: s/send media to same address for
which/send media to the same address from which/

s18.52, 2nd dest_addr para: Expand DoS acronym. 

s18.52, 'unicast/multicast' para: s/transmission needs/transmission
need/

s18.52, bottom of page 168:
OLD:
         The host address part of the tuple MAY be empty, for example
         ":58044", in cases when only destination port is desired to be
         specified. 
NEW:
         The host address part of the tuple MAY be empty, for example
         ":58044", in cases when it is desired to specify only the
         destination port. 

s18.52, 2nd para of src_addr section on page 169:
      s/media streams data packets/media stream's data packets/ (I think
there is only one implied - could be "data streams'" if many). 

s18.52, 'setup' section:  There seems to be some inconsistency in the
spcification of the 'active/passive/actpass' values.  a) Is there some
reason for specifying them in square brackets? b) should they say
["active:"] or ["active":] - both formats are used?  The ABNF has the
plain words with no brackets or quotes.

18.52, 'connection' section, 1st line:
s/Clients use the setup parameter/Clients use the connection parameter/
(I assume).

s19.2, para 1: s/both on URI level and port level/both on the URI level
and the port level/

s19.3, para 2: s/the client and server also needs to be aware/the client
and server also need to be aware/

s19.3.1, 'Any' para: s/accept whatever certificate presented/accept
whatever certificate is presented/

s19.3.1, 'Proxy' para: s/;/:/

s20: Proxy-Authorization seems to be missing from the ABNF altogether.

s20.2.1, 'smpte-range' production:  The reference should be to Section
4.4 I think - there is no Section 3.4 and s4.4 talks about SMPTE.

The next four comments are inconsistencies that need sorting out:

s20.2.2: Accept-Ranges and RTP-Info are classified as general headers in
Table 1 but appears in response-header here.

s20.2.2: User-Agent is classified as a request header in Table 3 but
appears in general-header here.

s20.2.2: Server is classified as a response header in Table 5 but
appears in general-header here.

s20.2.2: Accept-Credentials is classified as a request header in Table 3
but appears in response-header here.

s20.2.2, response-header production: Alphabetic sort fails at
MTag/Location. :-(

s21, para 2: s/appendix/an appendix/; s/the media security/media
security/

s21.1, Abuse of Server Logs:  [H15.1.1] doesn't really give much advice
beyond what is said here already.  One could copy the one sentence of
'mind out for the lawyers' advice here and save the indirection.

s21.1, transfer of sensitive info: Is there an equivalent of the Referer
header in RTSP?  Not sure there is but it would be good to explain one
way or the other (either there isn't one so it's less of a problem or
this is the equivalent...)

s21.1, Attacks based on file names etc: The reference should be to
[H15.2].

s21.1, DNS Spoofing:  Presumably RTSP will interact significantly with
content delivery networks.  Some of these work by DNS 'spoofing' that
was in its infancy when RFC 2616 was published.  Are there any other
issues that come out of the greater prevalence of CDNs since 1999?

s21.1, Session Hijacking:  The last part of this is written so that it
appears to mandate authentication in all cases.  As far as I understand
it is up to the client to decide if it needs authentication etc and some
content will be offered on unsecured URIs.  I think this needs to be
clearer that authentication will mitigate the problem but whether it is
done is up to the client if the server doesn't care.

s21.1, Persistently suspicious behaviour:  There seems to be a mismatch
between the title (persistently..) and the first sentence (a single
instance).  Do we have examples of the sort of security risk which is
supposed to be met with a 403 response the first time?

s21.1, last para: s/will be present by following the specification as
written,/will be instantiated if the specification is implemented as
written,/; s/prevent session hijacking/minimize the risk of session
hijacking/; s/strongly improved/greatly improved/

s21.1, last sentence:
>    Some of the above threats are such that
>    the implementation of the RTSP functionality itself needs to consider
>    which policy and strategy it uses to mitigate them.
It strikes me that this is not very helpful to a prospective
implementer.  The point of this section is at least in part to provide
that policy and strategy.  I am not quite sure how to rewrite this (or
if indeed other people think it does need rewriting). 

s21.2, para 1: s/like RTP/such as RTP,/; s/that exist/exist/

s21.2, Media Confidentiality: s/Thus also the signaling protocol
must/Thus the signaling protocol must also/

s21.2, Media Integity amd Auth: s/will have interest to substitute/will
be interested in substituting/

s21.2, Scope of Multicast: s/it is needed to consider the scope that
delivery has./the scope of the delivery must be considered./

s21.2.1, para 1: s/ascertaining the attackers/ascertaining the
attacker's/

s21.2.1, para 1: 
> Security mechanisms
>    that are acceptable in an increased generality are:
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Does this mean 'in order of increasing generality'?

s21.2.1, 2nd bullet: s/that accept to be/that have consented to be/

s21.2.1, last para on p204: Expand ICE acronym. (NAT is well-known).
 
s21.2.1, first para on p205: s/username/a username/; Expand STUN acronym

s21.2.2, RTP/RTCP Extensions: s/and disrupt video/and disruption of
video/

s21.2.2, next to last para:
OLD:
it is clear that strong
   security mechanism to protect RTP is necessary to support. 
NEW:
it is clear that it is necessary that a strong security mechanism is
supported to protect RTP.

s21.2.2, last para: s/beyond the mandatory to implement/beyond those
mandatory to implement/

s22: Ought to have the standard note about replacing RFCXXXX with the
number of the document when approved...

s22, para 2: s/follow the below defined procedure/follow the procedure
defined below/

s22, para 3: s/some of the requirements level/some of the registration
policies/

s22.1.3: References back to the sections which define the play.xx
feature tags should be added.  As previously stated, I am not entirely
sure what the required features are to meet the play.basic requirements.
 
s22.2.1: s/Methods are described in Section Section/RTSP Methods are
described in Section/

s22.3:  The rules about allocating in the sections above x50 should be
explained here (see s8.1.1).  The  numbers below x50 in each section
should be marked as a special category of reserved so they are only
allocated to HTTP analogues.  Is an experimental/private segment in each
category desirable?   

s22.9: Being allowed to register new Range header formats will currently
be restricted to times specified by NPT, SMPTE or UTC because no
registry is defined for Accept-Ranges.  Is this what is intended?




From joelja@bogus.com  Thu Jun  6 11:47:53 2013
Return-Path: <joelja@bogus.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 369D021E80A4; Thu,  6 Jun 2013 11:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 fZK-AwdujRVJ; Thu,  6 Jun 2013 11:47:52 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8263821E808E; Thu,  6 Jun 2013 11:47:52 -0700 (PDT)
Received: from joels-MacBook-Air.local (187.sub-70-208-146.myvzw.com [70.208.146.187]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r56IlmBT041950 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 6 Jun 2013 18:47:50 GMT (envelope-from joelja@bogus.com)
Message-ID: <51B0BF6E.4090501@bogus.com>
Date: Thu, 06 Jun 2013 09:57:18 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-ospf-manet-single-hop-mdr-03.txt> (Use of OSPF-MDR in Single-Hop Broadcast Networks) to Experimental RFC
References: <20130605150955.25672.65454.idtracker@ietfa.amsl.com> <CADnDZ8-JoLv4drWwx1DmU9Bgeo1ts7_h=WtNUwripmTYB3EZ9w@mail.gmail.com>
In-Reply-To: <CADnDZ8-JoLv4drWwx1DmU9Bgeo1ts7_h=WtNUwripmTYB3EZ9w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 06 Jun 2013 18:47:51 +0000 (UTC)
Cc: "draft-ietf-ospf-manet-single-hop-mdr@tools.ietf.org" <draft-ietf-ospf-manet-single-hop-mdr@tools.ietf.org>, "iesg@ietf.org" <iesg@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: Thu, 06 Jun 2013 18:47:53 -0000

On 6/6/13 3:15 AM, Abdussalam Baryun wrote:
> I send my request to the editors including questions but no reply from
> them to me. The thread [1] raised some issues, which is not mentioned
> in the I-D. The message [2] was ignored not answered (this is last
> reminder). The message [3] proposes using RFC5444 into this I-D, or
> raise the question of why not using MANET packet format within MANET
> domains (I need an answer).
>
> [1] http://www.ietf.org/mail-archive/web/manet/current/msg15400.html
> [2] http://www.ietf.org/mail-archive/web/manet/current/msg15412.html
> [3] http://www.ietf.org/mail-archive/web/manet/current/msg15418.html
>
> The I-D SHOULD not go forward if it still ignores the IETF community questions.
This sounds like an appeal of the working group consensus, not a last 
call comment.

If you have concerns with the WGLC those are raised first with the 
chairs, then with responsible AD, and then with the IESG as a whole.

I would observe that consensus does not require universal agreement. If 
you're in the rough from the vantage point of others, it's worth 
considering whether political capital, goodwill and the forebearance of 
your peers are best expended on this point.
>
> Regards
> AB
>
> On 6/5/13, The IESG <iesg-secretary@ietf.org> wrote:
>> The IESG has received a request from the Open Shortest Path First IGP WG
>> (ospf) to consider the following document:
>> - 'Use of OSPF-MDR in Single-Hop Broadcast Networks'
>>    <draft-ietf-ospf-manet-single-hop-mdr-03.txt> as Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-06-19. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>> RFC 5614 (OSPF-MDR) extends OSPF to support mobile ad hoc networks
>> (MANETs) by specifying its operation on the new OSPF interface of type
>> MANET.  This document describes the use of OSPF-MDR in a single-hop
>> broadcast network, which is a special case of a MANET in which each
>> router is a (one-hop) neighbor of each other router.  Unlike an OSPF
>> broadcast interface, such an interface can have a different cost
>> associated with each neighbor.  The document includes configuration
>> recommendations and simplified mechanisms that can be used in single-hop
>> broadcast networks.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>>


From abdussalambaryun@gmail.com  Thu Jun  6 12:33:49 2013
Return-Path: <abdussalambaryun@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 F21DF11E80E4; Thu,  6 Jun 2013 12:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 1afD2e6+ljog; Thu,  6 Jun 2013 12:33:48 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id F1D8B11E80ED; Thu,  6 Jun 2013 12:33:43 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr13so1027560pbb.20 for <multiple recipients>; Thu, 06 Jun 2013 12:33:43 -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=o75jj2qgmR5cnBYSH/XebRYvWN5w7q/6AuGIBfswFKI=; b=lGH6dRpN7V/ugzhESuWwHeJh9La0Trd0+iurIf+FgiSYMwbnUG2v4QpAGFgxcmK1hi 5dI7V/0BfyHjpzCub0qwjWf+7lih+XjG890m1P2NiPYuxOJPAjsBqyLifIFFp8mGODji M2yj3YuxXqBG9zdnU/1L0TwPvUCgeiQWZkePhb1WMUjPQBo3gfzn+baoAjmh3abYcMyj qxQq0eulNKIbm2EWDc1mkehaSvsA5IrX/vR5MKVpOjo0Wn6BjLKuhkpBoxg8Ik5Dgw5S ZoiAYwS5ytEAQx0wtD6+NOpUOu5hHvKvUwPpeh0G867ZQ1SGt97WCUNftNmLWV7kulI9 jbjQ==
MIME-Version: 1.0
X-Received: by 10.68.125.227 with SMTP id mt3mr40898937pbb.153.1370547223617;  Thu, 06 Jun 2013 12:33:43 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Thu, 6 Jun 2013 12:33:43 -0700 (PDT)
In-Reply-To: <09b601ce62db$77adc5c0$67095140$@olddog.co.uk>
References: <09b601ce62db$77adc5c0$67095140$@olddog.co.uk>
Date: Thu, 6 Jun 2013 21:33:43 +0200
Message-ID: <CADnDZ89jxuxzCGvwOqcDyO84DCmE10bDmA2zb94YQm=FPyqFZQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: adrian@olddog.co.uk
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>, iesg@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: Thu, 06 Jun 2013 19:33:49 -0000

On 6/6/13, Adrian Farrel <adrian@olddog.co.uk> wrote:
> Hi,
>
> It falls to me to make a call on this issue before the document moves on.
>
> Abdussalam has complained that he has not been acknowledged and has objected
> to
> the current text in section 8.
> The authors have responded on the MANET list
>
>> We believe that only comments that lead to significant improvements of
>> the draft deserve a listing in the acknowledgment section, and we have
>> therefore not modified the section.

What was the WG decision? Why any contribution that influnces the I-D
ideas is not acknowledged? IMO, if a technical-idea within the I-D was
discovered wrong by a participant, or a new technical-idea added to
I-D from an input, then the I-D should be acknowledged.

>
> I have reviewed the email threads on the MANET mailing list and do not
> consider
> that Abdussalam made contributions to the text of the document.

Didn't that person make review and discovered errors? Why don't you
consider discovering an error as a contribution? Why don't you
consider providing new ideas a contribution? What is your definition
to contribution?

> I also
> believe
> that the comments he made did not advance the content of the document.

So I understand that you need to have advance the content then you acknowledge.

> Furthermore, per multiple references (such as RFC 2026) the
> Acknowledgements
> section is used to "properly acknowledge major contributors.

I am trying to find that condition of *major contribution*,

>" Normal IETF
> business is to discuss not seek acknowledgement.

Ideas, Comments and reviews are included in the discuss for drafts
progress. Seeking acknowledgement is not wrong within IETF, but please
consider *not acknowledging reviews* within IETF documents is not IETF
culture (we are not paid so why you thinking much of the business, the
IETF business will only progress with acknowledging the volunteers).

>
> I do not propose to do an explicit consensus call on whether Abdussalam
> should
> be named in this draft.

IMO, it should have been done in the WG.


AB


> From: Abdussalam Baryun [mailto:abdussalambaryun@gmail.com]
> Sent: 03 June 2013 17:10
> To: ietf
> Cc: adrian@olddog.co.uk; iesg@ietf.org
> Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt>
> (Security Threats for NHDP) to Informational RFC
>
> I would hope that IETF add my name in the acknowledgement section of the
> I-D. I
> complained to AD about that my efforts in WGLC was not acknowledged by
> editors
> even after my request, however, I did not stop reviewing (trying not be
> discouraged) which I will complete on 6 June with the final comments.
> Therefore,
> this message (can be added as a comment on the I-D) is an objection to
> section 8
> that ignores acknowledge input/review effort related to the I-D.
>
> AB
>

From abdussalambaryun@gmail.com  Thu Jun  6 13:33:39 2013
Return-Path: <abdussalambaryun@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 A3DD621F972C; Thu,  6 Jun 2013 13:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.671
X-Spam-Level: 
X-Spam-Status: No, score=-1.671 tagged_above=-999 required=5 tests=[AWL=0.928,  BAYES_00=-2.599]
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 bpHyj16eOq9D; Thu,  6 Jun 2013 13:33:34 -0700 (PDT)
Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) by ietfa.amsl.com (Postfix) with ESMTP id 8C52721E80C7; Thu,  6 Jun 2013 13:33:34 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id x10so3861137pdj.15 for <multiple recipients>; Thu, 06 Jun 2013 13:33:34 -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:content-transfer-encoding; bh=laHXJcua8lP3iQK7v1JLV4OxmrxTbtLuwJTQMqDOb1Y=; b=npzs4WL8EOZikdd1gE9aIiI4NUA8n0Z0OnOUWam755sLBuTuyC439e+xW9sf9THAdh Hiegu/0VomaH+GRHhlOYukyYaOL0jtU4mE1UeyA7f3bfCqouf1HBHK5oRiWf0vnpHdH+ U5qYbzODE0+TiusmI6soH0jZVgkqL4ksQegaXPwU40KWA5UH3isB6aw8iTL1sKYaj1Lv mQOKdJQszxA3m/dF5bJOXhDUn+ei1rInEXATKwbIe3N8ABvSYXrQoa1BPRJ3u99I50tB joU8vN8NcfFKiaQk5bOAqV1enUIsuC6qX8QBb/3jywpOMbc8QRJIUxHZnGDqXqcu9O+3 LwSg==
MIME-Version: 1.0
X-Received: by 10.68.183.194 with SMTP id eo2mr20441569pbc.43.1370550814323; Thu, 06 Jun 2013 13:33:34 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Thu, 6 Jun 2013 13:33:34 -0700 (PDT)
In-Reply-To: <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com>
Date: Thu, 6 Jun 2013 22:33:34 +0200
Message-ID: <CADnDZ89VVtnky-n4GrNbeQ7v76sYx6ZfBp4Bnn4O1QnwR2iqZg@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "iesg@ietf.org" <iesg@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: Thu, 06 Jun 2013 20:33:39 -0000

Reply to your request dated 24/05/2013
I-D: draft-ietf-manet-nhdp-sec-threats-03
Draft Reviewed By: Abdussalam Baryun (AB)    Dated:06/06/2013
Reviewer Comment A3: Use Cases not considered and the Information Bases Thr=
eats.
+++++++++++++++++++++++++++++++++++++++
*Use-cases threats*

Reading the RFC6130 applicability section 3, the I-D does not consider
all the use-cases included in the that section 3.

AB> Does the use-case of NHDP [RFC6130] add any value to the threats,
or the I-D assumes only one use case which is OLSRv2 network.

The NHDP uses RFC5444 packets and RFC5444 messages, so what are the
threats to NHDP use for each? not mentioned in I-D.

RFC6130> NHDP Can use relevant link-layer information if it is available.
AB> is there any threat from that use-case? not mentioned in the I-D.

*Information bases threats*

RFC6130> Appendix F> This appendix illustrates various examples of
physical topologies, as well as how these are logically recorded by
NHDP from the point of
view of the router A. This representation is a composite of
information that would be contained within A=92s various Information
Bases after NHDP has been running for sufficiently long time for the
state to converge.

AB> Why the logically recording of the NHDP for all the examples not
mentioned in the I-D and were not threat analysed? If there is similar
level of threats related to all exampels in RFC6130, then please
mention that.


This is my last message, thanks.

Regards
AB

From iab-chair@iab.org  Thu Jun  6 13:50:53 2013
Return-Path: <iab-chair@iab.org>
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 8B7D011E80A2 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 13:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
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 LKkX8l58IEKn for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 13:50:49 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id D7B4521F96A9 for <ietf@ietf.org>; Thu,  6 Jun 2013 13:50:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D55C5124304 for <ietf@ietf.org>; Thu,  6 Jun 2013 13:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nzRSHdz-Q7iI for <ietf@ietf.org>; Thu,  6 Jun 2013 13:50:47 -0700 (PDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) by c8a.amsl.com (Postfix) with ESMTPSA id 931A3124302 for <ietf@ietf.org>; Thu,  6 Jun 2013 13:50:47 -0700 (PDT)
From: IAB Chair <iab-chair@iab.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Liaison Statement From the IESG and IAB to ISO/IEC JTC1/SC6 on TISec
Date: Thu, 6 Jun 2013 16:50:44 -0400
Message-Id: <E632AAD4-FD08-4C3B-A9BC-0F433109AF11@iab.org>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
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: Thu, 06 Jun 2013 20:50:53 -0000

The Liaison statement can be found here: =
https://datatracker.ietf.org/liaison/1258/

The Internet Society will forward this liaison statement to ISO/IEC =
JTC1/SC6 on their letterhead.  This will carry more weight than a =
statement just from the IESG and IAB because the Internet Society holds =
a Class A liaison with SC6 on behalf of the IETF.

This liaison is provided to ISO/IEC JTC1/SC6 because they are =
entertaining adopting the TISec.  The IESG and the IAB believe TISec =
provides the same services as IPsec.  The IESG rejected a request for a =
protocol number assignment for TISec in August of last year for that =
reason, but the IESG offered an experimental code point while TISec was =
under review in ISO.  A liaison was sent to ISO informing them of this =
decision in December (see ).

The TISec proponents have indicated that they believe that TISec is =
different than IPsec.  This liaison is a response this statement.  It =
points out how IPsec supports the same functionality, and it encourages
the TISec proponents to engage in the IETF process to specify the use of =
their national algorithms in IPsec, as has been done for other national =
algorithms.

On behalf of the IAB,
Russ Housley

On behalf of the IESG,
Jari Arkko


From ulrich@herberg.name  Thu Jun  6 13:52:57 2013
Return-Path: <ulrich@herberg.name>
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 3C6C811E8106 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 13:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 yqoEGNwCGMPq for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 13:52:56 -0700 (PDT)
Received: from mail-vb0-x232.google.com (mail-vb0-x232.google.com [IPv6:2607:f8b0:400c:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id B721111E8102 for <ietf@ietf.org>; Thu,  6 Jun 2013 13:52:55 -0700 (PDT)
Received: by mail-vb0-f50.google.com with SMTP id w16so2239540vbb.23 for <ietf@ietf.org>; Thu, 06 Jun 2013 13:52:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GwdeQDyzOtzLcxSBcHWu43K4EXUtCHwSjAQdI7HdVE8=; b=QQc9TGxJ/Yi3vshQyc2QC6MmtvV7nc8056+pwg0vbpWM9kVMiJQ3d3xo/feqBqihXx yC+iwKcYEZTHlAwRO8ZQPs8PgxYQ+XJU6bBKCPiBDouT1gmt3SlpGlt8Jdu6yeAbosZa keUBUmTKxdxUj3UKnsjqr+j0jHsYpalLWiVEw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=GwdeQDyzOtzLcxSBcHWu43K4EXUtCHwSjAQdI7HdVE8=; b=Vb0XDjfyOfUNZw3Q/jz/TC7fopYDlwX1mRmq9iTebLDM8DSeosxgQzmthzbPGZzgi9 nKlKJMAMsIPQclU4Ds7mIJYJmmPFHpYJIqiTNm4w96V/0PDxffMTmyYrtmhXCK0VwdYJ 8M4PxgZ4uT1L3NOvKG/zECK3OEF9h/EDkCgSJ/XlI2zv9k+CLdXiUU5tsqW7JweqFX+3 zzy106g8GEJwKvbbokvCbRoAETHPSrFZ/N7VAczvAlMJyk2VNK52BeNcm0FNOH5EDDLR YlB/YpqTBj3TX1quTYS0Mourwg8nVZWc1vTq7Q+4BK63SP7HdbUv8I7875DA6GY7Fh84 bisA==
MIME-Version: 1.0
X-Received: by 10.52.68.161 with SMTP id x1mr19371819vdt.83.1370551963162; Thu, 06 Jun 2013 13:52:43 -0700 (PDT)
Received: by 10.220.29.7 with HTTP; Thu, 6 Jun 2013 13:52:43 -0700 (PDT)
In-Reply-To: <CADnDZ89VVtnky-n4GrNbeQ7v76sYx6ZfBp4Bnn4O1QnwR2iqZg@mail.gmail.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CADnDZ89VVtnky-n4GrNbeQ7v76sYx6ZfBp4Bnn4O1QnwR2iqZg@mail.gmail.com>
Date: Thu, 6 Jun 2013 13:52:43 -0700
Message-ID: <CAK=bVC-T8DisV_yqoBZJ0h06LL2Y50WRgLyWU3XO-z99fgPTZA@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Ulrich Herberg <ulrich@herberg.name>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnGNFkY73XeNpGualT7vxrT/f4Lt5ZyQh7vO5G+D6pVP6vK+rIUqyV8xCKDHEXhm8SFXcns
Cc: ietf@ietf.org, "iesg@ietf.org" <iesg@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: Thu, 06 Jun 2013 20:52:57 -0000

AB,

while the IETF LC has already ended, I will reply to your comments below:

On Thu, Jun 6, 2013 at 1:33 PM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> Reply to your request dated 24/05/2013
> I-D: draft-ietf-manet-nhdp-sec-threats-03
> Draft Reviewed By: Abdussalam Baryun (AB)    Dated:06/06/2013
> Reviewer Comment A3: Use Cases not considered and the Information Bases T=
hreats.
> +++++++++++++++++++++++++++++++++++++++
> *Use-cases threats*
>
> Reading the RFC6130 applicability section 3, the I-D does not consider
> all the use-cases included in the that section 3.
>
> AB> Does the use-case of NHDP [RFC6130] add any value to the threats,
> or the I-D assumes only one use case which is OLSRv2 network.

I don't understand the question. The use case is a MANET running NHDP.
Section 5 in addition outlines consequences of security threats to
NHDP for protocols using the information from NHDP.


> The NHDP uses RFC5444 packets and RFC5444 messages, so what are the
> threats to NHDP use for each? not mentioned in I-D.

I don't understand the question. There is no danger from a message or
packet itself;  they may contain information that has either been
legitimately tampered with or that is "wrong" because of
misconfiguration. And these are the cases we have described.


> RFC6130> NHDP Can use relevant link-layer information if it is available.
> AB> is there any threat from that use-case? not mentioned in the I-D.

After discussion on the MANET mailing list, this was already added in
section 4.8 (even though the link quality itself is not a normative
part of RFC6130, the authors agreed to add that section).


> *Information bases threats*
>
> RFC6130> Appendix F> This appendix illustrates various examples of
> physical topologies, as well as how these are logically recorded by
> NHDP from the point of
> view of the router A. This representation is a composite of
> information that would be contained within A=92s various Information
> Bases after NHDP has been running for sufficiently long time for the
> state to converge.
>
> AB> Why the logically recording of the NHDP for all the examples not
> mentioned in the I-D and were not threat analysed? If there is similar
> level of threats related to all exampels in RFC6130, then please
> mention that.


I don't understand the question. The example in RFC6130 simply
illustrates how NHDP would perceive and store several sample
topologies. How would that represent a "level of threat"? The I-D
describes several security threats and explains in which situations
these could occur (and what effect it would have). That could happen
in an infinite amount of different topologies, so it is impossible
(and useless) to list all topologies where such attacks could occur.

Best regards
Ulrich

From adrian@olddog.co.uk  Thu Jun  6 14:02:04 2013
Return-Path: <adrian@olddog.co.uk>
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 101DC11E8115; Thu,  6 Jun 2013 14:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599]
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 gVl4MJ1dT5ru; Thu,  6 Jun 2013 14:01:57 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 6B09021F852A; Thu,  6 Jun 2013 14:01:48 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r56L1i1i028540;  Thu, 6 Jun 2013 22:01:44 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r56L1hFC028522 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Jun 2013 22:01:43 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>, <ietf@ietf.org>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com>	<CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CADnDZ89VVtnky-n4GrNbeQ7v76sYx6ZfBp4Bnn4O1QnwR2iqZg@mail.gmail.com>
In-Reply-To: <CADnDZ89VVtnky-n4GrNbeQ7v76sYx6ZfBp4Bnn4O1QnwR2iqZg@mail.gmail.com>
Subject: RE: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt>	(Security Threats for NHDP) to Informational RFC
Date: Thu, 6 Jun 2013 22:01:38 +0100
Message-ID: <0a0901ce62f9$0a17be30$1e473a90$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIhotg4CdXjJ2V6m9iU5kaOA6mt7QNAiXCHAc3XwDKYWjgKYA==
Content-Language: en-gb
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Thu, 06 Jun 2013 21:02:05 -0000

I find it somewhat disruptive that this email raises new questions on a draft
authored in a working group in which you participate, and that it has arrived
after the end of IETF last call.

I see a series of questions in this message, but no suggested textual changes. I
therefore conclude that you are requesting no changes and none shall be made. 

Thank you.
Adrian

> Reply to your request dated 24/05/2013
> I-D: draft-ietf-manet-nhdp-sec-threats-03
> Draft Reviewed By: Abdussalam Baryun (AB)    Dated:06/06/2013
> Reviewer Comment A3: Use Cases not considered and the Information Bases
> Threats.
> +++++++++++++++++++++++++++++++++++++++
> *Use-cases threats*


From adrian@olddog.co.uk  Thu Jun  6 14:17:09 2013
Return-Path: <adrian@olddog.co.uk>
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 07FD811E8105; Thu,  6 Jun 2013 14:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599]
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 KMM176parQTz; Thu,  6 Jun 2013 14:17:03 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id E0D8D11E8103; Thu,  6 Jun 2013 14:17:02 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r56LGwYL024476;  Thu, 6 Jun 2013 22:16:58 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r56LGtsn024464 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Jun 2013 22:16:55 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>
References: <09b601ce62db$77adc5c0$67095140$@olddog.co.uk> <CADnDZ89jxuxzCGvwOqcDyO84DCmE10bDmA2zb94YQm=FPyqFZQ@mail.gmail.com>
In-Reply-To: <CADnDZ89jxuxzCGvwOqcDyO84DCmE10bDmA2zb94YQm=FPyqFZQ@mail.gmail.com>
Subject: RE: Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
Date: Thu, 6 Jun 2013 22:16:50 +0100
Message-ID: <0a1401ce62fb$2aecfa10$80c6ee30$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJmjplEye0ftWpo3ykQGioJF/VNtALrNuNFl+Fo9RA=
Content-Language: en-gb
Cc: 'ietf' <ietf@ietf.org>, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Thu, 06 Jun 2013 21:17:09 -0000

Sorry to everyone for the noise this thread is creating.
Multiple questions that I have to answer.

> > It falls to me to make a call on this issue before the document moves on.
> >
> > Abdussalam has complained that he has not been acknowledged and has
> > objected to the current text in section 8.
> > The authors have responded on the MANET list
> >
> >> We believe that only comments that lead to significant improvements of
> >> the draft deserve a listing in the acknowledgment section, and we have
> >> therefore not modified the section.
> 
> What was the WG decision?

Are you asking whether there was an explicit consensus call within the working
group on whether or not you should be acknowledged in this document?
There was no such call in the working group or on the IETF list.

> Why any contribution that influnces the I-D ideas is not acknowledged?
> IMO, if a technical-idea within the I-D was discovered wrong by a
> participant, or a new technical-idea added to I-D from an input, then
> the I-D should be acknowledged.

This opinion does not apply to your comments on this document. You did not
discover a wrong technical-idea. Your comments did not lead directly to the
addition of any new technical-idea.

> > I have reviewed the email threads on the MANET mailing list and do not
> > consider that Abdussalam made contributions to the text of the document.
> 
> Didn't that person make review and discovered errors?

"That person" is you.
Yes, you made a review. Reviewing a document is not something authors
acknowledge in the IETF or (AFAIK) in academic journals.
No, I don't think you discovered errors of any significance.

Caveating my answers below as describing a contribution to a document (not a
contribution in the wider IETF sense)

> Why don't you consider discovering an error as a contribution?

I would personally consider discovering a major error as something I would
acknowledge it in a document I was editing.
I would personally consider discovering multiple minor errors as something I
would acknowledge it in a document I was editing.

However, there is no requirement for editors to act in that way. Furthermore,
you do not fit into these categories for this document.

> Why don't you consider providing new ideas a contribution?

I would consider providing major ideas as something I would acknowledge it in a
document I was editing.
I would consider providing smaller ideas through text for inclusion in the
document as something I would acknowledge it in a document I was editing.
You do not fit into these categories for this document.

> What is your definition to contribution?

As above, or written text that was included or modified for inclusion in a
document and represents a material or substantial part of the document.

> > I also believe that the comments he made did not advance the
> > content of the document.
> 
> So I understand that you need to have advance the content then you
> acknowledge.
>
> > Furthermore, per multiple references (such as RFC 2026) the
> > Acknowledgements section is used to "properly acknowledge
> > major contributors.
> 
> I am trying to find that condition of *major contribution*,

I would borrow from 2026 and 5378 to say a material or substantial contribution
to the document.

And, before you ask, no-one is going to write down a rule that says 139
characters is not substantial, but 140 is.

This is one of the places where a principal of reasonableness applies. I would
know a major contribution if I saw one. I did not see one from you in this case.

> >" Normal IETF business is to discuss not seek acknowledgement.
> 
> Ideas, Comments and reviews are included in the discuss for drafts
> progress. Seeking acknowledgement is not wrong within IETF, but please
> consider *not acknowledging reviews* within IETF documents is not IETF
> culture (we are not paid so why you thinking much of the business, the
> IETF business will only progress with acknowledging the volunteers).

If you want to change the way that the IETF participants (and document
authors/editors in particular) acknowledge reviews of their documents, then
please start a separate thread or, better still, write an I-D and see whether
you can gain consensus. The last time you brought this topic up on this list, I
do not recall seeing support.

The only reason I can find for someone being able to demand that they are named
in an Acknowledgements Section is for conformance to the IETF's Rights policies.

> > I do not propose to do an explicit consensus call on whether Abdussalam
> > should be named in this draft.
> 
> IMO, it should have been done in the WG.

Thank you for your opinion.
Are you asserting that consensus on the readiness of this document for a
publication request was incorrectly called by the working group chairs. This
would be a serious allegation against the chairs and I would require evidence
that there had been no consensus or that they had made an incorrect assessment
of the consensus.

Thank you,
Adrian


From abdussalambaryun@gmail.com  Thu Jun  6 14:48:51 2013
Return-Path: <abdussalambaryun@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 474B811E80B8; Thu,  6 Jun 2013 14:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 aWKJZNf2M3oN; Thu,  6 Jun 2013 14:48:50 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id B0CFB11E80A4; Thu,  6 Jun 2013 14:48:50 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx1so2055446pab.13 for <multiple recipients>; Thu, 06 Jun 2013 14:48:50 -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=atP5ul8uep/xRFgOdFFScFO7H7kMdjqFdPjkUk3i4GE=; b=SP/ZWXy3Rd0E/APOUKVtqFUTostuD65/BJo4wuUBC9ci68yOocuuF78xpU+oxdMIPr 7pRB+lqKIiXqsLzDbsh0rOGO524BuHwVwQd0K+/4W+9FG5EDVoiJGigURl5hzdbQT2lz nwzgBSjBZ1BwW0n2RNzqlrO8Sx0NAXwAEtKeXllEPxyMnlMsogldPi3vRxaEeL+q/iFR ngVhJVzFTrLI6VVKoEBiE7bVV8SpqPcqBCOlccrWoADBG8e5//GMyjAqDV/ufiE6HX5j ZwNYzWwlWRMpyl/3/NdOtoWIdZS/ULVSE/2ulZCVV/ZNR+7BE32TVkFLN4OwUaj1kAJ/ NQIw==
MIME-Version: 1.0
X-Received: by 10.66.144.98 with SMTP id sl2mr41424491pab.92.1370555330420; Thu, 06 Jun 2013 14:48:50 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Thu, 6 Jun 2013 14:48:50 -0700 (PDT)
In-Reply-To: <0a0901ce62f9$0a17be30$1e473a90$@olddog.co.uk>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CADnDZ89VVtnky-n4GrNbeQ7v76sYx6ZfBp4Bnn4O1QnwR2iqZg@mail.gmail.com> <0a0901ce62f9$0a17be30$1e473a90$@olddog.co.uk>
Date: Thu, 6 Jun 2013 23:48:50 +0200
Message-ID: <CADnDZ89XtZXLdjovzdPthUa8xqBvuMkJKZnVgBHm5jKzW_Orog@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: adrian@olddog.co.uk
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, iesg@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: Thu, 06 Jun 2013 21:48:51 -0000

I received an IESG message asking my comments so I gave it, regard to
your comments below, the reply is that I refer to missing information
needed in the I-D, so the reveiw suggests that there is something
missing. Did not suggested text because I know that it most probably
not be considered.

The Last call ends by 06.06.2013 so I still am in this date, not sure
why you close,

AB


On 6/6/13, Adrian Farrel <adrian@olddog.co.uk> wrote:
> I find it somewhat disruptive that this email raises new questions on a
> draft
> authored in a working group in which you participate, and that it has
> arrived
> after the end of IETF last call.
>
> I see a series of questions in this message, but no suggested textual
> changes. I
> therefore conclude that you are requesting no changes and none shall be
> made.
>
> Thank you.
> Adrian
>
>> Reply to your request dated 24/05/2013
>> I-D: draft-ietf-manet-nhdp-sec-threats-03
>> Draft Reviewed By: Abdussalam Baryun (AB)    Dated:06/06/2013
>> Reviewer Comment A3: Use Cases not considered and the Information Bases
>> Threats.
>> +++++++++++++++++++++++++++++++++++++++
>> *Use-cases threats*
>
>

From ogier@earthlink.net  Thu Jun  6 16:56:51 2013
Return-Path: <ogier@earthlink.net>
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 34A2221F8887 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 16:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 wvjJKHx+Ow35 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 16:56:46 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5DEE621F9950 for <ietf@ietf.org>; Thu,  6 Jun 2013 16:56:46 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=XhzQztlS56TV7z9dWgM7el522eunVtXWv3WdXK2cNquN6MP2AI6wjzaZEXOOyBBf; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [66.81.254.157] by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <ogier@earthlink.net>) id 1Ukk2t-00015P-8n for ietf@ietf.org; Thu, 06 Jun 2013 19:56:45 -0400
Message-ID: <51B122D8.9090801@earthlink.net>
Date: Thu, 06 Jun 2013 17:01:28 -0700
From: Richard Ogier <ogier@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-ospf-manet-single-hop-mdr-03.txt> (Use of OSPF-MDR in Single-Hop Broadcast Networks) to Experimental RFC
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: a073897a9455599e74bf435c0eb9d478e549f294dc8ae39d06ffaa237571437207c05baa4baf86f2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 66.81.254.157
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: Thu, 06 Jun 2013 23:56:51 -0000

AB,

As Joel pointed out, your questions should have been raised during the 
OSPF WG Last Call, which you did not participate in. You 
(inappropriately) posted questions on the MANET WG list after the OSPF 
WGLC was complete, and several people responded, most of them stating 
that RFC 5444 is not required for this document:

http://www.ietf.org/mail-archive/web/manet/current/msg15403.html
http://www.ietf.org/mail-archive/web/manet/current/msg15406.html
http://www.ietf.org/mail-archive/web/manet/current/msg15407.html
http://www.ietf.org/mail-archive/web/manet/current/msg15408.html

Although I should not be required to respond to your questions at this 
point, I will provide a few additional reasons why RFC 5444 and DLEP are 
not relevant for this document. (These reasons also apply to the 
parallel document draft-ietf-ospf-manet-single-hop-or-02.)

1. This draft does not propose a new interface, it only describes how 
the interface previously specified in RFC 5614 (and RFC 5820 for the 
other draft) can be configured in the special case of a single-hop 
MANET. Therefore, your comments should have been directed to RFC 5614 
(and RFC 5820).

2. RFCs 5614 and 5820 describe MANET extensions to OSPF, and one of the 
goals was to minimize changes to OSPF, so we decided to use OSPF packet 
formats (with minimal changes), rather than MANET packet formats that 
were designed without OSPF in mind. (This point is also made in the last 
message listed above.)

On the other hand, these are experimental documents, so your questions 
about using RFC 5444 and DLEP may be valid for future modifications to 
the proposed MANET extensions of OSPF (both RFCs 5614 and 5820). But 
they are not valid for draft-ietf-ospf-manet-single-hop-mdr or 
draft-ietf-ospf-manet-single-hop-or, not only because these two drafts 
have already completed WGLC, but also because they only describe how to 
configure RFCs 5614 and 5820 for the special case of a single-hop network.

Richard

On 6/6/13 3:15 AM, Abdussalam Baryun wrote:

 > I send my request to the editors including questions but no reply from
 > them to me. The thread [1] raised some issues, which is not mentioned
 > in the I-D. The message [2] was ignored not answered (this is last
 > reminder). The message [3] proposes using RFC5444 into this I-D, or
 > raise the question of why not using MANET packet format within MANET
 > domains (I need an answer).
 >
 > [1] http://www.ietf.org/mail-archive/web/manet/current/msg15400.html
 > [2] http://www.ietf.org/mail-archive/web/manet/current/msg15412.html
 > [3] http://www.ietf.org/mail-archive/web/manet/current/msg15418.html
 >
 > The I-D SHOULD not go forward if it still ignores the IETF community 
questions.
 >
 > Regards
 > AB
 >
 > On 6/5/13, The IESG <iesg-secretary@ietf.org>wrote:
 >> The IESG has received a request from the Open Shortest Path First 
IGP WG
 >> (ospf) to consider the following document:
 >> - 'Use of OSPF-MDR in Single-Hop Broadcast Networks'
 >> <draft-ietf-ospf-manet-single-hop-mdr-03.txt> as Experimental RFC
 >>
 >> The IESG plans to make a decision in the next few weeks, and solicits
 >> final comments on this action. Please send substantive comments to the
 >> ietf@ietf.orgmailing lists by 2013-06-19. Exceptionally, comments 
may be
 >> sent to iesg@ietf.orginstead. In either case, please retain the
 >> beginning of the Subject line to allow automated sorting.
 >>
 >> Abstract
 >>
 >>
 >> RFC 5614 (OSPF-MDR) extends OSPF to support mobile ad hoc networks
 >> (MANETs) by specifying its operation on the new OSPF interface of type
 >> MANET. This document describes the use of OSPF-MDR in a single-hop
 >> broadcast network, which is a special case of a MANET in which each
 >> router is a (one-hop) neighbor of each other router. Unlike an OSPF
 >> broadcast interface, such an interface can have a different cost
 >> associated with each neighbor. The document includes configuration
 >> recommendations and simplified mechanisms that can be used in 
single-hop
 >> broadcast networks.
 >>
 >>
 >>
 >>
 >> The file can be obtained via
 >> http://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/
 >>
 >> IESG discussion can be tracked via
 >> 
http://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/ballot/
 >>
 >>
 >> No IPR declarations have been submitted directly on this I-D.


From narten@us.ibm.com  Thu Jun  6 21:53:17 2013
Return-Path: <narten@us.ibm.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 DE4DC21F8AF7 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 21:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 9SsoNho7MsdM for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 21:53:11 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id E158E21F8319 for <ietf@ietf.org>; Thu,  6 Jun 2013 21:53:09 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 7 Jun 2013 00:53:08 -0400
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 7 Jun 2013 00:53:06 -0400
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 68F5DC9003E for <ietf@ietf.org>; Fri,  7 Jun 2013 00:53:05 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r574r5UT304830 for <ietf@ietf.org>; Fri, 7 Jun 2013 00:53:05 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r574r5is028688 for <ietf@ietf.org>; Fri, 7 Jun 2013 00:53:05 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r574r4a6028528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 7 Jun 2013 00:53:05 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r574r4ml010100 for <ietf@ietf.org>; Fri, 7 Jun 2013 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r574r3Wt010088 for ietf@ietf.org; Fri, 7 Jun 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>
Date: Fri, 07 Jun 2013 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13060704-7182-0000-0000-00000730819F
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: Fri, 07 Jun 2013 04:53:18 -0000

Total of 146 messages in the last 7 days.
 
script run at: Fri Jun  7 00:53:03 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.27% |   15 |  9.96% |   125797 | abdussalambaryun@gmail.com
  4.11% |    6 |  6.44% |    81389 | adrian@olddog.co.uk
  5.48% |    8 |  3.76% |    47556 | mohta@necom830.hpcl.titech.ac.jp
  4.11% |    6 |  4.30% |    54259 | warren@kumari.net
  3.42% |    5 |  3.58% |    45181 | john-ietf@jck.com
  3.42% |    5 |  3.28% |    41450 | l.wood@surrey.ac.uk
  3.42% |    5 |  3.16% |    39894 | dhc@dcrocker.net
  3.42% |    5 |  2.36% |    29749 | randy@psg.com
  2.74% |    4 |  2.53% |    31911 | carlosm3011@gmail.com
  2.74% |    4 |  2.18% |    27483 | arturo.servin@gmail.com
  1.37% |    2 |  3.38% |    42690 | ron.even.tlv@gmail.com
  2.74% |    4 |  1.86% |    23539 | mnot@mnot.net
  1.37% |    2 |  3.15% |    39833 | simo.veikkolainen@nokia.com
  2.05% |    3 |  1.88% |    23809 | scott.brim@gmail.com
  2.05% |    3 |  1.68% |    21225 | sm@resistor.net
  2.05% |    3 |  1.62% |    20488 | ted.lemon@nominum.com
  1.37% |    2 |  2.29% |    28971 | doug.mtview@gmail.com
  2.05% |    3 |  1.54% |    19411 | jmamodio@gmail.com
  0.68% |    1 |  2.80% |    35397 | elwynd@folly.org.uk
  2.05% |    3 |  1.37% |    17285 | iab-chair@iab.org
  0.68% |    1 |  2.66% |    33542 | cb.list6@gmail.com
  1.37% |    2 |  1.73% |    21883 | barryleiba@computer.org
  1.37% |    2 |  1.64% |    20761 | jcurran@istaff.org
  1.37% |    2 |  1.50% |    18953 | brian.e.carpenter@gmail.com
  1.37% |    2 |  1.44% |    18207 | ulrich@herberg.name
  1.37% |    2 |  1.37% |    17302 | hartmans-ietf@mit.edu
  1.37% |    2 |  1.35% |    17078 | aeopare@gmail.com
  1.37% |    2 |  1.27% |    16048 | msk@blackops.org
  1.37% |    2 |  1.10% |    13834 | spencerdawkins.ietf@gmail.com
  1.37% |    2 |  1.09% |    13711 | chris.dearlove@baesystems.com
  1.37% |    2 |  1.06% |    13376 | joelja@bogus.com
  1.37% |    2 |  0.94% |    11882 | cabo@tzi.org
  1.37% |    2 |  0.92% |    11641 | touch@isi.edu
  0.68% |    1 |  1.60% |    20151 | rjsparks@nostrum.com
  1.37% |    2 |  0.88% |    11081 | jari.arkko@piuha.net
  1.37% |    2 |  0.87% |    10956 | fgont@si6networks.com
  0.68% |    1 |  0.95% |    12013 | ke-oogaki@kddi.com
  0.68% |    1 |  0.88% |    11066 | narten@us.ibm.com
  0.68% |    1 |  0.73% |     9244 | ogier@earthlink.net
  0.68% |    1 |  0.67% |     8504 | framefritti@gmail.com
  0.68% |    1 |  0.66% |     8340 | d3e3e3@gmail.com
  0.68% |    1 |  0.63% |     7996 | david.black@emc.com
  0.68% |    1 |  0.63% |     7948 | ybmcu@panix.com
  0.68% |    1 |  0.62% |     7882 | daedulus@btconnect.com
  0.68% |    1 |  0.61% |     7654 | ietf@cdl.asgaard.org
  0.68% |    1 |  0.61% |     7651 | yi.jiazi@gmail.com
  0.68% |    1 |  0.60% |     7579 | elwynd@dial.pipex.com
  0.68% |    1 |  0.59% |     7486 | marka@isc.org
  0.68% |    1 |  0.55% |     6960 | dave@cridland.net
  0.68% |    1 |  0.55% |     6886 | amankin@verisign.com
  0.68% |    1 |  0.53% |     6748 | rwfranks@gmail.com
  0.68% |    1 |  0.52% |     6615 | bmanning@isi.edu
  0.68% |    1 |  0.52% |     6609 | jnc@mercury.lcs.mit.edu
  0.68% |    1 |  0.51% |     6418 | stephen.farrell@cs.tcd.ie
  0.68% |    1 |  0.50% |     6367 | dougb@dougbarton.us
  0.68% |    1 |  0.50% |     6353 | paul@cypherpunks.ca
  0.68% |    1 |  0.50% |     6328 | fred@cisco.com
  0.68% |    1 |  0.49% |     6164 | paf@frobbit.se
  0.68% |    1 |  0.45% |     5654 | ynir@checkpoint.com
  0.68% |    1 |  0.44% |     5502 | nsclick@gmx.de
  0.68% |    1 |  0.41% |     5235 | cos@aaaaa.org
  0.68% |    1 |  0.41% |     5212 | peter@akayla.com
  0.68% |    1 |  0.40% |     5074 | wjhns1@hardakers.net
--------+------+--------+----------+------------------------
100.00% |  146 |100.00% |  1263211 | Total


From abdussalambaryun@gmail.com  Fri Jun  7 01:23:30 2013
Return-Path: <abdussalambaryun@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 29C4221F965B for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 01:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.787
X-Spam-Level: 
X-Spam-Status: No, score=-1.787 tagged_above=-999 required=5 tests=[AWL=0.812,  BAYES_00=-2.599]
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 DHjTHA2qXPfV for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 01:23:24 -0700 (PDT)
Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) by ietfa.amsl.com (Postfix) with ESMTP id B41C121F963C for <ietf@ietf.org>; Fri,  7 Jun 2013 01:23:23 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id y10so4551426pdj.28 for <ietf@ietf.org>; Fri, 07 Jun 2013 01:23:23 -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=48lu+lg8Y/NBnwZYB/9INxvEQy0ctLPZDpP2vaWvMXw=; b=Q7yYEg4wudu4L1/5+rTFcQEY95w68KPEDp3/Mbn91XeBtbAlxkYgUfVpycJzXG0wPn 8tqKy+P0w9SFqagx3avCi5OyYacTssO8ofkoVZ6Ja2+2BEY0y1Kwzpkiv0RyjJWM8ApJ rnCq24PgCMb2CRl4HxXxhIjJ6bobAB3NTniqwCyivqW2WWMoae8QEsgotDUF2qS9fYRl MlSOP/SBSEDL+d8xwVWzrfyqgn9Q/xJQlKjmIkavGlC/b0CCvRXGYF8R/2I79kkQ/NHm 4mWIeDdvXVoRwIlF6g7xrmrFQCuNDyLt6WqlqgX/rwc8mXYeDDXjENi38dDjbX0abdK+ /EAA==
MIME-Version: 1.0
X-Received: by 10.68.52.10 with SMTP id p10mr20104686pbo.92.1370593403394; Fri, 07 Jun 2013 01:23:23 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Fri, 7 Jun 2013 01:23:23 -0700 (PDT)
In-Reply-To: <51B1087A.2060100@earthlink.net>
References: <51B1087A.2060100@earthlink.net>
Date: Fri, 7 Jun 2013 10:23:23 +0200
Message-ID: <CADnDZ89OjNuQPbEEGFoiC37XyR1ghdKpnT09i2XCGSxskb7G2A@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-ospf-manet-single-hop-mdr-03.txt> (Use of OSPF-MDR in Single-Hop Broadcast Networks) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Richard Ogier <ogier@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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: Fri, 07 Jun 2013 08:23:30 -0000

Hi Richard,

I send to the author of an IETF document a message but it was not
answered. I beleive that the question from the community was ignored,
I hope you understand the importance of community questions. Why does
the IETF name its documents RFCs, any one from the community can ask
questions even after the RFC is produced, so we SHOULD NOT be stoped
to comment on any document and the IETF SHOULD try to answer
communities questions, otherwise IETF SHOULD NOT request comments.
comments below,

On 6/7/13, Richard Ogier <ogier@earthlink.net> wrote:
> AB,
>
> As Joel pointed out, your questions should have been raised during the
> OSPF WG Last Call, which you did not participate in. You
> (inappropriately) posted questions on the MANET WG list after the OSPF
> WGLC was complete, and several people responded, most of them stating
> that RFC 5444 is not required for this document:

Please note that I got a message from IETF post or an AD post in MANET
WG, so I responded, and asked the author by their address (it was
appropriate/reasonable reaction). I may agree that I should send to
the origin WG, which I learn now, but only if that WG is open to
questions. I know I don't work in OPSF WG, but that does not mean any
one can stop me from commenting or asking questions outside that
blocked-WG. My questions were before the IETF last call (which is
enough).
>
> http://www.ietf.org/mail-archive/web/manet/current/msg15403.html
> http://www.ietf.org/mail-archive/web/manet/current/msg15406.html
> http://www.ietf.org/mail-archive/web/manet/current/msg15407.html
> http://www.ietf.org/mail-archive/web/manet/current/msg15408.html
>
> Although I should not be required to respond to your questions at this
> point,

I thought that within the IETF last call of the I-D, all the community
questions and comments are answered as long as the last call did not
end. Furthermore, the OPSF WG is blocking me (so no one unsubscribed
from the community can comment on the document) from sending my
thoughts yesterday even after I subscribed.

Thanks for your respond below,

AB
> I will provide a few additional reasons why RFC 5444 and DLEP are
> not relevant for this document. (These reasons also apply to the
> parallel document draft-ietf-ospf-manet-single-hop-or-02.)
>
> 1. This draft does not propose a new interface, it only describes how
> the interface previously specified in RFC 5614 (and RFC 5820 for the
> other draft) can be configured in the special case of a single-hop
> MANET. Therefore, your comments should have been directed to RFC 5614
> (and RFC 5820).
>
> 2. RFCs 5614 and 5820 describe MANET extensions to OSPF, and one of the
> goals was to minimize changes to OSPF, so we decided to use OSPF packet
> formats (with minimal changes), rather than MANET packet formats that
> were designed without OSPF in mind. (This point is also made in the last
> message listed above.)
>
> On the other hand, these are experimental documents, so your questions
> about using RFC 5444 and DLEP may be valid for future modifications to
> the proposed MANET extensions of OSPF (both RFCs 5614 and 5820). But
> they are not valid for draft-ietf-ospf-manet-single-hop-mdr or
> draft-ietf-ospf-manet-single-hop-or, not only because these two drafts
> have already completed WG Last Call, but also because they only describe
> how to configure RFCs 5614 and 5820 for the special case of a single-hop
> network.
>
> Richard
>
> On 6/6/13 3:15 AM, Abdussalam Baryun wrote:
>
>  > I send my request to the editors including questions but no reply from
>  > them to me. The thread [1] raised some issues, which is not mentioned
>  > in the I-D. The message [2] was ignored not answered (this is last
>  > reminder). The message [3] proposes using RFC5444 into this I-D, or
>  > raise the question of why not using MANET packet format within MANET
>  > domains (I need an answer).
>  >
>  > [1] http://www.ietf.org/mail-archive/web/manet/current/msg15400.html
>  > [2] http://www.ietf.org/mail-archive/web/manet/current/msg15412.html
>  > [3] http://www.ietf.org/mail-archive/web/manet/current/msg15418.html
>  >
>  > The I-D SHOULD not go forward if it still ignores the IETF community
> questions.
>  >
>  > Regards
>  > AB
>  >
>  > On 6/5/13, The IESG <iesg-secretary@ietf.org> wrote:
>  >> The IESG has received a request from the Open Shortest Path First
> IGP WG
>  >> (ospf) to consider the following document:
>  >> - 'Use of OSPF-MDR in Single-Hop Broadcast Networks'
>  >> <draft-ietf-ospf-manet-single-hop-mdr-03.txt> as Experimental RFC
>  >>
>  >> The IESG plans to make a decision in the next few weeks, and solicits
>  >> final comments on this action. Please send substantive comments to the
>  >> ietf@ietf.org mailing lists by 2013-06-19. Exceptionally, comments
> may be
>  >> sent to iesg@ietf.org instead. In either case, please retain the
>  >> beginning of the Subject line to allow automated sorting.
>  >>
>  >> Abstract
>  >>
>  >>
>  >> RFC 5614 (OSPF-MDR) extends OSPF to support mobile ad hoc networks
>  >> (MANETs) by specifying its operation on the new OSPF interface of type
>  >> MANET. This document describes the use of OSPF-MDR in a single-hop
>  >> broadcast network, which is a special case of a MANET in which each
>  >> router is a (one-hop) neighbor of each other router. Unlike an OSPF
>  >> broadcast interface, such an interface can have a different cost
>  >> associated with each neighbor. The document includes configuration
>  >> recommendations and simplified mechanisms that can be used in
> single-hop
>  >> broadcast networks.
>  >>
>  >>
>  >>
>  >>
>  >> The file can be obtained via
>  >> http://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/
>  >>
>  >> IESG discussion can be tracked via
>  >>
> http://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/ballot/
>
>
>  >>
>  >>
>  >> No IPR declarations have been submitted directly on this I-D.
>
>
>

From abdussalambaryun@gmail.com  Fri Jun  7 01:33:22 2013
Return-Path: <abdussalambaryun@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 B320821F963C for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 01:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 02ZhnnBqkHN2 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 01:33:22 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 055E521F9485 for <ietf@ietf.org>; Fri,  7 Jun 2013 01:33:21 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj3so1225306pad.0 for <ietf@ietf.org>; Fri, 07 Jun 2013 01:33:21 -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=b333WWy5anLdNHm4dBF2CHYOse3PCoHQlYAmcuWUAMU=; b=y6PAiJSMFw08Y7MZ5ea5bztEsjaV051d/FeIH/4QSngeWyx35L6/gg1Ts3imFdOjCC X8MjQN/92+09m19NLlp1t/TbJKxoo5oxHTtomp5QKx+DWBzWJ3RlcX7hTmOuUFY8yv6O zERnpo9WMCVas6Ak+6J/shW5gzsQObXJcaRLcaq7cM2rV/kmOV9/HOK0wKPvgZUUlGCE ufgKXU39AbezIElb7p2rJD1wHFWamuzAou/peCN6jJFzrulfGvVPYNb68QH5EGXdq0Vm LAg4kElWH0NV3Znv+jiWHN1S1l4FMKVFsq/CLdF18eOrmHGLjF0IlfRtTQ7ISOhO7B0b 4WfA==
MIME-Version: 1.0
X-Received: by 10.66.248.228 with SMTP id yp4mr1623824pac.158.1370594001706; Fri, 07 Jun 2013 01:33:21 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Fri, 7 Jun 2013 01:33:21 -0700 (PDT)
In-Reply-To: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>
Date: Fri, 7 Jun 2013 10:33:21 +0200
Message-ID: <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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: Fri, 07 Jun 2013 08:33:22 -0000

Hi thomas,

AB> Comment on the summary report>

 I recommend to add a column for subjects (number of subjects),
because the number of subject participated in is very important is
such summary.
 I think the pupose of this summary should be added as well in each
post, I don't know why, only I expect the purpose is that it informs
of work volume or overhead in such list.

AB

On 6/7/13, Thomas Narten <narten@us.ibm.com> wrote:
> Total of 146 messages in the last 7 days.
>
> script run at: Fri Jun  7 00:53:03 EDT 2013
>
>     Messages   |      Bytes        | Who
> --------+------+--------+----------+------------------------
>  10.27% |   15 |  9.96% |   125797 | abdussalambaryun@gmail.com
>   4.11% |    6 |  6.44% |    81389 | adrian@olddog.co.uk
>   5.48% |    8 |  3.76% |    47556 | mohta@necom830.hpcl.titech.ac.jp
>   4.11% |    6 |  4.30% |    54259 | warren@kumari.net
>   3.42% |    5 |  3.58% |    45181 | john-ietf@jck.com
>   3.42% |    5 |  3.28% |    41450 | l.wood@surrey.ac.uk
>   3.42% |    5 |  3.16% |    39894 | dhc@dcrocker.net
>   3.42% |    5 |  2.36% |    29749 | randy@psg.com
>   2.74% |    4 |  2.53% |    31911 | carlosm3011@gmail.com
>   2.74% |    4 |  2.18% |    27483 | arturo.servin@gmail.com
>   1.37% |    2 |  3.38% |    42690 | ron.even.tlv@gmail.com
>   2.74% |    4 |  1.86% |    23539 | mnot@mnot.net
>   1.37% |    2 |  3.15% |    39833 | simo.veikkolainen@nokia.com
>   2.05% |    3 |  1.88% |    23809 | scott.brim@gmail.com
>   2.05% |    3 |  1.68% |    21225 | sm@resistor.net
>   2.05% |    3 |  1.62% |    20488 | ted.lemon@nominum.com
>   1.37% |    2 |  2.29% |    28971 | doug.mtview@gmail.com
>   2.05% |    3 |  1.54% |    19411 | jmamodio@gmail.com
>   0.68% |    1 |  2.80% |    35397 | elwynd@folly.org.uk
>   2.05% |    3 |  1.37% |    17285 | iab-chair@iab.org
>   0.68% |    1 |  2.66% |    33542 | cb.list6@gmail.com
>   1.37% |    2 |  1.73% |    21883 | barryleiba@computer.org
>   1.37% |    2 |  1.64% |    20761 | jcurran@istaff.org
>   1.37% |    2 |  1.50% |    18953 | brian.e.carpenter@gmail.com
>   1.37% |    2 |  1.44% |    18207 | ulrich@herberg.name
>   1.37% |    2 |  1.37% |    17302 | hartmans-ietf@mit.edu
>   1.37% |    2 |  1.35% |    17078 | aeopare@gmail.com
>   1.37% |    2 |  1.27% |    16048 | msk@blackops.org
>   1.37% |    2 |  1.10% |    13834 | spencerdawkins.ietf@gmail.com
>   1.37% |    2 |  1.09% |    13711 | chris.dearlove@baesystems.com
>   1.37% |    2 |  1.06% |    13376 | joelja@bogus.com
>   1.37% |    2 |  0.94% |    11882 | cabo@tzi.org
>   1.37% |    2 |  0.92% |    11641 | touch@isi.edu
>   0.68% |    1 |  1.60% |    20151 | rjsparks@nostrum.com
>   1.37% |    2 |  0.88% |    11081 | jari.arkko@piuha.net
>   1.37% |    2 |  0.87% |    10956 | fgont@si6networks.com
>   0.68% |    1 |  0.95% |    12013 | ke-oogaki@kddi.com
>   0.68% |    1 |  0.88% |    11066 | narten@us.ibm.com
>   0.68% |    1 |  0.73% |     9244 | ogier@earthlink.net
>   0.68% |    1 |  0.67% |     8504 | framefritti@gmail.com
>   0.68% |    1 |  0.66% |     8340 | d3e3e3@gmail.com
>   0.68% |    1 |  0.63% |     7996 | david.black@emc.com
>   0.68% |    1 |  0.63% |     7948 | ybmcu@panix.com
>   0.68% |    1 |  0.62% |     7882 | daedulus@btconnect.com
>   0.68% |    1 |  0.61% |     7654 | ietf@cdl.asgaard.org
>   0.68% |    1 |  0.61% |     7651 | yi.jiazi@gmail.com
>   0.68% |    1 |  0.60% |     7579 | elwynd@dial.pipex.com
>   0.68% |    1 |  0.59% |     7486 | marka@isc.org
>   0.68% |    1 |  0.55% |     6960 | dave@cridland.net
>   0.68% |    1 |  0.55% |     6886 | amankin@verisign.com
>   0.68% |    1 |  0.53% |     6748 | rwfranks@gmail.com
>   0.68% |    1 |  0.52% |     6615 | bmanning@isi.edu
>   0.68% |    1 |  0.52% |     6609 | jnc@mercury.lcs.mit.edu
>   0.68% |    1 |  0.51% |     6418 | stephen.farrell@cs.tcd.ie
>   0.68% |    1 |  0.50% |     6367 | dougb@dougbarton.us
>   0.68% |    1 |  0.50% |     6353 | paul@cypherpunks.ca
>   0.68% |    1 |  0.50% |     6328 | fred@cisco.com
>   0.68% |    1 |  0.49% |     6164 | paf@frobbit.se
>   0.68% |    1 |  0.45% |     5654 | ynir@checkpoint.com
>   0.68% |    1 |  0.44% |     5502 | nsclick@gmx.de
>   0.68% |    1 |  0.41% |     5235 | cos@aaaaa.org
>   0.68% |    1 |  0.41% |     5212 | peter@akayla.com
>   0.68% |    1 |  0.40% |     5074 | wjhns1@hardakers.net
> --------+------+--------+----------+------------------------
> 100.00% |  146 |100.00% |  1263211 | Total
>
>

From prvs=5870ac8b49=magnus.westerlund@ericsson.com  Fri Jun  7 02:35:28 2013
Return-Path: <prvs=5870ac8b49=magnus.westerlund@ericsson.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 CC27021F9648; Fri,  7 Jun 2013 02:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 W8FLhUvFF6Sf; Fri,  7 Jun 2013 02:35:23 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 272E321F9371; Fri,  7 Jun 2013 02:35:21 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-94-51b1a958c107
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id DE.D5.15700.859A1B15; Fri,  7 Jun 2013 11:35:20 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Fri, 7 Jun 2013 11:35:20 +0200
Message-ID: <51B1A95B.2030208@ericsson.com>
Date: Fri, 7 Jun 2013 11:35:23 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Elwyn Davies <elwynd@folly.org.uk>
Subject: Re: Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
References: <1370477514.4596.9052.camel@mightyatom>
In-Reply-To: <1370477514.4596.9052.camel@mightyatom>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNLMWRmVeSWpSXmKPExsUyM+JvrW7Eyo2BBnM+2lhc/HKE3eL4gR3s FldffWaxeLZxPovF1OWPWRxYPb6ebGfxWLLkJ5PHl8uf2QKYo7htkhJLyoIz0/P07RK4Mx7/ ncFccN2kouPldOYGxnOaXYwcHBICJhKNq4BMTiBTTOLCvfVsXYxcHEICpxgl7m26zwjhLGOU OHB2MQtIFa+AtsTNyccZQWwWARWJX8f6wWw2AQuJmz8a2UBsUYFgiSPbN0PVC0qcnPkEzBYR UJPY/PUB2FBmgXWMEidnPwJrFhbwkdgyYTVYkZCAscTjr+9ZQWxOoOvutnaxQpwnKbHlRTs7 iM0soCcx5WoLI4QtL9G8dTYzRK+2RENTB+sERqFZSHbPQtIyC0nLAkbmVYzsuYmZOenlhpsY gWF9cMtv3R2Mp86JHGKU5mBREufV410cKCSQnliSmp2aWpBaFF9UmpNafIiRiYMTRHBJNTBm Njw9vXtNjUSWqHffHf6XIhdnHWQqOXH7tfbLwsgXdjn1jrV8DCI6Oey3tmjcFJDc/Trm/qna ur78ph9FVukpx5KmPdX9LeBY19627evxW3cXyOr3VT+WMRG5YP1/RexpIY41ey3Xf92z4ffL Kfwfr/U/FPzHIuo/RU8mv0p0eV339/f6E62VWIozEg21mIuKEwF2n0SPPgIAAA==
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, "mmusic \(E-mail\)" <mmusic@ietf.org>, IETF discussion <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: Fri, 07 Jun 2013 09:35:28 -0000

Hi Elwyn,

Many thanks for the detailed review. We will address the nits you have
raised, but I cut them out of this reply to focus on the more
substantial issues you have brought up.

See inline below.

On 2013-06-06 02:11, Elwyn Davies wrote:
> I am an additional Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please resolve these comments along with any other Last Call comments
> you may receive.
> 
> Document: draft-ietf-mmusic-rfc2326bis
> Reviewer: Elwyn Davies
> Review Date: 5 June 2013
> IETF LC End Date: 5 JUne 2013
> IESG Telechat date: (if known) -
> 
> Summary:
> Almost ready.  Generally this is an excellent and well written document,
> particularly given its size.  There are a few minor issues to sort out
> mainly at the nit level and some consistency issues to fix up.  The two
> issues that I have brought out below are really at what the IESG would
> call 'DISCUSS-DISCUSS' level.  The issue of URI scheme redefinition may
> well have already been cleared by the URI expert - the draft does not do
> itself any favours here by failing to explain what the syntax changes
> are in s4.2; this raises immediate red flags that only start to fade a
> couple of hundred pages later. The rudimentary nature of the pipeline
> mechanism is carried over from RTSP 1.0.  I'd like to be sure that this
> has been properly discussed in the WG as it looks pretty flaky to an
> outsider.  There are several inconsistencies between various lists of
> headers that need sorting out and there is no definition of
> Proxy-Authorization in the ABNF.
> 
> There are also a fairly large number of editorial nits but these are all
> localized and trivial to fix.  Finally I have't had time to review the
> appendices (maybe there will be a follow up).
> 
> Robert Sparks is the main gen-art reviewer for the document; he asked
> for additional eyes on the document given the size and his RAI
> background.  Having (just) seen his review, I think we have both picked
> up on the URI scheme and pipeline issues.  I am not sure that I concur
> with his view that there is significant normative material in the
> appendices - AFAICS the main protocol definition *is* in the main body
> of the document and the bits especiially in Appendices B and C are not
> the core of the protocol.  However this is based on a very cursory
> glance through something like 75 pages of the document.  However, I do
> concur with Robert's view that it needs a security expert to check the
> security stories.
> 
> Major(ish) issues:
> s4.2: This section (re-)defines the URI schemes "rtsp" and "rtsps". The 
> last sentence of para 1 states that the 'details of the syntax' of the 
> URIs 'have been changed'.  Is this a reasonable thing to do? Has this 
> been cleared with the URI expert reviewer?  I am not entirely clear what 
> the change involves and the draft doesn't explain exactly how the syntax 
> has been altered  and its consequences (if any) in s4.2.  Some details
> are finally given in s22.14.

These syntax changes where discussed in the reviews I got on the URI
list. That resulted in the explicitness in the template, but I forgot
about adding anything into Section 4.2. I see no issue with adding the
following clarification to Section 4.2:

   The details of the syntax of "rtsp" and "rtsps" URIs has been changed
   from RTSP 1.0.  These changes are:

   o  Support for IPV6 literal in host part and future IP literals
      through RFC 3986 defined mechanism.

   o  A new relative format to use in the RTSP protocol elements that is
      not required to start with "/".

   Neither should have any significant impact on interoperability.  If
   one is required to use IPv6 literals to reach an RTSP server, then
   that RTSP server must be IPv6 capable, and RTSP 1.0 is not a fully
   IPv6 capable protocol.  Thus, RTSP 2.0 support will be needed anyway.
   The second change will only occur in RTSP messages, that are
   explicitly identified as being RTSP 2.0 messages, thus a RTSP 1.0
   only agent will not be required to parse this variant.

I hope this makes it clear that these syntax changes is unlikely to hurt
the interoperability.

> 
> 
> Minor issues:
> s11, para 3: I guess that the WG decided that sticking with the RTSP 1.0
> model of sending requests and worrying about success of prior prior
> pipelined requests was the right answer.  I would have thought that it
> might have been helpful to provide qualifiers on the Pipelined-Requests
> header that allowed subsequent requests to be suppressed unless the
> previous command resulted in one of a given set of status codes with a
> 'reset' option to 'restart' the pipeline.  It strikes me that this would
> avoid some irritating need to work out how to recover from arbitrary
> failures in a command chain in a client.
> 

I assume you mean this Section 12 paragraph:

   If a pipelined request builds on the successful completion of one or
   more prior requests the requester must verify that all requests were
   executed as expected.  A common example will be two SETUP requests
   and a PLAY request.  In case one of the SETUP fails unexpectedly, the
   PLAY request can still be successfully executed.  However, the
   resulting presentation will not be as expected by the requesting
   client, as only a single media instead of two will be played.  In
   this case the client can send a PAUSE request, correct the failing
   SETUP request and then request it to be played.

I think I agree with your assessment, that it would have been nice.
However, we should have thought of that when we introduced this type of
pipelining 7 years ago. Making any changes to this at this stage is
counter productive. The reality is that all the "nice" features and
necessary clarifications has been retrofitted into RTSP 1.0 by the ones
that have been using RTSP 1.0. So changing anything will separate the
RTSP 1.0 and RTSP 2.0 implementations. The good thing is that I can't
remember any substantial complaints about this issue.

I hope this resolves your comments.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From stbryant@cisco.com  Fri Jun  7 02:54:33 2013
Return-Path: <stbryant@cisco.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 28B3221F9402 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 02:54:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.6
X-Spam-Level: 
X-Spam-Status: No, score=-106.6 tagged_above=-999 required=5 tests=[AWL=4.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 hAL94Qz0r9+k for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 02:54:26 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 7586621F944C for <ietf@ietf.org>; Fri,  7 Jun 2013 02:54:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=257; q=dns/txt; s=iport; t=1370598866; x=1371808466; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=UYMUiKS+aHp0A+ORwVA82qceQe0ZrvIjcuxTxBbiZIg=; b=DCa41A0nuQ6aiZgiBwKKIi0AP2ZUgq8CYzUEO46ooy+LHccrKjHrXwf6 /2yIVrwf9g5GMgqnpGweq+a+ycEvwEfn0SasUdoPvhW7VhIA1WiSB2B2n gLJHnS9oiVCXiIcdQAgR7BcpGIRKUF7qGduyAdQ7UsVY+ZjNR1ezGCFIz c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFAGKssVGQ/khL/2dsb2JhbABZgwkxu3aCeXwWdIIjAQEBBDhAARALGAkWBAsJAwIBAgFFBg0BBwEBiAm8MY84B4NcA5dAhh+LI4FYgTg
X-IronPort-AV: E=Sophos;i="4.87,821,1363132800"; d="scan'208";a="83182949"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 07 Jun 2013 09:54:25 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r579sNxi021911 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jun 2013 09:54:23 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r579sM8B014270; Fri, 7 Jun 2013 10:54:22 +0100 (BST)
Message-ID: <51B1ADCE.3050307@cisco.com>
Date: Fri, 07 Jun 2013 10:54:22 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Last Call: <draft-ietf-ospf-manet-single-hop-mdr-03.txt> (Use of OSPF-MDR in Single-Hop Broadcast Networks) to Experimental RFC
References: <51B1087A.2060100@earthlink.net> <CADnDZ89OjNuQPbEEGFoiC37XyR1ghdKpnT09i2XCGSxskb7G2A@mail.gmail.com>
In-Reply-To: <CADnDZ89OjNuQPbEEGFoiC37XyR1ghdKpnT09i2XCGSxskb7G2A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: Fri, 07 Jun 2013 09:54:33 -0000

On 07/06/2013 09:23, Abdussalam Baryun wrote:
> Thanks for your respond below, AB

Thank you Richard and Abdussalam for reaching agreement
on this. I regard the issue as now closed.

Regards

Stewart Bryant
(speaking as responsible Area Director)

From sm@resistor.net  Fri Jun  7 03:29:19 2013
Return-Path: <sm@resistor.net>
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 875C521F8E8C for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 03:29:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.339
X-Spam-Level: 
X-Spam-Status: No, score=-102.339 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Sxk2w6g+3OnC for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 03:29:15 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 03C0921F8E8F for <ietf@ietf.org>; Fri,  7 Jun 2013 03:29:14 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r57ASjvG027617; Fri, 7 Jun 2013 03:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1370600930; bh=TJyn7Q/r9x4MRPsVE3Ra2UayFyQGVmmYtNKkpcPFYNA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ViSd/vjhh+1cA1Ul9Ou5fimRv3qK2QSFt3j+b9AN8Z+GrQvo7AAMnufVt4pJuWENM QzLimdt6bSJrp2d8wwL9PFl32gT7dOin2qgKX89gNF0w+k6TG1+zXdmLsC+0e9MZso H+Dl5FG8am4iASDv/2PjwstrogiBTs1PRKUqKnOs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1370600930; i=@resistor.net; bh=TJyn7Q/r9x4MRPsVE3Ra2UayFyQGVmmYtNKkpcPFYNA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HtrOEPQKWbY3NIfsGbwTTLKx+GAHxAsMuTUhc9/N8FMD2zMHusQuvTKXNckP58RMi AQqtzI+wg4ERe1LZSaw0uYwBeDu/dzcrk2sXmyDYbk2rBsJUfpZgx+t8s6PIoLZ5BV XnBK69BIav0BNigRaBqZEKr6ftGsojRGAXC+a+YE=
Message-Id: <6.2.5.6.2.20130607025844.0cae1948@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 07 Jun 2013 03:24:43 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-eastlake-rfc5342bis-02.txt> (IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters) to Best Current Practice
In-Reply-To: <20130507110739.12847.4273.idtracker@ietfa.amsl.com>
References: <20130507110739.12847.4273.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Joe Abley <joe.abley@icann.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: Fri, 07 Jun 2013 10:29:19 -0000

At 04:07 07-05-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'IANA Considerations and IETF Protocol and Documentation Usage for IEEE
>    802 Parameters'
>   <draft-eastlake-rfc5342bis-02.txt> as Best Current Practice
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-06-04. Exceptionally, comments may be

Sorry for the late comments.  I'll defer to the authors on what to do 
about them.

In Section 2.1.3:

   "o  must be for standards purposes (either for an IETF Standard or
       other standard related to IETF work),"

The above is not that clear.  I suggest using "IETF Review".  BTW, 
the documentation requirement could also be fulfilled with 
"Specification Required".

Section 2.3.2.1 mentions changes to RFC 2153.  I suggest having an 
"Updates:" for that RFC.

In Section 3.1:

   "o  the assignment must be for standards use (either for an IETF
       Standard or other standard related to IETF work),"

IETF Review (see previous comment about that) could be used.

In Section 4:

   "If different policies from those above are required for such a
    parameter, a BCP or Standards Track RFC must be adopted updating this
    BCP and specifying the new policy and parameter."

"Standards Action" could be used for this.

In Section 5.1 I suggest using "IESG Approval".  BTW, IESG 
Ratification of an Expert Review approval recommendation looks unusual to me.

Regards,
-sm



From prvs=6870181dd3=magnus.westerlund@ericsson.com  Fri Jun  7 07:05:58 2013
Return-Path: <prvs=6870181dd3=magnus.westerlund@ericsson.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 55FD921F8756; Fri,  7 Jun 2013 07:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 yfQrbF2j5QHu; Fri,  7 Jun 2013 07:05:52 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 202DC21F84F5; Fri,  7 Jun 2013 07:05:50 -0700 (PDT)
X-AuditID: c1b4fb25-b7f4c6d000004656-ce-51b1e8b94b16
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id A2.82.18006.9B8E1B15; Fri,  7 Jun 2013 16:05:47 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.279.1; Fri, 7 Jun 2013 16:05:45 +0200
Message-ID: <51B1E8BD.80901@ericsson.com>
Date: Fri, 7 Jun 2013 16:05:49 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Elwyn Davies <elwynd@folly.org.uk>
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
References: <1370477514.4596.9052.camel@mightyatom> <51B1A95B.2030208@ericsson.com> <1370607960.4596.9114.camel@mightyatom>
In-Reply-To: <1370607960.4596.9114.camel@mightyatom>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDLMWRmVeSWpSXmKPExsUyM+Jvre7uFxsDDX6eYrG4+OUIu8XxAzvY La6++sxi8WzjfBaLqcsfsziwenw92c7isWTJTyaPL5c/swUwR3HbJCWWlAVnpufp2yVwZ7xY cp+toEuuYtPRWSwNjBMkuhg5OSQETCTuzzzKAmGLSVy4t56ti5GLQ0jgFKPE1NfNrBDOMkaJ 7U9OsYJU8QpoSkze8IEZxGYRUJG4+6WfEcRmE7CQuPmjkQ3EFhUIljiyfTMLRL2gxMmZT8Bs EQE1ic1fHzCCDGUWWMco8ay3GWyosECYxLwt3UwgtpBAjcThZ6/AbE6g83Z3/maCOE9SYsuL dnYQm1lAT2LK1RZGCFteonnrbGaIXm2JhqYO1gmMQrOQ7J6FpGUWkpYFjMyrGNlzEzNz0suN NjECA/vglt+qOxjvnBM5xCjNwaIkzqvHuzhQSCA9sSQ1OzW1ILUovqg0J7X4ECMTByeI4JJq YAxRMMrVvRF/XOGI73/rjKO/9zSa3rPYkBx1WW75tSRuMUOvP5o7tyZunZ4wR+qV0OyyFAaz k+8/WtaXuineTgUGmOnO74emb+ELnfphSUX6aodPB+69E8lkvtma/XPCZea0xPjrGw/t7vxb cc1CyE8ySuCq6d6CPW+FY87uPLX17Qbn81umLlNiKc5INNRiLipOBACdPXC5PwIAAA==
Cc: General Area Review Team <gen-art@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, "mmusic \(E-mail\)" <mmusic@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: Fri, 07 Jun 2013 14:05:58 -0000

Hi Elwyn,

On 2013-06-07 14:26, Elwyn Davies wrote:
> On Fri, 2013-06-07 at 11:35 +0200, Magnus Westerlund wrote:
>> Hi Elwyn,
>>
>> Many thanks for the detailed review. We will address the nits you have
>> raised, but I cut them out of this reply to focus on the more
>> substantial issues you have brought up.
> .. and thanks for the quick response.
> 
>>
>> See inline below.
> OK.  I think the responses clear those issues.
> 
> I have done a little bit more on the Appendices and liaised a bit with
> Robert Sparks.  'Highlights':
> 
> Appendix F: I missed that the text/parameter format appeared in the
> examples for GET_PARAMETER and SET_PARAMETER. It isn't stated in the
> definitions of these methods what encodings are acceptable for the
> message bodies that may go with these methods and their responses.

Exactly, that is intentional. These methods can use anything that has a
MIME type. Also it has HTTP's mechanisms for determining what formats
one supports.

> Clearly the new text/parameter MIME format is one.  Is it the only one?

It is the only one defined by IETF for this purpose. That is why it is
in the appendix so that RTSP users shall have something to define the
parameters they want in. However, they have to accept the limitations of
a basic text format.

> I guess you could use a application/json or an XML format but I guess
> these would also either have to be called out explicitly in the method
> descriptions or put in as feature extensions.  This needs to be
> clarified in the method descriptions (s13).  The upshot of all this is
> that I think Appendix F needs to be pulled back into Section 20 as
> currently it is the only way to encode the message bodies.

I can agree that the format negotiation for the bodies of
GET/SET_PARAMETER is not clear. I will look at proposing some
improvements of the text related to the handling of method bodies and
their format negotiation.

However, I am not pulling in Appendix F. It is an optional to use format
for parameter value pairs that can be used in these methods, it is not
required. Nor, does the specification define any parameters that are
transferred using this interface. The things that are in the appendix
are not core protocol, they represent either informational things, like
the examples and the state machine. The other appendices are normative
definitions of particular choices for things that can be combined or
used with RTSP, like RTP as media transport.

> 
> Appendix B: I appreciate that the state machine is illustrative and to
> an extent 'abstract'.  However, the tables are really written to
> describe the state machine in the server: the action column mostly
> describes the events that come into the server (apart from the notify
> actions) - sending these 'events' are actions in the client.  The 'real'
> state machine in the both the server and the client has a somewhat more
> complex form: I'd think that there was a STOPPED state in the server
> when the media has reached an end point and not been explictly paused
> and STARTING/PAUSING states in the client while the client waits for
> response to PLAY/PAUSE respectively.  I think a little bit more
> explanation about the dual nature of the columns would solve the
> problem.

There shouldn't be an issue to clarify this nature.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From mcr@sandelman.ca  Fri Jun  7 07:07:14 2013
Return-Path: <mcr@sandelman.ca>
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 DE0C421F8956 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 07:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.392
X-Spam-Level: 
X-Spam-Status: No, score=-2.392 tagged_above=-999 required=5 tests=[AWL=2.207,  BAYES_00=-2.599, GB_I_LETTER=-2]
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 Uw8BspjF9D+l for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 07:07:14 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 98C8F21F8930 for <ietf@ietf.org>; Fri,  7 Jun 2013 07:07:11 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E1C3420184; Fri,  7 Jun 2013 10:20:11 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 2697963A8C; Fri,  7 Jun 2013 10:06:18 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 18A9263A5E; Fri,  7 Jun 2013 10:06:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IAB Chair <iab-chair@iab.org>
Subject: Re: Liaison Statement From the IESG and IAB to ISO/IEC JTC1/SC6 on TISec
In-Reply-To: <E632AAD4-FD08-4C3B-A9BC-0F433109AF11@iab.org>
References: <E632AAD4-FD08-4C3B-A9BC-0F433109AF11@iab.org>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 07 Jun 2013 10:06:18 -0400
Message-ID: <3231.1370613978@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: ipsecme@ietf.org, IETF <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: Fri, 07 Jun 2013 14:07:15 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "IAB" =3D=3D IAB Chair <iab-chair@iab.org> writes:
    IAB> The Liaison statement can be found here:
    IAB> https://datatracker.ietf.org/liaison/1258/=20

    IAB> The Internet Society will forward this liaison statement to
    IAB> ISO/IEC JTC1/SC6 on their letterhead.  This will carry more
    IAB> weight than a statement just from the IESG and IAB because the
    IAB> Internet Society holds a Class A liaison with SC6 on behalf of
    IAB> the IETF.=20

Thanks for this heads up.
The ASCII art diagrams in the PDF at:
    https://datatracker.ietf.org/documents/LIAISON/liaison-2013-06-06-the-i=
esg-and-the-iab-isoiec-jtc1-sc6-liaison-from-the-isoc-to-isoiec-jtc1sc6-and=
-its-national-body-members-in-relation-to-iso-iecjtc1-sc6_n15618-attachment=
-1.pdf

are regretably formatted with non-constant size spaces, so the diagrams
are perhaps much less useful than they could be.  Perhaps this document
could also be made available in .txt format?

    IAB> The TISec proponents have indicated that they believe that
    IAB> TISec is different than IPsec.  This liaison is a response this
    IAB> statement.  It points out how IPsec supports the same
    IAB> functionality, and it encourages=20

    IAB> the TISec proponents to engage in the IETF process to specify
    IAB> the use of their national algorithms in IPsec, as has been done
    IAB> for other national algorithms.=20

I concur strongly with the IAB view, thank you for this.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUbHo2YqHRg3pndX9AQLqqwQAhdu//HAbzs9yvn4ujZGxYS7TVO9tRvpi
kOujCmSFl6SfZFA3kkn9fadZB4UhETATCsAYXpf8iHAV7Cuqebj/NXYFbznYLo3p
0OxQsl7rC9jM4JgXNnkDIz1ppz3rP+f090sFMc9bp+1SB3ORyhQzMzU2vib33ouK
mBXycXF8bsk=
=lubc
-----END PGP SIGNATURE-----
--=-=-=--

From Ted.Lemon@nominum.com  Fri Jun  7 07:40:07 2013
Return-Path: <Ted.Lemon@nominum.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 777B921F96C6 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 07:40:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.765
X-Spam-Level: 
X-Spam-Status: No, score=-106.765 tagged_above=-999 required=5 tests=[AWL=-0.166, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 ePfoOCZW+Ury for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 07:39:59 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 47FEF21F96EB for <ietf@ietf.org>; Fri,  7 Jun 2013 07:39:55 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKUbHwu8Wq++pZqLiy+JXKqoWC1e0ENbOh@postini.com; Fri, 07 Jun 2013 07:39:55 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D8E611B81D6 for <ietf@ietf.org>; Fri,  7 Jun 2013 07:39:54 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CEC7E19005D; Fri,  7 Jun 2013 07:39:54 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 7 Jun 2013 07:39:54 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
Thread-Topic: Weekly posting summary for ietf@ietf.org
Thread-Index: AQHOYzsLp8/g0Ry7ykWpXmTin4ybS5kqYjiAgABmagA=
Date: Fri, 7 Jun 2013 14:39:54 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>
In-Reply-To: <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <876E2E5954D8BF459DF2C855BB76632E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Thomas Narten <narten@us.ibm.com>, "<ietf@ietf.org>" <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: Fri, 07 Jun 2013 14:40:07 -0000

On Jun 7, 2013, at 4:33 AM, Abdussalam Baryun <abdussalambaryun@gmail.com> =
wrote:
> I recommend to add a column for subjects (number of subjects),
> because the number of subject participated in is very important is
> such summary.

It has always been my assumption that the point of this summary was to give=
 us all a reality check when we say too much on the IETF mailing list.   Sa=
ying things on the IETF mailing list is very expensive because it addresses=
 the entire IETF; we should choose our words carefully, and say no more tha=
n is absolutely necessary.   So I think that total volume is really the mos=
t important metric=97I was very upset a month or so ago when I noticed that=
 I'd been the most voluminous poster, and I've tried to avoid being the top=
 poster again since then.


From narten@us.ibm.com  Fri Jun  7 07:49:38 2013
Return-Path: <narten@us.ibm.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 6C45821F9050 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 07:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 n2MlJGFsugWq for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 07:49:31 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 820C521F93F8 for <ietf@ietf.org>; Fri,  7 Jun 2013 07:49:30 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 7 Jun 2013 10:49:29 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 7 Jun 2013 10:49:28 -0400
Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 9ECF36E803A for <ietf@ietf.org>; Fri,  7 Jun 2013 10:49:23 -0400 (EDT)
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r57EnRID310920 for <ietf@ietf.org>; Fri, 7 Jun 2013 10:49:27 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r57EnRtv024980 for <ietf@ietf.org>; Fri, 7 Jun 2013 10:49:27 -0400
Received: from cichlid.raleigh.ibm.com (sig-9-65-142-41.mts.ibm.com [9.65.142.41]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r57EnP8p024776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 7 Jun 2013 10:49:26 -0400
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r57EnN5N008971 for <ietf@ietf.org>; Fri, 7 Jun 2013 10:49:23 -0400
Message-Id: <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Weekly posting summary for ietf@ietf.org
In-reply-to: <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>
Comments: In-reply-to Ted Lemon <Ted.Lemon@nominum.com> message dated "Fri, 07 Jun 2013 14:39:54 -0000."
Date: Fri, 07 Jun 2013 10:49:23 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13060714-7182-0000-0000-00000732538F
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: Fri, 07 Jun 2013 14:49:38 -0000

What the weekly stats really ought to tally up is the readers/postings
ratio, so that folk would get more direct feedback as to whether what they are
posting is actually being read...

My strong suspicion would be that there is strong negative correlation
between frequency of posts and actual readers of those posts...

Also, I suspect that many people do not realize that a significant
chunk of IETF contributers are no longer subscribed to the ietf list
due to signal to noise ratio concerns...

Thomas


From d3e3e3@gmail.com  Fri Jun  7 08:40:27 2013
Return-Path: <d3e3e3@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 6139F21F9814 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 08:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.301
X-Spam-Level: 
X-Spam-Status: No, score=-101.301 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 rg+Dimx4Lb2Y for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 08:40:26 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF4421F9798 for <ietf@ietf.org>; Fri,  7 Jun 2013 08:40:26 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id g12so3481972oah.12 for <ietf@ietf.org>; Fri, 07 Jun 2013 08:40:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=nhsvMtK8XAx+dLuf/x04mBXpXdh7BbLz2nSMfZcOpQg=; b=epnqP0qCvrWOkD79uhteV97No72TO9PUla/kH7Vc84MpUWrqjxtS9d54LkaNw+Wqs0 RfT8T26UCgAZtbtLIOF/UDqomqQj8QuPjPhQrGJRCnoJzB8vRAneYMppt2KZdo78EjKb LvdAwoA0exXDLVOqUt2cg1SzXw1ak+kQmSefvT4GwkirEzUfOlo5GWsMHLyhKJVsvhvd A7MUeZLxIVgG8bZVuPhmTtXwppJIKjqkMRmJLoO4UaVBoc2iXei63MS7GWiCAhASpTi5 K5sDKkmyBt2LGSMHGJShHPADFTrxxYHBSl7UVl1/mKRZUQX3+xz65FGCr2RxAb7oAPa3 z8NA==
X-Received: by 10.182.129.129 with SMTP id nw1mr22100565obb.100.1370619626168;  Fri, 07 Jun 2013 08:40:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.12.65 with HTTP; Fri, 7 Jun 2013 08:40:06 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130607025844.0cae1948@resistor.net>
References: <20130507110739.12847.4273.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130607025844.0cae1948@resistor.net>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 7 Jun 2013 11:40:06 -0400
Message-ID: <CAF4+nEEkoAnZFhr8Qo3xuxZpqF-LRBDzkNZJygV6v80sxJO2Aw@mail.gmail.com>
Subject: Re: Last Call: <draft-eastlake-rfc5342bis-02.txt> (IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters) to Best Current Practice
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Joe Abley <joe.abley@icann.org>, 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: Fri, 07 Jun 2013 15:40:27 -0000

Hi SM,

On Fri, Jun 7, 2013 at 6:24 AM, SM <sm@resistor.net> wrote:
>
> At 04:07 07-05-2013, The IESG wrote:
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'IANA Considerations and IETF Protocol and Documentation Usage for IEEE
>>    802 Parameters'
>>   <draft-eastlake-rfc5342bis-02.txt> as Best Current Practice
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-06-04. Exceptionally, comments may be
>
> Sorry for the late comments.  I'll defer to the authors on what to do
> about them.
>
> In Section 2.1.3:
>
>   "o  must be for standards purposes (either for an IETF Standard or
>       other standard related to IETF work),"
>
> The above is not that clear.  I suggest using "IETF Review".  BTW, the
> documentation requirement could also be fulfilled with "Specification
> Required".

I agree that it is not a precise, perfectly "clear", mechanical rule.
That is why there is a Expert to make judgements.

This part is unchanged from RFC 5342 and actual experience does not
indicate any problem. I believe that, since RFC 5342 came out, seven
code points have been allocated under these provisions, all for single
MAC addresses, and the only request I am aware of that has not yet
been submitted is also for a single MAC address. I think it is silly
to bother the whole IETF (or even the whole IESG) for the allocation
of a single value when over ten million are available. I think it is
enough just to bother the Expert.

> Section 2.3.2.1 mentions changes to RFC 2153.  I suggest having an
> "Updates:" for that RFC.

OK.

> In Section 3.1:
>
>   "o  the assignment must be for standards use (either for an IETF
>       Standard or other standard related to IETF work),"
>
> IETF Review (see previous comment about that) could be used.

See previous response.

> In Section 4:
>
>   "If different policies from those above are required for such a
>    parameter, a BCP or Standards Track RFC must be adopted updating this
>    BCP and specifying the new policy and parameter."
>
> "Standards Action" could be used for this.

I believe the statement is brief, clear, and unambiguous and do not
see any reason to change it.

> In Section 5.1 I suggest using "IESG Approval".  BTW, IESG Ratification of
> an Expert Review approval recommendation looks unusual to me.

I believe the provisions of Section 5.1 are fine. In the extremely
rare cases (perhaps once every five years or so?) where a request
would require IESG Ratification, prior review by the Expert would be
beneficial so the IESG would have the benefit of the Expert's opinion
before they consider the request.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Regards,
> -sm

From andy@yumaworks.com  Fri Jun  7 08:48:06 2013
Return-Path: <andy@yumaworks.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 6B25C21F94D3 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 08:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.144
X-Spam-Level: 
X-Spam-Status: No, score=-1.144 tagged_above=-999 required=5 tests=[AWL=0.833,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 h5x3kPLpzlrd for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 08:48:06 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id F083821F9485 for <ietf@ietf.org>; Fri,  7 Jun 2013 08:48:05 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro2so4846614pbb.27 for <ietf@ietf.org>; Fri, 07 Jun 2013 08:48:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=ja3VtiUSf4cfmNxsPpVMBHMyFvPFgpgHVQAqYgvnRUs=; b=Jl4D+7+HlXzOB/UrXEML+g+otjWfTwANnpWIdWfL6a5GxpgkkAI1dxy/LK17i7fczj eNdkzgYHb8J1FtBF+lKJPj9jdbpZEO1HLNXp9a91U4gCVVcjutAnPKkT77lq8GYiPkjV dplbA3krlgGc2N9hvgV6kmtPz0sMBpVU6iStZphWcQAo24XNpNJx/8uG+olmGez0W7VB tMKwE7mXoxXbJuQds3WY7aiPwfT+BPtnwF40HW+le4gKPW4A30bi82Ac/vzvOBeMQETc Qz6WQrhIugPjWPWnEdhkucvlFBpOThdgTTo0X48/LQepyRKRdiAQMtPNgyhnr/TugEIO g+6w==
MIME-Version: 1.0
X-Received: by 10.66.82.162 with SMTP id j2mr3397936pay.168.1370620085482; Fri, 07 Jun 2013 08:48:05 -0700 (PDT)
Received: by 10.70.87.103 with HTTP; Fri, 7 Jun 2013 08:48:05 -0700 (PDT)
In-Reply-To: <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>
Date: Fri, 7 Jun 2013 08:48:05 -0700
Message-ID: <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
From: Andy Bierman <andy@yumaworks.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: multipart/alternative; boundary=f46d042de633514d1204de925b0b
X-Gm-Message-State: ALoCoQnUzJQ1jbeQHJ83SoEvMMnjdQR+FDyLa2EqUygPp+NaB779si9vG39ZXDKU9Fq+clA8tffB
Cc: "<ietf@ietf.org>" <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: Fri, 07 Jun 2013 15:48:06 -0000

--f46d042de633514d1204de925b0b
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jun 7, 2013 at 7:49 AM, Thomas Narten <narten@us.ibm.com> wrote:

> What the weekly stats really ought to tally up is the readers/postings
> ratio, so that folk would get more direct feedback as to whether what they
> are
> posting is actually being read...
>
> My strong suspicion would be that there is strong negative correlation
> between frequency of posts and actual readers of those posts...
>
> Also, I suspect that many people do not realize that a significant
> chunk of IETF contributers are no longer subscribed to the ietf list
> due to signal to noise ratio concerns...
>
>
So why not move the signal?
Put IETF Last Call mail on last-call@ietf.org and leave this list for
everything else.

I don't really want people counting their bytes when they are concerned
about
a technical issue in an I-D.  It may take several exchanges for a
disagreement
to be resolved.  Social pressure to stay out of the top-N report could have
a negative impact on last call debates.


Thomas
>
>
Andy

--f46d042de633514d1204de925b0b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Fri, Jun 7, 2013 at 7:49 AM, Thomas N=
arten <span dir=3D"ltr">&lt;<a href=3D"mailto:narten@us.ibm.com" target=3D"=
_blank">narten@us.ibm.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
What the weekly stats really ought to tally up is the readers/postings<br>
ratio, so that folk would get more direct feedback as to whether what they =
are<br>
posting is actually being read...<br>
<br>
My strong suspicion would be that there is strong negative correlation<br>
between frequency of posts and actual readers of those posts...<br>
<br>
Also, I suspect that many people do not realize that a significant<br>
chunk of IETF contributers are no longer subscribed to the ietf list<br>
due to signal to noise ratio concerns...<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div>So why not move the signal?</div><div>Put IETF Last =
Call mail on <a href=3D"mailto:last-call@ietf.org">last-call@ietf.org</a> a=
nd leave this list for everything else.</div>
<div><br></div><div>I don&#39;t really want people counting their bytes whe=
n they are concerned about</div><div>a technical issue in an I-D. =A0It may=
 take several exchanges for a disagreement</div><div>to be resolved. =A0Soc=
ial pressure to stay out of the top-N report could have</div>
<div>a negative impact on last call debates.</div><div><br></div><div><br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><font color=3D"#=
888888">
Thomas<br>
<br>
</font></span></blockquote></div><br><div>Andy</div><div><br></div>

--f46d042de633514d1204de925b0b--

From Ted.Lemon@nominum.com  Fri Jun  7 08:52:31 2013
Return-Path: <Ted.Lemon@nominum.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 7953321F86D3 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 08:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.752
X-Spam-Level: 
X-Spam-Status: No, score=-106.752 tagged_above=-999 required=5 tests=[AWL=-0.154, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Vh15iV5YTPd3 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 08:52:23 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 6F0E321F85C9 for <ietf@ietf.org>; Fri,  7 Jun 2013 08:52:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKUbIBsImL6eyQacapOli2EHuM4YMhv0nC@postini.com; Fri, 07 Jun 2013 08:52:17 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AFA3B1B81D6 for <ietf@ietf.org>; Fri,  7 Jun 2013 08:52:15 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A703019005D; Fri,  7 Jun 2013 08:52:15 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 7 Jun 2013 08:52:15 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
Thread-Topic: Weekly posting summary for ietf@ietf.org
Thread-Index: AQHOYzsLp8/g0Ry7ykWpXmTin4ybS5kqYjiAgABmagCAAAKmgIAAEGaAgAABKQA=
Date: Fri, 7 Jun 2013 15:52:14 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>
In-Reply-To: <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751CA801mbx01winnominum_"
MIME-Version: 1.0
Cc: Thomas Narten <narten@us.ibm.com>, "<ietf@ietf.org>" <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: Fri, 07 Jun 2013 15:52:31 -0000

--_000_8D23D4052ABE7A4490E77B1A012B6307751CA801mbx01winnominum_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Jun 7, 2013, at 11:48 AM, Andy Bierman <andy@yumaworks.com<mailto:andy@y=
umaworks.com>> wrote:
So why not move the signal?
Put IETF Last Call mail on last-call@ietf.org<mailto:last-call@ietf.org> an=
d leave this list for everything else.

The discussion still has to happen somewhere.   I certainly am not restrict=
ing my meaningful participation in last calls, but even in that case it is =
important to be restrained and not get into long fruitless discussions, whi=
ch, I am afraid, I am wont to do.


--_000_8D23D4052ABE7A4490E77B1A012B6307751CA801mbx01winnominum_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <E24910CFD7861B4383B2CE5F97888434@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Jun 7, 2013, at 11:48 AM, Andy Bierman &lt;<a href=3D"mailto:andy@y=
umaworks.com">andy@yumaworks.com</a>&gt;&nbsp;wrote:</div>
<blockquote type=3D"cite">
<div style=3D"font-family: Optima; font-size: medium; font-style: normal; f=
ont-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
So why not move the signal?</div>
<div style=3D"font-family: Optima; font-size: medium; font-style: normal; f=
ont-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
Put IETF Last Call mail on<span class=3D"Apple-converted-space">&nbsp;</spa=
n><a href=3D"mailto:last-call@ietf.org">last-call@ietf.org</a><span class=
=3D"Apple-converted-space">&nbsp;</span>and leave this list for everything =
else.</div>
</blockquote>
</div>
<br>
<div>The discussion still has to happen somewhere. &nbsp; I certainly am no=
t restricting my meaningful participation in last calls, but even in that c=
ase it is important to be restrained and not get into long fruitless discus=
sions, which, I am afraid, I am wont
 to do.</div>
<div><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307751CA801mbx01winnominum_--

From tjc@ecs.soton.ac.uk  Fri Jun  7 09:03:24 2013
Return-Path: <tjc@ecs.soton.ac.uk>
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 AACA721F8887 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
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 uD1F0Vquqdgq for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:03:14 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id EEF8F21F8411 for <ietf@ietf.org>; Fri,  7 Jun 2013 09:03:10 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r57G34sd018692 for <ietf@ietf.org>; Fri, 7 Jun 2013 17:03:04 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r57G34sd018692
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1370620984; bh=rmxE1pYBQg5BJpXCXTcozTaLHys=; h=From:Mime-Version:Subject:Date:References:To:In-Reply-To; b=2+dsMX5HI/zS8BWZcFosHpz3M9om8drMk27k4rjEGnGhcCgs1xQ/t/v73nkwJf29D 2mWxCX/KKYOuqQ/0lqDPZgVWXHirvrH0cXfpZnsyz6jKGnONrohHDUWvC0KKD1ZWQY oqjhVjrFsDpEAar9ytmpLYzkJbWmbXC2t4yRmb0g=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p56H340430660463Ib ret-id none; Fri, 07 Jun 2013 17:03:04 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r57G32R1018053 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 7 Jun 2013 17:03:02 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_02CE10AD-F4A1-4E4F-B946-68203EA9BF4E"
Message-ID: <EMEW3|9e374f039865cf00887326b27c809739p56H3403tjc|ecs.soton.ac.uk|F8B44DCF-77F8-45A0-9B6B-9D70755A6BAA@ecs.soton.ac.uk>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Weekly posting summary for ietf@ietf.org
Date: Fri, 7 Jun 2013 17:03:02 +0100
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <F8B44DCF-77F8-45A0-9B6B-9D70755A6BAA@ecs.soton.ac.uk>
To: "ietf@ietf.org list" <ietf@ietf.org>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p56H34043066046300; tid=p56H340430660463Ib; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r57G34sd018692
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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: Fri, 07 Jun 2013 16:03:34 -0000

--Apple-Mail=_02CE10AD-F4A1-4E4F-B946-68203EA9BF4E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On 7 Jun 2013, at 16:52, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Jun 7, 2013, at 11:48 AM, Andy Bierman <andy@yumaworks.com> wrote:
>> So why not move the signal?
>> Put IETF Last Call mail on last-call@ietf.org and leave this list for =
everything else.
>=20
> The discussion still has to happen somewhere.   I certainly am not =
restricting my meaningful participation in last calls, but even in that =
case it is important to be restrained and not get into long fruitless =
discussions, which, I am afraid, I am wont to do.

It's a significant problem for those who *have* to read the threads, in =
particular document authors, WG chairs, and ADs. Hats off to them for =
keeping up with it where they need to.

As another example, the v6ops list has recently also had four threads =
run well over the 100 message count, specifically end to end response =
time, ULA usage, "being careful" about ULAs and the semantic prefix =
thread.=20

Of course, a healthy debate is a good thing, as is having an open =
process for discussion. If we had very few comments that would certainly =
not be good either. But I fear that some valuable contributions are =
either being drowned out, or that some people with valuable input are =
being put off contributing.

Tim=

--Apple-Mail=_02CE10AD-F4A1-4E4F-B946-68203EA9BF4E
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 7 Jun 2013, at 16:52, Ted Lemon &lt;<a href="mailto:Ted.Lemon@nominum.com">Ted.Lemon@nominum.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>On Jun 7, 2013, at 11:48 AM, Andy Bierman &lt;<a href="mailto:andy@yumaworks.com">andy@yumaworks.com</a>&gt;&nbsp;wrote:</div>
<blockquote type="cite">
<div style="font-family: Optima; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
So why not move the signal?</div>
<div style="font-family: Optima; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
Put IETF Last Call mail on<span class="Apple-converted-space">&nbsp;</span><a href="mailto:last-call@ietf.org">last-call@ietf.org</a><span class="Apple-converted-space">&nbsp;</span>and leave this list for everything else.</div>
</blockquote>
</div>
<br>
<div>The discussion still has to happen somewhere. &nbsp; I certainly am not restricting my meaningful participation in last calls, but even in that case it is important to be restrained and not get into long fruitless discussions, which, I am afraid, I am wont
 to do.</div></div></blockquote><br></div><div>It's a significant problem for those who *have* to read the threads, in particular document authors, WG chairs, and ADs. Hats off to them for keeping up with it where they need to.</div><div><br></div><div>As another example, the v6ops list has recently also had four threads run well over the 100 message count, specifically end to end response time, ULA usage, "being careful" about ULAs and the semantic prefix thread.&nbsp;</div><div><br></div><div>Of course, a healthy debate is a good thing, as is having an open process for discussion. If we had very few comments that would certainly not be good either. But&nbsp;I fear that some valuable contributions are either being drowned out, or that some people with valuable input are being put off contributing.</div><div><br></div><div>Tim</div></body></html>
--Apple-Mail=_02CE10AD-F4A1-4E4F-B946-68203EA9BF4E--

From dwm@xpasc.com  Fri Jun  7 09:04:58 2013
Return-Path: <dwm@xpasc.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 71CC521F86F5 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 W1CD4YNlXzNK for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:04:52 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 1785C21F8887 for <ietf@ietf.org>; Fri,  7 Jun 2013 09:04:51 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id C97363F838 for <ietf@ietf.org>; Fri,  7 Jun 2013 16:04:50 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id r57G4o2S008884 for <ietf@ietf.org>; Fri, 7 Jun 2013 09:04:50 -0700
Date: Fri, 7 Jun 2013 09:04:50 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Weekly posting summary for ietf@ietf.org
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>
Message-ID: <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.87-g7939dec
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "<ietf@ietf.org>" <ietf@ietf.org>
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, 07 Jun 2013 16:04:58 -0000

As long as the summary has been brought up ...

I've wondered for some time whether the reported bytes is the
whole message I send included context quotes, or if there is
an attempt by the summary logic to factor out quoted
content.

Dave Morris

From jnc@mercury.lcs.mit.edu  Fri Jun  7 09:09:24 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
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 EB9CD21F93D2 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ud1J-sftKvUg for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:09:14 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB9A21F93D7 for <ietf@ietf.org>; Fri,  7 Jun 2013 09:09:14 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id CD4B418C0CA; Fri,  7 Jun 2013 12:09:13 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Weekly posting summary for ietf@ietf.org
Message-Id: <20130607160913.CD4B418C0CA@mercury.lcs.mit.edu>
Date: Fri,  7 Jun 2013 12:09:13 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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: Fri, 07 Jun 2013 16:09:24 -0000

    > From: David Morris <dwm@xpasc.com>

    > I've wondered for some time whether the reported bytes is the whole
    > message I send included context quotes, or if there is an attempt by
    > the summary logic to factor out quoted content.

I think it's a _feature_ to count the included content, so that people who
(often recursively) top-post on long prior messages, instead of editing down
to just the bit(s) they are replying to, have some negative feedback for that
(irritating) habit.

	Noel

From Ted.Lemon@nominum.com  Fri Jun  7 09:11:20 2013
Return-Path: <Ted.Lemon@nominum.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 89EE521F9638 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.742
X-Spam-Level: 
X-Spam-Status: No, score=-106.742 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 grwEK-AvS+2A for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:11:13 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id CC19721F96ED for <ietf@ietf.org>; Fri,  7 Jun 2013 09:11:13 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKUbIGIR1EHy3Iw7s7npndmovp7gSJE9Kl@postini.com; Fri, 07 Jun 2013 09:11:13 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 52A541B81D4 for <ietf@ietf.org>; Fri,  7 Jun 2013 09:11:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4BD8519005D for <ietf@ietf.org>; Fri,  7 Jun 2013 09:11:13 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 7 Jun 2013 09:11:13 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Weekly posting summary for ietf@ietf.org
Thread-Topic: Weekly posting summary for ietf@ietf.org
Thread-Index: AQHOYzsLp8/g0Ry7ykWpXmTin4ybS5kqYjiAgABmagCAAAKmgIAAEGaAgAABKQCAAAOFAIAAAcgA
Date: Fri, 7 Jun 2013 16:11:12 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751CA93F@mbx-01.win.nominum.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com>
In-Reply-To: <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6653E5314A73644789691FEFF1F1A570@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Fri, 07 Jun 2013 16:11:20 -0000

On Jun 7, 2013, at 12:04 PM, David Morris <dwm@xpasc.com> wrote:
> I've wondered for some time whether the reported bytes is the
> whole message I send included context quotes, or if there is
> an attempt by the summary logic to factor out quoted
> content.

A penalty for top-posting sounds okay to me!


From andy@yumaworks.com  Fri Jun  7 09:11:50 2013
Return-Path: <andy@yumaworks.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 85F7821F965B for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.56
X-Spam-Level: 
X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[AWL=0.416,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 vwR0c6wprAnv for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:11:39 -0700 (PDT)
Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.171]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF8421F96EC for <ietf@ietf.org>; Fri,  7 Jun 2013 09:11:37 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id y14so2101082pdi.30 for <ietf@ietf.org>; Fri, 07 Jun 2013 09:11:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=EnUQTiHRHkQsK0vysUUuI8IIBjtsePsa6CYGwDmtA0A=; b=TqNdWUp4E4lbslICB/j7dpCWeefQ5gym5V9GgeEW0wNrcZLH7i0uAlspBHTR25Jfj7 O1Abx8MAlAKE3mC/HCmNCSFp1BneulmcsaX+E/UYXDkP8u9TPnsZeqbyCEyGvNaVlj8V yZ3UjFO8JavHN31QP7qfOfIO2DbfOfMk3llWLHBaywqfpH0zoiQKwNFQSv+jw5Wjp+vC CE84GgiNS4A3B58HlLd6QhcU/tDBdCafOytMFBoP4LyA8/exyX+Rknmr9SunTkBnT5/k wpOZqa1c1z/afiafuuZtI6dzMbOl3ticEkZ1MKgyv8ccLdx66i7W9tex1eQuZydqej8D 1iZw==
MIME-Version: 1.0
X-Received: by 10.66.234.226 with SMTP id uh2mr1340125pac.38.1370621496679; Fri, 07 Jun 2013 09:11:36 -0700 (PDT)
Received: by 10.70.87.103 with HTTP; Fri, 7 Jun 2013 09:11:36 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>
Date: Fri, 7 Jun 2013 09:11:36 -0700
Message-ID: <CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
From: Andy Bierman <andy@yumaworks.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=047d7b15a4a16e71e804de92af83
X-Gm-Message-State: ALoCoQnd2tM/v3e88xCONPUZmXVe2ftRxvAjzYRrYfZZsoYoD5KPjYp7CV1DU6z5mmcWnjHEuRIC
Cc: Thomas Narten <narten@us.ibm.com>, "<ietf@ietf.org>" <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: Fri, 07 Jun 2013 16:11:50 -0000

--047d7b15a4a16e71e804de92af83
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jun 7, 2013 at 8:52 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

>  On Jun 7, 2013, at 11:48 AM, Andy Bierman <andy@yumaworks.com> wrote:
>
>  So why not move the signal?
>  Put IETF Last Call mail on last-call@ietf.org and leave this list for
> everything else.
>
>
> The discussion still has to happen somewhere.   I certainly am not
> restricting my meaningful participation in last calls, but even in that
> case it is important to be restrained and not get into long fruitless
> discussions, which, I am afraid, I am wont to do.
>
>

Some people consider the last call discussions to be signal
and the rest (vast majority) of discussions to be noise.
They would subscribe to a last-call mailing list, but not this one.


Andy

--047d7b15a4a16e71e804de92af83
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Fri, Jun 7, 2013 at 8:52 AM, Ted Lemo=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com" target=3D"=
_blank">Ted.Lemon@nominum.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">




<div style=3D"word-wrap:break-word">
<div>
<div>On Jun 7, 2013, at 11:48 AM, Andy Bierman &lt;<a href=3D"mailto:andy@y=
umaworks.com" target=3D"_blank">andy@yumaworks.com</a>&gt;=A0wrote:</div>
<blockquote type=3D"cite">
<div style=3D"font-family:Optima;font-size:medium;font-style:normal;font-va=
riant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;te=
xt-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px">

So why not move the signal?</div>
<div style=3D"font-family:Optima;font-size:medium;font-style:normal;font-va=
riant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;te=
xt-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px">

Put IETF Last Call mail on<span>=A0</span><a href=3D"mailto:last-call@ietf.=
org" target=3D"_blank">last-call@ietf.org</a><span>=A0</span>and leave this=
 list for everything else.</div>
</blockquote>
</div>
<br>
<div>The discussion still has to happen somewhere. =A0 I certainly am not r=
estricting my meaningful participation in last calls, but even in that case=
 it is important to be restrained and not get into long fruitless discussio=
ns, which, I am afraid, I am wont
 to do.</div>
<div><br>
</div>
</div>

</blockquote></div><br><div><br></div><div>Some people consider the last ca=
ll discussions to be signal</div><div>and the rest (vast majority) of discu=
ssions to be noise.</div><div>They would subscribe to a last-call mailing l=
ist, but not this one.</div>
<div><br></div><div><br></div><div>Andy</div><div><br></div>

--047d7b15a4a16e71e804de92af83--

From joelja@bogus.com  Fri Jun  7 09:13:39 2013
Return-Path: <joelja@bogus.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 59B1621F9600 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.288
X-Spam-Level: 
X-Spam-Status: No, score=-102.288 tagged_above=-999 required=5 tests=[AWL=-0.289, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
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 c+d4g967HpX6 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:13:39 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id E27AF21F92EC for <ietf@ietf.org>; Fri,  7 Jun 2013 09:13:38 -0700 (PDT)
Received: from joels-MacBook-Air.local ([196.38.103.34]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r57GCfZZ056669 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 7 Jun 2013 16:12:45 GMT (envelope-from joelja@bogus.com)
Message-ID: <51B20674.80704@bogus.com>
Date: Fri, 07 Jun 2013 18:12:36 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: Weekly posting summary for ietf@ietf.org
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>	<CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>	<201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>	<CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>	<F8B44DCF-77F8-45A0-9B6B-9D70755A6BAA@ecs.soton.ac.uk> <EMEW3|9e374f039865cf00887326b27c809739p56H3403tjc|ecs.soton.ac.uk|F8B44DCF-77F8-45A0-9B6B-9D70755A6BAA@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|9e374f039865cf00887326b27c809739p56H3403tjc|ecs.soton.ac.uk|F8B44DCF-77F8-45A0-9B6B-9D70755A6BAA@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 07 Jun 2013 16:12:46 +0000 (UTC)
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: Fri, 07 Jun 2013 16:13:39 -0000

On 6/7/13 6:03 PM, Tim Chown wrote:
> On 7 Jun 2013, at 16:52, Ted Lemon <Ted.Lemon@nominum.com 
> <mailto:Ted.Lemon@nominum.com>> wrote:
>
>> On Jun 7, 2013, at 11:48 AM, Andy Bierman <andy@yumaworks.com 
>> <mailto:andy@yumaworks.com>> wrote:
>>> So why not move the signal?
>>> Put IETF Last Call mail onlast-call@ietf.org 
>>> <mailto:last-call@ietf.org>and leave this list for everything else.
>>
>> The discussion still has to happen somewhere.   I certainly am not 
>> restricting my meaningful participation in last calls, but even in 
>> that case it is important to be restrained and not get into long 
>> fruitless discussions, which, I am afraid, I am wont to do.
>
> It's a significant problem for those who *have* to read the threads, 
> in particular document authors, WG chairs, and ADs. Hats off to them 
> for keeping up with it where they need to.
>
> As another example, the v6ops list has recently also had four threads 
> run well over the 100 message count, specifically end to end response 
> time, ULA usage, "being careful" about ULAs and the semantic prefix 
> thread.
v6ops had a single draft which attracted ~1100 messages over the course 
of a year so this isn't new or unusual over there. A small number of 
posters tend to be the majority of the volume on several topics, so if 
you're reading to understand the positions of the working group or to 
measure consensus on the list some judicious sorting is required.
> Of course, a healthy debate is a good thing, as is having an open 
> process for discussion. If we had very few comments that would 
> certainly not be good either. But I fear that some valuable 
> contributions are either being drowned out, or that some people with 
> valuable input are being put off contributing.

> Tim


From dwm@xpasc.com  Fri Jun  7 09:23:46 2013
Return-Path: <dwm@xpasc.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 9674521F8EBC for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level: 
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 VhfqDvRCfrff for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:23:40 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 12D3521F86D3 for <ietf@ietf.org>; Fri,  7 Jun 2013 09:23:36 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 9E5893F9C7 for <ietf@ietf.org>; Fri,  7 Jun 2013 16:23:35 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id r57GNZJM009063 for <ietf@ietf.org>; Fri, 7 Jun 2013 09:23:35 -0700
Date: Fri, 7 Jun 2013 09:23:35 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: Weekly posting summary for ietf@ietf.org
In-Reply-To: <20130607160913.CD4B418C0CA@mercury.lcs.mit.edu>
Message-ID: <alpine.LRH.2.01.1306070917140.4180@egate.xpasc.com>
References: <20130607160913.CD4B418C0CA@mercury.lcs.mit.edu>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.87-g7939dec
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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, 07 Jun 2013 16:23:47 -0000

On Fri, 7 Jun 2013, Noel Chiappa wrote:

>     > From: David Morris <dwm@xpasc.com>
> 
>     > I've wondered for some time whether the reported bytes is the whole
>     > message I send included context quotes, or if there is an attempt by
>     > the summary logic to factor out quoted content.
> 
> I think it's a _feature_ to count the included content, so that people who
> (often recursively) top-post on long prior messages, instead of editing down
> to just the bit(s) they are replying to, have some negative feedback for that
> (irritating) habit.

For now, I'm just trying to confirm my impression of the data. Folks who
don't make a case/case choice as to inline/top and removing chaff and
unneeded context probably aren't going to care where they stand on the
total byte count issue.

From tjc@ecs.soton.ac.uk  Fri Jun  7 09:33:47 2013
Return-Path: <tjc@ecs.soton.ac.uk>
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 A42F121F961B for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 agIpA5cX9Eu2 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:33:46 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id C6B6F21F9600 for <ietf@ietf.org>; Fri,  7 Jun 2013 09:33:43 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r57GXbZN026680 for <ietf@ietf.org>; Fri, 7 Jun 2013 17:33:37 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r57GXbZN026680
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1370622817; bh=Sylvh36nyNCpbMJbNgTwpI7pNs8=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=c5dUYCdmPSln8xcib/lwO3hfJ0FYlg6buzYB8nCewy1H4rK7zydBkruy0n955mhCI hQ4/78sDdqaoqBNB5mhMw4RkMBfzo7OwWE+sZMLJGA9hhiI4rxduOwjJknX0/hNhq7 0K5++KxsHEhOND2EfQpiEGlESEvMXZtPWoHjMdqw=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p56HXb04306608270F ret-id none; Fri, 07 Jun 2013 17:33:37 +0100
Received: from dhcp-207-6.wireless.soton.ac.uk (dhcp-207-6.wireless.soton.ac.uk [152.78.207.6]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r57GXaMZ000458 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 7 Jun 2013 17:33:36 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Weekly posting summary for ietf@ietf.org
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <51B20674.80704@bogus.com>
Date: Fri, 7 Jun 2013 17:33:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|ad26a296a779294903d295675390a663p56HXb03tjc|ecs.soton.ac.uk|2485C924-84D9-4BC1-8616-631A63DA68E8@ecs.soton.ac.uk>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>	<CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>	<201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>	<CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>	<F8B44DCF-77F8-45A0-9B6B-9D70755A6BAA@ecs.soton.ac.uk> <EMEW3|9e374f039865cf00887326b27c809739p56H3403tjc|ecs.soton.ac.uk|F8B44DCF-77F8-45A0-9B6B-9D70755A6BAA@ecs.soton.ac.uk> <51B20674.80704@bogus.com> <2485C924-84D9-4BC1-8616-631A63DA68E8@ecs.soton.ac.uk>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p56HXb043066082700; tid=p56HXb04306608270F; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r57GXbZN026680
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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: Fri, 07 Jun 2013 16:33:48 -0000

On 7 Jun 2013, at 17:12, joel jaeggli <joelja@bogus.com> wrote:

> On 6/7/13 6:03 PM, Tim Chown wrote:
>>=20
>> As another example, the v6ops list has recently also had four threads =
run well over the 100 message count, specifically end to end response =
time, ULA usage, "being careful" about ULAs and the semantic prefix =
thread.
> v6ops had a single draft which attracted ~1100 messages over the =
course of a year so this isn't new or unusual over there. A small number =
of posters tend to be the majority of the volume on several topics, so =
if you're reading to understand the positions of the working group or to =
measure consensus on the list some judicious sorting is required.

Indeed.  Sorting and sifting through 500+ emails about one homenet topic =
over on 6man was similarly challenging (for the homenet arch text).  And =
many of those long v6ops threads were/are relevant to that.

It would be nice to determine some way to keep discussions open, without =
creating unnecessary volume, and repeating already raised arguments.=20

Maybe the answer isn't email for judging consensus. As an outsider, I've =
seen the IESG/AD system, which seems to essentially allow positions on =
drafts to be expressed, and easily viewed at a glance. Maybe that's part =
of the answer, somehow. Some "position" view on a draft, that people can =
update/edit as the list discussion goes on, that becomes more useful "at =
a glance" for WG chairs and document editors?

We could continue as is with emails, but I've heard of a number of (very =
wise and valued) past contributors who no longer express their views, =
because of the problem of volume.

Or maybe it's not a valid concern.

Tim


From narten@us.ibm.com  Fri Jun  7 09:51:24 2013
Return-Path: <narten@us.ibm.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 1073521F9943 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 fomUBXgpMJOB for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 09:51:18 -0700 (PDT)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by ietfa.amsl.com (Postfix) with ESMTP id D9D0F21F9920 for <ietf@ietf.org>; Fri,  7 Jun 2013 09:51:17 -0700 (PDT)
Received: from /spool/local by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 7 Jun 2013 10:51:15 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 7 Jun 2013 10:51:12 -0600
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 557341FF005A for <ietf@ietf.org>; Fri,  7 Jun 2013 10:46:00 -0600 (MDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r57GpKnJ149210 for <ietf@ietf.org>; Fri, 7 Jun 2013 10:51:21 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r57GpBUK020073 for <ietf@ietf.org>; Fri, 7 Jun 2013 10:51:11 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-142-41.mts.ibm.com [9.65.142.41]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r57Gp9JC019944 for <ietf@ietf.org>; Fri, 7 Jun 2013 10:51:10 -0600
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r57Gp9Sf028501 for <ietf@ietf.org>; Fri, 7 Jun 2013 12:51:09 -0400
Message-Id: <201306071651.r57Gp9Sf028501@cichlid.raleigh.ibm.com>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Weekly posting summary for ietf@ietf.org
In-reply-to: <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com>
Comments: In-reply-to David Morris <dwm@xpasc.com> message dated "Fri, 07 Jun 2013 09:04:50 -0700."
Date: Fri, 07 Jun 2013 12:51:09 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13060716-7282-0000-0000-000018064814
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: Fri, 07 Jun 2013 16:51:24 -0000

> I've wondered for some time whether the reported bytes is the
> whole message I send included context quotes, or if there is
> an attempt by the summary logic to factor out quoted
> content.

Original script is here:
http://www.hactrn.net/hacks/mh-list-traffic/mh-list-traffic

I don't think I've modified it other than to keep it running under my
local setup.

>From my perspective, the intention/usefulness of the weekly posting is
to give folk a high-level view of who is posting and how often. It is
not uncommon to see certain individuals stand out. In some cases, that
makes perfect sense -- and the signal level is high. In other cases,
it shows (IMO) people who are too quick to post and who (too often)
say predictable things if you've read previous threads on the same
general topic. YMMV.

Beyond that (e.g., tweaking the priorities of how rankings are done),
I don't see much point.  Different people will have different opinions
on what to give priority to, and this is ultimately a judgement call.

Thomas


From ogier@earthlink.net  Thu Jun  6 15:04:21 2013
Return-Path: <ogier@earthlink.net>
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 9201511E8120 for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 15:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 V-NO+IE9vBCm for <ietf@ietfa.amsl.com>; Thu,  6 Jun 2013 15:04:16 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 762BC11E80AD for <ietf@ietf.org>; Thu,  6 Jun 2013 15:04:16 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=GoUxipFZunEZSUrYcfznewXqk2GF9ASVW5JdmpuyqQ59jS4J4JcABFYILtrLZGhg; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [66.81.254.30] by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <ogier@earthlink.net>) id 1UkiI1-0007Hw-4N; Thu, 06 Jun 2013 18:04:15 -0400
Message-ID: <51B1087A.2060100@earthlink.net>
Date: Thu, 06 Jun 2013 15:08:58 -0700
From: Richard Ogier <ogier@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org, abdussalambaryun@gmail.com
Subject: Re: Last Call: <draft-ietf-ospf-manet-single-hop-mdr-03.txt> (Use of OSPF-MDR in Single-Hop Broadcast Networks) to Experimental RFC
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: a073897a9455599e74bf435c0eb9d478e549f294dc8ae39dfb97adb6eac63003a0840c0aa92b0104350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 66.81.254.30
X-Mailman-Approved-At: Fri, 07 Jun 2013 10:17:17 -0700
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: Thu, 06 Jun 2013 22:04:21 -0000

AB,

As Joel pointed out, your questions should have been raised during the 
OSPF WG Last Call, which you did not participate in. You 
(inappropriately) posted questions on the MANET WG list after the OSPF 
WGLC was complete, and several people responded, most of them stating 
that RFC 5444 is not required for this document:

http://www.ietf.org/mail-archive/web/manet/current/msg15403.html
http://www.ietf.org/mail-archive/web/manet/current/msg15406.html
http://www.ietf.org/mail-archive/web/manet/current/msg15407.html
http://www.ietf.org/mail-archive/web/manet/current/msg15408.html

Although I should not be required to respond to your questions at this 
point, I will provide a few additional reasons why RFC 5444 and DLEP are 
not relevant for this document. (These reasons also apply to the 
parallel document draft-ietf-ospf-manet-single-hop-or-02.)

1. This draft does not propose a new interface, it only describes how 
the interface previously specified in RFC 5614 (and RFC 5820 for the 
other draft) can be configured in the special case of a single-hop 
MANET. Therefore, your comments should have been directed to RFC 5614 
(and RFC 5820).

2. RFCs 5614 and 5820 describe MANET extensions to OSPF, and one of the 
goals was to minimize changes to OSPF, so we decided to use OSPF packet 
formats (with minimal changes), rather than MANET packet formats that 
were designed without OSPF in mind. (This point is also made in the last 
message listed above.)

On the other hand, these are experimental documents, so your questions 
about using RFC 5444 and DLEP may be valid for future modifications to 
the proposed MANET extensions of OSPF (both RFCs 5614 and 5820). But 
they are not valid for draft-ietf-ospf-manet-single-hop-mdr or 
draft-ietf-ospf-manet-single-hop-or, not only because these two drafts 
have already completed WG Last Call, but also because they only describe 
how to configure RFCs 5614 and 5820 for the special case of a single-hop 
network.

Richard

On 6/6/13 3:15 AM, Abdussalam Baryun wrote:

 > I send my request to the editors including questions but no reply from
 > them to me. The thread [1] raised some issues, which is not mentioned
 > in the I-D. The message [2] was ignored not answered (this is last
 > reminder). The message [3] proposes using RFC5444 into this I-D, or
 > raise the question of why not using MANET packet format within MANET
 > domains (I need an answer).
 >
 > [1] http://www.ietf.org/mail-archive/web/manet/current/msg15400.html
 > [2] http://www.ietf.org/mail-archive/web/manet/current/msg15412.html
 > [3] http://www.ietf.org/mail-archive/web/manet/current/msg15418.html
 >
 > The I-D SHOULD not go forward if it still ignores the IETF community 
questions.
 >
 > Regards
 > AB
 >
 > On 6/5/13, The IESG <iesg-secretary@ietf.org> wrote:
 >> The IESG has received a request from the Open Shortest Path First 
IGP WG
 >> (ospf) to consider the following document:
 >> - 'Use of OSPF-MDR in Single-Hop Broadcast Networks'
 >> <draft-ietf-ospf-manet-single-hop-mdr-03.txt> as Experimental RFC
 >>
 >> The IESG plans to make a decision in the next few weeks, and solicits
 >> final comments on this action. Please send substantive comments to the
 >> ietf@ietf.org mailing lists by 2013-06-19. Exceptionally, comments 
may be
 >> sent to iesg@ietf.org instead. In either case, please retain the
 >> beginning of the Subject line to allow automated sorting.
 >>
 >> Abstract
 >>
 >>
 >> RFC 5614 (OSPF-MDR) extends OSPF to support mobile ad hoc networks
 >> (MANETs) by specifying its operation on the new OSPF interface of type
 >> MANET. This document describes the use of OSPF-MDR in a single-hop
 >> broadcast network, which is a special case of a MANET in which each
 >> router is a (one-hop) neighbor of each other router. Unlike an OSPF
 >> broadcast interface, such an interface can have a different cost
 >> associated with each neighbor. The document includes configuration
 >> recommendations and simplified mechanisms that can be used in 
single-hop
 >> broadcast networks.
 >>
 >>
 >>
 >>
 >> The file can be obtained via
 >> http://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/
 >>
 >> IESG discussion can be tracked via
 >> 
http://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/ballot/ 

 >>
 >>
 >> No IPR declarations have been submitted directly on this I-D.



From elwynd@folly.org.uk  Fri Jun  7 05:26:10 2013
Return-Path: <elwynd@folly.org.uk>
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 3EF0721F8B35; Fri,  7 Jun 2013 05:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
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 PyqxrcKbqLXM; Fri,  7 Jun 2013 05:26:06 -0700 (PDT)
Received: from a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id B629421F8ADC; Fri,  7 Jun 2013 05:26:05 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtp (Exim 4.77) (envelope-from <elwynd@folly.org.uk>) id 1Ukvk2-00081p-C1; Fri, 07 Jun 2013 13:26:02 +0100
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
From: Elwyn Davies <elwynd@folly.org.uk>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <51B1A95B.2030208@ericsson.com>
References: <1370477514.4596.9052.camel@mightyatom> <51B1A95B.2030208@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
Organization: Folly Consulting
Date: Fri, 07 Jun 2013 13:26:00 +0100
Message-Id: <1370607960.4596.9114.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 07 Jun 2013 10:17:17 -0700
Cc: General Area Review Team <gen-art@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, "mmusic \(E-mail\)" <mmusic@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: Fri, 07 Jun 2013 12:26:10 -0000

On Fri, 2013-06-07 at 11:35 +0200, Magnus Westerlund wrote:
> Hi Elwyn,
>=20
> Many thanks for the detailed review. We will address the nits you have
> raised, but I cut them out of this reply to focus on the more
> substantial issues you have brought up.
.. and thanks for the quick response.

>=20
> See inline below.
OK.  I think the responses clear those issues.

I have done a little bit more on the Appendices and liaised a bit with
Robert Sparks.  'Highlights':

Appendix F: I missed that the text/parameter format appeared in the
examples for GET_PARAMETER and SET_PARAMETER. It isn't stated in the
definitions of these methods what encodings are acceptable for the
message bodies that may go with these methods and their responses.
Clearly the new text/parameter MIME format is one.  Is it the only one?
I guess you could use a application/json or an XML format but I guess
these would also either have to be called out explicitly in the method
descriptions or put in as feature extensions.  This needs to be
clarified in the method descriptions (s13).  The upshot of all this is
that I think Appendix F needs to be pulled back into Section 20 as
currently it is the only way to encode the message bodies.

Appendix B: I appreciate that the state machine is illustrative and to
an extent 'abstract'.  However, the tables are really written to
describe the state machine in the server: the action column mostly
describes the events that come into the server (apart from the notify
actions) - sending these 'events' are actions in the client.  The 'real'
state machine in the both the server and the client has a somewhat more
complex form: I'd think that there was a STOPPED state in the server
when the media has reached an end point and not been explictly paused
and STARTING/PAUSING states in the client while the client waits for
response to PLAY/PAUSE respectively.  I think a little bit more
explanation about the dual nature of the columns would solve the
problem.

Appendix C: Pending.

Regards,
Elwyn
>=20
> On 2013-06-06 02:11, Elwyn Davies wrote:
> > I am an additional Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >=20
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >=20
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >=20
> > Document: draft-ietf-mmusic-rfc2326bis
> > Reviewer: Elwyn Davies
> > Review Date: 5 June 2013
> > IETF LC End Date: 5 JUne 2013
> > IESG Telechat date: (if known) -
> >=20
> > Summary:
> > Almost ready.  Generally this is an excellent and well written document=
,
> > particularly given its size.  There are a few minor issues to sort out
> > mainly at the nit level and some consistency issues to fix up.  The two
> > issues that I have brought out below are really at what the IESG would
> > call 'DISCUSS-DISCUSS' level.  The issue of URI scheme redefinition may
> > well have already been cleared by the URI expert - the draft does not d=
o
> > itself any favours here by failing to explain what the syntax changes
> > are in s4.2; this raises immediate red flags that only start to fade a
> > couple of hundred pages later. The rudimentary nature of the pipeline
> > mechanism is carried over from RTSP 1.0.  I'd like to be sure that this
> > has been properly discussed in the WG as it looks pretty flaky to an
> > outsider.  There are several inconsistencies between various lists of
> > headers that need sorting out and there is no definition of
> > Proxy-Authorization in the ABNF.
> >=20
> > There are also a fairly large number of editorial nits but these are al=
l
> > localized and trivial to fix.  Finally I have't had time to review the
> > appendices (maybe there will be a follow up).
> >=20
> > Robert Sparks is the main gen-art reviewer for the document; he asked
> > for additional eyes on the document given the size and his RAI
> > background.  Having (just) seen his review, I think we have both picked
> > up on the URI scheme and pipeline issues.  I am not sure that I concur
> > with his view that there is significant normative material in the
> > appendices - AFAICS the main protocol definition *is* in the main body
> > of the document and the bits especiially in Appendices B and C are not
> > the core of the protocol.  However this is based on a very cursory
> > glance through something like 75 pages of the document.  However, I do
> > concur with Robert's view that it needs a security expert to check the
> > security stories.
> >=20
> > Major(ish) issues:
> > s4.2: This section (re-)defines the URI schemes "rtsp" and "rtsps". The=
=20
> > last sentence of para 1 states that the 'details of the syntax' of the=20
> > URIs 'have been changed'.  Is this a reasonable thing to do? Has this=20
> > been cleared with the URI expert reviewer?  I am not entirely clear wha=
t=20
> > the change involves and the draft doesn't explain exactly how the synta=
x=20
> > has been altered  and its consequences (if any) in s4.2.  Some details
> > are finally given in s22.14.
>=20
> These syntax changes where discussed in the reviews I got on the URI
> list. That resulted in the explicitness in the template, but I forgot
> about adding anything into Section 4.2. I see no issue with adding the
> following clarification to Section 4.2:
>=20
>    The details of the syntax of "rtsp" and "rtsps" URIs has been changed
>    from RTSP 1.0.  These changes are:
>=20
>    o  Support for IPV6 literal in host part and future IP literals
>       through RFC 3986 defined mechanism.
>=20
>    o  A new relative format to use in the RTSP protocol elements that is
>       not required to start with "/".
>=20
>    Neither should have any significant impact on interoperability.  If
>    one is required to use IPv6 literals to reach an RTSP server, then
>    that RTSP server must be IPv6 capable, and RTSP 1.0 is not a fully
>    IPv6 capable protocol.  Thus, RTSP 2.0 support will be needed anyway.
>    The second change will only occur in RTSP messages, that are
>    explicitly identified as being RTSP 2.0 messages, thus a RTSP 1.0
>    only agent will not be required to parse this variant.
>=20
> I hope this makes it clear that these syntax changes is unlikely to hurt
> the interoperability.
>=20
> >=20
> >=20
> > Minor issues:
> > s11, para 3: I guess that the WG decided that sticking with the RTSP 1.=
0
> > model of sending requests and worrying about success of prior prior
> > pipelined requests was the right answer.  I would have thought that it
> > might have been helpful to provide qualifiers on the Pipelined-Requests
> > header that allowed subsequent requests to be suppressed unless the
> > previous command resulted in one of a given set of status codes with a
> > 'reset' option to 'restart' the pipeline.  It strikes me that this woul=
d
> > avoid some irritating need to work out how to recover from arbitrary
> > failures in a command chain in a client.
> >=20
>=20
> I assume you mean this Section 12 paragraph:
>=20
>    If a pipelined request builds on the successful completion of one or
>    more prior requests the requester must verify that all requests were
>    executed as expected.  A common example will be two SETUP requests
>    and a PLAY request.  In case one of the SETUP fails unexpectedly, the
>    PLAY request can still be successfully executed.  However, the
>    resulting presentation will not be as expected by the requesting
>    client, as only a single media instead of two will be played.  In
>    this case the client can send a PAUSE request, correct the failing
>    SETUP request and then request it to be played.
>=20
> I think I agree with your assessment, that it would have been nice.
> However, we should have thought of that when we introduced this type of
> pipelining 7 years ago. Making any changes to this at this stage is
> counter productive. The reality is that all the "nice" features and
> necessary clarifications has been retrofitted into RTSP 1.0 by the ones
> that have been using RTSP 1.0. So changing anything will separate the
> RTSP 1.0 and RTSP 2.0 implementations. The good thing is that I can't
> remember any substantial complaints about this issue.
>=20
> I hope this resolves your comments.
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From elwynd@folly.org.uk  Fri Jun  7 08:40:19 2013
Return-Path: <elwynd@folly.org.uk>
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 586AB21F9798; Fri,  7 Jun 2013 08:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=0.698,  BAYES_00=-2.599]
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 TBguRDe8Pqk6; Fri,  7 Jun 2013 08:40:14 -0700 (PDT)
Received: from a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id C662021F9732; Fri,  7 Jun 2013 08:40:07 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtp (Exim 4.77) (envelope-from <elwynd@folly.org.uk>) id 1Ukylo-0003mK-T1; Fri, 07 Jun 2013 16:40:05 +0100
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
From: Elwyn Davies <elwynd@folly.org.uk>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <51B1E8BD.80901@ericsson.com>
References: <1370477514.4596.9052.camel@mightyatom> <51B1A95B.2030208@ericsson.com> <1370607960.4596.9114.camel@mightyatom> <51B1E8BD.80901@ericsson.com>
Content-Type: text/plain
Organization: Folly Consulting
Date: Fri, 07 Jun 2013 16:40:02 +0100
Message-Id: <1370619602.4596.9175.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 07 Jun 2013 10:17:17 -0700
Cc: General Area Review Team <gen-art@ietf.org>, IETF discussion <ietf@ietf.org>, "mmusic \(E-mail\)" <mmusic@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.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: Fri, 07 Jun 2013 15:40:19 -0000

On Fri, 2013-06-07 at 16:05 +0200, Magnus Westerlund wrote:

> > Appendix F: I missed that the text/parameter format appeared in the
> > examples for GET_PARAMETER and SET_PARAMETER. It isn't stated in the
> > definitions of these methods what encodings are acceptable for the
> > message bodies that may go with these methods and their responses.
> 
> Exactly, that is intentional. These methods can use anything that has a
> MIME type. Also it has HTTP's mechanisms for determining what formats
> one supports.
> 
> > Clearly the new text/parameter MIME format is one.  Is it the only one?
> 
> It is the only one defined by IETF for this purpose. That is why it is
> in the appendix so that RTSP users shall have something to define the
> parameters they want in. However, they have to accept the limitations of
> a basic text format.
> 
> > I guess you could use a application/json or an XML format but I guess
> > these would also either have to be called out explicitly in the method
> > descriptions or put in as feature extensions.  This needs to be
> > clarified in the method descriptions (s13).  The upshot of all this is
> > that I think Appendix F needs to be pulled back into Section 20 as
> > currently it is the only way to encode the message bodies.
> 
> I can agree that the format negotiation for the bodies of
> GET/SET_PARAMETER is not clear. I will look at proposing some
> improvements of the text related to the handling of method bodies and
> their format negotiation.
Good. I don't see where the server tells what formats it accepts for
either GET_PARAMETER or SET_PARAMETER.  Also the Accept spec doesn't say
anything about SET_PARAMETER.  AFAICS the client could tell the server
what formats it accepts as a side-effect of DESCRIBE but that's a bit
arcane - and it is not clear how you would separate the formats for
DESCRIBE from those for GET_PARAM and SET_PARAM.
> 
> However, I am not pulling in Appendix F. It is an optional to use format
> for parameter value pairs that can be used in these methods, it is not
> required. Nor, does the specification define any parameters that are
> transferred using this interface. The things that are in the appendix
> are not core protocol, they represent either informational things, like
> the examples and the state machine. The other appendices are normative
> definitions of particular choices for things that can be combined or
> used with RTSP, like RTP as media transport.
> 
OK, it is possible to use GET_PARAM for basic requirements without using
message bodies, so you can get away without defining a lowest common
denominator format. However, the use of message bodies for SET_PARAM is
RECOMMENDED so it seems a little odd not to ensure that server and
client will have at least one format in common. (And its not as if we
are dealing with a hugely complicated bit of spec for
text/parameters! :-) ).  Then, given the example in GET_PARAMETER it
seems sensible to advise implementing text/parameters as the default for
GET_PARAM also.

/Elwyn




From mcr@sandelman.ca  Fri Jun  7 10:48:59 2013
Return-Path: <mcr@sandelman.ca>
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 0DCA521F9950 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 10:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599]
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 1o-CAd6M1aoL for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 10:48:58 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id DB82D21F994F for <ietf@ietf.org>; Fri,  7 Jun 2013 10:48:56 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E685D20184; Fri,  7 Jun 2013 14:01:55 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 662AD63A8C; Fri,  7 Jun 2013 13:48:01 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 27BD4639DF; Fri,  7 Jun 2013 13:48:01 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
In-Reply-To: <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 07 Jun 2013 13:48:01 -0400
Message-ID: <11736.1370627281@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Thomas Narten <narten@us.ibm.com>, "<ietf@ietf.org>" <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: Fri, 07 Jun 2013 17:48:59 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Andy" =3D=3D Andy Bierman <andy@yumaworks.com> writes:
    Andy> So why not move the signal?
    Andy> Put IETF Last Call mail on last-call@ietf.org and leave this list=
 for
    Andy> everything else.

Okay, that would work for me.
Where would the reply-to: on those posts be set to?

I also don't think we ever solved the problem of moderation of @ietf.org
lists.  Specifically, I'd like it so that once I'm subscribed to one
@ietf.org list, that I could post to all of them. (Well, I wouldn't
post, I'd be replying in most cases)

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUbIc0IqHRg3pndX9AQL6HQQAhR3r6xF9qSJrvLQ9fAl0pgt6YtOhxHZN
gSfy52n93LMBSTh6cvTTMu4Qj6L4ApE0NJQL09IinPTrrUzwRZYM0NHyTf6QJYxS
4qgVya86Xc2zaTlPtD6HrLjBImS/+fDGKBpx03JzXOM544pqF8Aio3gZxHR9//MK
aDmdsUtM/qw=
=s3+q
-----END PGP SIGNATURE-----
--=-=-=--

From bob.hinden@gmail.com  Fri Jun  7 10:57:24 2013
Return-Path: <bob.hinden@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 9C2E821F8FDC for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 10:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 bCNglFRJt64N for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 10:57:23 -0700 (PDT)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 464C521F8D0D for <ietf@ietf.org>; Fri,  7 Jun 2013 10:57:23 -0700 (PDT)
Received: by mail-ve0-f181.google.com with SMTP id db10so3217143veb.26 for <ietf@ietf.org>; Fri, 07 Jun 2013 10:57:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=WahMR9io3lCyjW1Q/zdxIb+3azvC7GX2faSgjnrRvYw=; b=FEzaed8apP3e+A8m5CJ/JZ5JXKEh/ZIXMy69tJA62YDTS+Iec/XMnrdIbDXpTlvSoA ml11+RbsWxtb8eUSE6M8LhXYku661+KOTSXw5aMbYotDyN6eR24A1n2A/VJU8X6hapr8 ES6hxCRB8FtH3M3HAoFLlOPqlA/UumvBkvrz3TtmbVhiEOHy8yEeyVI0CPEBVhTuoORt HpDhApnayZF4L9gBRstAIgXX++xFwNI5ee9jXHEwOSIykB44dAFROVbh6NbmoIdPTBiT gKFMXX+X5HjqqhyS7EoMTVsdgrMHvsqgfM83LsiHXjSsZgOIyJAiHs1abR2xTQWBkxEa Hbng==
X-Received: by 10.220.188.201 with SMTP id db9mr23707395vcb.30.1370627842669;  Fri, 07 Jun 2013 10:57:22 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id d18sm50843030veh.6.2013.06.07.10.57.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Jun 2013 10:57:21 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Weekly posting summary for ietf@ietf.org
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <201306071651.r57Gp9Sf028501@cichlid.raleigh.ibm.com>
Date: Fri, 7 Jun 2013 10:57:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E35BCF0-B218-4A72-82E3-309320113D6A@gmail.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com> <201306071651.r57Gp9Sf028501@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1508)
Cc: Bob Hinden <bob.hinden@gmail.com>, "<ietf@ietf.org>" <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: Fri, 07 Jun 2013 17:57:24 -0000

Thomas,

> =46rom my perspective, the intention/usefulness of the weekly posting =
is
> to give folk a high-level view of who is posting and how often. It is
> not uncommon to see certain individuals stand out. In some cases, that
> makes perfect sense -- and the signal level is high. In other cases,
> it shows (IMO) people who are too quick to post and who (too often)
> say predictable things if you've read previous threads on the same
> general topic. YMMV.

I agree with your conclusion. =20

I also wish that the signal level was higher.  The IETF list is =
important because we need to have a place where IETF wide issues can be =
discussed.  That doesn't work if many people unsubscribe due to the the =
low signal to noise level.  I hope that that people who consistently =
show up at the top of the posting summary will moderate their behavior.

Bob



From ulrich@herberg.name  Fri Jun  7 11:09:35 2013
Return-Path: <ulrich@herberg.name>
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 BE02721F8F6E for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 11:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 8-W6ScYbwSdU for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 11:09:35 -0700 (PDT)
Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 8FDA021F9732 for <ietf@ietf.org>; Fri,  7 Jun 2013 11:09:34 -0700 (PDT)
Received: by mail-vb0-f54.google.com with SMTP id f13so2937553vbg.13 for <ietf@ietf.org>; Fri, 07 Jun 2013 11:09:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SwYSQ5qMB6JW5ji4QOk4uAZR64sE9Zga7bilSIxM4kE=; b=ezPOc4N3/IhjKmDVGac50yxoRH3DLVIvDezUIklKVbam8HlLTUsBGaqUdsJlBtjwk2 pZVXHRCrYglZutJ78twjBJ+931vydRs+63bMa5VgqWJjxphLL7L4mqa7ppQhHsxiNor2 stGt/8O3cj0upECBvev9+CxXHjfZCdXRBJkGY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=SwYSQ5qMB6JW5ji4QOk4uAZR64sE9Zga7bilSIxM4kE=; b=jb5i1a4T/xyCwtd1Yilhasq3G3IwzUGM2+MzxuqLVC6SVZnCjAuPpeWE1NIqOpJUFJ uCowQiEqmdMHAcd0YP57bUrgHYsouoRNUQT5N60b9ndGaO1PlLRrvgwbp5LLblHlekSx e0yIZPLSO5kCIOWYs9IiVcppDjirQZ7VLmOm6ZfqIYxA9Som9AezJ5sF+yj2TSf0C0Sb sS9qaJOM2WaG5qMyC1hSjqKDUlJqyq6M6GVWNMNTa+zhZFRtNLX55U3uuzzAjEnYBYYc PnLPcD3wcvzDQFcxRaU2uNY2S14J8UXO3ndwXGZ7eh4lsrpdVQZuClntJQ2UA7xphZIx 3MwA==
MIME-Version: 1.0
X-Received: by 10.220.104.135 with SMTP id p7mr24013653vco.10.1370628573968; Fri, 07 Jun 2013 11:09:33 -0700 (PDT)
Received: by 10.220.29.7 with HTTP; Fri, 7 Jun 2013 11:09:33 -0700 (PDT)
In-Reply-To: <CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com>
Date: Fri, 7 Jun 2013 11:09:33 -0700
Message-ID: <CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
From: Ulrich Herberg <ulrich@herberg.name>
To: Andy Bierman <andy@yumaworks.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlxRjIw7ODiDVCF7ogGatIctb+z48Za+HcCUMw0rNzPfREUtNNKF0KUS2VxYPbSKS+6RdDc
Cc: Thomas Narten <narten@us.ibm.com>, "<ietf@ietf.org>" <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: Fri, 07 Jun 2013 18:09:36 -0000

I like the idea of a separate list for last calls. It would not solve
the issue of noise for all of us (and not reduce the overall amount of
emails), but it would separate general discussions from IETF LCs. I
have IETF emails filtered by mailing list into different IMAP folders,
and thus a separation could be useful for me.

Ulrich

On Fri, Jun 7, 2013 at 9:11 AM, Andy Bierman <andy@yumaworks.com> wrote:
>
>
> On Fri, Jun 7, 2013 at 8:52 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
>>
>> On Jun 7, 2013, at 11:48 AM, Andy Bierman <andy@yumaworks.com> wrote:
>>
>> So why not move the signal?
>> Put IETF Last Call mail on last-call@ietf.org and leave this list for
>> everything else.
>>
>>
>> The discussion still has to happen somewhere.   I certainly am not
>> restricting my meaningful participation in last calls, but even in that case
>> it is important to be restrained and not get into long fruitless
>> discussions, which, I am afraid, I am wont to do.
>>
>
>
> Some people consider the last call discussions to be signal
> and the rest (vast majority) of discussions to be noise.
> They would subscribe to a last-call mailing list, but not this one.
>
>
> Andy
>

From juliao@braga.eti.br  Fri Jun  7 11:17:52 2013
Return-Path: <juliao@braga.eti.br>
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 3276021F9950 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 11:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 W7wRvw1USRX2 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 11:17:51 -0700 (PDT)
Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com [IPv6:2607:f8b0:4002:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 9B89E21F9732 for <ietf@ietf.org>; Fri,  7 Jun 2013 11:17:51 -0700 (PDT)
Received: by mail-yh0-f47.google.com with SMTP id f64so436765yha.20 for <ietf@ietf.org>; Fri, 07 Jun 2013 11:17:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=sMk58xkPrSrVDnWmA9yzO0ezSoOqtEia/+9pSJ9B878=; b=hviCK2UIXzzeA8C7pqpnebxD5Y18OH/BWSKeKv9HJIBmcI/UEPXughIH3XF436+LfV 0Gpk7cMFAx1IcHriwMgFARXHPqqtm5YFBi2mhqGEMfCBWiQfZgl9EwNmMCA9mQ/24tZY gvS4i/yz56vqbX2CksJmY7Cce9m/OjwCSLt9d/a/6F9Jje/0kyFplKAxjgvsMnDsBzwD HXqhrbHAxcMQUNKtbvpafcTXne8jvCahiXCUCrjb0ABhJcBsrWRSrrbskDN50nmKY68O oD2jD/Gk30jILpuwbiHD9xz8qex0kv3JAYJR1TFk8XJZgheucA7dBDzb/8othjSbKM1H 7z/w==
X-Received: by 10.236.25.193 with SMTP id z41mr18458633yhz.22.1370629071195; Fri, 07 Jun 2013 11:17:51 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id w12sm120496093yhj.19.2013.06.07.11.17.48 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Jun 2013 11:17:50 -0700 (PDT)
Message-ID: <51B223C7.2010401@braga.eti.br>
Date: Fri, 07 Jun 2013 15:17:43 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Weekly posting summary for ietf@ietf.org
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com> <CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com>
In-Reply-To: <CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQk3+TIraHZkxEn5DwB+GSGuAVVARQ+6XEW6Hy8Zvi6d2zxa83dVK0KCod8sk+yUeh07g35L
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: Fri, 07 Jun 2013 18:17:52 -0000

+1

Em 07/06/2013 15:09, Ulrich Herberg escreveu:
> I like the idea of a separate list for last calls. It would not solve
> the issue of noise for all of us (and not reduce the overall amount of
> emails), but it would separate general discussions from IETF LCs. I
> have IETF emails filtered by mailing list into different IMAP folders,
> and thus a separation could be useful for me.
> 
> Ulrich

From brian.e.carpenter@gmail.com  Fri Jun  7 12:52:30 2013
Return-Path: <brian.e.carpenter@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 5A8B121F96E4 for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 12:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ttgDhksjRPal for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 12:52:29 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id DF46821F9675 for <ietf@ietf.org>; Fri,  7 Jun 2013 12:52:29 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp16so1547706pbb.0 for <ietf@ietf.org>; Fri, 07 Jun 2013 12:52:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=uvFUHSzqY61tgk6BhXHkh0PGhyLfcwD6X/fGtewZ+A4=; b=Swn3xKg632/wdReIXcBNPY9Mcdayst87I4cSOqTLI4E0zhkcbF9eanRxIIZa0KgTKW 2DM+7zHXWXkidQwUziUOItRyssQMj5RJ+AHebliUwigslgNKS8RecHc51L7neHbQL6tn +jT/f2jwpcFJbnWABcGGAnw7jki8L6g15Xcsec2hE1YiZCb4dcFhek/nIToKSsJyCfK7 Q3sNZuombHElgUKe/AAQIJN9wc9GchP3s4oiPDu5R7BsmXhvnXJoGX8orBcNELtpceFX 3sSBUBVftF2c1G4ZItEUmQ38W5mXc44F6riGkpzwmA7RC2XXhlJu2oZAteOIiqhmUSb/ ryQQ==
X-Received: by 10.68.204.196 with SMTP id la4mr148191pbc.190.1370634748926; Fri, 07 Jun 2013 12:52:28 -0700 (PDT)
Received: from [192.168.1.2] (70.71.252.27.dyn.cust.vf.net.nz. [27.252.71.70]) by mx.google.com with ESMTPSA id do4sm242320pbc.8.2013.06.07.12.52.26 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Jun 2013 12:52:28 -0700 (PDT)
Message-ID: <51B23A06.7060402@gmail.com>
Date: Sat, 08 Jun 2013 07:52:38 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>	<CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>	<201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>	<CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>	<CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com>	<CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com> <51B223C7.2010401@braga.eti.br>
In-Reply-To: <51B223C7.2010401@braga.eti.br>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Fri, 07 Jun 2013 19:52:30 -0000

Rule 1 for complex and divergent mail threads is to change the
Subject header when the subject changes. If you don't do that,
your mail is rather likely to get junked.

I think that IETF last call threads should stay on the main IETF
discussion list. That is exactly the right place for them.
It's rather trivial to filter them into a dedicated folder;
I have one called 'lastcallsin', that also picks up most
WG Last Call threads, although those have less standardised
subject headers.

   Brian

On 08/06/2013 06:17, Juliao Braga wrote:
> +1
> 
> Em 07/06/2013 15:09, Ulrich Herberg escreveu:
>> I like the idea of a separate list for last calls. It would not solve
>> the issue of noise for all of us (and not reduce the overall amount of
>> emails), but it would separate general discussions from IETF LCs. I
>> have IETF emails filtered by mailing list into different IMAP folders,
>> and thus a separation could be useful for me.
>>
>> Ulrich
> 

From melinda.shore@gmail.com  Fri Jun  7 13:00:39 2013
Return-Path: <melinda.shore@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 16D4E21F996D for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 13:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 qrzM6RVOtyqV for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 13:00:33 -0700 (PDT)
Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com [209.85.192.178]) by ietfa.amsl.com (Postfix) with ESMTP id 50EEA21F9970 for <ietf@ietf.org>; Fri,  7 Jun 2013 13:00:31 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w11so801507pde.9 for <ietf@ietf.org>; Fri, 07 Jun 2013 13:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=zWYpX892g7UIXfw8VeV1Ewlf0ALYWkTVIdX6CeYbQl4=; b=0zZEOLN/fdRr6kDokinoKiRqfgt+CSLCEGLcbv712bBi1W1fYsehjHPN0njWdOKnMx 2C3Igk6vUQr6SUVyZkhxcTN5xc4smb5kQocOb5bSmF2Gft7vZk8JsMRnQHBpjdAqyq1S JARt5hvLFQh2SVlCkJ+bRs1FDNQM0OKJpuOGBaRL8v5MafsLY/j9PgdlqBEMWAFb+Meq pF+4e8W8N5K14kUax8eOSrYk4xKfST+n0PwxrUAxle1psz3c5mpKVJdoS4jHhqcfC62o 8juxTJ89tlhG+nXCx2Z47ZxEtdAxtIg3G4rCABddwErh0xGjxMZqdfMLj3ke04qP3bl/ RHxQ==
X-Received: by 10.66.118.79 with SMTP id kk15mr4276253pab.193.1370635231166; Fri, 07 Jun 2013 13:00:31 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id kv2sm226096pbc.28.2013.06.07.13.00.29 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Jun 2013 13:00:30 -0700 (PDT)
Message-ID: <51B23BDB.2060202@gmail.com>
Date: Fri, 07 Jun 2013 12:00:27 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>	<CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>	<201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>	<CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>	<CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com>	<CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com> <51B223C7.2010401@braga.eti.br> <51B23A06.7060402@gmail.com>
In-Reply-To: <51B23A06.7060402@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Fri, 07 Jun 2013 20:00:39 -0000

On 6/7/13 11:52 AM, Brian E Carpenter wrote:
> Rule 1 for complex and divergent mail threads is to change the
> Subject header when the subject changes. If you don't do that,
> your mail is rather likely to get junked.
> 
> I think that IETF last call threads should stay on the main IETF
> discussion list. That is exactly the right place for them.

I tend to think so, as well.  You never know when someone's
going to stumble over something and make a comment that matters.
The cost is that you get jackasses being loud and petty, but frankly
you'd get that on a last call mailing list, anyway, since IETF
last calls have in a few cases been known to function as jackass
magnets.

It seems to me that the real problem isn't last calls, it's
people not understanding that behaving badly has a cost associated
with it, and that cost is that they're alienating people they'd
(apparently) like to work with and demolishing their chances of
getting an editorship or moving into leadership roles.

Melinda


From john-ietf@jck.com  Fri Jun  7 15:59:07 2013
Return-Path: <john-ietf@jck.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 5346F21F99DB for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 15:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 sSnw+LQ82E3m for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 15:59:02 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 342CC21F99CE for <ietf@ietf.org>; Fri,  7 Jun 2013 15:59:02 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ul5cZ-000NtM-9t; Fri, 07 Jun 2013 18:58:59 -0400
Date: Fri, 07 Jun 2013 18:58:57 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bob Hinden <bob.hinden@gmail.com>, Thomas Narten <narten@us.ibm.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
Message-ID: <710CFEA093055148BDE84DEC@[10.121.6.76]>
In-Reply-To: <7E35BCF0-B218-4A72-82E3-309320113D6A@gmail.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com> <201306071651.r57Gp9Sf028501@cichlid.raleigh.ibm.com> <7E35BCF0-B218-4A72-82E3-309320113D6A@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "<ietf@ietf.org>" <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: Fri, 07 Jun 2013 22:59:07 -0000

--On Friday, 07 June, 2013 10:57 -0700 Bob Hinden
<bob.hinden@gmail.com> wrote:

> Thomas,
> 
>> From my perspective, the intention/usefulness of the weekly
>> posting is to give folk a high-level view of who is posting
>> and how often. It is not uncommon to see certain individuals
>> stand out. In some cases, that makes perfect sense -- and the
>...
> I agree with your conclusion.  
> 
> I also wish that the signal level was higher.  The IETF list
> is important because we need to have a place where IETF wide
> issues can be discussed.  That doesn't work if many people
> unsubscribe due to the the low signal to noise level.

Agreed so far.

>  I hope
> that that people who consistently show up at the top of the
> posting summary will moderate their behavior.

And it is getting to that conclusion from the above that often
troubles me about the posting summary list rankings.  Assuming a
significant issues shows up on the list, whether in conjunction
with a Last Call or something else.  Posting a comment and then
following up the comments of others with a couple of more
postings constitutes three messages in a week, which is pretty
reasonable.  On the other hand, if there are four such issues in
a single week (it happens) then that same individual gets
"credited" with a dozen messages, which would make the top of
the list in many weeks.  

Because things do often seem to happen in clusters, the summary
list might be improved significantly by adding a four-week
average and rankings based on it.  That would help distinguish
the regular heavy posters from those whose numbers went up
because of a particular issue or set of issues in a given week
or two.

What that still wouldn't help with is distinguishing from a
theoretical very active and diligent IETF participant who
reviews and comments on every document that goes into Last Call
push every other issue discussed on the list and a troll who
comments on every Last Call and on other issues that he, she, or
it might even generate.  To measure that difference, one would
need a measure of the useful and relevant information content of
a message, not just a character/byte count.

best,
   john




From amorris@amsl.com  Fri Jun  7 16:01:16 2013
Return-Path: <amorris@amsl.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 3800D21F99DB; Fri,  7 Jun 2013 16:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 BOk4sW6qwIyM; Fri,  7 Jun 2013 16:01:15 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id CB6AB21F99CE; Fri,  7 Jun 2013 16:01:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id C59A0128CB5; Fri,  7 Jun 2013 16:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FoQveyyJ-yyX; Fri,  7 Jun 2013 16:01:07 -0700 (PDT)
Received: from [192.168.1.180] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c8a.amsl.com (Postfix) with ESMTPSA id 38B0C128B7F; Fri,  7 Jun 2013 16:01:07 -0700 (PDT)
From: Alexa Morris <amorris@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Additional NomCom Chair Email Aliases
Date: Fri, 7 Jun 2013 16:00:48 -0700
Message-Id: <9340BA4D-591F-4F87-99BB-0073CFDA242E@amsl.com>
To: ietf-announce@ietf.org, IETF-Discussion list <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
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: Fri, 07 Jun 2013 23:01:16 -0000

As you probably know, this has been an unusual year for the NomCom. Matt =
Lepinski is wrapping up the work of the 2012-13 NomCom, while Allison =
Mankin is actively recruiting volunteers for the 2013-14 NomCom. To =
address the fact that we currently have two active NomCom Chairs, and to =
acknowledge that such a situation may recur at some point, it was =
determined that each chair should have a unique email alias. We have =
recently created the following:

- nomcom-chair-2012@ietf.org, which sends mail to Matt Lepinski

- nomcom-chair-2013@ietf.org, which sends mail to Allison Mankin

The email alias nomcom-chair@ietf.org will also remain active, and will =
forward to Matt until the 2012-13 NomCom has completed their work. At =
that time we will configure it to forward to Allison, and we will alert =
the community about the change.=20

Please let me know if you have any questions or concerns.

Regards,
Alexa


----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From arturo.servin@gmail.com  Fri Jun  7 16:02:45 2013
Return-Path: <arturo.servin@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 314BB21F84AF for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 16:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 wY+J4qQmI9ZP for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 16:02:44 -0700 (PDT)
Received: from mail-gg0-x235.google.com (mail-gg0-x235.google.com [IPv6:2607:f8b0:4002:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 0E0F221F84D8 for <ietf@ietf.org>; Fri,  7 Jun 2013 16:02:31 -0700 (PDT)
Received: by mail-gg0-f181.google.com with SMTP id r4so808171ggn.40 for <ietf@ietf.org>; Fri, 07 Jun 2013 16:02:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=O7x9PclkEcp/SUzPueIo5SzX5R7y7HC7Ax33r0LNIOU=; b=cqJEswxyjVrXkOHHm824xI2jGe/QsVhreLoMDB6R83/FYQDlIlQVWpFG2ia9OgEyEK Ri+9Eb5w9n5Kjke68uE+MK59C7o3/d3udlIECavjp7c2Lz0p19qNAN+qiJyfHiV/4XVu iYRim1ZsTD8cHF2IeRJ4+OVPF7aj+FncXMdEnFVfX76pHX0kZOyb9PcVsonzjb6iRdi+ 5U8FXY97y1u2nFp+qyVPqG8db097rDyhScq5kh9JiLW4GhsvDbqyjt58En/YS/5m3xmz V/u7xIKLHIz4Fl6up8DmlpfKQra+368DCi49KZav/6E7qqBVh/AIcrurG8UEJehCM/Cp KP3A==
X-Received: by 10.236.201.70 with SMTP id a46mr412656yho.75.1370646150238; Fri, 07 Jun 2013 16:02:30 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba30:df31:c5ef:c620:6c4b:42e8]) by mx.google.com with ESMTPSA id v5sm1312012yhn.27.2013.06.07.16.02.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Jun 2013 16:02:29 -0700 (PDT)
Message-ID: <51B26680.6030706@gmail.com>
Date: Fri, 07 Jun 2013 20:02:24 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>	<CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>	<201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>	<CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>	<CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com>	<CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com> <51B223C7.2010401@braga.eti.br> <51B23A06.7060402@gmail.com>
In-Reply-To: <51B23A06.7060402@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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: Fri, 07 Jun 2013 23:02:45 -0000

	I have mixed opinions, filters in general work well (some false
positives like these ones that are moved to my "Last Call" filter) but
in general it is ok.

	But I would not oppose to a new list for LC only.

Regards,
as

On 6/7/13 4:52 PM, Brian E Carpenter wrote:
> I think that IETF last call threads should stay on the main IETF
> discussion list. That is exactly the right place for them.
> It's rather trivial to filter them into a dedicated folder;
> I have one called 'lastcallsin', that also picks up most
> WG Last Call threads, although those have less standardised
> subject headers.

From abdussalambaryun@gmail.com  Fri Jun  7 22:50:59 2013
Return-Path: <abdussalambaryun@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 0E5C921F86AE; Fri,  7 Jun 2013 22:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 v4ReZ88RMjUm; Fri,  7 Jun 2013 22:50:57 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id AF78A21F9A16; Fri,  7 Jun 2013 22:50:57 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id mc8so5488108pbc.4 for <multiple recipients>; Fri, 07 Jun 2013 22:50:49 -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=IPR7pd3S1sRKAIrDKXRPFy5AZQ+e5EmBJirwymzi0Uo=; b=cxx68DE/4wbGP/NqDCrWwcyHP1bffJD8/DNHQoRmlbieelm3fmqZ6zMT/TCFktvITy 0TSezaNBRad1H8+S7L1tTu1jw0DIu26VQ8gsP4mmpjoFt9WShWNLeoc5NzhDfZKqtSuX sLLe+FnLKOZcsy2SW+yxRHUKMzFHby3CEG2FFy7Ieq84ZnJ7NnAw5d40rIXYfsbbCzqo 717o/lnklNy3o7iVBS6qXLSXMujygsH40QnBZOPMNAEtaIloWva/cGSBur3bdGo7KJVS 6F8UobkCTHd3jk5IfaRBwTMc0HBNWgsWi7hZw24iHu6Q58JNnBnxCobFrqC76726PVnx /5mg==
MIME-Version: 1.0
X-Received: by 10.68.125.227 with SMTP id mt3mr1735377pbb.153.1370670649619; Fri, 07 Jun 2013 22:50:49 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Fri, 7 Jun 2013 22:50:49 -0700 (PDT)
In-Reply-To: <0a1401ce62fb$2aecfa10$80c6ee30$@olddog.co.uk>
References: <09b601ce62db$77adc5c0$67095140$@olddog.co.uk> <CADnDZ89jxuxzCGvwOqcDyO84DCmE10bDmA2zb94YQm=FPyqFZQ@mail.gmail.com> <0a1401ce62fb$2aecfa10$80c6ee30$@olddog.co.uk>
Date: Sat, 8 Jun 2013 07:50:49 +0200
Message-ID: <CADnDZ8-hWkU5XD7uUoJHgg7eWtRqRQOH2123fs0Gx3618TwKjA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: adrian@olddog.co.uk
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>, iesg@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: Sat, 08 Jun 2013 05:50:59 -0000

Dear Routing Area AD,

I had many comments/issues regarding your area always addressed to you
and  including this issue which I hope my all comments (past/present)
will help to make better practice/procedural progresses in this IETF
Area.
I am sorry also to any one receiving this email but I send it only to
an AD, IETF, and IESG. This is not noise but a signal to IETF to
progress, if you think it is noise please explain, and please notice
that all particpants have rights under the IETF procedures not only
managements. My reply below and if you want to continue discussing on
any other list please inform me, but if you reply copying any list, I
will have to do the same because you are part of management and I am
not.

On 6/6/13, Adrian Farrel <adrian@olddog.co.uk> wrote:
> Sorry to everyone for the noise this thread is creating.

This thread containing my messages never creates noise, I beleive you
may ne refering to your messages only as noise. Please note that I
don't accept this describtion, I think that community messages
regarding any I-D is never noise even if the IETF management could not
handle the volume. I RECOMMEND any receiver that has noise in it to
fix its problem without blaming transmitters.

> Multiple questions that I have to answer.

ok, that is why this list is discussing list for ietf progress,

>
>> > It falls to me to make a call on this issue before the document moves
>> > on.
>> >
>> > Abdussalam has complained that he has not been acknowledged and has
>> > objected to the current text in section 8.
>> > The authors have responded on the MANET list
>> >
>> >> We believe that only comments that lead to significant improvements of
>> >> the draft deserve a listing in the acknowledgment section, and we have
>> >> therefore not modified the section.
>>
>> What was the WG decision?
>
> Are you asking whether there was an explicit consensus call within the
> working
> group on whether or not you should be acknowledged in this document?

I think the question is clear, and is easy to answer. The answer is,
there was no decision made by the WG or the community regarding my
request of adding a name in the ack section. You send me back a
question saying explicit consensus, it is simpler to make my question
asking of notification of such reaction from management, which was not
either established. I did not get a message saying that any kind of
consensus was established privately/publicly on any IETF lists (please
ask the WG chair because I am sure I did not received any answer for
my request by the WG/community).

> There was no such call in the working group or on the IETF list.

Thanks for the answer, so I understand that the editors/management did
not answer my request (one person from the community), just because
they or AD did not beleive in my concerns without consulting the WG in
any way.

>
>> Why any contribution that influnces the I-D ideas is not acknowledged?
>> IMO, if a technical-idea within the I-D was discovered wrong by a
>> participant, or a new technical-idea added to I-D from an input, then
>> the I-D should be acknowledged.
>
> This opinion does not apply to your comments on this document. You did not
> discover a wrong technical-idea. Your comments did not lead directly to the
> addition of any new technical-idea.

The question of I-D managers not acknowledging such
input/contribution, was not answered if you agree to acknowledge
discovering an error or adding a new idea. Regarding the opinion, do
you agree with the opinion first? Regarding the error and missing
information, I did discover error in the document and did found
missing definitions if this informational I-D (after my contribution
there was changes made to the document, please notice that)
>
>> > I have reviewed the email threads on the MANET mailing list and do not
>> > consider that Abdussalam made contributions to the text of the
>> > document.
>>
>> Didn't that person make review and discovered errors?
>
> "That person" is you.

Yes but I said that because this message it not me defending me, it is
me defending future wrong reaction of ignoring to acknowledge the
persons in the community. If any I-D authors are best knowledgeable
people in a special field they should not try to seek to
dis-acknowledge the community efforts that changed few I-D ideas (even
if the community person is not expert, that does not mean that authors
have right to exclude contributors).

> Yes, you made a review. Reviewing a document is not something authors
> acknowledge in the IETF or (AFAIK) in academic journals.

I disagree with your opinion, but do you think your opinion is in the
IETF procedure, if yes please provide me with that procedure of not
acknowledgement. I respect your opinion but it is wrong because in one
sense yes documents in the world don't acknowledge all reviews
(usually when they don't request it), one the other hand the world
documents do acknowledge reviews when the document owner calls for
review. Please note that this I-D did request/call for review and I
was the only reveiwer in the WGLC, and my review made the authors
change some ideas.

> No, I don't think you discovered errors of any significance.

My comments and discussions are in the MANET WG. The errors were; 1)
not explaining the word *attack* in I-D version 2 and/or referencing
explainations. 2) wrong explaination of physical communication in
MANET.
Both ideas ware changed please see the two versions of I-D 2 and 3.

Example error idea in the I-D was:
[I-D wrong idea] As wireless radio waves can be captured as well as transmitted
by any wireless device within radio range.
[my discovery contribution]
http://www.ietf.org/mail-archive/web/manet/current/msg15250.html

>
> Caveating my answers below as describing a contribution to a document (not
> a
> contribution in the wider IETF sense)

An IETF I-D contribution is a contribution (don't care about the
editors' beleive of kind of contributions), small, large, substantial,
non-substantial, minor, major, from-expert, not-from-expert,
from-popular, from-non-popular, from-f2f-participant,
from-remote-participant, etc.
>
>> Why don't you consider discovering an error as a contribution?
>
> I would personally consider discovering a major error as something I would
> acknowledge it in a document I was editing.

You use word major as if we know what it means. Something minor to you
may be major to someone else don't you think. If your documents if for
experts please mention that in you documents, please know your
audiance/readers. I understand that IETF documents are for ALL the
Internet Community on EARTH. Therefore, the word major/minor is
relative to the reader not writer.

> I would personally consider discovering multiple minor errors as something
> I
> would acknowledge it in a document I was editing.

Again you say you, I want IETF opinion not editors, I want WG
decisions not your decisions, however, I already waiting for the IESG
decisions on this matter, and I understand that your decision is a one
part of that but not full/final. One error discovery or multiple, both
are contributions and are needed. In our volunteering work if the
work/I-D/RFC has many mistakes we don't blame the editors but the
community, but if the work had no mistake we give all credit to
authors, IMHO, we always should refer to the community in good or bad
outcomes of IETF documents. Therefore acknowledging the parts of
community is important.
>
> However, there is no requirement for editors to act in that way.

No, editors are required to edit/act what the community is seeking,
why are they called editors for the WG? the authority is for the WG
not editors.

> Furthermore,
> you do not fit into these categories for this document.

I do fit, I think you should not decide now, let it to be done through
IETF procedure.

>
>> Why don't you consider providing new ideas a contribution?
>
> I would consider providing major ideas as something I would acknowledge it
> in a
> document I was editing.
> I would consider providing smaller ideas through text for inclusion in the
> document as something I would acknowledge it in a document I was editing.
> You do not fit into these categories for this document.

I think I do fit from IETF point of view (maybe not yours). I gave my
discovery of error, and if the editors want text I will give them, it
is a discussion issue between both sides in a WG. Text is not much
important like the idea, the idea is the most important thing in any
organisation. English texting can be another contribution, or proof
readings, but the main contribution is the idea that was changed.

>
>> What is your definition to contribution?
>
> As above, or written text that was included or modified for inclusion in a
> document and represents a material or substantial part of the document.

the idea is more important than text, if changed sentence idea we
SHOULD acknowledge, if changed sentance text without changing idea we
do not have to acknowledge. So text changing/adding without new-idea
or English correction is not acknowledged im my opinion.

>
>> > I also believe that the comments he made did not advance the
>> > content of the document.
>>
>> So I understand that you need to have advance the content then you
>> acknowledge.
>>
>> > Furthermore, per multiple references (such as RFC 2026) the
>> > Acknowledgements section is used to "properly acknowledge
>> > major contributors.
>>
>> I am trying to find that condition of *major contribution*,
>
> I would borrow from 2026 and 5378 to say a material or substantial
> contribution
> to the document.
>
> And, before you ask, no-one is going to write down a rule that says 139
> characters is not substantial, but 140 is.
>
> This is one of the places where a principal of reasonableness applies. I
> would
> know a major contribution if I saw one. I did not see one from you in this
> case.

I will wait for the IESG decision on that. Major or minor is relative
to the readers not to the writers. You have big experience but that
does not mean you should exclude any minor contribution, I hope you
reconsider that. Some experts don't like to show that non-popular
found their mistakes, but Why thoes experts came to use IETF service
which calls-reviews to all levels of experties to contribute to the
document they author under IETF ownership?

>
>> >" Normal IETF business is to discuss not seek acknowledgement.
>>
>> Ideas, Comments and reviews are included in the discuss for drafts
>> progress. Seeking acknowledgement is not wrong within IETF, but please
>> consider *not acknowledging reviews* within IETF documents is not IETF
>> culture (we are not paid so why you thinking much of the business, the
>> IETF business will only progress with acknowledging the volunteers).
>
> If you want to change the way that the IETF participants (and document
> authors/editors in particular) acknowledge reviews of their documents, then
> please start a separate thread or, better still, write an I-D and see
> whether
> you can gain consensus.

I know that, but your advise comes back to you also, if you want to
change the community expectations close to your opinions, I advise you
to write an I-D that shows where to exclude participants to IETF
documents.

>The last time you brought this topic up on this
> list, I
> do not recall seeing support.

Few did not support which were less than 15 persons, because IMO,
there was no evidance of editors seeking to ignore reviewers
contributions. Also, change is difficult any where in any
organisation, so it will take time, IMO, people realise that
participating-experts of IETF are the minority comapared to the
community. I decided to complain any procedure error first and then
write about what happend, so I will wait to see what is the IESG
decision regarding the acknowledgement request. Please note that I
have many procedural I-D in mind but it depends on the right time to
submit it and get support.

>
> The only reason I can find for someone being able to demand that they are
> named
> in an Acknowledgements Section is for conformance to the IETF's Rights
> policies.

My reason is that the truth SHOULD be reflected on the document. If
you are editor I recommend you may say in the section thanks to x for
his minor contribution if that satisfies your WG you work with, but
not to ignore the truth. The truth is that IETF is calling for reviews
from the community mostly not only from companies, and that your
document changed an idea, so you ack.

>
>> > I do not propose to do an explicit consensus call on whether Abdussalam
>> > should be named in this draft.
>>
>> IMO, it should have been done in the WG.
>
> Thank you for your opinion.
> Are you asserting that consensus on the readiness of this document for a
> publication request was incorrectly called by the working group chairs.
> This
> would be a serious allegation against the chairs and I would require
> evidence
> that there had been no consensus or that they had made an incorrect
> assessment
> of the consensus.

No, I accepted that the I-D goes to IESG only the complaint request of
acknowledgement and the community reviews in IETF-LC. The wg chair
mentioned my complaint in his report. I wait for the IESG decisions
related to this I-D.

Best Regards

Abdussalam Baryun

A Participant working in IETF (subscribed)
A Memebr of Internet Society (registered)

From glenzorn@gmail.com  Fri Jun  7 23:31:19 2013
Return-Path: <glenzorn@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 E0ED921F9A0D for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 23:31:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 RqMefk45nQnE for <ietf@ietfa.amsl.com>; Fri,  7 Jun 2013 23:31:19 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 205C921F9A0B for <ietf@ietf.org>; Fri,  7 Jun 2013 23:31:19 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id wp1so3077221pac.31 for <ietf@ietf.org>; Fri, 07 Jun 2013 23:31:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=PVwtCDMDHDGTWfuX+SKcjPCc8qhGZ7kaa8lloeNSKsc=; b=Vo+1VgBYkSOVN+BLZtVeqWkTfIKOGYqR6vU9SWKqPPr1J9Ff1sTnLak+jgr/Fyt5/R Ae/fLgsYOEZB67DlOHxBn6NL9NJ8HnoxPKKF413tHEM1m+zHJ5gvx/SM5T//ADRxHxaO VFCXc7muDWSfPwBG3uJd1wTddELlubM5K0Di8T4o+KVcIa4ZvYh7uWukv+NHyEoK3jkP 2jc79HHpKR6TES1i2rYKGB4ER3++zVSfIUDNpCFdLYOOvLBVpUl/oNAidDhnL4lXFj7H qBtfs9Q7QxZKqkbRGUJuHuLxgRnKzUGjUqrkw8Z/RiMuBIkj0uzYbD5G22klJmXgkI/P oSxQ==
X-Received: by 10.66.253.195 with SMTP id ac3mr318567pad.107.1370673078814; Fri, 07 Jun 2013 23:31:18 -0700 (PDT)
Received: from [192.168.0.104] (ppp-58-11-236-89.revip2.asianet.co.th. [58.11.236.89]) by mx.google.com with ESMTPSA id fp2sm1916553pbb.36.2013.06.07.23.31.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Jun 2013 23:31:18 -0700 (PDT)
Message-ID: <51B2CFB2.3010803@gmail.com>
Date: Sat, 08 Jun 2013 13:31:14 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>	<CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>	<201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>	<CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>	<CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com>	<CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com> <51B223C7.2010401@braga.eti.br> <51B23A06.7060402@gmail.com>
In-Reply-To: <51B23A06.7060402@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 08 Jun 2013 06:31:20 -0000

On 06/08/2013 02:52 AM, Brian E Carpenter wrote:

> Rule 1 for complex and divergent mail threads is to change the
> Subject header when the subject changes. If you don't do that,
> your mail is rather likely to get junked.
>
> I think that IETF last call threads should stay on the main IETF
> discussion list. That is exactly the right place for them.

Since I've requested (read "begged" ;-) for such threads to be moved to 
their own list on several occasions, I disagree again.

> It's rather trivial to filter them into a dedicated folder;
> I have one called 'lastcallsin', that also picks up most
> WG Last Call threads, although those have less standardised
> subject headers.

This would appear to work consistently only as long as 'Rule 1' above is 
not followed.

>
>     Brian
>
> On 08/06/2013 06:17, Juliao Braga wrote:
>> +1
>>
>> Em 07/06/2013 15:09, Ulrich Herberg escreveu:
>>> I like the idea of a separate list for last calls. It would not solve
>>> the issue of noise for all of us (and not reduce the overall amount of
>>> emails), but it would separate general discussions from IETF LCs. I
>>> have IETF emails filtered by mailing list into different IMAP folders,
>>> and thus a separation could be useful for me.
>>>
>>> Ulrich
>>

From l.wood@surrey.ac.uk  Sat Jun  8 03:09:28 2013
Return-Path: <l.wood@surrey.ac.uk>
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 1797921F9A3A for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 03:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.948
X-Spam-Level: 
X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, UNPARSEABLE_RELAY=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 mXVLMwL5rEq0 for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 03:09:23 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.144]) by ietfa.amsl.com (Postfix) with ESMTP id D171921F9A35 for <ietf@ietf.org>; Sat,  8 Jun 2013 03:09:22 -0700 (PDT)
Received: from [195.245.231.67:32799] by server-8.bemta-5.messagelabs.com id B0/16-29170-1D203B15; Sat, 08 Jun 2013 10:09:21 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-82.messagelabs.com!1370686160!29669401!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26070 invoked from network); 8 Jun 2013 10:09:20 -0000
Received: from unknown (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-6.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 8 Jun 2013 10:09:20 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Sat, 8 Jun 2013 11:09:20 +0100
From: <l.wood@surrey.ac.uk>
To: <glenzorn@gmail.com>, <ietf@ietf.org>
Date: Sat, 8 Jun 2013 11:09:19 +0100
Subject: RE: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
Thread-Topic: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
Thread-Index: Ac5kEeT8b9+RdDP+So242SvCBA6nFQAHNOXg
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EA4@EXMB01CMS.surrey.ac.uk>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com> <CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com> <51B223C7.2010401@braga.eti.br> <51B23A06.7060402@gmail.com>,<51B2CFB2.3010803@gmail.com>
In-Reply-To: <51B2CFB2.3010803@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Sat, 08 Jun 2013 10:09:28 -0000

I believe that last calls must stay on this ietf list.

Any last-call-only list must be *in addition* to the ietf list, with all an=
nouncements crossposted, and anyone sensitive to general discussion can sub=
scribe to that instead.

Last calls need wide exposure.

(I'm acked in at least one RFC as a result of discussion on this list as a =
result of last call.)

I'd go further and say that if you're contributing to an ietf workgroup, su=
bscribing to ietf and ietf-announce should be mandatory for posting rights =
in that group. Sure, you can filter the mails to /dev/null, but getting a b=
road idea of what's going on is a good thing, no? I'm willing to bet that a=
t least half of our design problems have resulted from people doing narrowl=
y-focused work in only one group or area...

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Glen Zorn =
[glenzorn@gmail.com]
Sent: 08 June 2013 07:31
To: ietf@ietf.org
Subject: Re: Best list for IETF last calls [was: Weekly posting summary for=
     ietf@ietf.org]

On 06/08/2013 02:52 AM, Brian E Carpenter wrote:

> Rule 1 for complex and divergent mail threads is to change the
> Subject header when the subject changes. If you don't do that,
> your mail is rather likely to get junked.
>
> I think that IETF last call threads should stay on the main IETF
> discussion list. That is exactly the right place for them.

Since I've requested (read "begged" ;-) for such threads to be moved to
their own list on several occasions, I disagree again.

> It's rather trivial to filter them into a dedicated folder;
> I have one called 'lastcallsin', that also picks up most
> WG Last Call threads, although those have less standardised
> subject headers.

This would appear to work consistently only as long as 'Rule 1' above is
not followed.

>
>     Brian
>
> On 08/06/2013 06:17, Juliao Braga wrote:
>> +1
>>
>> Em 07/06/2013 15:09, Ulrich Herberg escreveu:
>>> I like the idea of a separate list for last calls. It would not solve
>>> the issue of noise for all of us (and not reduce the overall amount of
>>> emails), but it would separate general discussions from IETF LCs. I
>>> have IETF emails filtered by mailing list into different IMAP folders,
>>> and thus a separation could be useful for me.
>>>
>>> Ulrich
>>

From rpelletier@isoc.org  Sat Jun  8 05:58:16 2013
Return-Path: <rpelletier@isoc.org>
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 6161321F99AA for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 05:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 L0m8O76ojdpw for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 05:58:11 -0700 (PDT)
Received: from smtp70.ord1c.emailsrvr.com (smtp70.ord1c.emailsrvr.com [108.166.43.70]) by ietfa.amsl.com (Postfix) with ESMTP id 4D16B21F8ADC for <ietf@ietf.org>; Sat,  8 Jun 2013 05:58:11 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id D6A12148094; Sat,  8 Jun 2013 08:58:10 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp1.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id AA0FD148089;  Sat,  8 Jun 2013 08:58:10 -0400 (EDT)
Subject: Re: Weekly posting summary for ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>
Date: Sat, 8 Jun 2013 08:58:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE61343A-070F-4C34-92F8-275DB8116204@isoc.org>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1085)
Cc: "<ietf@ietf.org>" <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: Sat, 08 Jun 2013 12:58:16 -0000

On Jun 7, 2013, at 10:49 AM, Thomas Narten wrote:

> What the weekly stats really ought to tally up is the readers/postings
> ratio, so that folk would get more direct feedback as to whether what =
they are
> posting is actually being read...
>=20
> My strong suspicion would be that there is strong negative correlation
> between frequency of posts and actual readers of those posts...
>=20
> Also, I suspect that many people do not realize that a significant
> chunk of IETF contributers are no longer subscribed to the ietf list
> due to signal to noise ratio concerns...

This list has 2155 subscribers.

Rough, quick count numbers:
56 sent messages week ending 31 May
58 week ending 24 May
87 week ending 3 May
56 week ending 5 April
82 Week ending 8 March
28 week ending 8 Feb
68 week ending 11 Jan

Average:  62 or 3% on the list

Quick glance looks like same people most of the time sending messages

Would be interesting to just report on Last Call mail.  You might find =
justification=20
there by itself to create a Last-Call list.

Ray




>=20
> Thomas
>=20


From rpelletier@isoc.org  Sat Jun  8 06:03:17 2013
Return-Path: <rpelletier@isoc.org>
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 A8EAF21F9A1F for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 06:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4TGi47TQ1IFF for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 06:03:13 -0700 (PDT)
Received: from smtp86.ord1c.emailsrvr.com (smtp86.ord1c.emailsrvr.com [108.166.43.86]) by ietfa.amsl.com (Postfix) with ESMTP id 62D0521F99B4 for <ietf@ietf.org>; Sat,  8 Jun 2013 06:03:13 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 11B92500A8; Sat,  8 Jun 2013 09:03:13 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id C252050096;  Sat,  8 Jun 2013 09:03:12 -0400 (EDT)
Subject: Re: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EA4@EXMB01CMS.surrey.ac.uk>
Date: Sat, 8 Jun 2013 09:03:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9024F1F-65A2-4FDC-8750-772642041A88@isoc.org>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com> <CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com> <51B223C7.2010401@braga.eti.br> <51B23A06.7060402@gmail.com>, <51B2CFB2.3010803@gmail.com> <290E20B455C66743BE178C5C84F12408223F494EA4@EXMB01CMS.surrey.ac.uk>
To: <l.wood@surrey.ac.uk> <l.wood@surrey.ac.uk>
X-Mailer: Apple Mail (2.1085)
Cc: 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: Sat, 08 Jun 2013 13:03:17 -0000

On Jun 8, 2013, at 6:09 AM, <l.wood@surrey.ac.uk> <l.wood@surrey.ac.uk> =
wrote:

> I believe that last calls must stay on this ietf list.
>=20
> Any last-call-only list must be *in addition* to the ietf list, with =
all announcements crossposted, and anyone sensitive to general =
discussion can subscribe to that instead.
>=20
> Last calls need wide exposure.
>=20
> (I'm acked in at least one RFC as a result of discussion on this list =
as a result of last call.)
>=20
> I'd go further and say that if you're contributing to an ietf =
workgroup, subscribing to ietf and ietf-announce should be mandatory for =
posting rights in that group.

The ietf list has 2,155 subscribers, Announce, 3,203 with 915 =
duplicates, for total unique addresses of 4,442.

Ray


> Sure, you can filter the mails to /dev/null, but getting a broad idea =
of what's going on is a good thing, no? I'm willing to bet that at least =
half of our design problems have resulted from people doing =
narrowly-focused work in only one group or area...
>=20
> Lloyd Wood
> http://sat-net.com/L.Wood/
>=20
>=20
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Glen =
Zorn [glenzorn@gmail.com]
> Sent: 08 June 2013 07:31
> To: ietf@ietf.org
> Subject: Re: Best list for IETF last calls [was: Weekly posting =
summary for     ietf@ietf.org]
>=20
> On 06/08/2013 02:52 AM, Brian E Carpenter wrote:
>=20
>> Rule 1 for complex and divergent mail threads is to change the
>> Subject header when the subject changes. If you don't do that,
>> your mail is rather likely to get junked.
>>=20
>> I think that IETF last call threads should stay on the main IETF
>> discussion list. That is exactly the right place for them.
>=20
> Since I've requested (read "begged" ;-) for such threads to be moved =
to
> their own list on several occasions, I disagree again.
>=20
>> It's rather trivial to filter them into a dedicated folder;
>> I have one called 'lastcallsin', that also picks up most
>> WG Last Call threads, although those have less standardised
>> subject headers.
>=20
> This would appear to work consistently only as long as 'Rule 1' above =
is
> not followed.
>=20
>>=20
>>    Brian
>>=20
>> On 08/06/2013 06:17, Juliao Braga wrote:
>>> +1
>>>=20
>>> Em 07/06/2013 15:09, Ulrich Herberg escreveu:
>>>> I like the idea of a separate list for last calls. It would not =
solve
>>>> the issue of noise for all of us (and not reduce the overall amount =
of
>>>> emails), but it would separate general discussions from IETF LCs. I
>>>> have IETF emails filtered by mailing list into different IMAP =
folders,
>>>> and thus a separation could be useful for me.
>>>>=20
>>>> Ulrich
>>>=20


From jdrake@juniper.net  Sat Jun  8 06:12:18 2013
Return-Path: <jdrake@juniper.net>
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 5B97521F8411; Sat,  8 Jun 2013 06:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.467
X-Spam-Level: 
X-Spam-Status: No, score=-3.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
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 SJOHTLAVyOgM; Sat,  8 Jun 2013 06:12:12 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id 2F09E21F871D; Sat,  8 Jun 2013 06:12:12 -0700 (PDT)
Received: from mail74-tx2-R.bigfish.com (10.9.14.247) by TX2EHSOBE013.bigfish.com (10.9.40.33) with Microsoft SMTP Server id 14.1.225.23; Sat, 8 Jun 2013 13:12:11 +0000
Received: from mail74-tx2 (localhost [127.0.0.1])	by mail74-tx2-R.bigfish.com (Postfix) with ESMTP id 8DC261803C8; Sat,  8 Jun 2013 13:12:11 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.50; KIP:(null); UIP:(null); IPV:NLI; H:P-EMHUB03-HQ.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: -27
X-BigFish: PS-27(zzbb2dI98dI9371I1dbaI1432I1418I1447Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hz8dhz1033IL17326ah8275bh8275dhz31h2a8h683h839h944hd25he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1155h)
Received-SPF: softfail (mail74-tx2: transitioning domain of juniper.net does not designate 66.129.224.50 as permitted sender) client-ip=66.129.224.50; envelope-from=jdrake@juniper.net; helo=P-EMHUB03-HQ.jnpr.net ; -HQ.jnpr.net ; 
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
Received: from mail74-tx2 (localhost.localdomain [127.0.0.1]) by mail74-tx2 (MessageSwitch) id 1370697128538734_25168; Sat,  8 Jun 2013 13:12:08 +0000 (UTC)
Received: from TX2EHSMHS031.bigfish.com (unknown [10.9.14.253])	by mail74-tx2.bigfish.com (Postfix) with ESMTP id 6B708380257; Sat,  8 Jun 2013 13:12:08 +0000 (UTC)
Received: from P-EMHUB03-HQ.jnpr.net (66.129.224.50) by TX2EHSMHS031.bigfish.com (10.9.99.131) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sat, 8 Jun 2013 13:12:07 +0000
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sat, 8 Jun 2013 06:12:07 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Sat, 8 Jun 2013 06:12:06 -0700
Received: from co1outboundpool.messaging.microsoft.com (216.32.180.187) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Sat, 8 Jun 2013 06:23:40 -0700
Received: from mail92-co1-R.bigfish.com (10.243.78.234) by CO1EHSOBE039.bigfish.com (10.243.66.104) with Microsoft SMTP Server id 14.1.225.23; Sat, 8 Jun 2013 13:12:06 +0000
Received: from mail92-co1 (localhost [127.0.0.1])	by mail92-co1-R.bigfish.com (Postfix) with ESMTP id 22940580267; Sat,  8 Jun 2013 13:12:06 +0000 (UTC)
Received: from mail92-co1 (localhost.localdomain [127.0.0.1]) by mail92-co1 (MessageSwitch) id 1370697123902489_19610; Sat,  8 Jun 2013 13:12:03 +0000 (UTC)
Received: from CO1EHSMHS016.bigfish.com (unknown [10.243.78.235])	by mail92-co1.bigfish.com (Postfix) with ESMTP id D081A600049; Sat,  8 Jun 2013 13:12:03 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by CO1EHSMHS016.bigfish.com (10.243.66.26) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sat, 8 Jun 2013 13:12:03 +0000
Received: from BL2PRD0510MB349.namprd05.prod.outlook.com ([169.254.1.63]) by BL2PRD0510HT001.namprd05.prod.outlook.com ([10.255.100.36]) with mapi id 14.16.0311.000; Sat, 8 Jun 2013 13:12:03 +0000
From: John E Drake <jdrake@juniper.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
Thread-Topic: Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security	Threats for NHDP) to Informational RFC
Thread-Index: Ac5i22UgBxQKv2PhTiW4S3Ku8O2C3QAEVveAAAOZ7wAARD35gAAPaOr6
Date: Sat, 8 Jun 2013 13:12:02 +0000
Message-ID: <578288CA-29D7-4EFA-A298-F51A12EDAB45@juniper.net>
References: <09b601ce62db$77adc5c0$67095140$@olddog.co.uk> <CADnDZ89jxuxzCGvwOqcDyO84DCmE10bDmA2zb94YQm=FPyqFZQ@mail.gmail.com> <0a1401ce62fb$2aecfa10$80c6ee30$@olddog.co.uk>, <CADnDZ8-hWkU5XD7uUoJHgg7eWtRqRQOH2123fs0Gx3618TwKjA@mail.gmail.com>
In-Reply-To: <CADnDZ8-hWkU5XD7uUoJHgg7eWtRqRQOH2123fs0Gx3618TwKjA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [166.137.81.160]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%GMAIL.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%OLDDOG.CO.UK$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-OriginatorOrg: juniper.net
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, ietf <ietf@ietf.org>, "iesg@ietf.org" <iesg@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: Sat, 08 Jun 2013 13:12:18 -0000

AB,

This may surprise you, but not everyone cares what you think.

John

Sent from my iPhone

On Jun 8, 2013, at 1:51 AM, "Abdussalam Baryun" <abdussalambaryun@gmail.com=
> wrote:

> Dear Routing Area AD,
>=20
> I had many comments/issues regarding your area always addressed to you
> and  including this issue which I hope my all comments (past/present)
> will help to make better practice/procedural progresses in this IETF
> Area.
> I am sorry also to any one receiving this email but I send it only to
> an AD, IETF, and IESG. This is not noise but a signal to IETF to
> progress, if you think it is noise please explain, and please notice
> that all particpants have rights under the IETF procedures not only
> managements. My reply below and if you want to continue discussing on
> any other list please inform me, but if you reply copying any list, I
> will have to do the same because you are part of management and I am
> not.
>=20
> On 6/6/13, Adrian Farrel <adrian@olddog.co.uk> wrote:
>> Sorry to everyone for the noise this thread is creating.
>=20
> This thread containing my messages never creates noise, I beleive you
> may ne refering to your messages only as noise. Please note that I
> don't accept this describtion, I think that community messages
> regarding any I-D is never noise even if the IETF management could not
> handle the volume. I RECOMMEND any receiver that has noise in it to
> fix its problem without blaming transmitters.
>=20
>> Multiple questions that I have to answer.
>=20
> ok, that is why this list is discussing list for ietf progress,
>=20
>>=20
>>>> It falls to me to make a call on this issue before the document moves
>>>> on.
>>>>=20
>>>> Abdussalam has complained that he has not been acknowledged and has
>>>> objected to the current text in section 8.
>>>> The authors have responded on the MANET list
>>>>=20
>>>>> We believe that only comments that lead to significant improvements o=
f
>>>>> the draft deserve a listing in the acknowledgment section, and we hav=
e
>>>>> therefore not modified the section.
>>>=20
>>> What was the WG decision?
>>=20
>> Are you asking whether there was an explicit consensus call within the
>> working
>> group on whether or not you should be acknowledged in this document?
>=20
> I think the question is clear, and is easy to answer. The answer is,
> there was no decision made by the WG or the community regarding my
> request of adding a name in the ack section. You send me back a
> question saying explicit consensus, it is simpler to make my question
> asking of notification of such reaction from management, which was not
> either established. I did not get a message saying that any kind of
> consensus was established privately/publicly on any IETF lists (please
> ask the WG chair because I am sure I did not received any answer for
> my request by the WG/community).
>=20
>> There was no such call in the working group or on the IETF list.
>=20
> Thanks for the answer, so I understand that the editors/management did
> not answer my request (one person from the community), just because
> they or AD did not beleive in my concerns without consulting the WG in
> any way.
>=20
>>=20
>>> Why any contribution that influnces the I-D ideas is not acknowledged?
>>> IMO, if a technical-idea within the I-D was discovered wrong by a
>>> participant, or a new technical-idea added to I-D from an input, then
>>> the I-D should be acknowledged.
>>=20
>> This opinion does not apply to your comments on this document. You did n=
ot
>> discover a wrong technical-idea. Your comments did not lead directly to =
the
>> addition of any new technical-idea.
>=20
> The question of I-D managers not acknowledging such
> input/contribution, was not answered if you agree to acknowledge
> discovering an error or adding a new idea. Regarding the opinion, do
> you agree with the opinion first? Regarding the error and missing
> information, I did discover error in the document and did found
> missing definitions if this informational I-D (after my contribution
> there was changes made to the document, please notice that)
>>=20
>>>> I have reviewed the email threads on the MANET mailing list and do not
>>>> consider that Abdussalam made contributions to the text of the
>>>> document.
>>>=20
>>> Didn't that person make review and discovered errors?
>>=20
>> "That person" is you.
>=20
> Yes but I said that because this message it not me defending me, it is
> me defending future wrong reaction of ignoring to acknowledge the
> persons in the community. If any I-D authors are best knowledgeable
> people in a special field they should not try to seek to
> dis-acknowledge the community efforts that changed few I-D ideas (even
> if the community person is not expert, that does not mean that authors
> have right to exclude contributors).
>=20
>> Yes, you made a review. Reviewing a document is not something authors
>> acknowledge in the IETF or (AFAIK) in academic journals.
>=20
> I disagree with your opinion, but do you think your opinion is in the
> IETF procedure, if yes please provide me with that procedure of not
> acknowledgement. I respect your opinion but it is wrong because in one
> sense yes documents in the world don't acknowledge all reviews
> (usually when they don't request it), one the other hand the world
> documents do acknowledge reviews when the document owner calls for
> review. Please note that this I-D did request/call for review and I
> was the only reveiwer in the WGLC, and my review made the authors
> change some ideas.
>=20
>> No, I don't think you discovered errors of any significance.
>=20
> My comments and discussions are in the MANET WG. The errors were; 1)
> not explaining the word *attack* in I-D version 2 and/or referencing
> explainations. 2) wrong explaination of physical communication in
> MANET.
> Both ideas ware changed please see the two versions of I-D 2 and 3.
>=20
> Example error idea in the I-D was:
> [I-D wrong idea] As wireless radio waves can be captured as well as trans=
mitted
> by any wireless device within radio range.
> [my discovery contribution]
> http://www.ietf.org/mail-archive/web/manet/current/msg15250.html
>=20
>>=20
>> Caveating my answers below as describing a contribution to a document (n=
ot
>> a
>> contribution in the wider IETF sense)
>=20
> An IETF I-D contribution is a contribution (don't care about the
> editors' beleive of kind of contributions), small, large, substantial,
> non-substantial, minor, major, from-expert, not-from-expert,
> from-popular, from-non-popular, from-f2f-participant,
> from-remote-participant, etc.
>>=20
>>> Why don't you consider discovering an error as a contribution?
>>=20
>> I would personally consider discovering a major error as something I wou=
ld
>> acknowledge it in a document I was editing.
>=20
> You use word major as if we know what it means. Something minor to you
> may be major to someone else don't you think. If your documents if for
> experts please mention that in you documents, please know your
> audiance/readers. I understand that IETF documents are for ALL the
> Internet Community on EARTH. Therefore, the word major/minor is
> relative to the reader not writer.
>=20
>> I would personally consider discovering multiple minor errors as somethi=
ng
>> I
>> would acknowledge it in a document I was editing.
>=20
> Again you say you, I want IETF opinion not editors, I want WG
> decisions not your decisions, however, I already waiting for the IESG
> decisions on this matter, and I understand that your decision is a one
> part of that but not full/final. One error discovery or multiple, both
> are contributions and are needed. In our volunteering work if the
> work/I-D/RFC has many mistakes we don't blame the editors but the
> community, but if the work had no mistake we give all credit to
> authors, IMHO, we always should refer to the community in good or bad
> outcomes of IETF documents. Therefore acknowledging the parts of
> community is important.
>>=20
>> However, there is no requirement for editors to act in that way.
>=20
> No, editors are required to edit/act what the community is seeking,
> why are they called editors for the WG? the authority is for the WG
> not editors.
>=20
>> Furthermore,
>> you do not fit into these categories for this document.
>=20
> I do fit, I think you should not decide now, let it to be done through
> IETF procedure.
>=20
>>=20
>>> Why don't you consider providing new ideas a contribution?
>>=20
>> I would consider providing major ideas as something I would acknowledge =
it
>> in a
>> document I was editing.
>> I would consider providing smaller ideas through text for inclusion in t=
he
>> document as something I would acknowledge it in a document I was editing=
.
>> You do not fit into these categories for this document.
>=20
> I think I do fit from IETF point of view (maybe not yours). I gave my
> discovery of error, and if the editors want text I will give them, it
> is a discussion issue between both sides in a WG. Text is not much
> important like the idea, the idea is the most important thing in any
> organisation. English texting can be another contribution, or proof
> readings, but the main contribution is the idea that was changed.
>=20
>>=20
>>> What is your definition to contribution?
>>=20
>> As above, or written text that was included or modified for inclusion in=
 a
>> document and represents a material or substantial part of the document.
>=20
> the idea is more important than text, if changed sentence idea we
> SHOULD acknowledge, if changed sentance text without changing idea we
> do not have to acknowledge. So text changing/adding without new-idea
> or English correction is not acknowledged im my opinion.
>=20
>>=20
>>>> I also believe that the comments he made did not advance the
>>>> content of the document.
>>>=20
>>> So I understand that you need to have advance the content then you
>>> acknowledge.
>>>=20
>>>> Furthermore, per multiple references (such as RFC 2026) the
>>>> Acknowledgements section is used to "properly acknowledge
>>>> major contributors.
>>>=20
>>> I am trying to find that condition of *major contribution*,
>>=20
>> I would borrow from 2026 and 5378 to say a material or substantial
>> contribution
>> to the document.
>>=20
>> And, before you ask, no-one is going to write down a rule that says 139
>> characters is not substantial, but 140 is.
>>=20
>> This is one of the places where a principal of reasonableness applies. I
>> would
>> know a major contribution if I saw one. I did not see one from you in th=
is
>> case.
>=20
> I will wait for the IESG decision on that. Major or minor is relative
> to the readers not to the writers. You have big experience but that
> does not mean you should exclude any minor contribution, I hope you
> reconsider that. Some experts don't like to show that non-popular
> found their mistakes, but Why thoes experts came to use IETF service
> which calls-reviews to all levels of experties to contribute to the
> document they author under IETF ownership?
>=20
>>=20
>>>> " Normal IETF business is to discuss not seek acknowledgement.
>>>=20
>>> Ideas, Comments and reviews are included in the discuss for drafts
>>> progress. Seeking acknowledgement is not wrong within IETF, but please
>>> consider *not acknowledging reviews* within IETF documents is not IETF
>>> culture (we are not paid so why you thinking much of the business, the
>>> IETF business will only progress with acknowledging the volunteers).
>>=20
>> If you want to change the way that the IETF participants (and document
>> authors/editors in particular) acknowledge reviews of their documents, t=
hen
>> please start a separate thread or, better still, write an I-D and see
>> whether
>> you can gain consensus.
>=20
> I know that, but your advise comes back to you also, if you want to
> change the community expectations close to your opinions, I advise you
> to write an I-D that shows where to exclude participants to IETF
> documents.
>=20
>> The last time you brought this topic up on this
>> list, I
>> do not recall seeing support.
>=20
> Few did not support which were less than 15 persons, because IMO,
> there was no evidance of editors seeking to ignore reviewers
> contributions. Also, change is difficult any where in any
> organisation, so it will take time, IMO, people realise that
> participating-experts of IETF are the minority comapared to the
> community. I decided to complain any procedure error first and then
> write about what happend, so I will wait to see what is the IESG
> decision regarding the acknowledgement request. Please note that I
> have many procedural I-D in mind but it depends on the right time to
> submit it and get support.
>=20
>>=20
>> The only reason I can find for someone being able to demand that they ar=
e
>> named
>> in an Acknowledgements Section is for conformance to the IETF's Rights
>> policies.
>=20
> My reason is that the truth SHOULD be reflected on the document. If
> you are editor I recommend you may say in the section thanks to x for
> his minor contribution if that satisfies your WG you work with, but
> not to ignore the truth. The truth is that IETF is calling for reviews
> from the community mostly not only from companies, and that your
> document changed an idea, so you ack.
>=20
>>=20
>>>> I do not propose to do an explicit consensus call on whether Abdussala=
m
>>>> should be named in this draft.
>>>=20
>>> IMO, it should have been done in the WG.
>>=20
>> Thank you for your opinion.
>> Are you asserting that consensus on the readiness of this document for a
>> publication request was incorrectly called by the working group chairs.
>> This
>> would be a serious allegation against the chairs and I would require
>> evidence
>> that there had been no consensus or that they had made an incorrect
>> assessment
>> of the consensus.
>=20
> No, I accepted that the I-D goes to IESG only the complaint request of
> acknowledgement and the community reviews in IETF-LC. The wg chair
> mentioned my complaint in his report. I wait for the IESG decisions
> related to this I-D.
>=20
> Best Regards
>=20
> Abdussalam Baryun
>=20
> A Participant working in IETF (subscribed)
> A Memebr of Internet Society (registered)
>=20
>=20



From sm@resistor.net  Sat Jun  8 12:47:09 2013
Return-Path: <sm@resistor.net>
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 5C5DA21F9632 for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 12:47:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 3jHLDkO4F05o for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 12:47:08 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5531521F9600 for <ietf@ietf.org>; Sat,  8 Jun 2013 12:47:07 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r58Jl1Ww027183; Sat, 8 Jun 2013 12:47:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1370720826; bh=Mc1lHVcs1IWNQMuAdwevvHtrBi17aZylrTPV/tEFjS0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xVBe3Sw6eKEZuaNiQUibqyg6xANCS/na+0EcPPHsNdWDA5KngUb42UIPyVKgCfyA2 JP8pGC+69mzvrqthHX+wqQyBnBw64++NuXZmhEfNh+bH3hwnPd9dFIg6wjmJymOWUv fZ2cIe0Y0kkbE7tnOWxNfp/08CVxecSwAlD0wBu0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1370720826; i=@resistor.net; bh=Mc1lHVcs1IWNQMuAdwevvHtrBi17aZylrTPV/tEFjS0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Z8pNcZE0joYd25D96ub58oPZojBQr71e6eWuV0DcxXkPaCcD1hReaSlp2ORlYLUGL xQaWDdv/mfh9AtKsijVlhk+ZvkpkX6oi+1r33lYp5GeQmV5VOVG98ZUNYSM6jytOU/ sQjkaOTQEJeyiBNpcgqraKS947fnJNs78Eok0i14=
Message-Id: <6.2.5.6.2.20130608092332.0cb80b58@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 08 Jun 2013 11:09:04 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: ietf@ietf.org is a failure (was: Weekly posting summary for ietf@ietf.org)
In-Reply-To: <710CFEA093055148BDE84DEC@[10.121.6.76]>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com> <201306071651.r57Gp9Sf028501@cichlid.raleigh.ibm.com> <7E35BCF0-B218-4A72-82E3-309320113D6A@gmail.com> <710CFEA093055148BDE84DEC@[10.121.6.76]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john-ietf@jck.com>
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: Sat, 08 Jun 2013 19:47:09 -0000

At 15:58 07-06-2013, John C Klensin wrote:
>And it is getting to that conclusion from the above that often
>troubles me about the posting summary list rankings.  Assuming a
>significant issues shows up on the list, whether in conjunction
>with a Last Call or something else.  Posting a comment and then
>following up the comments of others with a couple of more
>postings constitutes three messages in a week, which is pretty
>reasonable.  On the other hand, if there are four such issues in
>a single week (it happens) then that same individual gets
>"credited" with a dozen messages, which would make the top of
>the list in many weeks.

I'll reuse some text from IETF 55:

  - Decisions are taken by backroom deals, intimidation and
    mob psychology

  - People unsubscribe in disgust in droves

Many years ago the following criticism was made against another body:

   "The process is stacked in favour of multinationals with expense accounts
    who can afford to talk on the phone for two hours a week and jet to world
    capitals for meetings."

The IESG once said that it prefers that comments on Last Calls be 
sent to the ietf@ietf.org list.  The IESG also said that authors, 
working group Chairs and the responsible Area Director are presumed 
to see all such messages.

Is posting the summary list ranking a form of intimidation?  I don't 
know.  If ietf@ietf.org is a failure as significant issues are not 
showing up on the list (see quoted text above) or if the IESG prefers 
that comments on Last Calls be sent to some other list it can say 
that.  If people unsubscribing in droves is a problem, the IESG could 
recommend having two hour phone calls a week and meetings in world 
capitals for Last Calls.  If the IESG believes that it is more 
practical to take decisions through backroom deals it can use a 
non-public list for handling Last Calls.

If a significant number of people cannot act or conduct themselves in 
a proper way, especially toward others, it is a social problem.  If 
people cannot filter the ietf@ietf.org mailing list, it is a 
technical problem.  The IETF has published a specification which 
describes a language for filtering email messages at time of final 
delivery.  After reading the latest messages to the list I might conclude that:

  (i)   people do not know about the mail filtering language

  (ii)  people are having technical difficulties using email

  (iii) it might rain tomorrow

As an off-topic comment, there are are alternative ways in making a 
decision; the best judgement of the most experienced or IETF Consensus.

Regards,
-sm 


From melinda.shore@gmail.com  Sat Jun  8 12:55:56 2013
Return-Path: <melinda.shore@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 495F521F9643 for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 12:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 djikZ+70sYDF for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 12:55:55 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id C18E621F9640 for <ietf@ietf.org>; Sat,  8 Jun 2013 12:55:55 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id xb12so5810748pbc.40 for <ietf@ietf.org>; Sat, 08 Jun 2013 12:55:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=xA7MhcRgKTUh9xBHtnaFgNs1AwVAcOpkvwES33S1c80=; b=Ka24uuidS8pux8+kSFMovySCFiFB5OBv0enJ8J3FO7cJA86N92HJ9Wqm2tuf9xmJaz XsxW7d7lhIqDuWK64jx06gHAa7WxMLAZaUc3SmfEm3l24Xe43qaeJPUejOgNXe+0vVk5 dUdDCAvPO09rgIppWAljdX7AUjPvfVvzHzOKDAB35BMoPxiS0Ifr6ittSeyW8m7D2ehB QHxG3qYtblxkx8gyI8z8C3KISDyNbsRR3RlI4LsuTAsE2QHBbaaSsJ0FfQ9V9K5F5atI IE6IFRB2mF/EzfXhiISTrkNdQ+kunJfDsdLC/8QJPb7jH0a+XnGSRGfaPDBpbYMj+/wr j2TQ==
X-Received: by 10.66.232.9 with SMTP id tk9mr8034167pac.20.1370721355468; Sat, 08 Jun 2013 12:55:55 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id xn5sm8025488pab.0.2013.06.08.12.55.53 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Jun 2013 12:55:54 -0700 (PDT)
Message-ID: <51B38C47.5020602@gmail.com>
Date: Sat, 08 Jun 2013 11:55:51 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: ietf@ietf.org is a failure
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com> <201306071651.r57Gp9Sf028501@cichlid.raleigh.ibm.com> <7E35BCF0-B218-4A72-82E3-309320113D6A@gmail.com> <710CFEA093055148BDE84DEC@[10.121.6.76]> <6.2.5.6.2.20130608092332.0cb80b58@resistor.net>
In-Reply-To: <6.2.5.6.2.20130608092332.0cb80b58@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Sat, 08 Jun 2013 19:55:56 -0000

On 6/8/13 10:09 AM, SM wrote:
> As an off-topic comment, there are are alternative ways in making a
> decision; the best judgement of the most experienced or IETF Consensus.

I don't think it's off-topic.  Consensus (rough or otherwise) requires
that at some point people can live with decisions with
which they disagree.  To the extent that we've seen recent misbehavior
on this list, it's from only one person who's rejecting the consensus
and rejecting the process.  It's really annoying but I don't think
it's particularly disruptive.  If it becomes disruptive, there's a
rarely-used hammer: the PR action.

Melinda


From brian.e.carpenter@gmail.com  Sat Jun  8 13:21:05 2013
Return-Path: <brian.e.carpenter@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 57C3521F962D for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 13:21:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level: 
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 7F3HvtjmYJdD for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 13:21:04 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id D817F21F962B for <ietf@ietf.org>; Sat,  8 Jun 2013 13:21:04 -0700 (PDT)
Received: by mail-pa0-f43.google.com with SMTP id hz11so2536005pad.2 for <ietf@ietf.org>; Sat, 08 Jun 2013 13:20:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=WI0NcgEd5h/rNat/AvSM7E5bbaZ6rvKl1zkcf0YyTMQ=; b=VpHTYZlCRSrg28005XbIaGwixy39b7pjoNYLEdnUQ9llCL+NbPHSB1WZXwG0Ni1PjB GT9MmKn0Z3jaLkX9NyDZ1M9ushabct0GgpAEeMnZWTB2VeybQK16zzBdfVw9a2vm5JEh auDiZKOkvOPTiw8qcV6+ftn0AmznTeBy8J4lrgGi7EnUiBqsyf+xzCrZydFKFtK0o0jy F782qXsM6LCT22PpH/t5wE6wF+9HjFb3rhGkQlISaPPeoZ0kx9pbMEQke33aGRNf9kvO 8SDK1RmbGwqfOTWFW2q2+vgHtVFrhgmhEWUAUI5svK892wKhGiS9JbXmv4AL/EEX5RUl 6Ndw==
X-Received: by 10.68.8.68 with SMTP id p4mr3953322pba.168.1370722855911; Sat, 08 Jun 2013 13:20:55 -0700 (PDT)
Received: from [192.168.1.2] (70.71.252.27.dyn.cust.vf.net.nz. [27.252.71.70]) by mx.google.com with ESMTPSA id pe9sm4048941pbc.35.2013.06.08.13.20.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Jun 2013 13:20:55 -0700 (PDT)
Message-ID: <51B39224.1030808@gmail.com>
Date: Sun, 09 Jun 2013 08:20:52 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: ietf@ietf.org is a failure
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>	<CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>	<201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>	<CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>	<alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com>	<201306071651.r57Gp9Sf028501@cichlid.raleigh.ibm.com>	<7E35BCF0-B218-4A72-82E3-309320113D6A@gmail.com>	<710CFEA093055148BDE84DEC@[10.121.6.76]>	<6.2.5.6.2.20130608092332.0cb80b58@resistor.net> <51B38C47.5020602@gmail.com>
In-Reply-To: <51B38C47.5020602@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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: Sat, 08 Jun 2013 20:21:05 -0000

On 09/06/2013 07:55, Melinda Shore wrote:
> On 6/8/13 10:09 AM, SM wrote:
>> As an off-topic comment, there are are alternative ways in making a
>> decision; the best judgement of the most experienced or IETF Consensus.
> 
> I don't think it's off-topic.  Consensus (rough or otherwise) requires
> that at some point people can live with decisions with
> which they disagree.  To the extent that we've seen recent misbehavior
> on this list, it's from only one person who's rejecting the consensus
> and rejecting the process.  It's really annoying but I don't think
> it's particularly disruptive.  If it becomes disruptive, there's a
> rarely-used hammer: the PR action.

I agree. Whatever misbehaviour Melinda means hasn't troubled me;
it must be a user or a thread that I filter to junk.
Disagreement is fine as long as people in the end understand
when they're in the rough and not in the consensus.

There are times when this list annoys me too, but it is far from
a failure IMHO.

   Brian



From andy@yumaworks.com  Sat Jun  8 18:20:03 2013
Return-Path: <andy@yumaworks.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 C8FF821F9374 for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 18:20:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 Opa-FcdHb1s3 for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 18:20:03 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB4E21F85BF for <ietf@ietf.org>; Sat,  8 Jun 2013 18:20:03 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id fb1so3448875pad.9 for <ietf@ietf.org>; Sat, 08 Jun 2013 18:20:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=gzwABxSoJsDCpGkz8KRj1jc26hklokrEfHB9yYU2NSA=; b=XvK3FBfLBjKbc0o24uFmjN9wkz7CX9oCr1kYsxafNvhaJ0/u1LW3n0nougIiWB5wte woDjKrEHdcBuKr9kqMu1Xommkl2rqZxe/nqyTCTL/OEEnsBpp7QmuxtVug+Hk4mqSkLn 2c5Ou3TaAM4OUT4jPRwOO1D6XY/JnKa3w733rJvPqY4TszQ8wVWj5sM0JCF0/b6npUsr J+SOW1u7kZu0Trg8zqRwUAwADM5EORndXEViTjnnaISDIIPgoXFXSUq65d/JyRYyYrVr HTRWb2zliCD3EzFKNmnEBwbtvOhOpoVtEyh1PWKCxI0dHhWNh8f7zhSXKffPUhnqhevf Txpg==
MIME-Version: 1.0
X-Received: by 10.68.103.194 with SMTP id fy2mr4432530pbb.158.1370740802801; Sat, 08 Jun 2013 18:20:02 -0700 (PDT)
Received: by 10.70.87.103 with HTTP; Sat, 8 Jun 2013 18:20:02 -0700 (PDT)
In-Reply-To: <51B39224.1030808@gmail.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com> <201306071651.r57Gp9Sf028501@cichlid.raleigh.ibm.com> <7E35BCF0-B218-4A72-82E3-309320113D6A@gmail.com> <710CFEA093055148BDE84DEC@10.121.6.76> <6.2.5.6.2.20130608092332.0cb80b58@resistor.net> <51B38C47.5020602@gmail.com> <51B39224.1030808@gmail.com>
Date: Sat, 8 Jun 2013 18:20:02 -0700
Message-ID: <CABCOCHTjta3c-sEWv1bQAzVZbjSXfJfN3iaO1JkEtvM4Fh8Gyw@mail.gmail.com>
Subject: Re: ietf@ietf.org is a failure
From: Andy Bierman <andy@yumaworks.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b5d63cea168c904deae7665
X-Gm-Message-State: ALoCoQlmyOk8av6uxmoUZeI4tt/aVeZgFHooq1desUZkcajFgwhK8TnaOsGLNHWl8ti1ltG/N9WN
Cc: 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: Sun, 09 Jun 2013 01:20:03 -0000

--047d7b5d63cea168c904deae7665
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I'm not sure how the desire for IETF Last Call discussions
to be on a dedicated and constrained mailing list in any way
implies that this generalized and unconstrained list is somehow a failure.

Filtering by subject line is unreliable.
For example, please provide a filter that will
not have any false positives or negatives over the
past 20,000 emails on this list. Do we have tools that make sure
no human has altered any subject line inappropriately?
Filtering by mailing list address is much easier and more reliable.


Andy




On Sat, Jun 8, 2013 at 1:20 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 09/06/2013 07:55, Melinda Shore wrote:
> > On 6/8/13 10:09 AM, SM wrote:
> >> As an off-topic comment, there are are alternative ways in making a
> >> decision; the best judgement of the most experienced or IETF Consensus.
> >
> > I don't think it's off-topic.  Consensus (rough or otherwise) requires
> > that at some point people can live with decisions with
> > which they disagree.  To the extent that we've seen recent misbehavior
> > on this list, it's from only one person who's rejecting the consensus
> > and rejecting the process.  It's really annoying but I don't think
> > it's particularly disruptive.  If it becomes disruptive, there's a
> > rarely-used hammer: the PR action.
>
> I agree. Whatever misbehaviour Melinda means hasn't troubled me;
> it must be a user or a thread that I filter to junk.
> Disagreement is fine as long as people in the end understand
> when they're in the rough and not in the consensus.
>
> There are times when this list annoys me too, but it is far from
> a failure IMHO.
>
>    Brian
>
>
>

--047d7b5d63cea168c904deae7665
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>I&#39;m not sure how the desire for IETF Last Call d=
iscussions</div><div>to be on a dedicated and constrained mailing list in a=
ny way</div><div>implies that this generalized and unconstrained list is so=
mehow a failure.</div>
<div><br></div><div>Filtering by subject line is unreliable.</div><div>For =
example, please provide a filter that will</div><div>not have any false pos=
itives or negatives over the</div><div>past 20,000 emails on this list. Do =
we have tools that make sure</div>
<div>no human has altered any subject line inappropriately?</div><div>Filte=
ring by mailing list address is much easier and more reliable.</div><div><b=
r></div><div><br></div><div>Andy</div><div><br></div><div><br></div><div>
<br></div><div><br><div class=3D"gmail_quote">On Sat, Jun 8, 2013 at 1:20 P=
M, Brian E Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpen=
ter@gmail.com" target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;</span>=
 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On 09/06/2013 07:55, Melinda Shore wrote:<br=
>
&gt; On 6/8/13 10:09 AM, SM wrote:<br>
&gt;&gt; As an off-topic comment, there are are alternative ways in making =
a<br>
&gt;&gt; decision; the best judgement of the most experienced or IETF Conse=
nsus.<br>
&gt;<br>
&gt; I don&#39;t think it&#39;s off-topic. =A0Consensus (rough or otherwise=
) requires<br>
&gt; that at some point people can live with decisions with<br>
&gt; which they disagree. =A0To the extent that we&#39;ve seen recent misbe=
havior<br>
&gt; on this list, it&#39;s from only one person who&#39;s rejecting the co=
nsensus<br>
&gt; and rejecting the process. =A0It&#39;s really annoying but I don&#39;t=
 think<br>
&gt; it&#39;s particularly disruptive. =A0If it becomes disruptive, there&#=
39;s a<br>
&gt; rarely-used hammer: the PR action.<br>
<br>
I agree. Whatever misbehaviour Melinda means hasn&#39;t troubled me;<br>
it must be a user or a thread that I filter to junk.<br>
Disagreement is fine as long as people in the end understand<br>
when they&#39;re in the rough and not in the consensus.<br>
<br>
There are times when this list annoys me too, but it is far from<br>
a failure IMHO.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0Brian<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--047d7b5d63cea168c904deae7665--

From brian.e.carpenter@gmail.com  Sat Jun  8 18:27:20 2013
Return-Path: <brian.e.carpenter@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 C65DD21F84AA for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 18:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 LvoUvGFCx7lc for <ietf@ietfa.amsl.com>; Sat,  8 Jun 2013 18:27:20 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB2321F842B for <ietf@ietf.org>; Sat,  8 Jun 2013 18:27:20 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa11so3445157pad.5 for <ietf@ietf.org>; Sat, 08 Jun 2013 18:27:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4v0foxdc6aGNwqAgh/+pIZZOeI27SJXqedn13IKUw0s=; b=uKG0QLJ1JF5cZKbtcNqiyIj7OMZTOqYRc+G6WRKGNpx5n9FV4ZpY/nG2ScEc5HvbPl njaqmX49g/t53nFAgqIXX70+7vD4YOnmXjsT51vXWoV8syF/P3MG2F6uujVsum1LnDNt L2mVYoSk4Wx5Jnxr0b7QGpxv1xW9n6A0jW/JKhdAEVQehg7fURfllxUo3lQf5X2y+0Ea lA9MoZAetRhp4buo9t5h7+EkcdA8KzbjVNPKwt1Kfh53bIsSJXMuM922GMrvn4xsBzL9 RCPQX3PfkaxfQaaXaii40M2ztlzjGLWJd5g45erEb8DOjrSAcAN3DjkRTet9S9u1E7nK n40g==
X-Received: by 10.68.197.98 with SMTP id it2mr4515361pbc.200.1370741237688; Sat, 08 Jun 2013 18:27:17 -0700 (PDT)
Received: from [192.168.1.2] (70.71.252.27.dyn.cust.vf.net.nz. [27.252.71.70]) by mx.google.com with ESMTPSA id 6sm4650321pbn.45.2013.06.08.18.27.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Jun 2013 18:27:17 -0700 (PDT)
Message-ID: <51B3D9F3.70306@gmail.com>
Date: Sun, 09 Jun 2013 13:27:15 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: ietf@ietf.org is a failure
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>	<CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>	<201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>	<CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>	<alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com>	<201306071651.r57Gp9Sf028501@cichlid.raleigh.ibm.com>	<7E35BCF0-B218-4A72-82E3-309320113D6A@gmail.com>	<710CFEA093055148BDE84DEC@10.121.6.76>	<6.2.5.6.2.20130608092332.0cb80b58@resistor.net>	<51B38C47.5020602@gmail.com>	<51B39224.1030808@gmail.com> <CABCOCHTjta3c-sEWv1bQAzVZbjSXfJfN3iaO1JkEtvM4Fh8Gyw@mail.gmail.com>
In-Reply-To: <CABCOCHTjta3c-sEWv1bQAzVZbjSXfJfN3iaO1JkEtvM4Fh8Gyw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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: Sun, 09 Jun 2013 01:27:20 -0000

On 09/06/2013 13:20, Andy Bierman wrote:
> Hi,
> 
> I'm not sure how the desire for IETF Last Call discussions
> to be on a dedicated and constrained mailing list in any way
> implies that this generalized and unconstrained list is somehow a failure.
> 
> Filtering by subject line is unreliable.
> For example, please provide a filter that will
> not have any false positives or negatives over the
> past 20,000 emails on this list. Do we have tools that make sure
> no human has altered any subject line inappropriately?
> Filtering by mailing list address is much easier and more reliable.

True, but it's a much coarser implement. Indeed, I mainly filter
to 'junk' rather than 'trash' so that once in a while I can
check for false positives. False negatives aren't that big a
problem in practice; the delete key works quickly.

   Brian

From dromasca@avaya.com  Sun Jun  9 00:38:18 2013
Return-Path: <dromasca@avaya.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 C274521F9344 for <ietf@ietfa.amsl.com>; Sun,  9 Jun 2013 00:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 BZzbb3RICDCf for <ietf@ietfa.amsl.com>; Sun,  9 Jun 2013 00:38:13 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 50E2921F8EAE for <ietf@ietf.org>; Sun,  9 Jun 2013 00:38:12 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0FAAcwtFGHCzI1/2dsb2JhbABZgmghMEm+QHgWdIIjAQEBAQMSCx00BAcMBAIBCA0EBAEBAQoOBgkHMhQJCAIEAQ0FCBqHawELoBKbBRMEjgeBADEHBhKCZ2EDk26KFIsAgViBN4FqJBk
X-IronPort-AV: E=Sophos;i="4.87,830,1363147200"; d="scan'208";a="15336565"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 09 Jun 2013 03:38:11 -0400
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 09 Jun 2013 03:33:28 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Sun, 9 Jun 2013 03:38:10 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IAB Chair <iab-chair@iab.org>
Subject: RE: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802	/ IETF Relationship"
Thread-Topic: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 / IETF Relationship"
Thread-Index: AQHOYres0GPmgHO6FkeqJfshJp2mM5ktARLA
Date: Sun, 9 Jun 2013 07:38:09 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA19881C@AZ-FFEXMB04.global.avaya.com>
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org> <51B08AD0.2070908@cs.tcd.ie>
In-Reply-To: <51B08AD0.2070908@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IAB <iab@iab.org>, IETF <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: Sun, 09 Jun 2013 07:38:18 -0000

Hi Steve,

We shall ask the question, but I can already guess the answers. Current IEE=
E rules (copyright rules I think) do not allow for sharing of work-in-progr=
ess drafts with no access control. You need to be a participant of some sor=
t in order to access such documents, and this validated by the fact that yo=
u know the username/password combination. These are IEEE, beyond the power =
of IEEE 802 to change.=20

As a chair who dealt with this for a number of years in the past I can bear=
 witness that this is not a huge task. The IEEE 802 entrusts the chair with=
 the username and password to access IEEE 802 WG documents. The IETF WG cha=
ir from time to time will forward this information on a per request basis t=
o IETF participants who need access to the IEEE 802 documents.=20

Regards,

Dan
=20

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Stephen Farrell
> Sent: Thursday, June 06, 2013 4:13 PM
> To: IAB Chair
> Cc: IAB; IETF
> Subject: Re: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE
> 802 / IETF Relationship"
>=20
>=20
> A couple of minor comments:
>=20
> - For some unfathomable reason IEEE people seem to call mailing lists
> "reflectors" - that might be worth a mention. Section 4 otherwise seems
> repetitive.
>=20
> -  3.3.1.4 says: Since it is
>    possible to participate in IETF without attending meetings, or even
>    joining a mailing list, IETF WG chairs will provide the information
>    to anyone who requests it.  However, since IEEE 802 work-in-progress
>    is copyrighted, incorporating material into IETF documents or posting
>    the username/password on mailing lists or websites is not permitted.
>=20
> That's a pretty bogus setup. I would think that if IEEE do want to share
> some or all drafts with us they could much more easily create a web page
> when those drafts are available without access control.
> Or we could if they didn't mind. (Or I could do it if there's no "we"
> that wants to:-) Asking IETF WG chairs to deal with passwords is a bit
> silly. I'm not objecting to this, but am suggesting someone ask IEEE if
> they'd like to consider the silliness here and fix it.
>=20
> S.
>=20
>=20
> On 06/05/2013 07:50 PM, IAB Chair wrote:
> > This is a call for review of "The IEEE 802 / IETF Relationship"
> > prior to potential approval as an IAB stream RFC.
> >
> > The document is available for inspection here:
> > https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/
> >
> > The Call for Review will last until 20 June 2013.
> > Please send comments to iab@iab.org.
> >
> > On behalf of the IAB,
> >   Russ Housley
> >   IAB Chair
> >
> >

From randy@psg.com  Sun Jun  9 03:42:26 2013
Return-Path: <randy@psg.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 65BBF21F8AF7 for <ietf@ietfa.amsl.com>; Sun,  9 Jun 2013 03:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 MMKVrgPCEv0m for <ietf@ietfa.amsl.com>; Sun,  9 Jun 2013 03:42:26 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0493721F88AC for <ietf@ietf.org>; Sun,  9 Jun 2013 03:42:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Uld4n-000PnC-OO; Sun, 09 Jun 2013 10:42:22 +0000
Date: Sun, 09 Jun 2013 12:42:18 +0200
Message-ID: <m2sj0rsgz9.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: ietf@ietf.org is a failure
In-Reply-To: <CABCOCHTjta3c-sEWv1bQAzVZbjSXfJfN3iaO1JkEtvM4Fh8Gyw@mail.gmail.com>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <alpine.LRH.2.01.1306070901590.4180@egate.xpasc.com> <201306071651.r57Gp9Sf028501@cichlid.raleigh.ibm.com> <7E35BCF0-B218-4A72-82E3-309320113D6A@gmail.com> <710CFEA093055148BDE84DEC@10.121.6.76> <6.2.5.6.2.20130608092332.0cb80b58@resistor.net> <51B38C47.5020602@gmail.com> <51B39224.1030808@gmail.com> <CABCOCHTjta3c-sEWv1bQAzVZbjSXfJfN3iaO1JkEtvM4Fh8Gyw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: 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: Sun, 09 Jun 2013 10:42:26 -0000

> I'm not sure how the desire for IETF Last Call discussions to be on a
> dedicated and constrained mailing list

many years ago, a housing development thought they had a bad crime rate.
so they built a fence around it and only let residents in.  the crime
rate stayed the same.  funny thing.

procmail is your friend.

randy

From doug.mtview@gmail.com  Sun Jun  9 10:43:02 2013
Return-Path: <doug.mtview@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 84BEA21F8B98; Sun,  9 Jun 2013 10:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level: 
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6, J_CHICKENPOX_44=0.6]
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 6PZx9MKZWhn3; Sun,  9 Jun 2013 10:43:01 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id DFEAB21F8AE8; Sun,  9 Jun 2013 10:43:00 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id mc8so6489322pbc.18 for <multiple recipients>; Sun, 09 Jun 2013 10:43:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=bWkw7g37zIX6e1lWWbwbbdplwsK02CE71bFu9ux43Bw=; b=LdukkgqLaYBDrEaRoNNLi0jpAxrqDItu9UIHwPzEzXP8HfBL7dxAK0wewQID+Pl5f2 8Bxj4zvpBHXtPQRW+N6kXOFxbpOrc8k2/6ciTUoV7c/0qJRYFAREgmQheK4O4ei4+PgL 4zYyW/Sa8JLhL95aLGGwIoLtb/CM+47pegnriXn0RyBHcp/12DeY0Ce25/9C2wwZneWh l/d5WQnfVVY8fvHxAuPzg18a5vsQkfUnLmSH/e++cD1hXWh6zxSgQwvUazAw4Df/wv+O fmBdwd40FmajnrnKpjbxWMs3kPqhNeIBpz7QgMoEeXPF2jwSsnZHtk0nlFWyfL8geYNO 4dJA==
X-Received: by 10.68.213.101 with SMTP id nr5mr6835060pbc.22.1370799780613; Sun, 09 Jun 2013 10:43:00 -0700 (PDT)
Received: from [192.168.2.201] (c-98-207-206-162.hsd1.ca.comcast.net. [98.207.206.162]) by mx.google.com with ESMTPSA id bs2sm12121324pad.17.2013.06.09.10.42.58 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Jun 2013 10:42:59 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_49B9FC99-6988-4C17-8055-2A1CDDD67446"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Review of: draft-otis-dkim-harmful
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <CAL0qLwZ6t7TNvowfQwC53a8nZMtb-06B4zwB3=rWJW+EEpAKzg@mail.gmail.com>
Date: Sun, 9 Jun 2013 10:42:57 -0700
Message-Id: <8F830D23-443A-4437-B926-10972FEAAF6D@gmail.com>
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net> <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com> <CAL0qLwZ6t7TNvowfQwC53a8nZMtb-06B4zwB3=rWJW+EEpAKzg@mail.gmail.com>
To: Murray S. Kucherawy <msk@blackops.org>
X-Mailer: Apple Mail (2.1503)
Cc: iesg <iesg@ietf.org>, IETF Discussion <ietf@ietf.org>, Dave Rand <dave_rand@trendmicro.com>, Douglas Otis <doug_otis@trendmicro.com>
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: Sun, 09 Jun 2013 17:43:02 -0000

--Apple-Mail=_49B9FC99-6988-4C17-8055-2A1CDDD67446
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Jun 4, 2013, at 9:13 AM, Murray S. Kucherawy <msk@blackops.org> =
wrote:

> On Tue, Jun 4, 2013 at 4:08 AM, Douglas Otis <doug.mtview@gmail.com> =
wrote:=20
> In its current form, DKIM simply attaches a domain name in an unseen =
message fragment, not a message.  The ease in which the only assured =
visible fragment of the message signed by the domain being forged makes =
it impossible for appropriate handling to be applied or likely harm =
prevented.
>=20
>=20
> There are existence proofs that contradict this claim.  They have been =
brought to your attention in the past.

Thank you for your response.  Could I trouble you for a reference to the =
proofs or for you to expand on what you specifically mean?  The draft =
otis-dkim-harmful addendum captured actual DKIM =46rom header field =
spoofing delivered to the in-box for several major providers.

> It appears you're continuing to assign semantics to DKIM signatures =
that simply aren't there.  I don't know what else can be done to clarify =
this.

The semantics of d=3Ddomain and dkim=3Dpass appear to be at the root of =
the problem.    What other semantics are you suggesting?

> Procedurally speaking, what path do you anticipate your draft =
following?

To require messages with invalidly repeated header fields to not return =
a "pass" for DKIM signature validation.

I apologize if I missed your response to a private query.   I hope to =
post an update shortly covering all expressed concerns. =20

Regards,
Douglas Otis





--Apple-Mail=_49B9FC99-6988-4C17-8055-2A1CDDD67446
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 4, 2013, at 9:13 AM, Murray S. Kucherawy &lt;<a href="mailto:msk@blackops.org">msk@blackops.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">On Tue, Jun 4, 2013 at 4:08 AM, Douglas Otis <span dir="ltr">&lt;<a href="mailto:doug.mtview@gmail.com" target="_blank">doug.mtview@gmail.com</a>&gt;</span> wrote: <br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div class="im">In its current form, DKIM simply attaches a domain name in an unseen message fragment, not a message. &nbsp;The ease in which the only assured visible fragment of the message signed by the domain being forged makes it impossible for appropriate handling to be applied or likely harm prevented.<br>
</div>
<br></blockquote></div><br></div><div class="gmail_extra">There are existence proofs that contradict this claim.&nbsp; They have been brought to your attention in the past.<br></div></div></blockquote><div><br></div>Thank you for your response. &nbsp;Could I trouble you for a reference to the proofs or for you to expand on what you specifically mean? &nbsp;The draft otis-dkim-harmful addendum captured actual DKIM From header field spoofing delivered to the in-box for several major providers.</div><div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">It appears you're continuing to assign semantics to DKIM signatures that simply aren't there.&nbsp; I don't know what else can be done to clarify this.<br></div></div></blockquote><div><br></div>The semantics of d=domain and dkim=pass appear to be at the root of the problem. &nbsp; &nbsp;What other semantics are you suggesting?</div><div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">
Procedurally speaking, what path do you anticipate your draft following?<br></div></div></blockquote><div><br></div><div>To require messages with invalidly repeated header fields to not return a "pass" for DKIM signature validation.</div></div><div><br></div><div>I apologize if I missed your response to a private query. &nbsp; I hope to post an update shortly covering all expressed concerns. &nbsp;</div><div><br></div><div>Regards,</div><div>Douglas Otis</div><div><br></div><div><br></div><div><br></div><div><br></div></body></html>
--Apple-Mail=_49B9FC99-6988-4C17-8055-2A1CDDD67446--

From d3e3e3@gmail.com  Sun Jun  9 11:06:53 2013
Return-Path: <d3e3e3@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 891D021F8D10; Sun,  9 Jun 2013 11:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.275
X-Spam-Level: 
X-Spam-Status: No, score=-102.275 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 cM0VhXJ5YODZ; Sun,  9 Jun 2013 11:06:52 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 655D521F8C40; Sun,  9 Jun 2013 11:06:52 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id i4so909279oah.10 for <multiple recipients>; Sun, 09 Jun 2013 11:06:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xDvdhVwkMqFe+OuTSmaxE2l3nt0fcE/Io6HndvH9QcI=; b=P2YEQHDn21KeuPOI0MhISLF7sDw6a6DCdNobVLi+XDXQXAGpYH4JtF3IVe78Hweqgx 4wRymCZxdXe6JBNKeLCfqQjes34Bhk2AqN8qDk/xrEGtINwTU8rBfgBBs5d/WhknhVPI cOASMYzJA1rE6hmWeiorINRgdgknXLMVGDEu9NUolWDZ8Sv1S8YzeLC3fSZE4zA164jq q/YTrhkNQYjxjcWvPOXZR+JqXKWKaux7qd67M1aU1hilKuLitCF8I6VJpDNW0MnZq5Ye 3VK9Rm+PkdzlHLZdCpXZEwuHctDXiN7Enr3ttuO725/hXwZsFyHYqHQg2FoeU7hiEAKS 8/JA==
X-Received: by 10.60.84.143 with SMTP id z15mr5370775oey.30.1370801210507; Sun, 09 Jun 2013 11:06:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.12.65 with HTTP; Sun, 9 Jun 2013 11:06:30 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712980CA206@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712980CA206@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 9 Jun 2013 14:06:30 -0400
Message-ID: <CAF4+nEER=JdeKV6PU_8m2jJ8O182WHcsQ-ayODUTCp1jRx-X+w@mail.gmail.com>
Subject: Re: Gen-ART review of draft-eastlake-rfc5342bis-03
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: General Area Review Team <gen-art@ietf.org>, "joe.abley@icann.org" <joe.abley@icann.org>, "ietf@ietf.org" <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: Sun, 09 Jun 2013 18:06:53 -0000

Hi David,

On Sun, Jun 9, 2013 at 1:47 PM, Black, David <david.black@emc.com> wrote:
> The -03 version of this draft resolves all of the concerns raised by
> the Gen-ART review of the -02 version.

Thanks.

> Unfortunately, a serious typo/thinko snuck into the -03 version (been
> there, done that, myself).  Section 3.2 currently says:
>
>    00-42 is a protocol number under the IANA OUI (that is,
>    00-00-0E-00-42) to be used for documentation purposes.
>
> The parenthetical expansion of the protocol number is incorrect.
> The correct expansion uses -5E- instead of -0E-:

My apologies, you are correct. However, I believe that, in context,
the typo is pretty obvious.

>    00-42 is a protocol number under the IANA OUI (that is,
>    00-00-5E-00-42) to be used for documentation purposes.
>
> I strongly suggest submitting a -04 version of this draft to make
> the necessary single character correction (e.g., as opposed to using
> a RFC Editor Note for that purpose).

I defer entirely to JoelJaeggli, the sponsoring AD.

I'd be happy to submit a -04 or it seems to me it could easily be
fixed with an RFC Editor Note or at AUTH48 time. (Actually, it seems
likely to me that during IESG consideration, some other change will be
decided on and this can be fixed at the same time.)

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks,
> --David
>
>> -----Original Message-----
>> From: Black, David
>> Sent: Wednesday, June 05, 2013 6:13 PM
>> To: d3e3e3@gmail.com; joe.abley@icann.org; General Area Review Team
>> Cc: Black, David; joelja@bogus.com; ietf@ietf.org
>> Subject: Gen-ART review of draft-eastlake-rfc5342bis-02
>>
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-eastlake-rfc5342bis-02
>> Reviewer: David L. Black
>> Review Date: June 5, 2013
>> IETF LC End Date: June 4, 2013
>>
>> Summary:
>> This draft is on the right track but has open issues, described in the review.
>>
>> This draft updates the IANA registered Ethernet parameters for IETF use,
>> including recording values assigned for documentation.  It also makes some
>> minor changes to IANA procedures.
>>
>> IANA should review this entire draft, not just its IANA Considerations
>> section;
>> Pearl Liang appears to have done that comprehensive review for IANA.
>>
>> Major issues: None
>>
>> Minor issues: One, the IANA review also found this issue.
>>
>> Section 3.2 states:
>>
>>       IANA will assign "00-00-0E-00-42" as the protocol number under the
>>       IANA OUI to be used for documentation purposes.
>>
>> IANA has not made this assignment, but this assignment request is not
>> recorded in the IANA Considerations section where IANA actions are
>> requested and recorded by IANA after they have been performed.  This
>> assignment needs to be added to the IANA Considerations section;
>> see item 5 in the IANA review.
>>
>> Nits/editorial comments:
>>
>> Section 1: This document uses an "IESG Ratification" process for some
>> assignments.  This is not the same process as the "IESG Approval" process
>> defined in RFC 5226.  As those names could be confused by a casual reader
>> who is not strongly familiar with IANA processes, I suggest adding a
>> statement that the "IESG Ratification" process is defined in this document
>> and is not the same as the "IESG Approval" process in RFC 5226.  This could
>> be added after the sentence that cites RFC 5226.
>>
>> Section 1.4: It would be helpful to point out that there is no OUI assigned
>> for documentation purposes, but there are identifiers based on the IANA OUI
>> that have been assigned for documentation purposes.
>>
>> In general, the use of the acronym IAB for Individual Address Block is
>> unfortunate, but unavoidable, and this is clearly pointed out in the
>> definition of the IAB acronym in section 1.2.  Nothing can or should be
>> done about this.
>>
>> idnits 2.12.17 did not find any nits.
>>
>> Thanks,
>> --David
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>

From carlosm3011@gmail.com  Sun Jun  9 13:45:23 2013
Return-Path: <carlosm3011@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 477CE21F8E41 for <ietf@ietfa.amsl.com>; Sun,  9 Jun 2013 13:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.954
X-Spam-Level: 
X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 F18WbACwSse4 for <ietf@ietfa.amsl.com>; Sun,  9 Jun 2013 13:45:22 -0700 (PDT)
Received: from mail-gh0-x229.google.com (mail-gh0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id BDBF821F8A03 for <ietf@ietf.org>; Sun,  9 Jun 2013 13:45:22 -0700 (PDT)
Received: by mail-gh0-f169.google.com with SMTP id r1so774996ghr.28 for <ietf@ietf.org>; Sun, 09 Jun 2013 13:45:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mAx7fBhi3iEKifuE494KUx8CyuggvrLUuqZiWCId0Zs=; b=p2pFFfsIuqjJKRxe/t6yDK6SqIqObTHihhEqvw8DThE/uYfzD3bJCixSmbnty6Era0 v2enNCeEn5rykLFHDEC7gedTcMKkXqyWuXj5vOt5LTGgxg1U/TFYynqoeaaQJnw0N6eV dFBt9mZ5TADKhsAs4mxevkBn+chHRns9snP+kBvu+qqHeUg3X0bfhufwDM+ApQyyZbPY e9o2RALiyvEU2scpcULwJSdy4eeVoeVbheRxXzv5b9lYLYy7yp98HjQdeS8fkGEPBRqQ EOhj100AX2UFzhuHe13nTGKaUyTdh8F1oLCaNNQiCKt6hEBv1woh/efDFa/OkfI//ufd vptQ==
X-Received: by 10.236.67.36 with SMTP id i24mr2905885yhd.172.1370810722251; Sun, 09 Jun 2013 13:45:22 -0700 (PDT)
Received: from europa.local ([2001:470:d815:fe0:24d4:ef85:5ef4:2973]) by mx.google.com with ESMTPSA id f19sm11767417yhj.3.2013.06.09.13.45.20 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Jun 2013 13:45:21 -0700 (PDT)
Message-ID: <51B4E95D.60702@gmail.com>
Date: Sun, 09 Jun 2013 17:45:17 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com>	<CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com>	<201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com>	<CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>	<CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com>	<CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com> <51B223C7.2010401@braga.eti.br> <51B23A06.7060402@gmail.com> <51B23BDB.2060202@gmail.com>
In-Reply-To: <51B23BDB.2060202@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
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: Sun, 09 Jun 2013 20:45:23 -0000

As long the subject clearly identifies a last call request thread, I
don't see why the LC's cannot stay here.

There are already too many mailing lists in the world.

My humble opinion.

~Carlos

On 6/7/13 5:00 PM, Melinda Shore wrote:
> On 6/7/13 11:52 AM, Brian E Carpenter wrote:
>> Rule 1 for complex and divergent mail threads is to change the
>> Subject header when the subject changes. If you don't do that,
>> your mail is rather likely to get junked.
>>
>> I think that IETF last call threads should stay on the main IETF
>> discussion list. That is exactly the right place for them.
> 
> I tend to think so, as well.  You never know when someone's
> going to stumble over something and make a comment that matters.
> The cost is that you get jackasses being loud and petty, but frankly
> you'd get that on a last call mailing list, anyway, since IETF
> last calls have in a few cases been known to function as jackass
> magnets.
> 
> It seems to me that the real problem isn't last calls, it's
> people not understanding that behaving badly has a cost associated
> with it, and that cost is that they're alienating people they'd
> (apparently) like to work with and demolishing their chances of
> getting an editorship or moving into leadership roles.
> 
> Melinda
> 

From peter@akayla.com  Sun Jun  9 22:37:35 2013
Return-Path: <peter@akayla.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 4E80221F896D; Sun,  9 Jun 2013 22:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 SQAnvgn0TM01; Sun,  9 Jun 2013 22:37:30 -0700 (PDT)
Received: from p3plsmtpa07-05.prod.phx3.secureserver.net (p3plsmtpa07-05.prod.phx3.secureserver.net [173.201.192.234]) by ietfa.amsl.com (Postfix) with ESMTP id 783B321F8607; Sun,  9 Jun 2013 22:37:30 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-05.prod.phx3.secureserver.net with  id mVdT1l00F1huGat01VdUhD; Sun, 09 Jun 2013 22:37:29 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-jabley-dnsext-eui48-eui64-rrtypes.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-jabley-dnsext-eui48-eui64-rrtypes-04
Date: Sun, 9 Jun 2013 22:37:27 -0700
Message-ID: <03c601ce659c$98abe9f0$ca03bdd0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5lmC2m6gwvYZg7TOq4hiziFSg7Gw==
Content-Language: en-us
Cc: gen-art@ietf.org, 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: Mon, 10 Jun 2013 05:37:35 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-jabley-dnsext-eui48-eui64-rrtypes-04
Reviewer: Peter Yee
Review Date: June-09-2013
IETF LC End Date: June-17-2013
IESG Telechat date: Unknown

Summary: This draft is basically ready for publication as an Informational
RFC, but has nits that should be fixed before publication. [Ready with nits]

This draft defines DNS Resources Record Types for encoding IEEE 802 EUI-48
and EUI-64 addresses.

General: I am aware of the debate on the IETF mailing list as to whether
this draft could potentially harm user privacy.  I'm of the opinion that
this draft makes a useful specification of new DNS Resource Record Types.
Misuse of this specification and many others could harm privacy, but that
shouldn't necessarily dissuade us from publishing this draft.  The security
considerations cover the issues adequately.

Major issues:

Minor issues:

Nits:

Page 1, Abstract, 1st paragraph: After "e.g.", append a comma and delete an
extraneous space before "Ethernet".

Page 3, Introduction, 1st paragraph, 2nd sentence: change "This" to "These"
and change "specification defines" to "specifications define".

Page 3, Introduction, 2nd paragraph: append a comma after "e.g.".

Page 8, 1st paragraph, 1st sentence: change "behaviour" to "behavior".
Let's settle on the American variant of English for this draft. ;-)

Page 10, 3rd paragraph: as others have pointed out, having "the querier
already know some other permanent identifier" is security by obscurity and
is not advised.

		-Peter Yee




From prvs=1873a61d1e=magnus.westerlund@ericsson.com  Mon Jun 10 00:51:59 2013
Return-Path: <prvs=1873a61d1e=magnus.westerlund@ericsson.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 1A2DD21F854D; Mon, 10 Jun 2013 00:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 pcjtc2IIixWP; Mon, 10 Jun 2013 00:51:52 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id F3BC721F8519; Mon, 10 Jun 2013 00:51:51 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-9c-51b58595c4b0
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 8A.1F.15700.59585B15; Mon, 10 Jun 2013 09:51:49 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Jun 2013 09:51:49 +0200
Message-ID: <51B585A7.7060109@ericsson.com>
Date: Mon, 10 Jun 2013 09:52:07 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Elwyn Davies <elwynd@folly.org.uk>
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
References: <1370477514.4596.9052.camel@mightyatom> <51B1A95B.2030208@ericsson.com> <1370607960.4596.9114.camel@mightyatom> <51B1E8BD.80901@ericsson.com> <1370619602.4596.9175.camel@mightyatom>
In-Reply-To: <1370619602.4596.9175.camel@mightyatom>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDLMWRmVeSWpSXmKPExsUyM+Jvre7U1q2BBstarCwufjnCbnH8wA52 i6uvPrNYPNs4n8Vi6vLHLA6sHl9PtrN4LFnyk8njy+XPbAHMUdw2SYklZcGZ6Xn6dgncGbN3 9jEWXJCrmPbfu4HxiUQXIyeHhICJxJ1Jn9khbDGJC/fWs3UxcnEICZxilFh+ZgsrhLOcUWL2 61csIFW8AtoSZ+csB7NZBFQlvu/5xApiswlYSNz80cgGYosKBEsc2b4Zql5Q4uTMJ2C2iICa xOavDxhBhjILrGOU+LGsCaxBWCBMYt6WbiaIbYcZJSZt2Ad2EyfQfe/7Glkg7pOU2PKiHSzO LKAnMeVqCyOELS/RvHU2M4gtBHRdQ1MH6wRGoVlIls9C0jILScsCRuZVjOy5iZk56eWGmxiB gX1wy2/dHYynzokcYpTmYFES59XjXRwoJJCeWJKanZpakFoUX1Sak1p8iJGJgxNEcEk1MIqq VfHFeD+1rMxKDxN78chSxLnK+Pq289Hik4MWPGyK0NvMWSva9eun0smTgsWZkRsKxPL8UvPm n/BgdL2QsTH/h8jtlpsBO7VjWsW1BcxPXIjlMchftWa9Ws8vlsZXM9WfvvO6uvL7SeZQNgbb QyIeYdci7KbnPYpcNbHsskBBul/lG/X5SizFGYmGWsxFxYkA7ohWYD8CAAA=
Cc: General Area Review Team <gen-art@ietf.org>, IETF discussion <ietf@ietf.org>, "mmusic \(E-mail\)" <mmusic@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.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: Mon, 10 Jun 2013 07:51:59 -0000

On 2013-06-07 17:40, Elwyn Davies wrote:
> On Fri, 2013-06-07 at 16:05 +0200, Magnus Westerlund wrote:
> 
>>> Appendix F: I missed that the text/parameter format appeared in the
>>> examples for GET_PARAMETER and SET_PARAMETER. It isn't stated in the
>>> definitions of these methods what encodings are acceptable for the
>>> message bodies that may go with these methods and their responses.
>>
>> Exactly, that is intentional. These methods can use anything that has a
>> MIME type. Also it has HTTP's mechanisms for determining what formats
>> one supports.
>>
>>> Clearly the new text/parameter MIME format is one.  Is it the only one?
>>
>> It is the only one defined by IETF for this purpose. That is why it is
>> in the appendix so that RTSP users shall have something to define the
>> parameters they want in. However, they have to accept the limitations of
>> a basic text format.
>>
>>> I guess you could use a application/json or an XML format but I guess
>>> these would also either have to be called out explicitly in the method
>>> descriptions or put in as feature extensions.  This needs to be
>>> clarified in the method descriptions (s13).  The upshot of all this is
>>> that I think Appendix F needs to be pulled back into Section 20 as
>>> currently it is the only way to encode the message bodies.
>>
>> I can agree that the format negotiation for the bodies of
>> GET/SET_PARAMETER is not clear. I will look at proposing some
>> improvements of the text related to the handling of method bodies and
>> their format negotiation.
> Good. I don't see where the server tells what formats it accepts for
> either GET_PARAMETER or SET_PARAMETER.  Also the Accept spec doesn't say
> anything about SET_PARAMETER.  AFAICS the client could tell the server
> what formats it accepts as a side-effect of DESCRIBE but that's a bit
> arcane - and it is not clear how you would separate the formats for
> DESCRIBE from those for GET_PARAM and SET_PARAM.

Yes, I think this negotiation should happen on per methods basis.
>>
>> However, I am not pulling in Appendix F. It is an optional to use format
>> for parameter value pairs that can be used in these methods, it is not
>> required. Nor, does the specification define any parameters that are
>> transferred using this interface. The things that are in the appendix
>> are not core protocol, they represent either informational things, like
>> the examples and the state machine. The other appendices are normative
>> definitions of particular choices for things that can be combined or
>> used with RTSP, like RTP as media transport.
>>
> OK, it is possible to use GET_PARAM for basic requirements without using
> message bodies, so you can get away without defining a lowest common
> denominator format. However, the use of message bodies for SET_PARAM is
> RECOMMENDED so it seems a little odd not to ensure that server and
> client will have at least one format in common. (And its not as if we
> are dealing with a hugely complicated bit of spec for
> text/parameters! :-) ).  Then, given the example in GET_PARAMETER it
> seems sensible to advise implementing text/parameters as the default for
> GET_PARAM also.

Sure, I personally don't have any issue with making it at least SHOULD
implement text/parameters. But from my horizon a forward pointer with
the normative requirements is sufficient to accomplish that.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From superuser@gmail.com  Mon Jun 10 01:18:22 2013
Return-Path: <superuser@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 EAEA421F8AF4; Mon, 10 Jun 2013 01:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 6QRiJgBbgW+g; Mon, 10 Jun 2013 01:18:21 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 37FE121F88AC; Mon, 10 Jun 2013 01:18:18 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id n12so2843411wgh.1 for <multiple recipients>; Mon, 10 Jun 2013 01:18:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=zwjSkzystSs+TpwPeldOXcuwtRlYffGPin6nR5R4sKA=; b=mv67qCx+oBZBRPetvplmh8jSIrg96OtfJMbDPKr8zxuqub3+olcAAqDTFQ0RY+f3FS CG6rJGWQax5ok+P8i7CpYMDziI3+sdESKeNhLP+a/NlN6I91USg2MRMiyA5smWopCKuT NaDX6PfSIPswKzr1BJxnuGzWZDjDtGhWb/WQrbwDYkyfGF8wFw1WsNW/oggFDc2Kbm1P BDSsjyE+VLhhs2KI2Kp3Ba6e2PKKeJ9qiSo8jhG7P70EHbgRJCeITCqQLb3KYxAQz0W3 ZzBS2NT8lFn4ucRhN0JvJFE+04oifow1aR8CRfNlQeIIhgO76jsEc4ty7Ujv6TW1D8NE xTFw==
MIME-Version: 1.0
X-Received: by 10.194.239.225 with SMTP id vv1mr4832694wjc.63.1370852297124; Mon, 10 Jun 2013 01:18:17 -0700 (PDT)
Sender: superuser@gmail.com
Received: by 10.180.74.203 with HTTP; Mon, 10 Jun 2013 01:18:17 -0700 (PDT)
In-Reply-To: <8F830D23-443A-4437-B926-10972FEAAF6D@gmail.com>
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net> <371CD7F9-8643-4214-B379-9497F71079A3@gmail.com> <CAL0qLwZ6t7TNvowfQwC53a8nZMtb-06B4zwB3=rWJW+EEpAKzg@mail.gmail.com> <8F830D23-443A-4437-B926-10972FEAAF6D@gmail.com>
Date: Mon, 10 Jun 2013 01:18:17 -0700
X-Google-Sender-Auth: EbDUtu3cg3DUW84RA_CXxmvZkBw
Message-ID: <CAL0qLwY7ydHLOR1swpGW34wAk5-tNxkQWy3i-=CW6_cW98serg@mail.gmail.com>
Subject: Re: Review of: draft-otis-dkim-harmful
From: "Murray S. Kucherawy" <msk@blackops.org>
To: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary=089e0149338435b15904dec86c57
Cc: Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Dave Rand <dave_rand@trendmicro.com>, IETF Discussion <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: Mon, 10 Jun 2013 08:18:22 -0000

--089e0149338435b15904dec86c57
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Jun 9, 2013 at 10:42 AM, Douglas Otis <doug.mtview@gmail.com> wrote:

>
> Procedurally speaking, what path do you anticipate your draft following?
>
>
> To require messages with invalidly repeated header fields to not return a
> "pass" for DKIM signature validation.
>
>
That's a technical response.  What I asked was a procedural question.

--089e0149338435b15904dec86c57
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sun, Jun 9, 2013 at 10:42 AM, Douglas Otis <span dir=3D=
"ltr">&lt;<a href=3D"mailto:doug.mtview@gmail.com" target=3D"_blank">doug.m=
tview@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><br><div=
><div class=3D"im"><blockquote type=3D"cite"><div dir=3D"ltr"><div class=3D=
"gmail_extra">

Procedurally speaking, what path do you anticipate your draft following?<br=
></div></div></blockquote><div><br></div></div><div>To require messages wit=
h invalidly repeated header fields to not return a &quot;pass&quot; for DKI=
M signature validation.</div>
</div><div><br></div></div></blockquote></div><br></div><div class=3D"gmail=
_extra">That&#39;s a technical response.=A0 What I asked was a procedural q=
uestion.<br></div></div>

--089e0149338435b15904dec86c57--

From lars@netapp.com  Mon Jun 10 08:05:25 2013
Return-Path: <lars@netapp.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 B2A0D21E805A for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 08:05:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.616
X-Spam-Level: 
X-Spam-Status: No, score=-6.616 tagged_above=-999 required=5 tests=[AWL=-2.128, BAYES_00=-2.599, GB_I_INVITATION=-2, SARE_NETPROD=0.111]
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 2REZxcC8a3Ma for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 08:05:21 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id A697421F96F5 for <ietf@ietf.org>; Mon, 10 Jun 2013 08:05:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,837,1363158000";  d="p7s'?scan'208";a="23982943"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx11-out.netapp.com with ESMTP; 10 Jun 2013 08:05:05 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Mon, 10 Jun 2013 08:05:04 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: ietf list <ietf@ietf.org>
Subject: Call for Nominations: Applied Networking Research Prize 2014
Thread-Topic: Call for Nominations: Applied Networking Research Prize 2014
Thread-Index: AQHOZeviNheXcWmZDUy5DAFpneVtmQ==
Date: Mon, 10 Jun 2013 15:05:04 +0000
Message-ID: <C232F279-696A-457D-8BB3-68601C35DD07@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_2C12E72A-A46B-4F57-ABD9-47F87A035947"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "anrp@irtf.org" <anrp@irtf.org>
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: Mon, 10 Jun 2013 15:05:25 -0000

--Apple-Mail=_2C12E72A-A46B-4F57-ABD9-47F87A035947
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


                  CALL FOR NOMINATIONS:

       APPLIED NETWORKING RESEARCH PRIZE (ANRP) 2014

                  http://irtf.org/anrp

********************************************************************
***     Submit nominations for the 2014 award period of the      ***
***  Applied Networking Research Prize until November 30, 2013!  ***
***                                                              ***
***    (Please share this announcement with your colleagues.)    ***
********************************************************************

The Applied Networking Research Prize (ANRP) is awarded for recent
results in applied networking research that are relevant for
transitioning into shipping Internet products and related
standardization efforts. Researchers with relevant, recent results
are encouraged to apply for this prize, which will offer them the
opportunity to present and discuss their work with the engineers,
network operators, policy makers and scientists that participate in
the Internet Engineering Task Force (IETF) and its research arm, the
Internet Research Task Force (IRTF). Third-party nominations for this
prize are also encouraged. The goal of the Applied Networking
Research Prize is to recognize the best new ideas in networking, and
bring them to the IETF and IRTF especially in cases where they would
not otherwise see much exposure or discussion.

The Applied Networking Research Prize (ANRP) consists of:

=95 cash prize of $500 (USD)
=95 invited talk at the IRTF Open Meeting
=95 travel grant to attend a week-long IETF meeting (airfare, hotel,
registration, stipend)
=95 recognition at the IETF plenary
=95 invitation to related social activities
=95 potential for additional travel grants to future IETF meetings,
based on community feedback

The Applied Networking Research Prize will be awarded once per
calendar year. Each year, several winners will be chosen and invited
to present their work at one of the three IETF meetings during the
year.


HOW TO NOMINATE

Only a single person can be nominated for the award. The basis of the
nomination is a peer-reviewed, original journal, conference or
workshop paper they authored, which was recently published or
accepted for publication. The nominee must be one of the main authors
of the nominated paper. Both self nominations (nominating one=92s own
paper) and third-party nominations (nominating someone else=92s paper)
are encouraged.

The nominated paper should provide a scientific foundation for
possible future IETF engineering work or IRTF research and
experimentation, analyze the behavior of Internet protocols in
operational deployments or realistic testbeds, make an important
contribution to the understanding of Internet scalability,
performance, reliability, security or capability, or otherwise be of
relevance to ongoing or future IETF or IRTF activities.

Applicants must briefly describe how the nominated paper relates to
these goals, and are encouraged to describe how a presentation of
these research results would foster their transition into new IETF
engineering or IRTF experimentation, or otherwise seed new activities
that will have an impact on the real-world Internet.

The goal of the Applied Networking Research Prize (ANRP) is to foster
the transitioning of research results into real-world benefits for
the Internet. Therefore, applicants must indicate that they (or the
nominee, in case of third-party nominations) are available to attend
at least one of the year=92s IETF meetings in person and in its
entirety.

Nominations must include:

=95 the name and email address of the nominee
=95 a bibliographic reference to the published (or accepted)
nominated paper
=95 a PDF copy of the nominated paper
=95 a statement that describes how the nominated paper fulfills the
goals of the award
=95 a statement about which of the year=92s IETF meetings the nominee
would be available to attend in person and in its entirety
=95 a brief biography or CV of the nominee
=95 optionally, any other supporting information (link to nominee=92s
web site, etc.)

Nominations are submitted via the submission site at
http://irtf.org/anrp/2014/. In exceptional cases, nominations may
also be submitted by email to anrp@irtf.org.


SELECTION PROCESS

A small selection committee comprised of individuals knowledgeable
about the IRTF, IETF and the broader networking research community
will evaluate the submissions against these selection criteria.


IMPORTANT DATES

Applications close: November 30, 2013 (hard)
Notifications:      December 20, 2013


SPONSORS

The Applied Networking Research Prize (ANRP) is supported by the
Internet Society (ISOC), as part of its Internet Research Award
Programme, in coordination with the Internet Research Task Force
(IRTF).


HELP PUBLICIZE THE ANRP

If you would like to help publicize the ANRP within your
organization, you are welcome to print and use the flyer at
http://irtf.org/anrp-2014-flyer.pdf


--Apple-Mail=_2C12E72A-A46B-4F57-ABD9-47F87A035947
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINBzCCBkIw
ggUqoAMCAQICEDirAC//rpa3Vv85Wvtd5xswDQYJKoZIhvcNAQEFBQAwgcoxCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3IgYXV0aG9yaXplZCB1c2Ug
b25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0
aW9uIEF1dGhvcml0eSAtIEczMB4XDTExMDkwMTAwMDAwMFoXDTIxMDgzMTIzNTk1OVowgaYxCzAJ
BgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEfMB0GA1UECxMWU3ltYW50
ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQD
Ey5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEc0MIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxuwn/R1j9DsdisHTHMjIgoa2uEqGkqqBXHLKMA0vnkEi
VzAhJZCao/SsKsaIF4ZhchN2LuwDyyebjyCAN+DkitpVplAP/LlcI2mJQqG6H6/vDvmkyQrx+Dey
xtmSSq5937hEH5u6P4wG/tgjT0hRI2pghKjuJy9g35byGiqMPI8AzE/L+iCOvDX24fCatgXz/B0/
xhR7DtryBeTTgwKmxWlwtKnkVunbHVz0pjbia7UeKi3cvrvuOgSwMAitX2hsxr0GloiE5+apZC28
ODC7iCbDZ2ZmtLR3+cChxw5y72bi5bnK4POFdzWY3tQcsP5mceI4y258T0BV65fZqBge7QIDAQAB
o4ICRDCCAkAwOAYIKwYBBQUHAQEELDAqMCgGCCsGAQUFBzABhhxodHRwOi8vcGtpLW9jc3AudmVy
aXNpZ24uY29tMBIGA1UdEwEB/wQIMAYBAf8CAQAwbAYDVR0gBGUwYzBhBgtghkgBhvhFAQcXATBS
MCYGCCsGAQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGguY29tL2NwczAoBggrBgEFBQcCAjAcGhpo
dHRwOi8vd3d3LnN5bWF1dGguY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZl
cmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVZlcmlTaWduTVBLSS0yLTk3MB0GA1UdDgQWBBSt+cOTci21uShh5KTXYNXECl4aATCB
8QYDVR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIElu
Yy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZl
cmlTaWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWdu
IENsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItb
dVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBANaPwdqbiPKzbE0fWC+6AVFddMFG6MO4
e5/WQPHv/zK6iWvADjRDn6SZ5qTwXUgzYoWFYf4jiCKMYJsrnGVJlMSiOCRIpVylUEto6WIip5Po
mSJuPVu7EEIOH0x1RzRWCY/4vYw881y70pZwVHBiTe/REL6dSCxe7IZrB4LwPeElJygs4BZ2HrP9
5WKW0oo9Xyuu+1zCE7dlY8s0dkOf1oeZq26tlcEAP0Yngf813iMOQ9wUXzL5yinvwlIw9ZnduYH4
OiUgjYJo8rkhhXRmBOGGORYy8i3WKqjJ3tkAAk/jGCDFpYFWtpXe04Kt+HslvmR8LqC6cCz4+XXi
dE0HbYQwgga9MIIFpaADAgECAhBcHtb173S3Zimo+RJj8ZJuMA0GCSqGSIb3DQEBBQUAMIGmMQsw
CQYDVQQGEwJVUzEdMBsGA1UEChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFu
dGVjIFRydXN0IE5ldHdvcmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UE
AxMuU3ltYW50ZWMgQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHNDAeFw0xMjEy
MTcwMDAwMDBaFw0xMzEyMTgyMzU5NTlaMIHBMS4wLAYDVQQDDCVQZXJzb25hIE5vdCBWYWxpZGF0
ZWQgLSAxMzU1NzU2NDEyNzI0MR4wHAYJKoZIhvcNAQkBFg9sYXJzQG5ldGFwcC5jb20xDzANBgNV
BAsMBlMvTUlNRTEeMBwGA1UECwwVUGVyc29uYSBOb3QgVmFsaWRhdGVkMR8wHQYDVQQLDBZTeW1h
bnRlYyBUcnVzdCBOZXR3b3JrMR0wGwYDVQQKDBRTeW1hbnRlYyBDb3Jwb3JhdGlvbjCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBANWkuu7uQOPw8ji7+u/ZDX+P8pwLX3a57b+qK9jkhUeW
9D5cKKI/7uU2u3HVqunJSvfz/cm6BCT9PF9QMitgKydjnzQvnhJmjo30uufsIIVbkrMgBamPmDck
tdW2wJA/IHvg6siTrRRJ+PIDFtNsu0IPQMSjYLBJN7OvYBl8WC291uEB3PW1XN77/RxhBdd00nP8
xeJjiSol5xUassDP5/gAkTGp6YCxulqtkMN4AqRNnnW1cS3GaSKGVnD+4/znuzNqrY5eEL87miPz
SKg3XvSaoTRNMb1SrE0kI8a35T7zeopaQ3cjlZD4cVlsQe/A4nTwZXnUYYGKPsxt0j8y5ykCAwEA
AaOCAsgwggLEMAwGA1UdEwEB/wQCMAAwDgYDVR0PAQH/BAQDAgWgMCAGA1UdJQEB/wQWMBQGCCsG
AQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQUPsgtqNipyEoJQEaE5C/M7ejkMGUwGgYDVR0RBBMw
EYEPbGFyc0BuZXRhcHAuY29tMB8GA1UdIwQYMBaAFK35w5NyLbW5KGHkpNdg1cQKXhoBMIIBKwYI
KwYBBQUHAQEEggEdMIIBGTCCARUGCCsGAQUFBzAChoIBB2xkYXA6Ly9kaXJlY3RvcnkudmVyaXNp
Z24uY29tL0NOJTIwJTNEJTIwU3ltYW50ZWMlMjBDbGFzcyUyMDElMjBJbmRpdmlkdWFsJTIwU3Vi
c2NyaWJlciUyMENBJTIwLSUyMEc0JTJDJTIwT1UlMjAlM0QlMjBQZXJzb25hJTIwTm90JTIwVmFs
aWRhdGVkJTJDJTIwT1UlMjAlM0QlMjBTeW1hbnRlYyUyMFRydXN0JTIwTmV0d29yayUyQyUyME8l
MjAlM0QlMjBTeW1hbnRlYyUyMENvcnBvcmF0aW9uJTJDJTIwQyUyMCUzRCUyMFVTP2NBQ2VydGlm
aWNhdGU7YmluYXJ5MF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9wa2ktY3JsLnN5bWF1dGguY29t
L2NhXzU2MWMxMDM2OTBjOTdhNjkyNDdhMGVmMDcxYWM4MWFmL0xhdGVzdENSTC5jcmwwbAYDVR0g
BGUwYzBhBgtghkgBhvhFAQcXATBSMCYGCCsGAQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGguY29t
L2NwczAoBggrBgEFBQcCAjAcGhpodHRwOi8vd3d3LnN5bWF1dGguY29tL3JwYTAqBgpghkgBhvhF
ARADBBwwGgYRYIZIAYb4RQEQAQICBAGGsxcWBTEwOTIyMA0GCSqGSIb3DQEBBQUAA4IBAQAzvR5s
H2ex5C1+qykxtOOdO+VkD1uygAoUxdh7K67SvXqbTF6c5oOVI80EwbjbZKFUk90Jf3D6HxlN/O69
smO+gCVAe3S+vXRB3XUaNPciBnqqUHJpuTlJhcqMPWpG30ZifNBQC8acFuNBHsdQyZNnbUeYHFYK
Di0CayGxT9bagFoUNBmDOJ7kvnBATaMQhX6y0aVBf3fUU5RXr0NEITVlEozE/KZWRN+vfuufICT0
keHCtoXkwI2kzH9VW7eroQk7t8/wowK8z2gW5Hm8ZWl+fbsfFEFVmJ633Ey7GiCmTzovQKgSuV4m
a7cYD68kzWVk+9SnBdZILEfefjjrRvmuMYID5DCCA+ACAQEwgbswgaYxCzAJBgNVBAYTAlVTMR0w
GwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0
d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEc0AhBcHtb173S3Zimo+RJj8ZJuMAkG
BSsOAwIaBQCgggH9MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEz
MDYxMDE1MDUwNlowIwYJKoZIhvcNAQkEMRYEFHpVa6utknQVPje4/OxzLLwHfLrJMIHMBgkrBgEE
AYI3EAQxgb4wgbswgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlv
bjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3Qg
VmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJl
ciBDQSAtIEc0AhBcHtb173S3Zimo+RJj8ZJuMIHOBgsqhkiG9w0BCRACCzGBvqCBuzCBpjELMAkG
A1UEBhMCVVMxHTAbBgNVBAoTFFN5bWFudGVjIENvcnBvcmF0aW9uMR8wHQYDVQQLExZTeW1hbnRl
YyBUcnVzdCBOZXR3b3JrMR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMT
LlN5bWFudGVjIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzQCEFwe1vXvdLdm
Kaj5EmPxkm4wDQYJKoZIhvcNAQEBBQAEggEAhmbiSNBsj7KTDc5eOI1jHx0TTnoz4FBuFbg4vo/g
euC3cqjgB0Ck8ZuRTajaxODu2K7Sp5vXILArlSRV5uyXuDBomvXXY7qZR4Ae9yfc9vy5QoY2ZDUW
iNqqY6/fZSB24OLgq48qJ7vy8OdgUyD0NBNk4DQBgjUijHjgNU0ECwdITiIgb0hVYJLOxu7IgRmj
hSOpkmndwMc62cO28uQwXcwGVjp9ex3yH5uCRVAWNvQlkrrkI7ZFdw7w1mmxHqFh43aGZxY9Of79
YJxU+06GWwfZNcRZCD+qluN0RdCoWkFDiGp0hjNHzWf2MlcIG9IKH1tTs8/16j9ndOWLZeF1HQAA
AAAAAA==

--Apple-Mail=_2C12E72A-A46B-4F57-ABD9-47F87A035947--

From yi.jiazi@gmail.com  Sat Jun  8 06:10:56 2013
Return-Path: <yi.jiazi@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 D83B621F997C; Sat,  8 Jun 2013 06:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 SYoE0zIszh61; Sat,  8 Jun 2013 06:10:55 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 1FAC921F9A42; Sat,  8 Jun 2013 06:10:50 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id c10so299933wiw.2 for <multiple recipients>; Sat, 08 Jun 2013 06:10:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=d7zIvzdgp5A2WFk7dDSAPfTdRxhWJh1tpPdkT3IAKco=; b=K2aJKCkxQSmPq2BsvEGAXrmyy0kql/RugWt77vWEPDbRCtwLEtrN22BshL1vdQwU2X r3x8dvuz4//oqMFJRyzPUyiECAevlTtLk9sw2AnKlwQELeUncHkR2O/uJCFeeWQv4dL1 DFrc+qwPrLOL88aLfsu39oyN7igg6FV7yujtx6Cq/5334mMYEK0Ng5b2tjAQVK5YBOAZ SiyRe2vhoENK1IdfWf3V4VKye5Px7AK77HBFsgxlSMt4OiqYlH6gkX9/Cwv5H7vHHYBJ z1lrYPjrIeYBiDDXKJcYnXLEzF5ANvIbxfCS1sf9qZ2Pc/OPVBseggP96/exHIunUkNd 4+RA==
X-Received: by 10.180.211.197 with SMTP id ne5mr954194wic.54.1370697043374; Sat, 08 Jun 2013 06:10:43 -0700 (PDT)
Received: from jy-mac-pro.home (128-79-35-43.hfc.dyn.abo.bbox.fr. [128.79.35.43]) by mx.google.com with ESMTPSA id dj7sm2239006wib.6.2013.06.08.06.10.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Jun 2013 06:10:42 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Jiazi Yi <yi.jiazi@gmail.com>
In-Reply-To: <CADnDZ8-hWkU5XD7uUoJHgg7eWtRqRQOH2123fs0Gx3618TwKjA@mail.gmail.com>
Date: Sat, 8 Jun 2013 15:10:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B573F31A-64CF-4425-8757-6DD2DF0AD897@gmail.com>
References: <09b601ce62db$77adc5c0$67095140$@olddog.co.uk> <CADnDZ89jxuxzCGvwOqcDyO84DCmE10bDmA2zb94YQm=FPyqFZQ@mail.gmail.com> <0a1401ce62fb$2aecfa10$80c6ee30$@olddog.co.uk> <CADnDZ8-hWkU5XD7uUoJHgg7eWtRqRQOH2123fs0Gx3618TwKjA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Mon, 10 Jun 2013 09:30:17 -0700
Cc: adrian@olddog.co.uk, ietf <ietf@ietf.org>, iesg@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: Sat, 08 Jun 2013 13:10:57 -0000

Hi,=20

As co-editor of this document, I didn't expect the "acknowledgement" =
issue can result in such long discussion.=20

I have to repeat that, the decision regarding the acknowledgment section =
is made following the instructions from rfc 5378 and rfc 2026.=20

We think the facts are:

	o AB made a lot of comments on this draft.
	o The comments made didn't have any major impact to the draft. =
There were *very* few editorial nits discovered by AB, but not technical =
contribution - not to mention "major" impact.=20

Therefore, I don't see the need of adding AB to the acknowledgment =
section.=20

Ulrich (also co-editor) has sent the same opinion to the manet mailing =
list. There are a few WG participants showed that they agree with our =
observation. In the meantime, I didn't see any other WG participant =
support AB's proposal.=20

best

Jiazi

On Jun 8, 2013, at 07:50 , Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> Dear Routing Area AD,
>=20
> I had many comments/issues regarding your area always addressed to you
> and  including this issue which I hope my all comments (past/present)
> will help to make better practice/procedural progresses in this IETF
> Area.
> I am sorry also to any one receiving this email but I send it only to
> an AD, IETF, and IESG. This is not noise but a signal to IETF to
> progress, if you think it is noise please explain, and please notice
> that all particpants have rights under the IETF procedures not only
> managements. My reply below and if you want to continue discussing on
> any other list please inform me, but if you reply copying any list, I
> will have to do the same because you are part of management and I am
> not.
>=20
> On 6/6/13, Adrian Farrel <adrian@olddog.co.uk> wrote:
>> Sorry to everyone for the noise this thread is creating.
>=20
> This thread containing my messages never creates noise, I beleive you
> may ne refering to your messages only as noise. Please note that I
> don't accept this describtion, I think that community messages
> regarding any I-D is never noise even if the IETF management could not
> handle the volume. I RECOMMEND any receiver that has noise in it to
> fix its problem without blaming transmitters.
>=20
>> Multiple questions that I have to answer.
>=20
> ok, that is why this list is discussing list for ietf progress,
>=20
>>=20
>>>> It falls to me to make a call on this issue before the document =
moves
>>>> on.
>>>>=20
>>>> Abdussalam has complained that he has not been acknowledged and has
>>>> objected to the current text in section 8.
>>>> The authors have responded on the MANET list
>>>>=20
>>>>> We believe that only comments that lead to significant =
improvements of
>>>>> the draft deserve a listing in the acknowledgment section, and we =
have
>>>>> therefore not modified the section.
>>>=20
>>> What was the WG decision?
>>=20
>> Are you asking whether there was an explicit consensus call within =
the
>> working
>> group on whether or not you should be acknowledged in this document?
>=20
> I think the question is clear, and is easy to answer. The answer is,
> there was no decision made by the WG or the community regarding my
> request of adding a name in the ack section. You send me back a
> question saying explicit consensus, it is simpler to make my question
> asking of notification of such reaction from management, which was not
> either established. I did not get a message saying that any kind of
> consensus was established privately/publicly on any IETF lists (please
> ask the WG chair because I am sure I did not received any answer for
> my request by the WG/community).
>=20
>> There was no such call in the working group or on the IETF list.
>=20
> Thanks for the answer, so I understand that the editors/management did
> not answer my request (one person from the community), just because
> they or AD did not beleive in my concerns without consulting the WG in
> any way.
>=20
>>=20
>>> Why any contribution that influnces the I-D ideas is not =
acknowledged?
>>> IMO, if a technical-idea within the I-D was discovered wrong by a
>>> participant, or a new technical-idea added to I-D from an input, =
then
>>> the I-D should be acknowledged.
>>=20
>> This opinion does not apply to your comments on this document. You =
did not
>> discover a wrong technical-idea. Your comments did not lead directly =
to the
>> addition of any new technical-idea.
>=20
> The question of I-D managers not acknowledging such
> input/contribution, was not answered if you agree to acknowledge
> discovering an error or adding a new idea. Regarding the opinion, do
> you agree with the opinion first? Regarding the error and missing
> information, I did discover error in the document and did found
> missing definitions if this informational I-D (after my contribution
> there was changes made to the document, please notice that)
>>=20
>>>> I have reviewed the email threads on the MANET mailing list and do =
not
>>>> consider that Abdussalam made contributions to the text of the
>>>> document.
>>>=20
>>> Didn't that person make review and discovered errors?
>>=20
>> "That person" is you.
>=20
> Yes but I said that because this message it not me defending me, it is
> me defending future wrong reaction of ignoring to acknowledge the
> persons in the community. If any I-D authors are best knowledgeable
> people in a special field they should not try to seek to
> dis-acknowledge the community efforts that changed few I-D ideas (even
> if the community person is not expert, that does not mean that authors
> have right to exclude contributors).
>=20
>> Yes, you made a review. Reviewing a document is not something authors
>> acknowledge in the IETF or (AFAIK) in academic journals.
>=20
> I disagree with your opinion, but do you think your opinion is in the
> IETF procedure, if yes please provide me with that procedure of not
> acknowledgement. I respect your opinion but it is wrong because in one
> sense yes documents in the world don't acknowledge all reviews
> (usually when they don't request it), one the other hand the world
> documents do acknowledge reviews when the document owner calls for
> review. Please note that this I-D did request/call for review and I
> was the only reveiwer in the WGLC, and my review made the authors
> change some ideas.
>=20
>> No, I don't think you discovered errors of any significance.
>=20
> My comments and discussions are in the MANET WG. The errors were; 1)
> not explaining the word *attack* in I-D version 2 and/or referencing
> explainations. 2) wrong explaination of physical communication in
> MANET.
> Both ideas ware changed please see the two versions of I-D 2 and 3.
>=20
> Example error idea in the I-D was:
> [I-D wrong idea] As wireless radio waves can be captured as well as =
transmitted
> by any wireless device within radio range.
> [my discovery contribution]
> http://www.ietf.org/mail-archive/web/manet/current/msg15250.html
>=20
>>=20
>> Caveating my answers below as describing a contribution to a document =
(not
>> a
>> contribution in the wider IETF sense)
>=20
> An IETF I-D contribution is a contribution (don't care about the
> editors' beleive of kind of contributions), small, large, substantial,
> non-substantial, minor, major, from-expert, not-from-expert,
> from-popular, from-non-popular, from-f2f-participant,
> from-remote-participant, etc.
>>=20
>>> Why don't you consider discovering an error as a contribution?
>>=20
>> I would personally consider discovering a major error as something I =
would
>> acknowledge it in a document I was editing.
>=20
> You use word major as if we know what it means. Something minor to you
> may be major to someone else don't you think. If your documents if for
> experts please mention that in you documents, please know your
> audiance/readers. I understand that IETF documents are for ALL the
> Internet Community on EARTH. Therefore, the word major/minor is
> relative to the reader not writer.
>=20
>> I would personally consider discovering multiple minor errors as =
something
>> I
>> would acknowledge it in a document I was editing.
>=20
> Again you say you, I want IETF opinion not editors, I want WG
> decisions not your decisions, however, I already waiting for the IESG
> decisions on this matter, and I understand that your decision is a one
> part of that but not full/final. One error discovery or multiple, both
> are contributions and are needed. In our volunteering work if the
> work/I-D/RFC has many mistakes we don't blame the editors but the
> community, but if the work had no mistake we give all credit to
> authors, IMHO, we always should refer to the community in good or bad
> outcomes of IETF documents. Therefore acknowledging the parts of
> community is important.
>>=20
>> However, there is no requirement for editors to act in that way.
>=20
> No, editors are required to edit/act what the community is seeking,
> why are they called editors for the WG? the authority is for the WG
> not editors.
>=20
>> Furthermore,
>> you do not fit into these categories for this document.
>=20
> I do fit, I think you should not decide now, let it to be done through
> IETF procedure.
>=20
>>=20
>>> Why don't you consider providing new ideas a contribution?
>>=20
>> I would consider providing major ideas as something I would =
acknowledge it
>> in a
>> document I was editing.
>> I would consider providing smaller ideas through text for inclusion =
in the
>> document as something I would acknowledge it in a document I was =
editing.
>> You do not fit into these categories for this document.
>=20
> I think I do fit from IETF point of view (maybe not yours). I gave my
> discovery of error, and if the editors want text I will give them, it
> is a discussion issue between both sides in a WG. Text is not much
> important like the idea, the idea is the most important thing in any
> organisation. English texting can be another contribution, or proof
> readings, but the main contribution is the idea that was changed.
>=20
>>=20
>>> What is your definition to contribution?
>>=20
>> As above, or written text that was included or modified for inclusion =
in a
>> document and represents a material or substantial part of the =
document.
>=20
> the idea is more important than text, if changed sentence idea we
> SHOULD acknowledge, if changed sentance text without changing idea we
> do not have to acknowledge. So text changing/adding without new-idea
> or English correction is not acknowledged im my opinion.
>=20
>>=20
>>>> I also believe that the comments he made did not advance the
>>>> content of the document.
>>>=20
>>> So I understand that you need to have advance the content then you
>>> acknowledge.
>>>=20
>>>> Furthermore, per multiple references (such as RFC 2026) the
>>>> Acknowledgements section is used to "properly acknowledge
>>>> major contributors.
>>>=20
>>> I am trying to find that condition of *major contribution*,
>>=20
>> I would borrow from 2026 and 5378 to say a material or substantial
>> contribution
>> to the document.
>>=20
>> And, before you ask, no-one is going to write down a rule that says =
139
>> characters is not substantial, but 140 is.
>>=20
>> This is one of the places where a principal of reasonableness =
applies. I
>> would
>> know a major contribution if I saw one. I did not see one from you in =
this
>> case.
>=20
> I will wait for the IESG decision on that. Major or minor is relative
> to the readers not to the writers. You have big experience but that
> does not mean you should exclude any minor contribution, I hope you
> reconsider that. Some experts don't like to show that non-popular
> found their mistakes, but Why thoes experts came to use IETF service
> which calls-reviews to all levels of experties to contribute to the
> document they author under IETF ownership?
>=20
>>=20
>>>> " Normal IETF business is to discuss not seek acknowledgement.
>>>=20
>>> Ideas, Comments and reviews are included in the discuss for drafts
>>> progress. Seeking acknowledgement is not wrong within IETF, but =
please
>>> consider *not acknowledging reviews* within IETF documents is not =
IETF
>>> culture (we are not paid so why you thinking much of the business, =
the
>>> IETF business will only progress with acknowledging the volunteers).
>>=20
>> If you want to change the way that the IETF participants (and =
document
>> authors/editors in particular) acknowledge reviews of their =
documents, then
>> please start a separate thread or, better still, write an I-D and see
>> whether
>> you can gain consensus.
>=20
> I know that, but your advise comes back to you also, if you want to
> change the community expectations close to your opinions, I advise you
> to write an I-D that shows where to exclude participants to IETF
> documents.
>=20
>> The last time you brought this topic up on this
>> list, I
>> do not recall seeing support.
>=20
> Few did not support which were less than 15 persons, because IMO,
> there was no evidance of editors seeking to ignore reviewers
> contributions. Also, change is difficult any where in any
> organisation, so it will take time, IMO, people realise that
> participating-experts of IETF are the minority comapared to the
> community. I decided to complain any procedure error first and then
> write about what happend, so I will wait to see what is the IESG
> decision regarding the acknowledgement request. Please note that I
> have many procedural I-D in mind but it depends on the right time to
> submit it and get support.
>=20
>>=20
>> The only reason I can find for someone being able to demand that they =
are
>> named
>> in an Acknowledgements Section is for conformance to the IETF's =
Rights
>> policies.
>=20
> My reason is that the truth SHOULD be reflected on the document. If
> you are editor I recommend you may say in the section thanks to x for
> his minor contribution if that satisfies your WG you work with, but
> not to ignore the truth. The truth is that IETF is calling for reviews
> from the community mostly not only from companies, and that your
> document changed an idea, so you ack.
>=20
>>=20
>>>> I do not propose to do an explicit consensus call on whether =
Abdussalam
>>>> should be named in this draft.
>>>=20
>>> IMO, it should have been done in the WG.
>>=20
>> Thank you for your opinion.
>> Are you asserting that consensus on the readiness of this document =
for a
>> publication request was incorrectly called by the working group =
chairs.
>> This
>> would be a serious allegation against the chairs and I would require
>> evidence
>> that there had been no consensus or that they had made an incorrect
>> assessment
>> of the consensus.
>=20
> No, I accepted that the I-D goes to IESG only the complaint request of
> acknowledgement and the community reviews in IETF-LC. The wg chair
> mentioned my complaint in his report. I wait for the IESG decisions
> related to this I-D.
>=20
> Best Regards
>=20
> Abdussalam Baryun
>=20
> A Participant working in IETF (subscribed)
> A Memebr of Internet Society (registered)


From david.black@emc.com  Sun Jun  9 10:47:58 2013
Return-Path: <david.black@emc.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 DF6A521F8E9D; Sun,  9 Jun 2013 10:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 AQYsBVBit40f; Sun,  9 Jun 2013 10:47:53 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id F2BA321F8D10; Sun,  9 Jun 2013 10:47:52 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r59HlSAC003579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Jun 2013 13:47:28 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sun, 9 Jun 2013 13:47:13 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r59HlDKS031140; Sun, 9 Jun 2013 13:47:13 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Sun, 9 Jun 2013 13:47:12 -0400
From: "Black, David" <david.black@emc.com>
To: "d3e3e3@gmail.com" <d3e3e3@gmail.com>, "joe.abley@icann.org" <joe.abley@icann.org>, General Area Review Team <gen-art@ietf.org>
Date: Sun, 9 Jun 2013 13:47:12 -0400
Subject: Gen-ART review of draft-eastlake-rfc5342bis-03
Thread-Topic: Gen-ART review of draft-eastlake-rfc5342bis-03
Thread-Index: Ac5iOdqxPgeHIMhASdCnl829MYVBxwC/mpbg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712980CA206@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 10 Jun 2013 09:30:17 -0700
Cc: "Black, David" <david.black@emc.com>, "ietf@ietf.org" <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: Sun, 09 Jun 2013 17:47:58 -0000

The -03 version of this draft resolves all of the concerns raised by
the Gen-ART review of the -02 version.

Unfortunately, a serious typo/thinko snuck into the -03 version (been
there, done that, myself).  Section 3.2 currently says:

   00-42 is a protocol number under the IANA OUI (that is,
   00-00-0E-00-42) to be used for documentation purposes.

The parenthetical expansion of the protocol number is incorrect.
The correct expansion uses -5E- instead of -0E-:

   00-42 is a protocol number under the IANA OUI (that is,
   00-00-5E-00-42) to be used for documentation purposes.

I strongly suggest submitting a -04 version of this draft to make
the necessary single character correction (e.g., as opposed to using
a RFC Editor Note for that purpose).

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Wednesday, June 05, 2013 6:13 PM
> To: d3e3e3@gmail.com; joe.abley@icann.org; General Area Review Team
> Cc: Black, David; joelja@bogus.com; ietf@ietf.org
> Subject: Gen-ART review of draft-eastlake-rfc5342bis-02
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-eastlake-rfc5342bis-02
> Reviewer: David L. Black
> Review Date: June 5, 2013
> IETF LC End Date: June 4, 2013
>=20
> Summary:
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> This draft updates the IANA registered Ethernet parameters for IETF use,
> including recording values assigned for documentation.  It also makes som=
e
> minor changes to IANA procedures.
>=20
> IANA should review this entire draft, not just its IANA Considerations
> section;
> Pearl Liang appears to have done that comprehensive review for IANA.
>=20
> Major issues: None
>=20
> Minor issues: One, the IANA review also found this issue.
>=20
> Section 3.2 states:
>=20
> 	IANA will assign "00-00-0E-00-42" as the protocol number under the
> 	IANA OUI to be used for documentation purposes.
>=20
> IANA has not made this assignment, but this assignment request is not
> recorded in the IANA Considerations section where IANA actions are
> requested and recorded by IANA after they have been performed.  This
> assignment needs to be added to the IANA Considerations section;
> see item 5 in the IANA review.
>=20
> Nits/editorial comments:
>=20
> Section 1: This document uses an "IESG Ratification" process for some
> assignments.  This is not the same process as the "IESG Approval" process
> defined in RFC 5226.  As those names could be confused by a casual reader
> who is not strongly familiar with IANA processes, I suggest adding a
> statement that the "IESG Ratification" process is defined in this documen=
t
> and is not the same as the "IESG Approval" process in RFC 5226.  This cou=
ld
> be added after the sentence that cites RFC 5226.
>=20
> Section 1.4: It would be helpful to point out that there is no OUI assign=
ed
> for documentation purposes, but there are identifiers based on the IANA O=
UI
> that have been assigned for documentation purposes.
>=20
> In general, the use of the acronym IAB for Individual Address Block is
> unfortunate, but unavoidable, and this is clearly pointed out in the
> definition of the IAB acronym in section 1.2.  Nothing can or should be
> done about this.
>=20
> idnits 2.12.17 did not find any nits.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From david.black@emc.com  Sun Jun  9 12:10:25 2013
Return-Path: <david.black@emc.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 8E01B21F8FF8; Sun,  9 Jun 2013 12:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 E0S7HY1NjaRD; Sun,  9 Jun 2013 12:10:21 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 203B621F8FA4; Sun,  9 Jun 2013 12:10:20 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r59J9uMc022128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Jun 2013 15:09:56 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sun, 9 Jun 2013 15:09:50 -0400
Received: from mxhub11.corp.emc.com (mxhub11.corp.emc.com [10.254.92.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r59J9nP2020631; Sun, 9 Jun 2013 15:09:49 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub11.corp.emc.com ([10.254.92.106]) with mapi; Sun, 9 Jun 2013 15:09:49 -0400
From: "Black, David" <david.black@emc.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 9 Jun 2013 15:09:48 -0400
Subject: RE: Gen-ART review of draft-eastlake-rfc5342bis-03
Thread-Topic: Gen-ART review of draft-eastlake-rfc5342bis-03
Thread-Index: Ac5lPCQkdinnaPkPQMKO9qA5DiYy8gACFpAw
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712980CA213@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712980CA206@MX15A.corp.emc.com> <CAF4+nEER=JdeKV6PU_8m2jJ8O182WHcsQ-ayODUTCp1jRx-X+w@mail.gmail.com>
In-Reply-To: <CAF4+nEER=JdeKV6PU_8m2jJ8O182WHcsQ-ayODUTCp1jRx-X+w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 10 Jun 2013 09:30:17 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "joe.abley@icann.org" <joe.abley@icann.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>
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: Sun, 09 Jun 2013 19:10:25 -0000

> > I strongly suggest submitting a -04 version of this draft to make
> > the necessary single character correction (e.g., as opposed to using
> > a RFC Editor Note for that purpose).
>
> I defer entirely to Joel Jaeggli, the sponsoring AD.

I'm happy to leave that decision up to Joel.

I'm concerned about readers who aren't as
cognizant of and comfortable/familiar with the relationships among
OUIs and the identifiers based on them as people like you and me.

Thanks,
--David

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Sunday, June 09, 2013 2:07 PM
> To: Black, David
> Cc: joe.abley@icann.org; General Area Review Team; joelja@bogus.com;
> ietf@ietf.org
> Subject: Re: Gen-ART review of draft-eastlake-rfc5342bis-03
>=20
> Hi David,
>=20
> On Sun, Jun 9, 2013 at 1:47 PM, Black, David <david.black@emc.com> wrote:
> > The -03 version of this draft resolves all of the concerns raised by
> > the Gen-ART review of the -02 version.
>=20
> Thanks.
>=20
> > Unfortunately, a serious typo/thinko snuck into the -03 version (been
> > there, done that, myself).  Section 3.2 currently says:
> >
> >    00-42 is a protocol number under the IANA OUI (that is,
> >    00-00-0E-00-42) to be used for documentation purposes.
> >
> > The parenthetical expansion of the protocol number is incorrect.
> > The correct expansion uses -5E- instead of -0E-:
>=20
> My apologies, you are correct. However, I believe that, in context,
> the typo is pretty obvious.
>=20
> >    00-42 is a protocol number under the IANA OUI (that is,
> >    00-00-5E-00-42) to be used for documentation purposes.
> >
> > I strongly suggest submitting a -04 version of this draft to make
> > the necessary single character correction (e.g., as opposed to using
> > a RFC Editor Note for that purpose).
>=20
> I defer entirely to JoelJaeggli, the sponsoring AD.
>=20
> I'd be happy to submit a -04 or it seems to me it could easily be
> fixed with an RFC Editor Note or at AUTH48 time. (Actually, it seems
> likely to me that during IESG consideration, some other change will be
> decided on and this can be fixed at the same time.)
>=20
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>=20
> > Thanks,
> > --David
> >
> >> -----Original Message-----
> >> From: Black, David
> >> Sent: Wednesday, June 05, 2013 6:13 PM
> >> To: d3e3e3@gmail.com; joe.abley@icann.org; General Area Review Team
> >> Cc: Black, David; joelja@bogus.com; ietf@ietf.org
> >> Subject: Gen-ART review of draft-eastlake-rfc5342bis-02
> >>
> >> I am the assigned Gen-ART reviewer for this draft. For background on
> >> Gen-ART, please see the FAQ at
> >>
> >> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >>
> >> Please resolve these comments along with any other Last Call comments
> >> you may receive.
> >>
> >> Document: draft-eastlake-rfc5342bis-02
> >> Reviewer: David L. Black
> >> Review Date: June 5, 2013
> >> IETF LC End Date: June 4, 2013
> >>
> >> Summary:
> >> This draft is on the right track but has open issues, described in the
> review.
> >>
> >> This draft updates the IANA registered Ethernet parameters for IETF us=
e,
> >> including recording values assigned for documentation.  It also makes =
some
> >> minor changes to IANA procedures.
> >>
> >> IANA should review this entire draft, not just its IANA Considerations
> >> section;
> >> Pearl Liang appears to have done that comprehensive review for IANA.
> >>
> >> Major issues: None
> >>
> >> Minor issues: One, the IANA review also found this issue.
> >>
> >> Section 3.2 states:
> >>
> >>       IANA will assign "00-00-0E-00-42" as the protocol number under t=
he
> >>       IANA OUI to be used for documentation purposes.
> >>
> >> IANA has not made this assignment, but this assignment request is not
> >> recorded in the IANA Considerations section where IANA actions are
> >> requested and recorded by IANA after they have been performed.  This
> >> assignment needs to be added to the IANA Considerations section;
> >> see item 5 in the IANA review.
> >>
> >> Nits/editorial comments:
> >>
> >> Section 1: This document uses an "IESG Ratification" process for some
> >> assignments.  This is not the same process as the "IESG Approval" proc=
ess
> >> defined in RFC 5226.  As those names could be confused by a casual rea=
der
> >> who is not strongly familiar with IANA processes, I suggest adding a
> >> statement that the "IESG Ratification" process is defined in this docu=
ment
> >> and is not the same as the "IESG Approval" process in RFC 5226.  This =
could
> >> be added after the sentence that cites RFC 5226.
> >>
> >> Section 1.4: It would be helpful to point out that there is no OUI ass=
igned
> >> for documentation purposes, but there are identifiers based on the IAN=
A OUI
> >> that have been assigned for documentation purposes.
> >>
> >> In general, the use of the acronym IAB for Individual Address Block is
> >> unfortunate, but unavoidable, and this is clearly pointed out in the
> >> definition of the IAB acronym in section 1.2.  Nothing can or should b=
e
> >> done about this.
> >>
> >> idnits 2.12.17 did not find any nits.
> >>
> >> Thanks,
> >> --David
> >> ----------------------------------------------------
> >> David L. Black, Distinguished Engineer
> >> EMC Corporation, 176 South St., Hopkinton, MA  01748
> >> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> >> david.black@emc.com        Mobile: +1 (978) 394-7754
> >> ----------------------------------------------------
> >


From housley@vigilsec.com  Mon Jun 10 11:45:14 2013
Return-Path: <housley@vigilsec.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 35B4421F8EC3; Mon, 10 Jun 2013 11:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 1UgtfUYwLhcq; Mon, 10 Jun 2013 11:45:09 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id C16ED21F91AB; Mon, 10 Jun 2013 11:45:08 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 2E453F24072; Mon, 10 Jun 2013 14:45:23 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id ceJRf+0LtkET; Mon, 10 Jun 2013 14:44:24 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 69DE6F2406E; Mon, 10 Jun 2013 14:45:22 -0400 (EDT)
Subject: Re: Last Call: <draft-ietf-pkix-est-07.txt> (Enrollment over Secure Transport) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>
Date: Mon, 10 Jun 2013 14:45:06 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1085)
Cc: IETF PKIX <pkix@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: Mon, 10 Jun 2013 18:45:14 -0000

I have read the document, I a support publication on the standards track.

Russ


On Jun 10, 2013, at 10:45 AM, The IESG wrote:

> 
> The IESG has received a request from the Public-Key Infrastructure
> (X.509) WG (pkix) to consider the following document:
> - 'Enrollment over Secure Transport'
>  <draft-ietf-pkix-est-07.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-24. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>   This document profiles certificate enrollment for clients using
>   Certificate Management over CMS (CMC) messages over a secure
>   transport.  This profile, called Enrollment over Secure Transport
>   (EST), describes a simple yet functional certificate management
>   protocol targeting Public Key Infrastructure (PKI) clients that need
>   to acquire client certificates and associated Certification Authority
>   (CA) certificate(s).  It also supports client-generated public/
>   private key pairs as well as key pairs generated by the CA.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-pkix-est/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-pkix-est/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 


From conte@isoc.org  Mon Jun 10 13:06:51 2013
Return-Path: <conte@isoc.org>
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 2145421E8056 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 13:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.109
X-Spam-Level: 
X-Spam-Status: No, score=-101.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 3OAgiQat6tKn for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 13:06:46 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0248.outbound.messaging.microsoft.com [213.199.154.248]) by ietfa.amsl.com (Postfix) with ESMTP id ED4E521E804E for <ietf@ietf.org>; Mon, 10 Jun 2013 13:06:45 -0700 (PDT)
Received: from mail182-db9-R.bigfish.com (10.174.16.237) by DB9EHSOBE035.bigfish.com (10.174.14.98) with Microsoft SMTP Server id 14.1.225.23; Mon, 10 Jun 2013 20:06:44 +0000
Received: from mail182-db9 (localhost [127.0.0.1])	by mail182-db9-R.bigfish.com (Postfix) with ESMTP id 5D43B120172	for <ietf@ietf.org>; Mon, 10 Jun 2013 20:06:44 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.117; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0610HT003.namprd06.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -2
X-BigFish: PS-2(zz552Ic85fh1be0Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz17326ah18c673h8275bh8275dhz2dh2a8h668h839hbe3he5bhf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1bceh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1155h)
Received: from mail182-db9 (localhost.localdomain [127.0.0.1]) by mail182-db9 (MessageSwitch) id 1370894801402323_9000; Mon, 10 Jun 2013 20:06:41 +0000 (UTC)
Received: from DB9EHSMHS025.bigfish.com (unknown [10.174.16.233])	by mail182-db9.bigfish.com (Postfix) with ESMTP id 5E28F3C0053	for <ietf@ietf.org>; Mon, 10 Jun 2013 20:06:41 +0000 (UTC)
Received: from BL2PRD0610HT003.namprd06.prod.outlook.com (157.56.240.117) by DB9EHSMHS025.bigfish.com (10.174.14.35) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 10 Jun 2013 20:06:41 +0000
Received: from BL2PRD0610MB374.namprd06.prod.outlook.com ([169.254.5.235]) by BL2PRD0610HT003.namprd06.prod.outlook.com ([10.255.101.38]) with mapi id 14.16.0311.000; Mon, 10 Jun 2013 20:06:35 +0000
From: Steve Conte <conte@isoc.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Applications open for ISOC Fellowship to IETF 88 (Vancouver)
Thread-Topic: Applications open for ISOC Fellowship to IETF 88 (Vancouver)
Thread-Index: AQHOZhYCCReSAmN6XUe0eODyePIY0w==
Date: Mon, 10 Jun 2013 20:06:34 +0000
Message-ID: <CDDB7FD8.15A96%conte@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.101.5]
Content-Type: multipart/alternative; boundary="_000_CDDB7FD815A96conteisocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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: Mon, 10 Jun 2013 20:06:51 -0000

--_000_CDDB7FD815A96conteisocorg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear Colleagues,

The Internet Society has announced that it is inviting applications for its=
 latest Internet Society Fellowships to the IETF.  The Fellowship programme=
 allows engineers from emerging and developing economies to attend an Inter=
net Engineering Task Force (IETF) meeting.

As you know, the IETF is the Internet's premier standards-making body, resp=
onsible for the development of protocols used in IP-based networks. IETF pa=
rticipants represent an international community of network designers, opera=
tors, vendors, and researchers involved in the technical operation of the I=
nternet and the continuing evolution of Internet architecture.

Fellowships will be awarded through a competitive application process. The =
Internet Society is currently accepting fellowship applications for the IET=
F 88 in Vancouver, Canada:

* IETF 88, November 03-08, 2013, Vancouver, British Columbia, Canada

Information and links to apply can be found at: http://www.internetsociety.=
org/fellows-ietf

Fellowship applications are due by 05 July 2013.

I encourage you apply or pass this information about this program to indivi=
duals involved in your network that have a keen interest in the Internet pr=
otocol development activities of the IETF.

The Internet Society Fellowships to the IETF are sponsored by Afilias, SIDN=
, Google, Microsoft, and Verisign.

If you have questions, please do not hesitate to contact Steve Conte <conte=
@isoc.org>.

Kind Regards,

Steve Conte

-----
Steve Conte
Internet Leadership Programme
The Internet Society
conte@isoc.org


--_000_CDDB7FD815A96conteisocorg_
Content-Type: text/html; charset="us-ascii"
Content-ID: <E94539CF488A014BB01AE0EF2303CF63@namprd06.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>
<div>
<div>
<div>Dear Colleagues,</div>
<div><br>
</div>
<div>The Internet Society has announced that it is inviting applications fo=
r its latest Internet Society Fellowships to the IETF. &nbsp;The Fellowship=
 programme allows engineers from emerging and developing economies to atten=
d an Internet Engineering Task Force
 (IETF) meeting.</div>
<div><br>
</div>
<div>As you know, the IETF is the Internet's premier standards-making body,=
 responsible for the development of protocols used in IP-based networks. IE=
TF participants represent an international community of network designers, =
operators, vendors, and researchers
 involved in the technical operation of the Internet and the continuing evo=
lution of Internet architecture.</div>
<div><br>
</div>
<div>Fellowships will be awarded through a competitive application process.=
 The Internet Society is currently accepting fellowship applications for th=
e IETF 88 in Vancouver, Canada:</div>
<div><br>
</div>
<div>* IETF 88, November 03-08, 2013, Vancouver, British Columbia, Canada</=
div>
<div><br>
</div>
<div>Information and links to apply can be found at: http://www.internetsoc=
iety.org/fellows-ietf</div>
<div><br>
</div>
<div>Fellowship applications are due by 05 July 2013.</div>
<div><br>
</div>
<div>I encourage you apply or pass this information about this program to i=
ndividuals involved in your network that have a keen interest in the Intern=
et protocol development activities of the IETF.</div>
<div><br>
</div>
<div>The Internet Society Fellowships to the IETF are sponsored by Afilias,=
 SIDN, Google, Microsoft, and Verisign.</div>
<div><br>
</div>
<div>If you have questions, please do not hesitate to contact Steve Conte &=
lt;conte@isoc.org&gt;.</div>
<div><br>
</div>
<div>Kind Regards,</div>
<div><br>
</div>
<div>Steve Conte</div>
</div>
<div><br>
</div>
<div>
<div>-----</div>
<div>Steve Conte</div>
<div>Internet Leadership Programme</div>
<div>The Internet Society</div>
<div>conte@isoc.org</div>
<div><br>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_CDDB7FD815A96conteisocorg_--

From ulrich@herberg.name  Mon Jun 10 13:34:05 2013
Return-Path: <ulrich@herberg.name>
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 D485821F8749 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 13:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 DL0Qk9l2EwZ9 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 13:34:04 -0700 (PDT)
Received: from mail-vb0-x231.google.com (mail-vb0-x231.google.com [IPv6:2607:f8b0:400c:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id C40CB21F86CA for <ietf@ietf.org>; Mon, 10 Jun 2013 13:34:01 -0700 (PDT)
Received: by mail-vb0-f49.google.com with SMTP id 12so1199731vbf.36 for <ietf@ietf.org>; Mon, 10 Jun 2013 13:34:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hSw971eJSZ1FDPo78t98YLAaqqN9Isw5lVu+whRpxAk=; b=hmqlMlEXB4wRSWKfmgeM2liNWMefNn6TeQ3WkuMaBHPUFfEU4q6Z/IjhGy3caL5iIz 4sHSmBjeDqOImnD6mW9yU/EdNKZwSPxdUKXK9zTHbnrqrIr7EW9V8R1anRL/DJ3pyBc1 LYyupddFmsfZRuE3AIFdQskIrtztaD4Mso5eQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=hSw971eJSZ1FDPo78t98YLAaqqN9Isw5lVu+whRpxAk=; b=nszlRZ9yaPor1O6UKLxMedx4+LoE4skKaA5mbL+uk9FTQof8DFN15tlud2gl+8NmwQ k+f0wMV3bD1nURGz6rxdl+MVKJUPQlckTwdxsrkcRmhq3oR0ryyVgaKK6+2s2tbY/hMF pSeVtqJLriTw4S2x88092bIPnXA5lIYuD2FXrMqIVu6gzHeNXT1QoKfPyqSCD4XiUMys Ph24qidzrKnQYbRfFQj2owLmoR8NF69LgAvVUb9tRkZ8gKV9j5gSisRdUadtV4R6y4cZ oS3UWr6XyLrFHbRbbjxQBQd/zTuRSSVZlyVUdKy1gUAqcdOUHeDczRbN/tKv0Eahr/Sr QFfw==
MIME-Version: 1.0
X-Received: by 10.52.232.69 with SMTP id tm5mr5584921vdc.117.1370896441192; Mon, 10 Jun 2013 13:34:01 -0700 (PDT)
Received: by 10.220.29.7 with HTTP; Mon, 10 Jun 2013 13:34:01 -0700 (PDT)
In-Reply-To: <20130523222242.3631.36122.idtracker@ietfa.amsl.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com>
Date: Mon, 10 Jun 2013 13:34:01 -0700
Message-ID: <CAK=bVC9WJdDoi481bLxa9ibHa690Vg3xa-iWfrG2F4jGgCPc+w@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Ulrich Herberg <ulrich@herberg.name>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQk+amH0t33GRq3WvEjUDsjcAeFYGiAnl0ekdem2KSGv7hqe6Ev1W0fKBnpnV9R/rXjHkECW
Cc: manet@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: Mon, 10 Jun 2013 20:34:05 -0000

We have submitted a new revision of the draft, addressing one comment
from Adrian during IETF LC (which we wanted to address in the previous
revision, but forgot about it). We added a new section that can
trigger future work, as requested by Adrian.

To the WG: Obviously, the new text is up for discussion if anyone has
any issues with it.

Best regards
Ulrich

On Thu, May 23, 2013 at 3:22 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'Security Threats for NHDP'
>   <draft-ietf-manet-nhdp-sec-threats-03.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-06. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>    This document analyses common security threats of the Neighborhood
>    Discovery Protocol (NHDP), and describes their potential impacts on
>    MANET routing protocols using NHDP.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

From presnick@qti.qualcomm.com  Mon Jun 10 13:37:35 2013
Return-Path: <presnick@qti.qualcomm.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 4752821F9A87 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 13:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 4n7NEHpEK+5V for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 13:37:31 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 1A59A21F9A47 for <ietf@ietf.org>; Mon, 10 Jun 2013 13:37:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1370896651; x=1402432651; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=HRZ1rrqd0YnZTrRm4vqtCyi5zx7cVFNCmJj+m51jixs=; b=ax4DfQKHrKpdjzexypwuP0bSuT0pz6NRvTYwNMHFmpAyQNbwxBWSfjA1 TAvQWYvcWT3yKne85naEu4+cjuTLTwpeFgHdrJMzTIJ+l8YRct1gqfhuI bpW55Me4+zKqv7BEH9WSd0o3RDVDnlWU7UKT4Np32y26+3vXHebEv8Xj5 A=;
X-IronPort-AV: E=Sophos;i="4.87,840,1363158000"; d="scan'208";a="55453153"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine02.qualcomm.com with ESMTP; 10 Jun 2013 13:37:26 -0700
X-IronPort-AV: E=Sophos;i="4.87,840,1363158000"; d="scan'208";a="462540964"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 10 Jun 2013 13:37:26 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 10 Jun 2013 13:37:26 -0700
Message-ID: <51B63905.2020807@qti.qualcomm.com>
Date: Mon, 10 Jun 2013 15:37:25 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <ietf@ietf.org>
Subject: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>
In-Reply-To: <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
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: Mon, 10 Jun 2013 20:37:35 -0000

Russ, our IAB chair and former IETF chair, just sent a message to the 
IETF list regarding a Last Call on draft-ietf-pkix-est. Here is the 
entire contents of his message, save quoting the whole Last Call request:

On 6/10/13 1:45 PM, Russ Housley wrote:
> I have read the document, I a support publication on the standards track.
>
> Russ

A month ago, we had another very senior member of the community post 
just such a message (in that case directly to the IESG) in response to a 
different Last Call. I took that senior member of the community to task 
for it. But apparently Russ either disagrees with my complaint or didn't 
notice that discussion on the IESG list, so I think it's worth airing 
here in public:

A statement such as the above is almost entirely useless to me as an 
IESG member trying to determine consensus. It is content-free.

We don't vote in the IETF, so a statement of support without a reason is 
meaningless. We should not be encouraging folks to send such things, and 
having the IAB chair do so is encouraging bad behavior. Had I not known 
Russ and his particular expertise, I would have no reason to take it 
into consideration *at all*. We should not have to determine the 
reputation of the poster to determine the weight of the message. Even 
given my background knowledge of who Russ is, I cannot tell from that 
message which one of the following Russ is saying:

- This document precisely describes a protocol of which I have been an 
implementer, and I was able to independently develop an interoperable 
implementation from the document.
- This document is about a technology with which I have familiarity and 
I have reviewed the technical details. It's fine.
- I've seen objection X to the document and I think the objection is 
incorrect for such-and-so reasons.
- My company has a vested interest in this technology becoming a 
standard, and even though I know nothing about it, I support it becoming 
a standards track document.
- My Aunt Gertrude is the document editor and she said that she needs 
statements of support, so here I am.
- I have a running wager on when we're going to reach RFC 7000 and I 
want to increase my odds of winning.

I take it I am supposed to presume from my friendship and knowledge of 
Russ that one of the first three is true and that the last three are 
not. (Well, maybe the last one might be true.) But if instead of from 
"Russ Housely", the message was from "Foo Bar", I would have absolutely 
no way to distinguish among the above.

I think we should stop with these one-line statements of support. They 
don't add anything to the consensus call. I'm disappointed that Russ 
contributed to this pattern.

Other opinions?

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From sob@harvard.edu  Mon Jun 10 14:52:17 2013
Return-Path: <sob@harvard.edu>
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 9530621F9A8E for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 14:52:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 dMre-M7ev3n5 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 14:52:12 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id B1BAC21F9A6A for <ietf@ietf.org>; Mon, 10 Jun 2013 14:52:12 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000004.university.harvard.edu [10.35.202.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id B6CE8E9597; Mon, 10 Jun 2013 17:52:10 -0400 (EDT)
Received: from ENTWHUBT0000001.university.harvard.edu (10.32.8.202) by entwedge0000004.university.harvard.edu (10.35.202.51) with Microsoft SMTP Server (TLS) id 14.2.342.3; Mon, 10 Jun 2013 17:52:05 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.137]) by ENTWHUBT0000001.university.harvard.edu ([10.32.8.202]) with mapi id 14.02.0342.003; Mon, 10 Jun 2013 17:52:10 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZiTBosr+fQKr20eVp92ps5Ia4w==
Date: Mon, 10 Jun 2013 21:52:10 +0000
Message-ID: <29FD6766-240D-454F-AF8C-1754C5D05454@harvard.edu>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>
In-Reply-To: <51B63905.2020807@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [173.166.5.69]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <7107E0391F98E54191DFC8604B171D8A@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <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: Mon, 10 Jun 2013 21:52:17 -0000

better than saying "I have not read the document but I support publication"

I do not see all that much help in having someone list reasons they support=
 publication unless
there is some particularly wonderful feature or the prose is particularly c=
lear

the reverse is not the case, I think there is real value in someone saying =
in detail why the do not support
publication of a document

Scott

On Jun 10, 2013, at 4:37 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote=
:

> Russ, our IAB chair and former IETF chair, just sent a message to the IET=
F list regarding a Last Call on draft-ietf-pkix-est. Here is the entire con=
tents of his message, save quoting the whole Last Call request:
>=20
> On 6/10/13 1:45 PM, Russ Housley wrote:
>> I have read the document, I a support publication on the standards track=
.
>>=20
>> Russ
>=20
> A month ago, we had another very senior member of the community post just=
 such a message (in that case directly to the IESG) in response to a differ=
ent Last Call. I took that senior member of the community to task for it. B=
ut apparently Russ either disagrees with my complaint or didn't notice that=
 discussion on the IESG list, so I think it's worth airing here in public:
>=20
> A statement such as the above is almost entirely useless to me as an IESG=
 member trying to determine consensus. It is content-free.
>=20
> We don't vote in the IETF, so a statement of support without a reason is =
meaningless. We should not be encouraging folks to send such things, and ha=
ving the IAB chair do so is encouraging bad behavior. Had I not known Russ =
and his particular expertise, I would have no reason to take it into consid=
eration *at all*. We should not have to determine the reputation of the pos=
ter to determine the weight of the message. Even given my background knowle=
dge of who Russ is, I cannot tell from that message which one of the follow=
ing Russ is saying:
>=20
> - This document precisely describes a protocol of which I have been an im=
plementer, and I was able to independently develop an interoperable impleme=
ntation from the document.
> - This document is about a technology with which I have familiarity and I=
 have reviewed the technical details. It's fine.
> - I've seen objection X to the document and I think the objection is inco=
rrect for such-and-so reasons.
> - My company has a vested interest in this technology becoming a standard=
, and even though I know nothing about it, I support it becoming a standard=
s track document.
> - My Aunt Gertrude is the document editor and she said that she needs sta=
tements of support, so here I am.
> - I have a running wager on when we're going to reach RFC 7000 and I want=
 to increase my odds of winning.
>=20
> I take it I am supposed to presume from my friendship and knowledge of Ru=
ss that one of the first three is true and that the last three are not. (We=
ll, maybe the last one might be true.) But if instead of from "Russ Housely=
", the message was from "Foo Bar", I would have absolutely no way to distin=
guish among the above.
>=20
> I think we should stop with these one-line statements of support. They do=
n't add anything to the consensus call. I'm disappointed that Russ contribu=
ted to this pattern.
>=20
> Other opinions?
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


From stpeter@stpeter.im  Mon Jun 10 14:55:04 2013
Return-Path: <stpeter@stpeter.im>
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 5455621F9AA2 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 14:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.79
X-Spam-Level: 
X-Spam-Status: No, score=-101.79 tagged_above=-999 required=5 tests=[AWL=0.809, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 9RAT+1mN6VGL for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 14:54:58 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 2A3F321F9AA6 for <ietf@ietf.org>; Mon, 10 Jun 2013 14:54:57 -0700 (PDT)
Received: from ergon.local (unknown [24.8.129.242]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C27094115C; Mon, 10 Jun 2013 16:08:25 -0600 (MDT)
Message-ID: <51B64B2F.1060808@stpeter.im>
Date: Mon, 10 Jun 2013 15:54:55 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>
In-Reply-To: <51B63905.2020807@qti.qualcomm.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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: Mon, 10 Jun 2013 21:55:04 -0000

On 6/10/13 2:37 PM, Pete Resnick wrote:

> I think we should stop with these one-line statements of support.

+1 ;-)

/psa



From dhc@dcrocker.net  Mon Jun 10 14:59:34 2013
Return-Path: <dhc@dcrocker.net>
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 9A19F21F99D5 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 14:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 bnGSSiEksWus for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 14:59:29 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6D3A921F99F4 for <ietf@ietf.org>; Mon, 10 Jun 2013 14:59:29 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5ALxMsi029906 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 10 Jun 2013 14:59:25 -0700
Message-ID: <51B64C37.1050304@dcrocker.net>
Date: Mon, 10 Jun 2013 16:59:19 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <29FD6766-240D-454F-AF8C-1754C5D05454@harvard.edu>
In-Reply-To: <29FD6766-240D-454F-AF8C-1754C5D05454@harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 10 Jun 2013 14:59:25 -0700 (PDT)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Mon, 10 Jun 2013 21:59:34 -0000

On 6/10/2013 4:52 PM, Bradner, Scott wrote:
> etter than saying "I have not read the document but I support publication"
>
> I do not see all that much help in having someone list reasons they support publication unless
> there is some particularly wonderful feature or the prose is particularly clear
>
> the reverse is not the case, I think there is real value in someone saying in detail why the do not support
> publication of a document


Content free statements of support turn the public query into a pure 
popularity contest and/or a game of personal authority.  Is your support 
more important than Pete's non-support?  Absent substance in the 
statements, we've no idea how to evaluate any disparity.

Statements that include substance about the nature and technical 
adequacies are a form of showing one's work on an exam: they demonstrate 
the substance that is the basis the support, not just the fact of it.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From Ted.Lemon@nominum.com  Mon Jun 10 15:06:24 2013
Return-Path: <Ted.Lemon@nominum.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 3F3D521F9AE0 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 15:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.642
X-Spam-Level: 
X-Spam-Status: No, score=-106.642 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 2dvpPJtBgIVg for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 15:06:17 -0700 (PDT)
Received: from exprod7og129.obsmtp.com (exprod7og129.obsmtp.com [64.18.2.122]) by ietfa.amsl.com (Postfix) with ESMTP id 71F4021F9ADE for <ietf@ietf.org>; Mon, 10 Jun 2013 15:06:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob129.postini.com ([64.18.6.12]) with SMTP ID DSNKUbZN2A/y05XbSyjHDoc7NvyhGuroGWrH@postini.com; Mon, 10 Jun 2013 15:06:17 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 00FA41B81EA for <ietf@ietf.org>; Mon, 10 Jun 2013 15:06:16 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id EA38319005D; Mon, 10 Jun 2013 15:06:15 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 15:06:16 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkv8qgAgAAD74A=
Date: Mon, 10 Jun 2013 22:06:15 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751CF444@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <29FD6766-240D-454F-AF8C-1754C5D05454@harvard.edu>
In-Reply-To: <29FD6766-240D-454F-AF8C-1754C5D05454@harvard.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <037E326BCE723240AF265B1F990E0DE9@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "<ietf@ietf.org>" <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: Mon, 10 Jun 2013 22:06:24 -0000

On Jun 10, 2013, at 5:52 PM, "Bradner, Scott" <sob@harvard.edu> wrote:
> I do not see all that much help in having someone list reasons they suppo=
rt publication unless
> there is some particularly wonderful feature or the prose is particularly=
 clear

I don't really see any point in expressing support for a document during IE=
TF last call unless it is as a rejoinder to some valid expression of non-su=
pport.   A valid expression of non-support would point out some technical p=
oint that either was not considered by the working group, or was considered=
, but the working group wasn't competent to evaluate the question.   Or it =
would point out some process failure that occurred in the working group.

Even if you review the document during IETF last call, unless you find a pr=
oblem with it there's not much point in saying anything.


From dwm@xpasc.com  Mon Jun 10 15:20:02 2013
Return-Path: <dwm@xpasc.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 DA6E721F9005 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 15:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.276
X-Spam-Level: 
X-Spam-Status: No, score=-2.276 tagged_above=-999 required=5 tests=[AWL=0.323,  BAYES_00=-2.599]
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 nIYTVfUdaY5y for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 15:19:57 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 13CCE21F9408 for <ietf@ietf.org>; Mon, 10 Jun 2013 15:19:56 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 856E54039E for <ietf@ietf.org>; Mon, 10 Jun 2013 22:19:55 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id r5AMJoEL008097 for <ietf@ietf.org>; Mon, 10 Jun 2013 15:19:50 -0700
Date: Mon, 10 Jun 2013 15:19:50 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Content-free Last Call comments
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751CF444@mbx-01.win.nominum.com>
Message-ID: <alpine.LRH.2.01.1306101514260.8035@egate.xpasc.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <29FD6766-240D-454F-AF8C-1754C5D05454@harvard.edu> <8D23D4052ABE7A4490E77B1A012B6307751CF444@mbx-01.win.nominum.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.87-g7939dec
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "<ietf@ietf.org>" <ietf@ietf.org>
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: Mon, 10 Jun 2013 22:20:03 -0000

On Mon, 10 Jun 2013, Ted Lemon wrote:

> On Jun 10, 2013, at 5:52 PM, "Bradner, Scott" <sob@harvard.edu> wrote:
> > I do not see all that much help in having someone list reasons they support publication unless
> > there is some particularly wonderful feature or the prose is particularly clear
> 
> I don't really see any point in expressing support for a document during
> IETF last call unless it is as a rejoinder to some valid expression of
> non-support.  A valid expression of non-support would point out some
> technical point that either was not considered by the working group, or
> was considered, but the working group wasn't competent to evaluate the
> question.  Or it would point out some process failure that occurred in
> the working group.
> 
> Even if you review the document during IETF last call, unless you find a 
> problem with it there's not much point in saying anything.

I don't think there is another way to indicate you've reviewed a draft and
found no issues. Surely rough concensus must include confidence that
that silence means more than ignorance and I'm not aware of any mechanism
to evaluate the level of review exercised during last call.

From Ted.Lemon@nominum.com  Mon Jun 10 15:39:12 2013
Return-Path: <Ted.Lemon@nominum.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 53CBB21F99D2 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 15:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.64
X-Spam-Level: 
X-Spam-Status: No, score=-106.64 tagged_above=-999 required=5 tests=[AWL=-0.041, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 NAU82ygRAf53 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 15:39:05 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB4121F99B6 for <ietf@ietf.org>; Mon, 10 Jun 2013 15:39:04 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUbZViEcswhFn2jIMuH5VPqlrue+JSpHY@postini.com; Mon, 10 Jun 2013 15:39:05 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2B3821B81D6 for <ietf@ietf.org>; Mon, 10 Jun 2013 15:39:04 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2038119005D for <ietf@ietf.org>; Mon, 10 Jun 2013 15:39:04 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 15:39:04 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkv8qgAgAAD74CAAAPLAIAABV4A
Date: Mon, 10 Jun 2013 22:39:03 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751CF572@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <29FD6766-240D-454F-AF8C-1754C5D05454@harvard.edu> <8D23D4052ABE7A4490E77B1A012B6307751CF444@mbx-01.win.nominum.com> <alpine.LRH.2.01.1306101514260.8035@egate.xpasc.com>
In-Reply-To: <alpine.LRH.2.01.1306101514260.8035@egate.xpasc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <238E707614E42B46ABFB252821931319@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Mon, 10 Jun 2013 22:39:12 -0000

On Jun 10, 2013, at 6:19 PM, David Morris <dwm@xpasc.com> wrote:
> I don't think there is another way to indicate you've reviewed a draft an=
d
> found no issues. Surely rough concensus must include confidence that
> that silence means more than ignorance and I'm not aware of any mechanism
> to evaluate the level of review exercised during last call.

The expectation is that the working group gave the document sufficient revi=
ew; the point of the IETF last call then is to backstop that review, not au=
gment it.   A document that receives no comment in IETF last call is assume=
d to have consensus.


From sm@resistor.net  Mon Jun 10 16:33:58 2013
Return-Path: <sm@resistor.net>
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 6942321F99A9 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 16:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.437
X-Spam-Level: 
X-Spam-Status: No, score=-102.437 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Kd7lAtSfA1IW for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 16:33:57 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A7D121F999C for <ietf@ietf.org>; Mon, 10 Jun 2013 16:33:57 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5ANXq4g010312; Mon, 10 Jun 2013 16:33:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1370907236; bh=qNREPOV5S+hcIpQXX+mRdmkbQnscbPWTHwm/7li2rDo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=yxQ+wHBmQxLVVV/+xvy7782nqFXI31LP/e4ITyfWGvc3rQXsNGLT0HchMihCY5Xpn 2akOWj0lAwc+/oz5z57zdWWs5cS1g+qtwDpYtVhMCwoOo5O9N6YGH6Ivo0wqshT1v6 s7YqYcJpF7dzEblL/B5dAjj1XrRZaRItUVfVzfoc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1370907236; i=@resistor.net; bh=qNREPOV5S+hcIpQXX+mRdmkbQnscbPWTHwm/7li2rDo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=IhQNFc90LpyPQiL+xnMLc2nSX9zYUbLLPP26IOmAb7TarPhI1jwPSwy0CDj5M+sL6 r7Uyb4XV335ryvMgiGrhBzU1P5zjYUguY7ThA2fdE2yNaB+HNZgRgoCfGrXnfy8Nfp 1fmsB8rNoWGojpYzx5tpMh6/soW2y3bLFMvIaRXQ=
Message-Id: <6.2.5.6.2.20130610150249.0ccd9c90@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 10 Jun 2013 16:21:49 -0700
To: Pete Resnick <presnick@qti.qualcomm.com>
From: SM <sm@resistor.net>
Subject: Re: Content-free Last Call comments
In-Reply-To: <51B63905.2020807@qti.qualcomm.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Mon, 10 Jun 2013 23:33:58 -0000

Hi Pete,
At 13:37 10-06-2013, Pete Resnick wrote:
>A month ago, we had another very senior member of the community post 
>just such a message (in that case directly to the IESG) in response 
>to a different Last Call. I took that senior member of the community 
>to task for it. But apparently Russ either disagrees with my 
>complaint or didn't notice that discussion on the IESG list, so I 
>think it's worth airing here in public:

I don't expect IAB or IESG members to be infallible, i.e. they are 
individuals after all.

>A statement such as the above is almost entirely useless to me as an 
>IESG member trying to determine consensus. It is content-free.

Yes.

>We don't vote in the IETF, so a statement of support without a 
>reason is meaningless. We should not be encouraging folks to send 
>such things, and having the IAB chair do so is encouraging bad 
>behavior. Had I not known Russ and his particular expertise, I would 
>have no reason to take it into consideration *at all*. We should not 
>have to determine the reputation of the poster to determine the 
>weight of the message. Even given my background knowledge of who 
>Russ is, I cannot tell from that message which one of the following 
>Russ is saying:

The comment was from an individual.  The issue is that if you do a 
blind review of the messages you don't know who sent the message and 
the only weight you could give is to the content of the message.

>I think we should stop with these one-line statements of support. 
>They don't add anything to the consensus call. I'm disappointed that 
>Russ contributed to this pattern.

I agree that one-line statements are not of much use.  It's more 
tedious to write a statement to support a proposal than an objection 
to it.  Non-silent Last Calls usually draw objections.  It's going to 
be difficult to balance that if one-line statements of support (or 
objections) are not considered in a determination of consensus.

Regards,
-sm 


From Ted.Lemon@nominum.com  Mon Jun 10 16:46:37 2013
Return-Path: <Ted.Lemon@nominum.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 130EF21F99C5 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 16:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.639
X-Spam-Level: 
X-Spam-Status: No, score=-106.639 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 3BR0hVuZ+jLZ for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 16:46:30 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 525A221F99C6 for <ietf@ietf.org>; Mon, 10 Jun 2013 16:46:30 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKUbZlVukhTlr4YhysFNK63fky5WVOQ2FH@postini.com; Mon, 10 Jun 2013 16:46:30 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E35AF1B81B3 for <ietf@ietf.org>; Mon, 10 Jun 2013 16:46:29 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D7AB819005D; Mon, 10 Jun 2013 16:46:29 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 16:46:29 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: SM <sm@resistor.net>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkwC7SAgAAG4wA=
Date: Mon, 10 Jun 2013 23:46:29 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751CF72F@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <6.2.5.6.2.20130610150249.0ccd9c90@resistor.net>
In-Reply-To: <6.2.5.6.2.20130610150249.0ccd9c90@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <858C57ECA72D654393F986406924D5A9@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "<ietf@ietf.org>" <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: Mon, 10 Jun 2013 23:46:37 -0000

On Jun 10, 2013, at 7:21 PM, SM <sm@resistor.net> wrote:
> I agree that one-line statements are not of much use.  It's more tedious =
to write a statement to support a proposal than an objection to it.  Non-si=
lent Last Calls usually draw objections.  It's going to be difficult to bal=
ance that if one-line statements of support (or objections) are not conside=
red in a determination of consensus.

Determining consensus in an IETF last call is a bit more complicated than t=
hat.   It's not a working group last call.   If someone objects to publicat=
ion during IETF last call, and their objection has already been discussed a=
nd addressed in the working group, the objection in IETF last call doesn't =
break that consensus.


From marka@isc.org  Mon Jun 10 17:31:36 2013
Return-Path: <marka@isc.org>
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 0F32111E80AE for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 17:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
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 er8nLfBTHKrV for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 17:31:35 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 675EF11E80A5 for <ietf@ietf.org>; Mon, 10 Jun 2013 17:31:35 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id AE57CC94F8; Tue, 11 Jun 2013 00:31:27 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1370910695; bh=4kiU6/h7sjOm1DJ/P3taASOdLkqPU1gk0C4W92dOc8A=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=r60p0bybmAA4UiKeoTFKZ0Ssoz77NvJKHch+tCwEFYXVO5mUkcqv8zDd92yQm5JzA oZ0fBy9nBjbQ30Hh7W9f/Pw9hKMfTKjZzy18z3kGWICdPdBoUpSOzQuuRPqtTTO59k li2rFZvghTN0e5tyVl1PujfMh3WNkIXbWPCCsT8A=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Tue, 11 Jun 2013 00:31:27 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 65825216C43; Tue, 11 Jun 2013 00:31:27 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id B4E3B35B17AC; Tue, 11 Jun 2013 10:31:24 +1000 (EST)
To: Ted Lemon <Ted.Lemon@nominum.com>
From: Mark Andrews <marka@isc.org>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <6.2.5.6.2.20130610150249.0ccd9c90@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751CF72F@mbx-01.win.nominum.com>
Subject: Re: Content-free Last Call comments
In-reply-to: Your message of "Mon, 10 Jun 2013 23:46:29 +0000." <8D23D4052ABE7A4490E77B1A012B6307751CF72F@mbx-01.win.nominum.com>
Date: Tue, 11 Jun 2013 10:31:24 +1000
Message-Id: <20130611003124.B4E3B35B17AC@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: SM <sm@resistor.net>, Pete Resnick <presnick@qti.qualcomm.com>, "<ietf@ietf.org>" <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: Tue, 11 Jun 2013 00:31:36 -0000

In message <8D23D4052ABE7A4490E77B1A012B6307751CF72F@mbx-01.win.nominum.com>, T
ed Lemon writes:
> On Jun 10, 2013, at 7:21 PM, SM <sm@resistor.net> wrote:
> > I agree that one-line statements are not of much use.  It's more tedious =
> to write a statement to support a proposal than an objection to it.  Non-si=
> lent Last Calls usually draw objections.  It's going to be difficult to bal=
> ance that if one-line statements of support (or objections) are not conside=
> red in a determination of consensus.
> 
> Determining consensus in an IETF last call is a bit more complicated than t=
> hat.   It's not a working group last call.   If someone objects to publicat=
> ion during IETF last call, and their objection has already been discussed a=
> nd addressed in the working group, the objection in IETF last call doesn't =
> break that consensus.

Which breaks some of the reasons why we do IETF last calls.  WGs do get too
focused on a problem and do fail to do a balance response to problems.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From stephen.farrell@cs.tcd.ie  Mon Jun 10 17:37:12 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
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 EF48F21E809C for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 17:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 rg02IqS5QHoX for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 17:37:07 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id C350421F9942 for <ietf@ietf.org>; Mon, 10 Jun 2013 17:37:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 50217BE7C; Tue, 11 Jun 2013 01:36:42 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nYwgvpnSkOze; Tue, 11 Jun 2013 01:36:41 +0100 (IST)
Received: from [10.87.48.12] (unknown [86.42.23.89]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 12281BE76; Tue, 11 Jun 2013 01:36:41 +0100 (IST)
Message-ID: <51B6710E.4040800@cs.tcd.ie>
Date: Tue, 11 Jun 2013 01:36:30 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>
In-Reply-To: <51B63905.2020807@qti.qualcomm.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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: Tue, 11 Jun 2013 00:37:13 -0000

Hi Pete,

I think you err when you say this:

> A statement such as the above is almost entirely useless to me as an
> IESG member trying to determine consensus. It is content-free.

In fact, you do know Russ. If you did not, then the above would be
far closer to correct. But in reality you do know a lot more than
you claim below. With overwhelming probability, your choice #2
applies and I'm very surprised you don't also think that. If it
made a significant difference and I wasn't sure I'd ask Russ to
clarify. For me, I read Russ' mail and I concluded he meant #2.
And I'm confident in that conclusion.

So I'm really bemused when you say that you don't know how to
interpret Russ' mail.

Declaring that mail problematic also seems quite purist to me.
And insisting on purity seems to me worse than being slightly
but harmlessly ambiguous.

At the same time I agree we do not want a procession of +1 mails.
But then we won't get that for this draft. And if we did get that
for any draft, some IETF participants (probably incl. you and I)
would notice that and query it or object. So perhaps you're also
being a tad trigger-happy on jumping on this message.

Lastly, I think evaluating IETF LC messages only in terms
of how they help the IESG evaluate consensus or not is wrong.
Those messages are for and from the IETF community. So if
e.g. some renowned NFS person who's hardly known to the IESG
were to have sent an equivalent message, that might have been
quite good input that Martin or Spencer could have translated for
you. And that's just fine. And it would be fine if Russ' mail
had been directed not at the IESG but at some other part of the
community.

So bottom line, I think you're wrong, Russ' mail was not
content-free.

S.

PS: Yes, this is a not-very-good academic accusing an employee
of an industrial behemoth of excess purity. Go figure:-)

On 06/10/2013 09:37 PM, Pete Resnick wrote:
> Russ, our IAB chair and former IETF chair, just sent a message to the
> IETF list regarding a Last Call on draft-ietf-pkix-est. Here is the
> entire contents of his message, save quoting the whole Last Call request:
> 
> On 6/10/13 1:45 PM, Russ Housley wrote:
>> I have read the document, I a support publication on the standards track.
>>
>> Russ
> 
> A month ago, we had another very senior member of the community post
> just such a message (in that case directly to the IESG) in response to a
> different Last Call. I took that senior member of the community to task
> for it. But apparently Russ either disagrees with my complaint or didn't
> notice that discussion on the IESG list, so I think it's worth airing
> here in public:
> 
> A statement such as the above is almost entirely useless to me as an
> IESG member trying to determine consensus. It is content-free.
> 
> We don't vote in the IETF, so a statement of support without a reason is
> meaningless. We should not be encouraging folks to send such things, and
> having the IAB chair do so is encouraging bad behavior. Had I not known
> Russ and his particular expertise, I would have no reason to take it
> into consideration *at all*. We should not have to determine the
> reputation of the poster to determine the weight of the message. Even
> given my background knowledge of who Russ is, I cannot tell from that
> message which one of the following Russ is saying:
> 
> - This document precisely describes a protocol of which I have been an
> implementer, and I was able to independently develop an interoperable
> implementation from the document.
> - This document is about a technology with which I have familiarity and
> I have reviewed the technical details. It's fine.
> - I've seen objection X to the document and I think the objection is
> incorrect for such-and-so reasons.
> - My company has a vested interest in this technology becoming a
> standard, and even though I know nothing about it, I support it becoming
> a standards track document.
> - My Aunt Gertrude is the document editor and she said that she needs
> statements of support, so here I am.
> - I have a running wager on when we're going to reach RFC 7000 and I
> want to increase my odds of winning.
> 
> I take it I am supposed to presume from my friendship and knowledge of
> Russ that one of the first three is true and that the last three are
> not. (Well, maybe the last one might be true.) But if instead of from
> "Russ Housely", the message was from "Foo Bar", I would have absolutely
> no way to distinguish among the above.
> 
> I think we should stop with these one-line statements of support. They
> don't add anything to the consensus call. I'm disappointed that Russ
> contributed to this pattern.
> 
> Other opinions?
> 
> pr
> 

From Ted.Lemon@nominum.com  Mon Jun 10 18:31:34 2013
Return-Path: <Ted.Lemon@nominum.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 3C5F921F9732 for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 18:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.637
X-Spam-Level: 
X-Spam-Status: No, score=-106.637 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 lT3KNCCZB92k for <ietf@ietfa.amsl.com>; Mon, 10 Jun 2013 18:31:27 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 7B77C21F96EA for <ietf@ietf.org>; Mon, 10 Jun 2013 18:31:27 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUbZ975KoK+fyqPj8Jht9c4P+gs2zu19l@postini.com; Mon, 10 Jun 2013 18:31:27 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0EFAA1B81D6 for <ietf@ietf.org>; Mon, 10 Jun 2013 18:31:27 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F1CBD19005D; Mon, 10 Jun 2013 18:31:26 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 18:31:20 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkwC7SAgAAG4wD//5dE04AAhgQA
Date: Tue, 11 Jun 2013 01:31:20 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751CF8CA@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <6.2.5.6.2.20130610150249.0ccd9c90@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751CF72F@mbx-01.win.nominum.com> <20130611003124.B4E3B35B17AC@drugs.dv.isc.org>
In-Reply-To: <20130611003124.B4E3B35B17AC@drugs.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <438C7F091A277E45A3D8CF60CD52ACB3@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: SM <sm@resistor.net>, Pete Resnick <presnick@qti.qualcomm.com>, "<ietf@ietf.org>" <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: Tue, 11 Jun 2013 01:31:34 -0000

On Jun 10, 2013, at 8:31 PM, Mark Andrews <marka@isc.org> wrote:
> Which breaks some of the reasons why we do IETF last calls.  WGs do get t=
oo
> focused on a problem and do fail to do a balance response to problems.

If enough IETF last call people agree that the working group made a mistake=
, that could change the consensus evaluation, but there would have to be a =
substantive argument made.   Revisiting the arguments that happened during =
WGLC in IETF last call with the same participants can't possibly change the=
 consensus.


From mnot@mnot.net  Tue Jun 11 00:51:52 2013
Return-Path: <mnot@mnot.net>
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 4341121F9A82 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 00:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.599
X-Spam-Level: 
X-Spam-Status: No, score=-105.599 tagged_above=-999 required=5 tests=[AWL=-3.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 44M4pwIQe63I for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 00:51:47 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 5F30D21F9A83 for <ietf@ietf.org>; Tue, 11 Jun 2013 00:51:35 -0700 (PDT)
Received: from 131-113-150-228.event.mita.keio.ac.jp (unknown [131.113.150.228]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 3833022E257; Tue, 11 Jun 2013 03:51:28 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Content-free Last Call comments
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <51B63905.2020807@qti.qualcomm.com>
Date: Tue, 11 Jun 2013 16:51:28 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <30E650BD-F609-4B44-86E1-BA25CE903779@mnot.net>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1508)
Cc: 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: Tue, 11 Jun 2013 07:51:52 -0000

I'm seeing two things here.

One is that you need some context of *why* something is supported, as =
per your examples.=20

The other is that you need a level of detail that's more than "one =
line."

However, I'd note that *all* of those examples are (in my MUA) one line =
each.

So, can you clarify? I.e., if Russ had included one of those lines, =
would that have been enough?

I'd support asking for that level of detail. OTOH I'm not for making =
people "show their work" to a greater level of detail; the overhead of =
participating in an effort is high, and the most relevant people are =
often exhausted by this point in the process. We shouldn't pile more =
work onto them (he says, conscious of the work piled onto ADs as well).

Regards,


On 11/06/2013, at 5:37 AM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> Russ, our IAB chair and former IETF chair, just sent a message to the =
IETF list regarding a Last Call on draft-ietf-pkix-est. Here is the =
entire contents of his message, save quoting the whole Last Call =
request:
>=20
> On 6/10/13 1:45 PM, Russ Housley wrote:
>> I have read the document, I a support publication on the standards =
track.
>>=20
>> Russ
>=20
> A month ago, we had another very senior member of the community post =
just such a message (in that case directly to the IESG) in response to a =
different Last Call. I took that senior member of the community to task =
for it. But apparently Russ either disagrees with my complaint or didn't =
notice that discussion on the IESG list, so I think it's worth airing =
here in public:
>=20
> A statement such as the above is almost entirely useless to me as an =
IESG member trying to determine consensus. It is content-free.
>=20
> We don't vote in the IETF, so a statement of support without a reason =
is meaningless. We should not be encouraging folks to send such things, =
and having the IAB chair do so is encouraging bad behavior. Had I not =
known Russ and his particular expertise, I would have no reason to take =
it into consideration *at all*. We should not have to determine the =
reputation of the poster to determine the weight of the message. Even =
given my background knowledge of who Russ is, I cannot tell from that =
message which one of the following Russ is saying:
>=20
> - This document precisely describes a protocol of which I have been an =
implementer, and I was able to independently develop an interoperable =
implementation from the document.
> - This document is about a technology with which I have familiarity =
and I have reviewed the technical details. It's fine.
> - I've seen objection X to the document and I think the objection is =
incorrect for such-and-so reasons.
> - My company has a vested interest in this technology becoming a =
standard, and even though I know nothing about it, I support it becoming =
a standards track document.
> - My Aunt Gertrude is the document editor and she said that she needs =
statements of support, so here I am.
> - I have a running wager on when we're going to reach RFC 7000 and I =
want to increase my odds of winning.
>=20
> I take it I am supposed to presume from my friendship and knowledge of =
Russ that one of the first three is true and that the last three are =
not. (Well, maybe the last one might be true.) But if instead of from =
"Russ Housely", the message was from "Foo Bar", I would have absolutely =
no way to distinguish among the above.
>=20
> I think we should stop with these one-line statements of support. They =
don't add anything to the consensus call. I'm disappointed that Russ =
contributed to this pattern.
>=20
> Other opinions?
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20

--
Mark Nottingham   http://www.mnot.net/




From sm@resistor.net  Tue Jun 11 01:30:36 2013
Return-Path: <sm@resistor.net>
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 59CB021F9A50 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 01:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.455
X-Spam-Level: 
X-Spam-Status: No, score=-102.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 NMj0UFaIGOqK for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 01:30:35 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5E321F9A4C for <ietf@ietf.org>; Tue, 11 Jun 2013 01:30:35 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5B8UUHe007486 for <ietf@ietf.org>; Tue, 11 Jun 2013 01:30:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1370939434; bh=9ZnYZgvJQOgp9EexGyRUeQhuDxBkEneUuPl4oHBaYuA=; h=Date:To:From:Subject:In-Reply-To:References; b=vsqXG/rQKQOCr5aYoi9K9eYeLJvBu+7ZPNosq7Dkk8TFsN2O6ot5Ciynvm5XRakUa HE1mnOUyAx+/buFvSnHBi6ClhIKOPOdZucdQXXT++wETeDUgyWXzvXp2kat5D2hwCH iceZkCed9ihojd3Zw0DAi9RTpHJGy2901Ad2ORYA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1370939434; i=@resistor.net; bh=9ZnYZgvJQOgp9EexGyRUeQhuDxBkEneUuPl4oHBaYuA=; h=Date:To:From:Subject:In-Reply-To:References; b=fgvQxlWGjV67tyUqdGznhVojMjR+RaOv/2MroHASpCz/HPCscPc0GEV4Pa1tmkRjG wQftGoiaerA3FTc9UidfZp9UP4qisfG3zBIcOQIqpLSTKajkoF/923TzlB9x7cR1DA gtnB9N4uVoAVyeAlQeWK0y4dJAjMPgWx5RMNNnpk=
Message-Id: <6.2.5.6.2.20130611000605.0b853d00@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 11 Jun 2013 01:30:03 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-pkix-est-07.txt> (Enrollment over Secure Transport) to Proposed Standard
In-Reply-To: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Tue, 11 Jun 2013 08:30:36 -0000

At 07:45 10-06-2013, The IESG wrote:
>The IESG has received a request from the Public-Key Infrastructure
>(X.509) WG (pkix) to consider the following document:
>- 'Enrollment over Secure Transport'
>   <draft-ietf-pkix-est-07.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-06-24. Exceptionally, comments may be

There weren't any comments during the WGLC of 
draft-ietf-pkix-est-06.  The AD review of draft-ietf-pkix-est-06 was 
posted to the mailing list and the only comments after that was "this 
version address my concerns".

I read the document.  It is about the use of an obsolete Proposed 
Standard or later versions of that specification.  The comments from 
three individuals who happen to be Area Directors creates a 
conundrum; should I give more weight to them or to a content-free 
comment?  I do not support the publication of this document as a 
Proposed Standard as it is doubtful that it has the consensus of the 
working group.

Regards,
-sm 


From randy@psg.com  Tue Jun 11 01:52:02 2013
Return-Path: <randy@psg.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 8051021F9A7E for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 01:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
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 v7OfImGf8Ezv for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 01:52:02 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0159721F9A7B for <ietf@ietf.org>; Tue, 11 Jun 2013 01:52:02 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UmKJ1-000Bmz-VJ; Tue, 11 Jun 2013 08:51:56 +0000
Date: Tue, 11 Jun 2013 10:51:53 +0200
Message-ID: <m261xlowra.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Content-free Last Call comments
In-Reply-To: <30E650BD-F609-4B44-86E1-BA25CE903779@mnot.net>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <30E650BD-F609-4B44-86E1-BA25CE903779@mnot.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: Pete Resnick <presnick@qti.qualcomm.com>, 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: Tue, 11 Jun 2013 08:52:02 -0000

so now i am expected to do a write-up of why i show simple support of a
document i have read?  may i use carbon paper for the triplicate, or
will a copier suffice?  surely we can find a way to waste more time and
effort.

randy

From abdussalambaryun@gmail.com  Tue Jun 11 01:57:04 2013
Return-Path: <abdussalambaryun@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 7149821F9A7B for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 01:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 CWa-bQTIKBzL for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 01:57:03 -0700 (PDT)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id AB8E721F9A8C for <ietf@ietf.org>; Tue, 11 Jun 2013 01:57:03 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id uo1so3497034pbc.31 for <ietf@ietf.org>; Tue, 11 Jun 2013 01:57:03 -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=zVLpHltBuhPNdgf2nAEQT+8eECCOjVDhu1AkpMWMbNc=; b=ZD+f1yQ1Kb25WHuBW41e2Y23ofppcExjaoyPSPE9qr7Liy7xr1MD8Zm6WHJJ4kh279 DAx7UOx0+b0mxMSAGmecX9loYePONNw0IcMOhZNSScyBv6P9InR6lUpTUKrZEOXHXPwK K98u2tw8VJUFehqMFuM+qzXEevyK+g17EwKTWKmXI6K4tFYGDF4rLXvhRP8F9e8bdwr1 PYNfwn3zKupiGep8v6nQNk5ZepYr9CqBFSCZSccdhsJgj5DZpUc0aGrz9T2JvFwHs3iW qXUrwm9cWWpwPNX5ijRcHdf/EGgvCAqD3s0TrJ2iWjbpK4TjfZ58hrebJzug1l8yNmis 2KDA==
MIME-Version: 1.0
X-Received: by 10.66.164.71 with SMTP id yo7mr7586462pab.92.1370941023396; Tue, 11 Jun 2013 01:57:03 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Tue, 11 Jun 2013 01:57:03 -0700 (PDT)
In-Reply-To: <CAK=bVC9WJdDoi481bLxa9ibHa690Vg3xa-iWfrG2F4jGgCPc+w@mail.gmail.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CAK=bVC9WJdDoi481bLxa9ibHa690Vg3xa-iWfrG2F4jGgCPc+w@mail.gmail.com>
Date: Tue, 11 Jun 2013 10:57:03 +0200
Message-ID: <CADnDZ8-0gKXtvhK2xGdofFzgn+zg4mMvquhoeAM7qq=vQ6=TNg@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Ulrich Herberg <ulrich@herberg.name>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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: Tue, 11 Jun 2013 08:57:04 -0000

The IETF Last Call has finished after 06.06.13 and now you request
discussions. I think only IESG can call for discussions not editors.

On 6/10/13, Ulrich Herberg <ulrich@herberg.name> wrote:
> We have submitted a new revision of the draft, addressing one comment
> from Adrian during IETF LC (which we wanted to address in the previous
> revision, but forgot about it). We added a new section that can
> trigger future work, as requested by Adrian.

I don't see that Adrian requested a future work section, could you
refer to his input for that or was that private request. May be
comments in last call made you think to add missing information as
future. What is the reason for future work in this informational
draft?
>
> To the WG: Obviously, the new text is up for discussion if anyone has
> any issues with it.

Is that a new text or new idea? if I don't know what the Editors
discussed privately (outside IETF) how can I discuss inside IETF?
However, I will not review any more for this draft because it has
special policy for refering to contributions.

AB

>
> Best regards
> Ulrich
>
> On Thu, May 23, 2013 at 3:22 PM, The IESG <iesg-secretary@ietf.org> wrote:
>>
>> The IESG has received a request from the Mobile Ad-hoc Networks WG
>> (manet) to consider the following document:
>> - 'Security Threats for NHDP'
>>   <draft-ietf-manet-nhdp-sec-threats-03.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-06-06. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>    This document analyses common security threats of the Neighborhood
>>    Discovery Protocol (NHDP), and describes their potential impacts on
>>    MANET routing protocols using NHDP.
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

From adrian@olddog.co.uk  Tue Jun 11 02:59:55 2013
Return-Path: <adrian@olddog.co.uk>
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 94CB421F9648 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 02:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level: 
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599]
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 l914jPWkUJt4 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 02:59:50 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 9028E21F8B35 for <ietf@ietf.org>; Tue, 11 Jun 2013 02:59:50 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5B9xm3H011801;  Tue, 11 Jun 2013 10:59:48 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5B9xfAH011667 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 11 Jun 2013 10:59:42 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com>	<CAK=bVC9WJdDoi481bLxa9ibHa690Vg3xa-iWfrG2F4jGgCPc+w@mail.gmail.com> <CADnDZ8-0gKXtvhK2xGdofFzgn+zg4mMvquhoeAM7qq=vQ6=TNg@mail.gmail.com>
In-Reply-To: <CADnDZ8-0gKXtvhK2xGdofFzgn+zg4mMvquhoeAM7qq=vQ6=TNg@mail.gmail.com>
Subject: RE: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt>	(Security Threats for NHDP) to Informational RFC
Date: Tue, 11 Jun 2013 10:59:37 +0100
Message-ID: <0f0e01ce668a$64e851f0$2eb8f5d0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIhotg4CdXjJ2V6m9iU5kaOA6mt7QFQ8iNmAfePQ/2Yb4migA==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Tue, 11 Jun 2013 09:59:55 -0000

> > We have submitted a new revision of the draft, addressing one comment
> > from Adrian during IETF LC (which we wanted to address in the previous
> > revision, but forgot about it). We added a new section that can
> > trigger future work, as requested by Adrian.
> 
> I don't see that Adrian requested a future work section, could you
> refer to his input for that or was that private request. May be
> comments in last call made you think to add missing information as
> future. What is the reason for future work in this informational
> draft?

Abdussalam,

Look and ye shall see. Seek and ye shall find. 

http://www.ietf.org/mail-archive/web/manet/current/msg15423.html
> 2. Please consider adding a short section that may drive new work by
>   suggesting which threats need to be addressed in new protocol work,
>   which in deployment, and which by applications.

Adrian


From Ted.Lemon@nominum.com  Tue Jun 11 04:02:43 2013
Return-Path: <Ted.Lemon@nominum.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 5D2AE21F9648 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.634
X-Spam-Level: 
X-Spam-Status: No, score=-106.634 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 fY8Tz1k02J4C for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:02:36 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id C57D221F8E84 for <ietf@ietf.org>; Tue, 11 Jun 2013 04:02:28 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUbcDxNz9ppv/s3RTeDTDRZT1LFDLPGX2@postini.com; Tue, 11 Jun 2013 04:02:28 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 370681B81D0 for <ietf@ietf.org>; Tue, 11 Jun 2013 04:02:28 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2470D19005D; Tue, 11 Jun 2013 04:02:28 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 11 Jun 2013 04:02:28 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Randy Bush <randy@psg.com>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkwmhkAgAAQ4YCAACR7gA==
Date: Tue, 11 Jun 2013 11:02:28 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751CFFE6@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <30E650BD-F609-4B44-86E1-BA25CE903779@mnot.net> <m261xlowra.wl%randy@psg.com>
In-Reply-To: <m261xlowra.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9ED166F42B60C24B93333D9E999E29F2@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Mark Nottingham <mnot@mnot.net>, Pete Resnick <presnick@qti.qualcomm.com>, "<ietf@ietf.org>" <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: Tue, 11 Jun 2013 11:02:43 -0000

On Jun 11, 2013, at 4:51 AM, Randy Bush <randy@psg.com> wrote:
> so now i am expected to do a write-up of why i show simple support of a
> document i have read?  may i use carbon paper for the triplicate, or
> will a copier suffice?  surely we can find a way to waste more time and
> effort.

If you say "I support publication," in IETF last call without saying why, y=
ou are arguably wasting other peoples' time.   If you say "I read the docum=
ent and I think it's technically solid; furthermore, it addresses a real ne=
ed," then you've spent a solid 5 seconds more typing, and we have something=
 to go on.   Keep your carbon paper in the drawer where it belongs.


From l.wood@surrey.ac.uk  Tue Jun 11 04:18:30 2013
Return-Path: <l.wood@surrey.ac.uk>
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 9041B21F957B for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:18:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.998
X-Spam-Level: 
X-Spam-Status: No, score=-2.998 tagged_above=-999 required=5 tests=[AWL=0.600,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=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 G39v9sG9hrUB for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:18:25 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.173]) by ietfa.amsl.com (Postfix) with ESMTP id 837CD21F86D5 for <ietf@ietf.org>; Tue, 11 Jun 2013 04:18:24 -0700 (PDT)
Received: from [195.245.230.131:9739] by server-13.bemta-3.messagelabs.com id 7D/B2-19597-C7707B15; Tue, 11 Jun 2013 11:18:20 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-78.messagelabs.com!1370949500!28395774!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 4234 invoked from network); 11 Jun 2013 11:18:20 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-10.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 11 Jun 2013 11:18:20 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Tue, 11 Jun 2013 12:18:20 +0100
From: <l.wood@surrey.ac.uk>
To: <randy@psg.com>, <mnot@mnot.net>
Date: Tue, 11 Jun 2013 12:17:34 +0100
Subject: RE: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: Ac5mgQBknUiIeWmcQiySwNHeaul0PAAFEWiu
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EA9@EXMB01CMS.surrey.ac.uk>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <30E650BD-F609-4B44-86E1-BA25CE903779@mnot.net>, <m261xlowra.wl%randy@psg.com>
In-Reply-To: <m261xlowra.wl%randy@psg.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: presnick@qti.qualcomm.com, 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: Tue, 11 Jun 2013 11:18:30 -0000

We have to know, not that you have read the document, but that you have -un=
derstood- it.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Randy Bush=
 [randy@psg.com]
Sent: 11 June 2013 09:51
To: Mark Nottingham
Cc: Pete Resnick; ietf@ietf.org
Subject: Re: Content-free Last Call comments

so now i am expected to do a write-up of why i show simple support of a
document i have read?  may i use carbon paper for the triplicate, or
will a copier suffice?  surely we can find a way to waste more time and
effort.

randy

From l.wood@surrey.ac.uk  Tue Jun 11 04:25:48 2013
Return-Path: <l.wood@surrey.ac.uk>
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 67F8221F9399 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.084
X-Spam-Level: 
X-Spam-Status: No, score=-3.084 tagged_above=-999 required=5 tests=[AWL=0.514,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=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 Rf0n4BvGmp4f for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:25:38 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.175]) by ietfa.amsl.com (Postfix) with ESMTP id 84D3A21F9695 for <ietf@ietf.org>; Tue, 11 Jun 2013 04:25:24 -0700 (PDT)
Received: from [195.245.230.131:63567] by server-15.bemta-3.messagelabs.com id F8/3A-32363-D1907B15; Tue, 11 Jun 2013 11:25:17 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-78.messagelabs.com!1370949917!26906844!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10996 invoked from network); 11 Jun 2013 11:25:17 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-4.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 11 Jun 2013 11:25:17 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Tue, 11 Jun 2013 12:25:16 +0100
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <presnick@qti.qualcomm.com>
Date: Tue, 11 Jun 2013 12:20:39 +0100
Subject: RE: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: Ac5mO+UtPAjQGpJXRp6CzHslUkSyVgAWc8x6
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EAA@EXMB01CMS.surrey.ac.uk>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>,<51B6710E.4040800@cs.tcd.ie>
In-Reply-To: <51B6710E.4040800@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 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: Tue, 11 Jun 2013 11:25:49 -0000

Ad-hominem arguments are not good arguments.

Peer review depends on what the peer says, not who the peer is - something =
any academic should know.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Stephen Fa=
rrell [stephen.farrell@cs.tcd.ie]
Sent: 11 June 2013 01:36
To: Pete Resnick
Cc: ietf@ietf.org
Subject: Re: Content-free Last Call comments

Hi Pete,

I think you err when you say this:

> A statement such as the above is almost entirely useless to me as an
> IESG member trying to determine consensus. It is content-free.

In fact, you do know Russ. If you did not, then the above would be
far closer to correct. But in reality you do know a lot more than
you claim below. With overwhelming probability, your choice #2
applies and I'm very surprised you don't also think that. If it
made a significant difference and I wasn't sure I'd ask Russ to
clarify. For me, I read Russ' mail and I concluded he meant #2.
And I'm confident in that conclusion.

So I'm really bemused when you say that you don't know how to
interpret Russ' mail.

Declaring that mail problematic also seems quite purist to me.
And insisting on purity seems to me worse than being slightly
but harmlessly ambiguous.

At the same time I agree we do not want a procession of +1 mails.
But then we won't get that for this draft. And if we did get that
for any draft, some IETF participants (probably incl. you and I)
would notice that and query it or object. So perhaps you're also
being a tad trigger-happy on jumping on this message.

Lastly, I think evaluating IETF LC messages only in terms
of how they help the IESG evaluate consensus or not is wrong.
Those messages are for and from the IETF community. So if
e.g. some renowned NFS person who's hardly known to the IESG
were to have sent an equivalent message, that might have been
quite good input that Martin or Spencer could have translated for
you. And that's just fine. And it would be fine if Russ' mail
had been directed not at the IESG but at some other part of the
community.

So bottom line, I think you're wrong, Russ' mail was not
content-free.

S.

PS: Yes, this is a not-very-good academic accusing an employee
of an industrial behemoth of excess purity. Go figure:-)

On 06/10/2013 09:37 PM, Pete Resnick wrote:
> Russ, our IAB chair and former IETF chair, just sent a message to the
> IETF list regarding a Last Call on draft-ietf-pkix-est. Here is the
> entire contents of his message, save quoting the whole Last Call request:
>
> On 6/10/13 1:45 PM, Russ Housley wrote:
>> I have read the document, I a support publication on the standards track=
.
>>
>> Russ
>
> A month ago, we had another very senior member of the community post
> just such a message (in that case directly to the IESG) in response to a
> different Last Call. I took that senior member of the community to task
> for it. But apparently Russ either disagrees with my complaint or didn't
> notice that discussion on the IESG list, so I think it's worth airing
> here in public:
>
> A statement such as the above is almost entirely useless to me as an
> IESG member trying to determine consensus. It is content-free.
>
> We don't vote in the IETF, so a statement of support without a reason is
> meaningless. We should not be encouraging folks to send such things, and
> having the IAB chair do so is encouraging bad behavior. Had I not known
> Russ and his particular expertise, I would have no reason to take it
> into consideration *at all*. We should not have to determine the
> reputation of the poster to determine the weight of the message. Even
> given my background knowledge of who Russ is, I cannot tell from that
> message which one of the following Russ is saying:
>
> - This document precisely describes a protocol of which I have been an
> implementer, and I was able to independently develop an interoperable
> implementation from the document.
> - This document is about a technology with which I have familiarity and
> I have reviewed the technical details. It's fine.
> - I've seen objection X to the document and I think the objection is
> incorrect for such-and-so reasons.
> - My company has a vested interest in this technology becoming a
> standard, and even though I know nothing about it, I support it becoming
> a standards track document.
> - My Aunt Gertrude is the document editor and she said that she needs
> statements of support, so here I am.
> - I have a running wager on when we're going to reach RFC 7000 and I
> want to increase my odds of winning.
>
> I take it I am supposed to presume from my friendship and knowledge of
> Russ that one of the first three is true and that the last three are
> not. (Well, maybe the last one might be true.) But if instead of from
> "Russ Housely", the message was from "Foo Bar", I would have absolutely
> no way to distinguish among the above.
>
> I think we should stop with these one-line statements of support. They
> don't add anything to the consensus call. I'm disappointed that Russ
> contributed to this pattern.
>
> Other opinions?
>
> pr
>

From abdussalambaryun@gmail.com  Tue Jun 11 04:28:25 2013
Return-Path: <abdussalambaryun@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 A549721F9399 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 EbGGiV6KE7SS for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:28:25 -0700 (PDT)
Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id CE73E21F96E1 for <ietf@ietf.org>; Tue, 11 Jun 2013 04:28:24 -0700 (PDT)
Received: by mail-pb0-f43.google.com with SMTP id md12so7312381pbc.2 for <ietf@ietf.org>; Tue, 11 Jun 2013 04:28:20 -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=ZDYzJZggWB705Dh2rgJRI0s0RMGqFKThAYh5DZmfFvM=; b=t5yBC2fuPB1FDq21olO+JyHH71J07vdwFdEAO5ay3rPzCNSZso4DkaLg9Iq/0I9wEj iz4xHxukngBK80BlUCD/945CfqVibuYGCLvtSuXk/+Q/qvT33QoFbyuBtlbybfAnS29R rGUFWQ+LPpXon2kxvYAjScvDEf6pKar/rLwochrqhCz14e6kUrSqpTF8qFy30kbVGJHQ urtmcSWSil0I9YTEwolnoH0+WJNh4GAjB+WxY2pKoW6iaN4yuDCqL+WgQHf25wyOGs9Z 06GkNFX8nR1/hIpITK8xTVqdJEXGLqm0aq7k3kB7RxvpgfRcl70gcdl6DDFciSK64gud MkRQ==
MIME-Version: 1.0
X-Received: by 10.66.248.228 with SMTP id yp4mr18227171pac.158.1370950100083;  Tue, 11 Jun 2013 04:28:20 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Tue, 11 Jun 2013 04:28:19 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751CFFE6@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <30E650BD-F609-4B44-86E1-BA25CE903779@mnot.net> <m261xlowra.wl%randy@psg.com> <8D23D4052ABE7A4490E77B1A012B6307751CFFE6@mbx-01.win.nominum.com>
Date: Tue, 11 Jun 2013 13:28:19 +0200
Message-ID: <CADnDZ8-rvJVzjXCmPUKkWyHHPwiPYgaqJntb7eLXGaY+ZC_E_w@mail.gmail.com>
Subject: Re: Content-free Last Call comments
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pete Resnick <presnick@qti.qualcomm.com>
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: Tue, 11 Jun 2013 11:28:25 -0000

A comment is a comment (important for discussing) which I want to see,
no matter if content-free or not, the origin requester (IETF Last
Call/WGLC) of such comments SHOULD specify which type of comment they
want if necessary. As long as it is a comment-on-discuss-lists any can
ask questions to the commentor to know the comment-reason if
necessary. IMO, we don't want no-comment, ignorance, or no answers if
requested, which will mean no discussions.

AB

From cabo@tzi.org  Tue Jun 11 04:33:35 2013
Return-Path: <cabo@tzi.org>
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 68C4821F96EA for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 9LWkrQvv6K4k for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:33:29 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 3B37321F9695 for <ietf@ietf.org>; Tue, 11 Jun 2013 04:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r5BBXPVD012845; Tue, 11 Jun 2013 13:33:26 +0200 (CEST)
Received: from [10.0.1.4] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 7A1CC33B5; Tue, 11 Jun 2013 13:33:25 +0200 (CEST)
Subject: Re: Content-free Last Call comments
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EA9@EXMB01CMS.surrey.ac.uk>
Date: Tue, 11 Jun 2013 13:33:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DF3084E-7722-46F6-98F1-1AA1857912A2@tzi.org>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <30E650BD-F609-4B44-86E1-BA25CE903779@mnot.net>, <m261xlowra.wl%randy@psg.com> <290E20B455C66743BE178C5C84F12408223F494EA9@EXMB01CMS.surrey.ac.uk>
To: <l.wood@surrey.ac.uk>
X-Mailer: Apple Mail (2.1508)
Cc: 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: Tue, 11 Jun 2013 11:33:35 -0000

On Jun 11, 2013, at 13:17, <l.wood@surrey.ac.uk> wrote:

> We have to know, not that you have read the document, but that you =
have -understood- it.

Process experiment:
end all Internet-Drafts with a multiple-choice test.

Gr=FC=DFe, Carsten


From dave@cridland.net  Tue Jun 11 04:36:51 2013
Return-Path: <dave@cridland.net>
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 277A921F949F for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.609
X-Spam-Level: 
X-Spam-Status: No, score=-1.609 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, URI_HEX=0.368]
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 IIuElsFgZ0ls for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:36:50 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD8521F9458 for <ietf@ietf.org>; Tue, 11 Jun 2013 04:36:49 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id ef5so11643418obb.1 for <ietf@ietf.org>; Tue, 11 Jun 2013 04:36:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XWkbIvu2JhtVi/XazrMjhFfEfYEw6ui8Wvx7VDHtWy8=; b=dIdP3u1phOCOHhqNrdDGILqWnT75O/NerJRH3NAAc6SeqpOv3up7obkX0uF2KffapE ZNxnwciKQCtW5/+5o/6GOhX+Pq56G1b5ya1JoVHCAD6RzVDk/S6oUaqEBzVi/ndRdr1Q jNmYlAT1U8oQPAMKySjsgtMx/c1b7erNcsmdc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=XWkbIvu2JhtVi/XazrMjhFfEfYEw6ui8Wvx7VDHtWy8=; b=kiPQNBNcNyGCqLoU8lj1XDc+bONah/wShDW8RzjQsRSDmI0Ntud1Vs43HvbxK5AEva y8WbaIGABb7QVY1uIoro7gSVj1g/QGMxmP95Cs6q3Jfy9g2Mpa/nNvDRV05EuPUU67yq znDrYAXN6IhrHIfymvr9++X6mG+Xb7iOrwMkQxQi40Ju9TVQFhWsBBiyzYzoWSXHjInt +V0dgJUjX8tdD4ogOEJZ3dhviZsp1eI2H5/BddP/590xjv1oXVeVMItusm0kWminZ/MI qeLbgFpJyBz7wTBxUC0nAwPcdPENaY9mArPVDZKI3IM06xTZISEEUc8JDXnXxB8AyHhV 4V/g==
MIME-Version: 1.0
X-Received: by 10.182.200.129 with SMTP id js1mr11642812obc.5.1370950609462; Tue, 11 Jun 2013 04:36:49 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Tue, 11 Jun 2013 04:36:49 -0700 (PDT)
In-Reply-To: <51B63905.2020807@qti.qualcomm.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>
Date: Tue, 11 Jun 2013 12:36:49 +0100
Message-ID: <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com>
Subject: Re: Content-free Last Call comments
From: Dave Cridland <dave@cridland.net>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=001a11c2369614fef404dedf5042
X-Gm-Message-State: ALoCoQmstyhhB1//Um+tYTTyvgBzUEzKQSlJLgUZmhOPXnhFUSxGQqnzQTOt0Z9uKcM6Kiz7h1nv
Cc: "ietf@ietf.org Discussion" <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: Tue, 11 Jun 2013 11:36:51 -0000

--001a11c2369614fef404dedf5042
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jun 10, 2013 at 9:37 PM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> A statement such as the above is almost entirely useless to me as an IESG
> member trying to determine consensus. It is content-free.
>

I think this is, in part, due to the question asked.

The IETF's Last Call announcement presumes much on the part of those
reading it. You're aiming to solicit something that's not asked for.

Compare and contrast with the XSF's Last Call announcements, in particular
the questionnaire at the end. Note that in this thread, almost all
respondents are actually filling it in, and further note that at least some
of those are experienced IETF participants, suggesting that even the jaded
IETF folk might join in.

http://jabber.996255.n3.nabble.com/LAST-CALL-XEP-0308-Last-Message-Correction-td14079.html

I'd suggest that putting together a set of five questions you're hoping to
have answered would be sensible and useful.

Perhaps:

1) Do you believe this document is needed?

2) Is the document ready for publication as-is?

3) Are you intending to, or have you already, implemented and/or deployed
this specification?

4) Does the document adequately explain the risks involved in implementing
and/or deploying this specification?

5) Is the document sufficiently clear to allow unambiguous understanding of
how to implement and/or deploy the specification?

Dave.

--001a11c2369614fef404dedf5042
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Jun 10, 2013 at 9:37 PM, Pete Resnick <span dir=3D=
"ltr">&lt;<a href=3D"mailto:presnick@qti.qualcomm.com" target=3D"_blank">pr=
esnick@qti.qualcomm.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"=
><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">A statement such as the above is almost entirely useless t=
o me as an IESG member trying to determine consensus. It is content-free.<b=
r>
</blockquote><div><br></div><div style>I think this is, in part, due to the=
 question asked.</div><div style><br></div><div style>The IETF&#39;s Last C=
all announcement presumes much on the part of those reading it. You&#39;re =
aiming to solicit something that&#39;s not asked for.</div>
<div style><br></div><div style>Compare and contrast with the XSF&#39;s Las=
t Call announcements, in particular the questionnaire at the end. Note that=
 in this thread, almost all respondents are actually filling it in, and fur=
ther note that at least some of those are experienced IETF participants, su=
ggesting that even the jaded IETF folk might join in.</div>
<div style><br></div><div style><a href=3D"http://jabber.996255.n3.nabble.c=
om/LAST-CALL-XEP-0308-Last-Message-Correction-td14079.html">http://jabber.9=
96255.n3.nabble.com/LAST-CALL-XEP-0308-Last-Message-Correction-td14079.html=
</a><br>
</div><div style><br></div><div style>I&#39;d suggest that putting together=
 a set of five questions you&#39;re hoping to have answered would be sensib=
le and useful.</div><div style><br></div><div style>Perhaps:</div><div styl=
e>
<br></div><div style>1) Do you believe this document is needed?</div><div s=
tyle><br></div><div style>2) Is the document ready for publication as-is?</=
div><div style><br></div><div style>3) Are you intending to, or have you al=
ready, implemented and/or deployed this specification?</div>
<div style><br></div><div style>4) Does the document adequately explain the=
 risks involved in implementing and/or deploying this specification?</div><=
div style><br></div><div style>5) Is the document sufficiently clear to all=
ow unambiguous understanding of how to implement and/or deploy the specific=
ation?</div>
<div style><br></div><div style>Dave.</div></div></div></div>

--001a11c2369614fef404dedf5042--

From mansaxel@besserwisser.org  Tue Jun 11 04:52:49 2013
Return-Path: <mansaxel@besserwisser.org>
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 A517E21F955A for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 99t8Sg3hcvKf for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:52:49 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id BBEB921F942B for <ietf@ietf.org>; Tue, 11 Jun 2013 04:52:48 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id A93E99E71; Tue, 11 Jun 2013 13:52:46 +0200 (CEST)
Date: Tue, 11 Jun 2013 13:52:46 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Content-free Last Call comments
Message-ID: <20130611115246.GG22738@besserwisser.org>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <6.2.5.6.2.20130610150249.0ccd9c90@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751CF72F@mbx-01.win.nominum.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lQSB8Tqijvu1+4Ba"
Content-Disposition: inline
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751CF72F@mbx-01.win.nominum.com>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: SM <sm@resistor.net>, Pete Resnick <presnick@qti.qualcomm.com>, "<ietf@ietf.org>" <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: Tue, 11 Jun 2013 11:52:49 -0000

--lQSB8Tqijvu1+4Ba
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: Content-free Last Call comments Date: Mon, Jun 10, 2013 at 11:=
46:29PM +0000 Quoting Ted Lemon (Ted.Lemon@nominum.com):
=20
> Determining consensus in an IETF last call is a bit more complicated
> than that.   It's not a working group last call.   If someone objects to
> publication during IETF last call, and their objection has already been
> discussed and addressed in the working group, the objection in IETF last
> call doesn't break that consensus.
=20
So, if wg discussion has been ordered mute by the wg chairs because
some wg participants believe the group-think consensus is good enough,
can those objections again be raised in IETF LC or are they set in stone?

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
NATHAN ... your PARENTS were in a CARCRASH!!  They're VOIDED -- They
COLLAPSED They had no CHAINSAWS ... They had no MONEY MACHINES ... They
did PILLS in SKIMPY GRASS SKIRTS ... Nathan, I EMULATED them ... but
they were OFF-KEY ...

--lQSB8Tqijvu1+4Ba
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlG3D44ACgkQ02/pMZDM1cUaigCfUpk54zgrbeTWFBUAV53k8HMB
+LAAnA8ojNQM0vw0Quer83o5SPi8OEoM
=Aysl
-----END PGP SIGNATURE-----

--lQSB8Tqijvu1+4Ba--

From mansaxel@besserwisser.org  Tue Jun 11 04:56:01 2013
Return-Path: <mansaxel@besserwisser.org>
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 A6EE021F919D for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 IA+IRhOMQD0k for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:56:00 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id DC39F21F8EFE for <ietf@ietf.org>; Tue, 11 Jun 2013 04:55:57 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 5EA759E71; Tue, 11 Jun 2013 13:55:56 +0200 (CEST)
Date: Tue, 11 Jun 2013 13:55:56 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Content-free Last Call comments
Message-ID: <20130611115556.GH22738@besserwisser.org>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <6.2.5.6.2.20130610150249.0ccd9c90@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751CF72F@mbx-01.win.nominum.com> <20130611115246.GG22738@besserwisser.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HuscSE0D68UGttcd"
Content-Disposition: inline
In-Reply-To: <20130611115246.GG22738@besserwisser.org>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: SM <sm@resistor.net>, Pete Resnick <presnick@qti.qualcomm.com>, "<ietf@ietf.org>" <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: Tue, 11 Jun 2013 11:56:01 -0000

--HuscSE0D68UGttcd
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: Content-free Last Call comments Date: Tue, Jun 11, 2013 at 01:=
52:46PM +0200 Quoting M=C3=A5ns Nilsson (mansaxel@besserwisser.org):

> So, if wg discussion has been ordered mute by the wg chairs because
> some wg participants believe the group-think consensus is good enough,
> can those objections again be raised in IETF LC or are they set in stone?

s/they/the WG decisions/

My apologies.=20
--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Once, there was NO fun ... This was before MENU planning, FASHION
statements or NAUTILUS equipment ... Then, in 1985 ... FUN was
completely encoded in this tiny MICROCHIP ... It contain 14,768 vaguely
amusing SIT-COM pilots!!  We had to wait FOUR BILLION years but we
finally got JERRY LEWIS, MTV and a large selection of creme-filled
snack cakes!

--HuscSE0D68UGttcd
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlG3EEwACgkQ02/pMZDM1cVRFACgp+wKHZETE9mUKbyCUEMCQAmX
m5UAoKG1Crb4KfwjPkEggu0NaYt4VLgm
=KN1b
-----END PGP SIGNATURE-----

--HuscSE0D68UGttcd--

From dhc@dcrocker.net  Tue Jun 11 04:58:37 2013
Return-Path: <dhc@dcrocker.net>
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 B32BE21F9458 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 MtaU1m+tbUPY for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 04:58:30 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id AE90B21F957B for <ietf@ietf.org>; Tue, 11 Jun 2013 04:58:30 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5BBwQiB011238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Tue, 11 Jun 2013 04:58:29 -0700
Message-ID: <51B710DD.5020805@dcrocker.net>
Date: Tue, 11 Jun 2013 06:58:21 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com>
In-Reply-To: <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 11 Jun 2013 04:58:29 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Tue, 11 Jun 2013 11:58:38 -0000

On 6/11/2013 6:36 AM, Dave Cridland wrote:
> I think this is, in part, due to the question asked.
>
> The IETF's Last Call announcement presumes much on the part of those
> reading it. You're aiming to solicit something that's not asked for.
>
> Compare and contrast with the XSF's Last Call announcements, in

Re-formulating the LC text sounds like an excellent idea, to call for 
more substantive comments.


> I'd suggest that putting together a set of five questions you're hoping
> to have answered would be sensible and useful.
>
> Perhaps:


If we want the statements of support to be meaningful, they need to have 
the creator of the statement do some real work -- more than mechanically 
checking boxes -- demonstrating the 'understanding' that Lloyd suggests. 
  Multiple guess questions don't demonstrate understanding; worse, they 
are too easily plagiarized as part of a campaign.

One of the unfortunate realities in the current IETF is periodically 
seeing patterns of support that have more to do with politicking for a 
draft than for commenting on a critical review of it.  There is no 
perfect protection against this, but asking each statement of support to 
demonstrate the commenter's own understanding will help.

We also sometimes have drafts that have had little working group 
activity.  This is independent of the quality of the work, but it means 
that there's little sense of community need or interest.  It's not 
supposed to happen, but it's become more common in the current IETF. 
Again, there's no perfect protection against that, but seeing public 
activity during IETF LC that demonstrates enough community interest to 
do the minimal work of offering a capsule commentary on the draft will help.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From Ted.Lemon@nominum.com  Tue Jun 11 05:12:13 2013
Return-Path: <Ted.Lemon@nominum.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 1A9D221F8EAD for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 05:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.48
X-Spam-Level: 
X-Spam-Status: No, score=-106.48 tagged_above=-999 required=5 tests=[AWL=-0.181, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 GwuFpY14r7yP for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 05:12:06 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id 3D56821F8D10 for <ietf@ietf.org>; Tue, 11 Jun 2013 05:12:06 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUbcUEx/u6Qov7k8ahlFxrCyUqLNbasZy@postini.com; Tue, 11 Jun 2013 05:12:06 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B66461B81E0 for <ietf@ietf.org>; Tue, 11 Jun 2013 05:12:03 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A8C3819005D; Tue, 11 Jun 2013 05:12:03 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 11 Jun 2013 05:12:03 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: =?Windows-1252?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkwC7SAgAAG4wCAAMrtAIAABWIA
Date: Tue, 11 Jun 2013 12:12:02 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751D0466@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <6.2.5.6.2.20130610150249.0ccd9c90@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751CF72F@mbx-01.win.nominum.com> <20130611115246.GG22738@besserwisser.org>
In-Reply-To: <20130611115246.GG22738@besserwisser.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <A6202CE19248FB4EA17CD70A661EE36E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: SM <sm@resistor.net>, Pete Resnick <presnick@qti.qualcomm.com>, "<ietf@ietf.org>" <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: Tue, 11 Jun 2013 12:12:13 -0000

On Jun 11, 2013, at 7:52 AM, M=E5ns Nilsson <mansaxel@besserwisser.org> wro=
te:
> So, if wg discussion has been ordered mute by the wg chairs because
> some wg participants believe the group-think consensus is good enough,
> can those objections again be raised in IETF LC or are they set in stone?

You can always challenge the WG chair's finding, but you don't need to hass=
le the whole IETF to do that=97just talk to the responsible AD for the work=
ing group, or to the IESG as a whole if the responsible AD fails you.   Tha=
t's what the appeals process is supposed to be for.

You can of course raise the point on the IETF mailing list, and that is lik=
ely to result in the responsible AD considering the question of whether the=
 WG chairs made the right call=97I certainly would do so if someone raised =
such a point on a document for which I was responsible AD.   But if the res=
ponsible AD decides that the chair made the right call, the objection you r=
aise in IETF last call doesn't count against the working group consensus.


From dave@cridland.net  Tue Jun 11 05:25:24 2013
Return-Path: <dave@cridland.net>
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 9641421F9408 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 05:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.793
X-Spam-Level: 
X-Spam-Status: No, score=-1.793 tagged_above=-999 required=5 tests=[AWL=0.184,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 ZvOLadGJnqT0 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 05:25:11 -0700 (PDT)
Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 9A3AD21F8F78 for <ietf@ietf.org>; Tue, 11 Jun 2013 05:25:11 -0700 (PDT)
Received: by mail-oa0-f54.google.com with SMTP id o17so7404103oag.27 for <ietf@ietf.org>; Tue, 11 Jun 2013 05:25:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=47gqHe++emK93HIl9XoeKFw7omDonHBjeyCQRLW0rFY=; b=gRPMhQIaH7xbZkmsV0RBcv863XLbmvzW5fnyW0bGGhlOzJtjwhGFKvZlqxnP3/ABTK wkJClvFW95ZQgioeva/GuJRhu+pg7ksFYyv2imqjuYW1BGCiWStkYZ48RVqxWM/8ujsb dW7Rfq/qU9AitCL2kvE+mptnAGKkVAidtVGvw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=47gqHe++emK93HIl9XoeKFw7omDonHBjeyCQRLW0rFY=; b=m3R92O/4GlbH7uTB73KN7orZywn7JRXxDwy1NaNQgZ+KsqN5X9ifXeRdO3nA7VlP4B m1Sc5eZojCfqNU1hRPsFo3y3Bk6AjKE+oo8J/ZFe6qAja0r8oBU+6skQ+vPUgzz8BfG8 Us09UBouEn0cxjo7EVzAgcj57o1cAVngnZc40Hb9mG81UKjWbaZk4vun+s6KDy83sauy Ql552mNKC/Wpx8dXFVG3wnCOwJhQHMK26EsHS5OGWHACS72p0osAPK+2T6ILsglrzCCJ zJNx6SkV+2X+csMoRClS4o01t0K3YpGbwT8M4lVwzkbMsJYSE1k7p+ylJXqZEO4Yonzg zeYA==
MIME-Version: 1.0
X-Received: by 10.182.200.129 with SMTP id js1mr11769631obc.5.1370953511090; Tue, 11 Jun 2013 05:25:11 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Tue, 11 Jun 2013 05:25:11 -0700 (PDT)
In-Reply-To: <51B710DD.5020805@dcrocker.net>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com> <51B710DD.5020805@dcrocker.net>
Date: Tue, 11 Jun 2013 13:25:11 +0100
Message-ID: <CAKHUCzw1c4WMOqCCrdhus69FoQL0kexHJ-q_BMB7UaDHMkFVAw@mail.gmail.com>
Subject: Re: Content-free Last Call comments
From: Dave Cridland <dave@cridland.net>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11c23696084e8704dedffd9b
X-Gm-Message-State: ALoCoQm12A/Fj6GB3mSMX5ggWl+UTiGd0XetDynBm48z34OCjJLM2/Uv8BNgiA1USAEBgoMGGQNx
Cc: "ietf@ietf.org Discussion" <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: Tue, 11 Jun 2013 12:25:25 -0000

--001a11c23696084e8704dedffd9b
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 11, 2013 at 12:58 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> If we want the statements of support to be meaningful, they need to have
> the creator of the statement do some real work -- more than mechanically
> checking boxes -- demonstrating the 'understanding' that Lloyd suggests.
>  Multiple guess questions don't demonstrate understanding; worse, they are
> too easily plagiarized as part of a campaign.
>
>
We want understanding, of course, but I think requiring Russ to demonstrate
that by writing a paragraph or six on the finer points of the proposal
would be daft.


> One of the unfortunate realities in the current IETF is periodically
> seeing patterns of support that have more to do with politicking for a
> draft than for commenting on a critical review of it.  There is no perfect
> protection against this, but asking each statement of support to
> demonstrate the commenter's own understanding will help.
>
>
If the politicking is from multiple organizations who all want to implement
and deploy, then I'm all in favour...

If there's only one implementer willing to say as much, then even quite a
slew of deployment wannabees would have me concerned for the viability of
the protocol.

I'd note that the XSF's questions are only concerned with implementation
rather than deployment - maybe that helps, I'm not sure either way.

We also sometimes have drafts that have had little working group activity.
>  This is independent of the quality of the work, but it means that there's
> little sense of community need or interest.  It's not supposed to happen,
> but it's become more common in the current IETF. Again, there's no perfect
> protection against that, but seeing public activity during IETF LC that
> demonstrates enough community interest to do the minimal work of offering a
> capsule commentary on the draft will help.


Perhaps having a shepherd-style write up included in the last call
announcement? (Or available via a URL there).

Dave.

--001a11c23696084e8704dedffd9b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jun 11, 2013 at 12:58 PM, Dave Crocker <span dir=3D"ltr">&l=
t;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a=
>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><span style=3D"color:rgb(3=
4,34,34)">If we want the statements of support to be meaningful, they need =
to have the creator of the statement do some real work -- more than mechani=
cally checking boxes -- demonstrating the &#39;understanding&#39; that Lloy=
d suggests. =A0Multiple guess questions don&#39;t demonstrate understanding=
; worse, they are too easily plagiarized as part of a campaign.</span><br>
</div>
<br></blockquote><div><br></div><div style>We want understanding, of course=
, but I think requiring Russ to demonstrate that by writing a paragraph or =
six on the finer points of the proposal would be daft.</div><div style>
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
One of the unfortunate realities in the current IETF is periodically seeing=
 patterns of support that have more to do with politicking for a draft than=
 for commenting on a critical review of it. =A0There is no perfect protecti=
on against this, but asking each statement of support to demonstrate the co=
mmenter&#39;s own understanding will help.<br>

<br></blockquote><div><br></div><div style>If the politicking is from multi=
ple organizations who all want to implement and deploy, then I&#39;m all in=
 favour...</div><div style><br></div><div style>If there&#39;s only one imp=
lementer willing to say as much, then even quite a slew of deployment wanna=
bees would have me concerned for the viability of the protocol.</div>
<div style><br></div><div style>I&#39;d note that the XSF&#39;s questions a=
re only concerned with implementation rather than deployment - maybe that h=
elps, I&#39;m not sure either way.</div><div><br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">

We also sometimes have drafts that have had little working group activity. =
=A0This is independent of the quality of the work, but it means that there&=
#39;s little sense of community need or interest. =A0It&#39;s not supposed =
to happen, but it&#39;s become more common in the current IETF. Again, ther=
e&#39;s no perfect protection against that, but seeing public activity duri=
ng IETF LC that demonstrates enough community interest to do the minimal wo=
rk of offering a capsule commentary on the draft will help.</blockquote>
<div><br></div><div style>Perhaps having a shepherd-style write up included=
 in the last call announcement? (Or available via a URL there).</div><div s=
tyle><br></div><div style>Dave.</div></div></div></div>

--001a11c23696084e8704dedffd9b--

From dhc@dcrocker.net  Tue Jun 11 05:45:30 2013
Return-Path: <dhc@dcrocker.net>
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 C9E9121F874E for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 05:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 WVTjTawfmD4Y for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 05:45:25 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BC6A421F8613 for <ietf@ietf.org>; Tue, 11 Jun 2013 05:45:25 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5BCjKXj012069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Jun 2013 05:45:23 -0700
Message-ID: <51B71BDB.2000204@dcrocker.net>
Date: Tue, 11 Jun 2013 05:45:15 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com> <51B710DD.5020805@dcrocker.net> <CAKHUCzw1c4WMOqCCrdhus69FoQL0kexHJ-q_BMB7UaDHMkFVAw@mail.gmail.com>
In-Reply-To: <CAKHUCzw1c4WMOqCCrdhus69FoQL0kexHJ-q_BMB7UaDHMkFVAw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 11 Jun 2013 05:45:23 -0700 (PDT)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Tue, 11 Jun 2013 12:45:30 -0000

On 6/11/2013 5:25 AM, Dave Cridland wrote:
> We want understanding, of course, but I think requiring Russ to
> demonstrate that by writing a paragraph or six on the finer points of
> the proposal would be daft.

That's the problem with special-case exceptions, such as requiring less 
work by an august personage.  It reduces to a cult of personality and it 
doesn't scale.  For an organizational culture of the type the IETF 
expresses, that doesn't fit.  The opinions of people IETF management 
positions are not supposed to automatically have more weight in 
determining the specifics of our specifications; they are supposed to 
make their case, just like everyone else.

We try to distinguish between comment when wearing a formal IETF hat 
versus without a hat.  So it's not the IETF Chair making the comment, 
it's "merely" a well-known personage.

It's easy to give special rights to such folk, such as not requiring 
them to offer the substance behind their statement, but it actually has 
a pretty insidious effect.  It's gets us used to pro-forma postings; it 
gets us relying on a few folk to sway things; it gets us to count rather 
than think.


> If the politicking is from multiple organizations who all want to
> implement and deploy, then I'm all in favour...

Pete Resnick has been working on a careful formulation of what the IETF 
means when it talks about 'rough consensus'.  My own interpretation of 
what he's developing -- and I want to stress this is me speaking, not me 
speaking for Pete -- is that consensus is a combination of both numbers 
and substance.  The mere fact that "almost everyone" is in favor of 
something can't be enough.  What is also required is that the arguments 
of objectors must have inadequately persuasive substance.  One voice 
with a really solid concern, which withstands independent review, needs 
to be able to upset an overwhelming agreement.

So no, the fact that the politicking is from multiple organizations 
needs to be insufficient.



>     We also sometimes have drafts that have had little working group
>     activity.
...
> Perhaps having a shepherd-style write up included in the last call
> announcement? (Or available via a URL there).

Perhaps something like that, yeah.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From dave@cridland.net  Tue Jun 11 06:27:02 2013
Return-Path: <dave@cridland.net>
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 9004C21F8F24 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.885
X-Spam-Level: 
X-Spam-Status: No, score=-1.885 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 pfZX+71iKOR9 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:27:01 -0700 (PDT)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 7EBE621F8EFE for <ietf@ietf.org>; Tue, 11 Jun 2013 06:27:01 -0700 (PDT)
Received: by mail-ob0-f177.google.com with SMTP id ta17so11512583obb.22 for <ietf@ietf.org>; Tue, 11 Jun 2013 06:27:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PBqEs4fy2XvehXgP94rtB8uUM0oorEIrLAmfik0qOiQ=; b=fABe3/smRXXVihuU2QCEKcjLP5Vlw9800yL4Ha45daDqkVKHu+sToViMm0QW1pxCao YcMTru9IhsZmsVAhsOb8dWQmMK8iDkm3yi5wqleEGluRbOUQrB5XoXBMr5xb4g1cf/v4 pwLw2NzrLLfTrMbMCg5LRzYJL1pvqHub+9h+U=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=PBqEs4fy2XvehXgP94rtB8uUM0oorEIrLAmfik0qOiQ=; b=B3+Xsmzm2oopYOfQKDNBlQxMtg3pqYvxVxo7XcS5K26Ub8pqFA92fuusVL5KHknPzS O5zN/bweG6Q/jtSO4g4RgT4LHyjJh25waZa+cdfmGyhsipFXGdoyfNzmLSfPaTHCxKEx sQnEeIbtamFZZLSUfrBO6Sue4j5J7auUeUq+XgBGbD5a4CmUGcrc+j0zubAsRQMsh6Lc 9ny1xL9yhd9uWVopRRULcv7VMp5a8kgsgTVjYUSs7QSgBLjgyFgO5F8Ybz3CvA6yLWSl Sn2b/HyWTDrJIWJVcIDYBs6r5V2C6+cCyiNPa16Qu3ylTq4jzAwiZl1kTs6QWvkfHnBw dvVA==
MIME-Version: 1.0
X-Received: by 10.182.24.131 with SMTP id u3mr12066655obf.29.1370957221032; Tue, 11 Jun 2013 06:27:01 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Tue, 11 Jun 2013 06:27:00 -0700 (PDT)
In-Reply-To: <51B71BDB.2000204@dcrocker.net>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com> <51B710DD.5020805@dcrocker.net> <CAKHUCzw1c4WMOqCCrdhus69FoQL0kexHJ-q_BMB7UaDHMkFVAw@mail.gmail.com> <51B71BDB.2000204@dcrocker.net>
Date: Tue, 11 Jun 2013 14:27:00 +0100
Message-ID: <CAKHUCzw3PxaakdckiJyJhXf2FA2O7U0Qa7UBJCTaT0zRJ13tJQ@mail.gmail.com>
Subject: Re: Content-free Last Call comments
From: Dave Cridland <dave@cridland.net>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11c3025229884704dee0da3e
X-Gm-Message-State: ALoCoQlXGe4YRH023qCio32LfFOr+XzEhCHc7V4TsvejrYZXGvUMyMhYxIIVyA5O+pyv1bPy5/Ku
Cc: "ietf@ietf.org Discussion" <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: Tue, 11 Jun 2013 13:27:02 -0000

--001a11c3025229884704dee0da3e
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 11, 2013 at 1:45 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 6/11/2013 5:25 AM, Dave Cridland wrote:
>
>> We want understanding, of course, but I think requiring Russ to
>> demonstrate that by writing a paragraph or six on the finer points of
>> the proposal would be daft.
>>
>
> That's the problem with special-case exceptions, such as requiring less
> work by an august personage.  It reduces to a cult of personality and it
> doesn't scale.  For an organizational culture of the type the IETF
> expresses, that doesn't fit.  The opinions of people IETF management
> positions are not supposed to automatically have more weight in determining
> the specifics of our specifications; they are supposed to make their case,
> just like everyone else.
>
> We try to distinguish between comment when wearing a formal IETF hat
> versus without a hat.  So it's not the IETF Chair making the comment, it's
> "merely" a well-known personage.
>
> It's easy to give special rights to such folk, such as not requiring them
> to offer the substance behind their statement, but it actually has a pretty
> insidious effect.  It's gets us used to pro-forma postings; it gets us
> relying on a few folk to sway things; it gets us to count rather than think.
>
>
Ah, sorry, that's not what I meant - I included Russ's name purely because
he was the original exemplar, not because he's special in any particular
way.

I meant that requiring anyone to demonstrate understand of the draft by
jumping through hoops would, ipso facto, require them to jump through hoops.


>
>
>  If the politicking is from multiple organizations who all want to
>> implement and deploy, then I'm all in favour...
>>
>
> Pete Resnick has been working on a careful formulation of what the IETF
> means when it talks about 'rough consensus'.  My own interpretation of what
> he's developing -- and I want to stress this is me speaking, not me
> speaking for Pete -- is that consensus is a combination of both numbers and
> substance.  The mere fact that "almost everyone" is in favor of something
> can't be enough.  What is also required is that the arguments of objectors
> must have inadequately persuasive substance.  One voice with a really solid
> concern, which withstands independent review, needs to be able to upset an
> overwhelming agreement.
>
> So no, the fact that the politicking is from multiple organizations needs
> to be insufficient.
>
>
Again, I think you're misunderstanding me - I meant (somewhat facetiously)
I'm in favour of the politicking, not that I think that it should carry the
day automatically. If there are unanswered objections, that should indeed
count against. More generally, in the case of the XSF's small set of
questions, if people answer the last call with one-word answers to those
and nothing further, this gives that community sufficient information to
gauge whether to advance a proposal along the standards track there - in
other words, given a fairly minimal bar, any engagement meeting that bar is
valuable.

That bar has to be high enough to carry more than the single bit of
information Russ's note carried on its own, though, but it also needs to be
low enough that it won't prove a barrier to response.

I think the XSF's questions are close to the right level (I think the XSF
could, if it wanted, tweak these and improve them after this number of
years); I don't think it would be very hard to find some similarly
reasonable start point for the IETF.

Dave.

--001a11c3025229884704dee0da3e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jun 11, 2013 at 1:45 PM, Dave Crocker <span dir=3D"ltr">&lt=
;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 6/11/2013 5:25 AM, Dave=
 Cridland wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
We want understanding, of course, but I think requiring Russ to<br>
demonstrate that by writing a paragraph or six on the finer points of<br>
the proposal would be daft.<br>
</blockquote>
<br></div>
That&#39;s the problem with special-case exceptions, such as requiring less=
 work by an august personage. =A0It reduces to a cult of personality and it=
 doesn&#39;t scale. =A0For an organizational culture of the type the IETF e=
xpresses, that doesn&#39;t fit. =A0The opinions of people IETF management p=
ositions are not supposed to automatically have more weight in determining =
the specifics of our specifications; they are supposed to make their case, =
just like everyone else.<br>

<br>
We try to distinguish between comment when wearing a formal IETF hat versus=
 without a hat. =A0So it&#39;s not the IETF Chair making the comment, it&#3=
9;s &quot;merely&quot; a well-known personage.<br>
<br>
It&#39;s easy to give special rights to such folk, such as not requiring th=
em to offer the substance behind their statement, but it actually has a pre=
tty insidious effect. =A0It&#39;s gets us used to pro-forma postings; it ge=
ts us relying on a few folk to sway things; it gets us to count rather than=
 think.<div class=3D"im">
<br></div></blockquote><div><br></div><div style>Ah, sorry, that&#39;s not =
what I meant - I included Russ&#39;s name purely because he was the origina=
l exemplar, not because he&#39;s special in any particular way.</div><div s=
tyle>
<br></div><div style>I meant that requiring anyone to demonstrate understan=
d of the draft by jumping through hoops would, ipso facto, require them to =
jump through hoops.</div><div style>=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<div class=3D"im">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
If the politicking is from multiple organizations who all want to<br>
implement and deploy, then I&#39;m all in favour...<br>
</blockquote>
<br></div>
Pete Resnick has been working on a careful formulation of what the IETF mea=
ns when it talks about &#39;rough consensus&#39;. =A0My own interpretation =
of what he&#39;s developing -- and I want to stress this is me speaking, no=
t me speaking for Pete -- is that consensus is a combination of both number=
s and substance. =A0The mere fact that &quot;almost everyone&quot; is in fa=
vor of something can&#39;t be enough. =A0What is also required is that the =
arguments of objectors must have inadequately persuasive substance. =A0One =
voice with a really solid concern, which withstands independent review, nee=
ds to be able to upset an overwhelming agreement.<br>

<br>
So no, the fact that the politicking is from multiple organizations needs t=
o be insufficient.<div class=3D"im"><br></div></blockquote><div><br></div><=
div style>Again, I think you&#39;re misunderstanding me - I meant (somewhat=
 facetiously) I&#39;m in favour of the politicking, not that I think that i=
t should carry the day automatically. If there are unanswered objections, t=
hat should indeed count against. More generally, in the case of the XSF&#39=
;s small set of questions, if people answer the last call with one-word ans=
wers to those and nothing further, this gives that community sufficient inf=
ormation to gauge whether to advance a proposal along the standards track t=
here - in other words, given a fairly minimal bar, any engagement meeting t=
hat bar is valuable.</div>
<div><br></div><div style>That bar has to be high enough to carry more than=
 the single bit of information Russ&#39;s note carried on its own, though, =
but it also needs to be low enough that it won&#39;t prove a barrier to res=
ponse.</div>
<div style><br></div><div style>I think the XSF&#39;s questions are close t=
o the right level (I think the XSF could, if it wanted, tweak these and imp=
rove them after this number of years); I don&#39;t think it would be very h=
ard to find some similarly reasonable start point for the IETF.</div>
<div style><br></div><div style>Dave.</div></div></div></div>

--001a11c3025229884704dee0da3e--

From turners@ieca.com  Tue Jun 11 06:31:43 2013
Return-Path: <turners@ieca.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 8350321F9701 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.237
X-Spam-Level: 
X-Spam-Status: No, score=-102.237 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 rh3Zl2OGsQZz for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:31:37 -0700 (PDT)
Received: from gateway13.websitewelcome.com (gateway13.websitewelcome.com [67.18.68.4]) by ietfa.amsl.com (Postfix) with ESMTP id 4D18521F9005 for <ietf@ietf.org>; Tue, 11 Jun 2013 06:31:37 -0700 (PDT)
Received: by gateway13.websitewelcome.com (Postfix, from userid 5007) id 5AFFA674BB65F; Tue, 11 Jun 2013 08:31:29 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway13.websitewelcome.com (Postfix) with ESMTP id 4AB2E674BB626 for <ietf@ietf.org>; Tue, 11 Jun 2013 08:31:29 -0500 (CDT)
Received: from [173.73.135.101] (port=49159 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1UmOfg-0005eu-JB; Tue, 11 Jun 2013 08:31:36 -0500
Message-ID: <51B726B7.5070205@ieca.com>
Date: Tue, 11 Jun 2013 09:31:35 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <6.2.5.6.2.20130610150249.0ccd9c90@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751CF72F@mbx-01.win.nominum.com> <20130611115246.GG22738@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B6307751D0466@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751D0466@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (thunderfish.local) [173.73.135.101]:49159
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 4
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: SM <sm@resistor.net>, Pete Resnick <presnick@qti.qualcomm.com>, =?windows-1252?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>, "<ietf@ietf.org>" <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: Tue, 11 Jun 2013 13:31:43 -0000

On 6/11/13 8:12 AM, Ted Lemon wrote:
> On Jun 11, 2013, at 7:52 AM, Måns Nilsson <mansaxel@besserwisser.org> wrote:
>> So, if wg discussion has been ordered mute by the wg chairs because
>> some wg participants believe the group-think consensus is good enough,
>> can those objections again be raised in IETF LC or are they set in stone?
>
> You can always challenge the WG chair's finding, but you don't need to hassle the whole IETF to do that—just talk to the responsible AD for the working group, or to the IESG as a whole if the responsible AD fails you.   That's what the appeals process is supposed to be for.
>
> You can of course raise the point on the IETF mailing list, and that is likely to result in the responsible AD considering the question of whether the WG chairs made the right call—I certainly would do so if someone raised such a point on a document for which I was responsible AD.   But if the responsible AD decides that the chair made the right call, the objection you raise in IETF last call doesn't count against the working group consensus.

Engaging during IETF LC on a point made during WGLC or earlier that 
wasn't adopted is a-okay in my book.  I think of it as raising 
awareness.  I mean maybe the authors and WG chair didn't get it right. 
But, then what Ted said kicks in.

spt

From randy@psg.com  Tue Jun 11 06:41:36 2013
Return-Path: <randy@psg.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 CD6F421F999A for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:41:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599]
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 6mFqte3FOfdd for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:41:36 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5778721F998B for <ietf@ietf.org>; Tue, 11 Jun 2013 06:41:36 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UmOpH-000Cxw-Ix; Tue, 11 Jun 2013 13:41:32 +0000
Date: Tue, 11 Jun 2013 15:41:29 +0200
Message-ID: <m2ehc8ojcm.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Dave Crocker <dhc@dcrocker.net>
Subject: Re: Content-free Last Call comments
In-Reply-To: <51B710DD.5020805@dcrocker.net>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com> <51B710DD.5020805@dcrocker.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <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: Tue, 11 Jun 2013 13:41:37 -0000

> Re-formulating the LC text sounds like an excellent idea, to call for 
> more substantive comments.

perhaps we should go to the source of the problem and require a phd
dissertation and defense from draft authors.

how much process chaos can we create?

randy

From Ted.Lemon@nominum.com  Tue Jun 11 06:43:33 2013
Return-Path: <Ted.Lemon@nominum.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 6FFFA21F998D for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.623
X-Spam-Level: 
X-Spam-Status: No, score=-106.623 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 u40T-Ue2yElk for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:43:26 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 6BBF721F99B4 for <ietf@ietf.org>; Tue, 11 Jun 2013 06:43:26 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUbcpfECHdwqL6oGRild7pgd+TnZUrVfk@postini.com; Tue, 11 Jun 2013 06:43:26 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 51C6A1B801A for <ietf@ietf.org>; Tue, 11 Jun 2013 06:43:24 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 468BA19005D; Tue, 11 Jun 2013 06:43:24 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 11 Jun 2013 06:43:24 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Randy Bush <randy@psg.com>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkw2Q+AgAAGBICAABzRgIAAAIiA
Date: Tue, 11 Jun 2013 13:43:23 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751D089D@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com> <51B710DD.5020805@dcrocker.net> <m2ehc8ojcm.wl%randy@psg.com>
In-Reply-To: <m2ehc8ojcm.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <269BF87D485A8747B4BCA17FA45D68A4@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Disgust <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: Tue, 11 Jun 2013 13:43:33 -0000

On Jun 11, 2013, at 9:41 AM, Randy Bush <randy@psg.com> wrote:
> how much process chaos can we create?

Don't ask questions you don't want answered!   :)


From dave@cridland.net  Tue Jun 11 06:48:04 2013
Return-Path: <dave@cridland.net>
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 CE76421F99CF for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level: 
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[AWL=0.061,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 sMtkyxPaC85n for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:48:04 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id CF66521F99D3 for <ietf@ietf.org>; Tue, 11 Jun 2013 06:47:48 -0700 (PDT)
Received: by mail-ob0-f171.google.com with SMTP id dn14so11771669obc.30 for <ietf@ietf.org>; Tue, 11 Jun 2013 06:47:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zaW0TSgmZWT8cMPIk3oPQh120nCC+pjT113VfY0CFvo=; b=RuUKJLwXAw+uGZ1WOeAUYk1C1RJ1vPcNZVr08WvcUj8bPzGNKRFRkOEeV+0KUuUsWx OhKsAZjzc4AFqD0M36f9L1FBCt1gR4yRik18h8EaAvg7YEuAN+jCjeWzKEKWcZR9nA8P oqWB0OD0HnTviVvaoJSV2WcCpPcpiFHSK6O2w=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=zaW0TSgmZWT8cMPIk3oPQh120nCC+pjT113VfY0CFvo=; b=KD/JKsG1By+QUcq5ONHy21HrB2BybZt0LmCuf+Do2UNvDUSbGIojo+GGbHRidUZMmc UDkc8mzntyXkRHPq/DPD1FF/h440TIikA+p5rK3vHuVA1sa+HDRd4aHAQ52OLLU3yqeK dYZaiBeCaDecp9VJq9lFJ0KKhsQq7QLxXb42YNZKkqn3A09/TOi1dL29J5nwVo9SKV1j EAQtSYo7uRn2gICYFiLD/GRe3Yrq+jLGOVq8TelDapxvd/weG4knuqFI9Iv6XQQYRSLe cbfbYpdMiKpaGuEVN4Pf2VHYSIymexugHtPRev9mHpoY3X7ndKZ+W+WnC3ZNEGiCYDAf H8Lg==
MIME-Version: 1.0
X-Received: by 10.60.33.4 with SMTP id n4mr11686390oei.49.1370958468272; Tue, 11 Jun 2013 06:47:48 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Tue, 11 Jun 2013 06:47:48 -0700 (PDT)
In-Reply-To: <m2ehc8ojcm.wl%randy@psg.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com> <51B710DD.5020805@dcrocker.net> <m2ehc8ojcm.wl%randy@psg.com>
Date: Tue, 11 Jun 2013 14:47:48 +0100
Message-ID: <CAKHUCzwQ24hKL5G5a3L=idugAJgwQjx2X5xZbEaRSm+8-8H8Ow@mail.gmail.com>
Subject: Re: Content-free Last Call comments
From: Dave Cridland <dave@cridland.net>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=089e011619f680e1a004dee124f1
X-Gm-Message-State: ALoCoQlyipHto52lpDYIUpK/w+UXWv+w65E+TA4G3dJ3TcqnP1USxKXsVT4L+M1cO4CaVViQjdim
Cc: IETF Disgust <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: Tue, 11 Jun 2013 13:48:04 -0000

--089e011619f680e1a004dee124f1
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 11, 2013 at 2:41 PM, Randy Bush <randy@psg.com> wrote:

> > Re-formulating the LC text sounds like an excellent idea, to call for
> > more substantive comments.
>
> perhaps we should go to the source of the problem and require a phd
> dissertation and defense from draft authors.
>
> how much process chaos can we create?
>
>
I think using a reductio ad absurdum is a little unfair when I've
demonstrated that the proposed reformulation works (whilst being purely
voluntary) in a similar organization with common participants.

In particular, I'm not suggesting any change to process.

Dave.

--089e011619f680e1a004dee124f1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jun 11, 2013 at 2:41 PM, Randy Bush <span dir=3D"ltr">&lt;<=
a href=3D"mailto:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt; Re-formulating the LC=
 text sounds like an excellent idea, to call for<br>
&gt; more substantive comments.<br>
<br>
</div>perhaps we should go to the source of the problem and require a phd<b=
r>
dissertation and defense from draft authors.<br>
<br>
how much process chaos can we create?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div style>I think using a reductio ad absurdum is a litt=
le unfair when I&#39;ve demonstrated that the proposed reformulation works =
(whilst being purely voluntary) in a similar organization with common parti=
cipants.</div>
<div style><br></div><div style>In particular, I&#39;m not suggesting any c=
hange to process.</div><div style><br></div><div style>Dave.</div></div></d=
iv></div>

--089e011619f680e1a004dee124f1--

From l.wood@surrey.ac.uk  Tue Jun 11 06:57:05 2013
Return-Path: <l.wood@surrey.ac.uk>
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 4F86621F9A0D for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.964
X-Spam-Level: 
X-Spam-Status: No, score=-2.964 tagged_above=-999 required=5 tests=[AWL=0.266,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001,  URI_HEX=0.368]
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 zS2ZB8XfAwjz for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 06:57:00 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.173]) by ietfa.amsl.com (Postfix) with ESMTP id B283B21F9A08 for <ietf@ietf.org>; Tue, 11 Jun 2013 06:56:40 -0700 (PDT)
Received: from [195.245.230.131:26416] by server-13.bemta-3.messagelabs.com id C5/6C-19597-49C27B15; Tue, 11 Jun 2013 13:56:36 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-78.messagelabs.com!1370958995!30123362!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28865 invoked from network); 11 Jun 2013 13:56:36 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-8.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 11 Jun 2013 13:56:36 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Tue, 11 Jun 2013 14:56:35 +0100
From: <l.wood@surrey.ac.uk>
To: <dave@cridland.net>, <presnick@qti.qualcomm.com>
Date: Tue, 11 Jun 2013 14:55:44 +0100
Subject: RE: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: Ac5mmAYqSr+qjIMAQoW9rPN3qqgPcgAE1e0g
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EAB@EXMB01CMS.surrey.ac.uk>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>, <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com>
In-Reply-To: <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 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: Tue, 11 Jun 2013 13:57:05 -0000

How many RFCs describe things that are implemented?
How many RFCs describe things that are deployed?

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Dave Cridl=
and [dave@cridland.net]
Sent: 11 June 2013 12:36
To: Pete Resnick
Cc: ietf@ietf.org Discussion
Subject: Re: Content-free Last Call comments

On Mon, Jun 10, 2013 at 9:37 PM, Pete Resnick <presnick@qti.qualcomm.com<ma=
ilto:presnick@qti.qualcomm.com>> wrote:
A statement such as the above is almost entirely useless to me as an IESG m=
ember trying to determine consensus. It is content-free.

I think this is, in part, due to the question asked.

The IETF's Last Call announcement presumes much on the part of those readin=
g it. You're aiming to solicit something that's not asked for.

Compare and contrast with the XSF's Last Call announcements, in particular =
the questionnaire at the end. Note that in this thread, almost all responde=
nts are actually filling it in, and further note that at least some of thos=
e are experienced IETF participants, suggesting that even the jaded IETF fo=
lk might join in.

http://jabber.996255.n3.nabble.com/LAST-CALL-XEP-0308-Last-Message-Correcti=
on-td14079.html

I'd suggest that putting together a set of five questions you're hoping to =
have answered would be sensible and useful.

Perhaps:

1) Do you believe this document is needed?

2) Is the document ready for publication as-is?

3) Are you intending to, or have you already, implemented and/or deployed t=
his specification?

4) Does the document adequately explain the risks involved in implementing =
and/or deploying this specification?

5) Is the document sufficiently clear to allow unambiguous understanding of=
 how to implement and/or deploy the specification?

Dave.

From warren@kumari.net  Tue Jun 11 10:22:04 2013
Return-Path: <warren@kumari.net>
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 5268621F942B for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 10:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 q5o7YqMVNqn3 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 10:21:59 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9A0121F9408 for <ietf@ietf.org>; Tue, 11 Jun 2013 10:21:59 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 5F1411B401CE; Tue, 11 Jun 2013 13:21:58 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Content-free Last Call comments
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <51B63905.2020807@qti.qualcomm.com>
Date: Tue, 11 Jun 2013 13:21:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <645B25A3-7974-431B-9723-25648F83D03D@kumari.net>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1503)
Cc: 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: Tue, 11 Jun 2013 17:22:04 -0000

[ Not sure if this is adding to the Signal or the Noise on the Discuss =
list, but it *will* help bump up my ranking on the "Weekly posting =
summary", which I use to justify my participation to my management. =
That's what it's for, isn't it?!* ]=20
On Jun 10, 2013, at 4:37 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> Russ, our IAB chair and former IETF chair, just sent a message to the =
IETF list regarding a Last Call on draft-ietf-pkix-est. Here is the =
entire contents of his message, save quoting the whole Last Call =
request:
>=20
> On 6/10/13 1:45 PM, Russ Housley wrote:
>> I have read the document, I a support publication on the standards =
track.
>>=20
>> Russ
>=20
> A month ago, we had another very senior member of the community post =
just such a message (in that case directly to the IESG) in response to a =
different Last Call. I took that senior member of the community to task =
for it. But apparently Russ either disagrees with my complaint or didn't =
notice that discussion on the IESG list, so I think it's worth airing =
here in public:
>=20
> A statement such as the above is almost entirely useless to me as an =
IESG member trying to determine consensus. It is content-free.

I disagree.

>=20
> We don't vote in the IETF, so a statement of support without a reason =
is meaningless. We should not be encouraging folks to send such things, =
and having the IAB chair do so is encouraging bad behavior. Had I not =
known Russ and his particular expertise, I would have no reason to take =
it into consideration *at all*. We should not have to determine the =
reputation of the poster to determine the weight of the message. Even =
given my background knowledge of who Russ is, I cannot tell from that =
message which one of the following Russ is saying:
>=20
> - This document precisely describes a protocol of which I have been an =
implementer, and I was able to independently develop an interoperable =
implementation from the document.
> - This document is about a technology with which I have familiarity =
and I have reviewed the technical details. It's fine.
> - I've seen objection X to the document and I think the objection is =
incorrect for such-and-so reasons.
> - My company has a vested interest in this technology becoming a =
standard, and even though I know nothing about it, I support it becoming =
a standards track document.
> - My Aunt Gertrude is the document editor and she said that she needs =
statements of support, so here I am.
> - I have a running wager on when we're going to reach RFC 7000 and I =
want to increase my odds of winning.
>=20
> I take it I am supposed to presume from my friendship and knowledge of =
Russ that one of the first three is true and that the last three are =
not.
> (Well, maybe the last one might be true.) But if instead of from "Russ =
Housely", the message was from "Foo Bar", I would have absolutely no way =
to distinguish among the above.

Actually, yes.

Russ has been participating in the IETF (and specifically in the area =
where he posted the above email) for a long time -- you know this, =
because you've also been participating.
In *my opinion* he has shown himself to be diligent and sane. This means =
that *I* would give his comment and support great weight -- I'd *assume* =
he has read and understood the document, and is supporting it because =
#1, 2, 3 and / or 6. If Foo Bar had posted the comment, and in *my* =
opinion  Foo Bar is a total nutter, I would give his comment less, or =
possibly negative,  weight. Obviously your opinions of Russ and Foo may =
be opposite to mine -- you apply your own weighting to each comment -- =
that's why we pay you the big bucks=85

If Foo Bar is new enough to the IETF and cannot reasonably expect =
everyone on the IESG (or in a WG or wherever) to know and have formed an =
opinion of him, then it is *Foo Bar's* responsibility to more fully =
support his comments.=20

Do folk who actually *participate* actively and sanely get to assume =
that they have earned some standing and credibility? Yup. I view this as =
a feature, not a bug.=20

If I go to my doctor and he tells me that I simply have a cold (and not, =
like I'm convinced, the plague), I should presumably weight his comments =
higher than those of my crazy next door neighbor (who, apparently, =
routinely communicates with beings from another dimension), yes?=20

We want to reward merit and participation, not make the process so =
annoying that those who participate get annoyed and wander off.

If anyone *opposes* a draft, I think that it behooves them to explain =
what the issue is, regardless of who they are. This is similar to at a =
restaurant -- when the waiter asks if you are enjoying your [steak|tofu] =
it's fine to say "Yes thanks, great", but if express displeasure you =
should be ready to explain what you didn't like.


>=20
> I think we should stop with these one-line statements of support. They =
don't add anything to the consensus call. I'm disappointed that Russ =
contributed to this pattern.
>=20
> Other opinions?

My opinion is that the folk on the IETF / WG chairs / anyone evaluating =
information uses their opinion on the source of that information as =
input to it's weight. This is why we have people judging consensus (see =
http://tools.ietf.org/html/draft-resnick-on-consensus-01 :-P) and not =
voting / an algorithm.

W

>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


[*]: :-P
--=20
"He who laughs last, thinks slowest."=20
    -- Anonymous



From johnl@iecc.com  Tue Jun 11 10:44:03 2013
Return-Path: <johnl@iecc.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 DD79F21F8ECE for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 10:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 CwRzvSErDw3E for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 10:43:59 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 109CD21F8904 for <ietf@ietf.org>; Tue, 11 Jun 2013 10:43:56 -0700 (PDT)
Received: (qmail 50379 invoked from network); 11 Jun 2013 17:43:55 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Jun 2013 17:43:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51b761da.xn--hew.k1306; i=johnl@user.iecc.com; bh=tkTDYkLuqT0/HMjnzqn3aUDbYlFw46Fw3uu0oRx1voc=; b=Z46uC2EC0YSrG2xXH6A7Cvg9nzFp3TSzJcoHF96Kv3G9kP0iP+K/8LNu2hBwBPlMbmTaCG2Xp4/zVVj2CJ4+F5iMDMi+PAEpFeAZxgLZ4SzHOYYmZcZ/6FnI0SQDxMxU/5HEnFmBxfsTnV9mR7xKhYSt0Rzeo8ydSVQbO7tiMiGFaXGTKSRCabevEW4nC4b99RM2QSfeH24/S2jwakrrw6hsFsw6G5OTa/NKBi0DdxCQVGF5t+aRNK8VwBZeC5nk
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51b761da.xn--hew.k1306; olt=johnl@user.iecc.com; bh=tkTDYkLuqT0/HMjnzqn3aUDbYlFw46Fw3uu0oRx1voc=; b=dgpEFV334eMGdAjxC2Bz2R/n8bb7troYgBKdKJhOA9+6veRXvsU/ITV7Ga+vCy6+UyVM2bKcJOlD6+dzHOnSwHGSN3SbSkVoeEwzTekL9D5xsJ8KjAT2L4DfiuVIcw6P7BmTlqTalZ20aguQ139LVC5GIl7s5gKW3qwxEtOnt8YRw3If2Ayeuc7AszI14scmZfTEpGvbM2M20tRtakrt/PiLQzxwjVGHvky5CdwZLB1ZnMH1+wpPle+knJpvbxJi
Date: 11 Jun 2013 17:43:32 -0000
Message-ID: <20130611174332.79781.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Content-free Last Call comments
In-Reply-To: <20130611115246.GG22738@besserwisser.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: mansaxel@besserwisser.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: Tue, 11 Jun 2013 17:44:04 -0000

>So, if wg discussion has been ordered mute by the wg chairs because
>some wg participants believe the group-think consensus is good enough,
>can those objections again be raised in IETF LC or are they set in stone?

If that were ever to happen, I don't see why not.

In the recent cases I've seen where someone claims this is an issue,
what actually happned is that a person only tangentially involved in
the WG is obsessing about some technical wart and refuses to (or
worse, can't) understand the overall context that led the WG to decide
what it did.

It's hard to see any benefit to rehashing such arguments in front of
the whole IETF.

R's,
John

From dougb@dougbarton.us  Tue Jun 11 10:52:07 2013
Return-Path: <dougb@dougbarton.us>
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 F422F21F966B for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 10:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 bv6wgJmz1oUh for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 10:52:02 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id A795021F94D3 for <ietf@ietf.org>; Tue, 11 Jun 2013 10:52:02 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id D7E7722B13 for <ietf@ietf.org>; Tue, 11 Jun 2013 17:52:01 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1370973121; bh=94GfGDfygLkJflriVZsb9z7YyxoO9axQONATVJBkyuQ=; h=Date:From:To:Subject:References:In-Reply-To; b=rtJKjJS8UwodJT4vM4xJ7R/hgnEOReBFVcYLy8cS4Vndbu/q+u3x4Fu3BSgHuEY1y hysGjUnkksjMJGoCeyKb5Zjtu+Rik7AoubR0hAo7/Hgn6x7GOqQq7ZlOl7nXoKrQg6 Y3r9MMKwXUI/APinksiwFHAhQhT9sVEcc7XBNGXc=
Message-ID: <51B763C1.1050205@dougbarton.us>
Date: Tue, 11 Jun 2013 10:52:01 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Content-free Last Call comments
References: <20130611174332.79781.qmail@joyce.lan>
In-Reply-To: <20130611174332.79781.qmail@joyce.lan>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Tue, 11 Jun 2013 17:52:07 -0000

On 06/11/2013 10:43 AM, John Levine wrote:
>> So, if wg discussion has been ordered mute by the wg chairs because
>> some wg participants believe the group-think consensus is good enough,
>> can those objections again be raised in IETF LC or are they set in stone?
>
> If that were ever to happen, I don't see why not.
>
> In the recent cases I've seen where someone claims this is an issue,
> what actually happned is that a person only tangentially involved in
> the WG is obsessing about some technical wart and refuses to (or
> worse, can't) understand the overall context that led the WG to decide
> what it did.
>
> It's hard to see any benefit to rehashing such arguments in front of
> the whole IETF.

The flip side of that argument is that we don't want to assume working 
groups are infallible, or more importantly not subject to the groupthink 
phenomenon. Otherwise what is IETF LC for?

Doug


From Ted.Lemon@nominum.com  Tue Jun 11 11:02:40 2013
Return-Path: <Ted.Lemon@nominum.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 841DD21F9922 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 11:02:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.623
X-Spam-Level: 
X-Spam-Status: No, score=-106.623 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 v-d8e0Om7WhY for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 11:02:31 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 39D1721F9814 for <ietf@ietf.org>; Tue, 11 Jun 2013 11:02:31 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUbdmNuVLP5qQTWolQxR4rJsbD4vYnioY@postini.com; Tue, 11 Jun 2013 11:02:31 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A526B1B81DB for <ietf@ietf.org>; Tue, 11 Jun 2013 11:02:30 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 7F43519005D; Tue, 11 Jun 2013 11:02:30 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 11 Jun 2013 11:02:30 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkwC7SAgAAG4wCAAMrtAIAAYgEAgAACXoCAAALtgA==
Date: Tue, 11 Jun 2013 18:02:29 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751D1222@mbx-01.win.nominum.com>
References: <20130611174332.79781.qmail@joyce.lan> <51B763C1.1050205@dougbarton.us>
In-Reply-To: <51B763C1.1050205@dougbarton.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <DDEF489A9B01FA4B885C8C5CA6DAF25C@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <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: Tue, 11 Jun 2013 18:02:40 -0000

On Jun 11, 2013, at 1:52 PM, Doug Barton <dougb@dougbarton.us> wrote:
> The flip side of that argument is that we don't want to assume working gr=
oups are infallible, or more importantly not subject to the groupthink phen=
omenon. Otherwise what is IETF LC for?

The IETF last call is for catching things the working group missed, not for=
 rehashing arguments that were beaten to death in the working group.   It i=
s certainly possible for a discussion in the working group to go one way, a=
nd then for the same discussion to come up in IETF last call and go the oth=
er way, because the experts on the topic were not included in the discussio=
n, or because their advice was inappropriately ignored.   This does happen;=
 unfortunately, when it happens it often doesn't get caught in IETF last ca=
ll anyway.


From melinda.shore@gmail.com  Tue Jun 11 12:10:04 2013
Return-Path: <melinda.shore@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 22B3921F9113 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 12:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 NK94hkNfqXga for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 12:09:58 -0700 (PDT)
Received: from mail-pd0-f179.google.com (mail-pd0-f179.google.com [209.85.192.179]) by ietfa.amsl.com (Postfix) with ESMTP id 3CAE521F8ECB for <ietf@ietf.org>; Tue, 11 Jun 2013 12:09:58 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id q10so3083981pdj.10 for <ietf@ietf.org>; Tue, 11 Jun 2013 12:09:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=B/zcvacoIQaqUVOsieRHklpsT8gcKclP2/CLcH80F1c=; b=wGsPziwtV+YZk+oQReOCGkpb1ZxUI5U7YmDzapYVKCCupYJYanRmmTsMHs6H8l8btY tif13ii1rt84E1bzs1BbosuVSRHsWjI7unu5UHXR78+MozdOuBozM84opylvz5lCcTv2 ezuHlFi5X6x7ETnqpzXvHC4WnDr4FtjTSaHWgTA4B/FHvgkdetYbXuuO4qRE5L1E4La1 y1Rrv2jk22Rchi+PKqb5D3wjyeq9sNnicVHx4WxAxqmNV5QYQ4DjYzNg6q6DispJzGIS vho1OqBSEHskphOOsoXOHCxpBS9MVllv2wAl/U4hJPmlzqR+u9sB1/7y1KyQ1y+y71zG tPeQ==
X-Received: by 10.66.220.197 with SMTP id py5mr20385337pac.86.1370977797986; Tue, 11 Jun 2013 12:09:57 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id dr6sm21244376pac.11.2013.06.11.12.09.56 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 11 Jun 2013 12:09:57 -0700 (PDT)
Message-ID: <51B77602.80903@gmail.com>
Date: Tue, 11 Jun 2013 11:09:54 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Content-free Last Call comments
References: <20130611174332.79781.qmail@joyce.lan> <51B763C1.1050205@dougbarton.us>
In-Reply-To: <51B763C1.1050205@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Tue, 11 Jun 2013 19:10:04 -0000

On 6/11/13 9:52 AM, Doug Barton wrote:
> The flip side of that argument is that we don't want to assume working
> groups are infallible, or more importantly not subject to the groupthink
> phenomenon. Otherwise what is IETF LC for?

Right.  We've had some issues with document quality, and I
can think of several documents that sailed through WG last
call and should not have.

Melinda



From dhc@dcrocker.net  Tue Jun 11 12:14:05 2013
Return-Path: <dhc@dcrocker.net>
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 A1B9B21F8F09 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 12:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.769
X-Spam-Level: 
X-Spam-Status: No, score=-5.769 tagged_above=-999 required=5 tests=[AWL=-0.830, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock10=1.66]
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 5A7OAlfHGn-d for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 12:14:00 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CEA8621F8F9E for <ietf@ietf.org>; Tue, 11 Jun 2013 12:13:59 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5BJDulq021897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Jun 2013 12:13:59 -0700
Message-ID: <51B776EE.7000402@dcrocker.net>
Date: Tue, 11 Jun 2013 12:13:50 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Bullseye (was Re: [IETF] Content-free Last Call comments)
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <645B25A3-7974-431B-9723-25648F83D03D@kumari.net>
In-Reply-To: <645B25A3-7974-431B-9723-25648F83D03D@kumari.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 11 Jun 2013 12:13:59 -0700 (PDT)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Tue, 11 Jun 2013 19:14:05 -0000

On 6/11/2013 10:21 AM, Warren Kumari wrote:
> [ Not sure if this is adding to the Signal or the Noise on the
> Discuss list, but it*will*  help bump up my ranking on the "Weekly
> posting summary", which I use to justify my participation to my
> management. That's what it's for, isn't it?!* ]


oh boy. we need to put that on a t-shirt.  it's just perfect.  and 
universal.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From melinda.shore@gmail.com  Tue Jun 11 12:14:37 2013
Return-Path: <melinda.shore@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 6614921F9972 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 12:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 LYMzk61rATmO for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 12:14:31 -0700 (PDT)
Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) by ietfa.amsl.com (Postfix) with ESMTP id 9056621F939E for <ietf@ietf.org>; Tue, 11 Jun 2013 12:14:28 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id 10so8974352pdi.39 for <ietf@ietf.org>; Tue, 11 Jun 2013 12:14:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=8owxjB80cU8sin9OTm4IS864jd/oZ6LiaOV3/aozidg=; b=u7Mmu1OD0aT5qBlPnQBnA7YSOUpQR1mrSc/hXsxoFU4MThhKg9Zaj4JS+5pCWOyJKK d/VM6pkvTBDx+0S7Ayrv/fpfHe5cWuDuMC4grCBO7D0eJO2qPpz+JRVASETNeDwZIvub ZHq7byEnvaeAxht6cCylLepjoXBtbmMQEnzZox9L/CpcmArZYsoT22Ai+W9TBNV6Z1Js jY2LaNET5NqxxUSuvgyuHjyTXk4mvm1ztmU673kVg2rhdnIe42/YR+l5/2Ku8vXMz9KD WqwFXESaG3il/lIag9p5kxqX10dDsfmywKoGpYEhT0wdVf1Ex5crPoOl/qcU2rLcQLXT M1hA==
X-Received: by 10.68.108.163 with SMTP id hl3mr15918760pbb.160.1370978068247;  Tue, 11 Jun 2013 12:14:28 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id u6sm1471498pbb.46.2013.06.11.12.14.26 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 11 Jun 2013 12:14:27 -0700 (PDT)
Message-ID: <51B77711.9050703@gmail.com>
Date: Tue, 11 Jun 2013 11:14:25 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Content-free Last Call comments
References: <20130611174332.79781.qmail@joyce.lan> <51B763C1.1050205@dougbarton.us> <8D23D4052ABE7A4490E77B1A012B6307751D1222@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751D1222@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Tue, 11 Jun 2013 19:14:37 -0000

On 6/11/13 10:02 AM, Ted Lemon wrote:
> The IETF last call is for catching things the working group missed,
> not for rehashing arguments that were beaten to death in the working
> group. 

I am not sure I fully understand why we're having this conversation,
or rather why this aspect of the broader discussion requires attention.
Sometimes working groups make mistakes, and I don't think that in
practice there'd be general objection to having serious problems
identified during IETF last call.  Yes, there have been cases where
cranks who can't let go of an idea that was rejected try to flog it
to death, but that doesn't mean that identifying and dealing with
real problems should be dismissed.

Melinda

From presnick@qti.qualcomm.com  Tue Jun 11 12:46:07 2013
Return-Path: <presnick@qti.qualcomm.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 6DA3B21F9412 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 12:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 21rUQ-u-wiXL for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 12:46:03 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 298D621F8DDD for <ietf@ietf.org>; Tue, 11 Jun 2013 12:46:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1370979963; x=1402515963; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=yIatzzl6AnHNwOn/UgCGkbvM/RWJmmSczaKIWo/QdJk=; b=Toj2jsvZuX4Gr5JM4lEel3WILwHtgVSwAbAinLrATvHiOlWxfMus7Q1S cXilXO8IvNHu8Ff2NhYdhqZFRi5W7y8OTIGQQmCtj/gNCCtsb/97zSrli 0FjHhOaUZIKJ86AcJ9CgAN5c227eXRkOPbL7V3c6EAV8+xiJLeFfCZQkh k=;
X-IronPort-AV: E=Sophos;i="4.87,847,1363158000"; d="scan'208";a="55774919"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 11 Jun 2013 12:46:02 -0700
X-IronPort-AV: E=Sophos;i="4.87,846,1363158000"; d="scan'208";a="488812118"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 11 Jun 2013 12:46:02 -0700
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 11 Jun 2013 12:46:02 -0700
Message-ID: <51B77E77.1030601@qti.qualcomm.com>
Date: Tue, 11 Jun 2013 14:45:59 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie>
In-Reply-To: <51B6710E.4040800@cs.tcd.ie>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [172.30.39.5]
Cc: 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: Tue, 11 Jun 2013 19:46:07 -0000

It's interesting to see that people are interpreting me to mean I want 
more text. I don't. I want less. Save your breath. There is no reason to 
send one line of support, and it only encourages the view that we're 
voting. Details below.

Specifically on Stephen's message:

On 6/10/13 7:36 PM, Stephen Farrell wrote:
> I think you err when you say this:
>
>    
>> A statement such as the above is almost entirely useless to me as an
>> IESG member trying to determine consensus. It is content-free.
>>      
> In fact, you do know Russ. If you did not, then the above would be
> far closer to correct. But in reality you do know a lot more than
> you claim below. With overwhelming probability, your choice #2
> applies and I'm very surprised you don't also think that. If it
> made a significant difference and I wasn't sure I'd ask Russ to
> clarify. For me, I read Russ' mail and I concluded he meant #2.
> And I'm confident in that conclusion.
>
> So I'm really bemused when you say that you don't know how to
> interpret Russ' mail.
>    

Let's separate out a few issues. There's what the message means itself, 
there's its usefulness and how much weight it should be given, and then 
there's what's problematic about it. I think you've conflated a few things.

As you know, on the earlier message I called out on the IESG list, I 
guessed wrong that the sender was claiming choice #3 (that is, I 
thought, incorrectly, that the sender disagreed with a recent argument 
against publication, but simply didn't explain why). In fact in that 
case, not only wasn't it choice #4, it was also neither choice #1 (an 
implementer claiming implementation) nor choice #2 (an expert on the 
topic), my other two guesses, but rather a generally smart IETFer who 
thought the work seemed like a good idea. So I'm a little disinclined to 
guess on motives. In the case of Russ's message, I did guess it was 
choice #2, but I wasn't really sure.

But let's separate what Russ meant from the weight it should be given. 
The message was that a person (let's presume with some expertise in the 
area) had read it. So what? Didn't this document go through a WG? 
Weren't a good bunch of experts already reading and reviewing this 
document? If this was during the WG discussion and the chairs solicited 
some final check reviews, *maybe* the message could have some use. But 
during IETF Last Call? Even if the message was sent because it was 
trying to say, "I'm an expert on this stuff and it looks technically 
sound", is that going to change anything that the IESG should do about 
the document? I just think at Last Call, these statements of support are 
either harmless-but-useless or they are nefarious.

> Declaring that mail problematic also seems quite purist to me.
>    

I always find it amusing that when Stephen and I disagree, it's almost 
always because he presumes I want purity (and usually a new process), 
which I don't, and it seems to me that he wants no rules-of-thumb at all 
and that everything should be on a case-by-case basis. (I guess that 
means that I'm into purity, where Stephen has no principles. ;-) ) I 
think general principles are a fine thing, and we should try to stick to 
them, but I've got no interest in purity.

The single piece of mail isn't problematic at all. As I said, probably 
harmless but useless. But the overall impression it gives *is* 
problematic. It encourages the view that we are voting, that a simple 
statement of support is important to our process. (What really set my 
hair on end was the "I support publication" bit. That always sounds like 
a vote for a new RFC. From Russ, I have a pretty good idea that he 
didn't mean it that way, but it's a poor formulation and not what we 
should be encouraging.) It also indicates that during Last Call, we want 
to hear that a document is getting reviewed. I would like to presume 
that documents get serious reviews in the WG, and that Last Call time is 
for people who haven't been participating in the WG to do a final check, 
letting us know if there's something *wrong*. If the document wasn't 
getting good review in the WG and needs statements of support at Last 
Call time, something has seriously failed earlier in the process. The 
chair or responsible AD should have been saying early on, "Dear Expert, 
can you please have a read over this document and see if it's sane." 
Last Call is the wrong time for that to happen. This just encourages 
more of the tail-heavy process that we discussed earlier.

> At the same time I agree we do not want a procession of +1 mails.
>    

Right. And having senior members of the community doing so will 
encourage such behavior in the future.

> But then we won't get that for this draft. And if we did get that
> for any draft, some IETF participants (probably incl. you and I)
> would notice that and query it or object.

I'd rather have all of us crusty folks model good behavior rather than 
having to complain about bad behavior later, especially when we'll get 
responses like, "But the chair did it." We've already seen a couple of 
comments to my message from non-crusty-folks indicating that any +1 is 
just dandy. Blech.

> Lastly, I think evaluating IETF LC messages only in terms
> of how they help the IESG evaluate consensus or not is wrong.
> Those messages are for and from the IETF community. So if
> e.g. some renowned NFS person who's hardly known to the IESG
> were to have sent an equivalent message, that might have been
> quite good input that Martin or Spencer could have translated for
> you. And that's just fine. And it would be fine if Russ' mail
> had been directed not at the IESG but at some other part of the
> community.
>    

So this is the most interesting argument. But I would say that requiring 
this kind of interpretation/translation is problematic as a general rule 
when the messages are going to the IETF list in response to a Last Call. 
If a renowned NFS person is doing a review of an NFS document, I think 
that's great. And I think that's helpful to Martin or Spencer. But if 
all they're going to say is, "I don't have any concerns", it doesn't 
seem to me to be that useful a piece of info on the IETF list at Last 
Call time. Again, at best it encourages the idea that just because Über 
NFS person endorses the document, that weighs in its favor. The 
important thing to hear at Last Call time are objections, not 
endorsements. As a note to the IESG saying, "Just in case you didn't 
think this got review from the right people before, I, Über NFS person, 
hereby say that I reviewed it and have no problem with it", that has 
some content, but it does indicate that we are waiting until too late in 
the process to be thinking about such things.

> So bottom line, I think you're wrong, Russ' mail was not content-free.
>    

Yeah, you haven't convinced me.

> PS: Yes, this is a not-very-good academic accusing an employee
> of an industrial behemoth of excess purity. Go figure:-)

I'll note that I hide in a small R&D corner of my industrial behemoth, 
mostly teaching classes to other engineers. You, on the other hand, 
probably still write code. :-)

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From brian.e.carpenter@gmail.com  Tue Jun 11 13:06:33 2013
Return-Path: <brian.e.carpenter@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 52BAA21F99D6 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 13:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.509
X-Spam-Level: 
X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 PifxaIXIMNJJ for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 13:06:32 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id D618821F9998 for <ietf@ietf.org>; Tue, 11 Jun 2013 13:06:32 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id lf11so3204640pab.10 for <ietf@ietf.org>; Tue, 11 Jun 2013 13:06:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EP1PfTAcRlNwMIF1DujVLQRUQYSAKa9E/DpP7VBJmOo=; b=iGnhHY72Wk71l5h+eg70CcgHdxaExNbg8CDg9xbKg4RYtVhxIbWquzl30x0J/t87cj UFmFcM8a4Y8XzFCulSs2nTLitdqh2mWYC6UyqiHCcmDLXPpPIXz5lmTVdHZTEYwyZxuq Zd2kJDP+BjFqyTnPYUrsNncyYm9F8Xxh17cZ3l6sFGJspjmEaJO09FdxrTvN2vOpbB19 mX/InvBv88I6uTMEbi7nWLSBsQPiNcfEoINNs0U1cI3s1hl1yhHZjDvZWcEmQ00HVFX8 2obcitk6QlqnmMVhVqU5kzv+KMVHrzcY/Qzce2nIrWy3KK/nWdVjUzUyeZBdZcBzJMlC cG+w==
X-Received: by 10.68.163.4 with SMTP id ye4mr16222188pbb.207.1370981192630; Tue, 11 Jun 2013 13:06:32 -0700 (PDT)
Received: from [192.168.1.2] (13.162.252.27.dyn.cust.vf.net.nz. [27.252.162.13]) by mx.google.com with ESMTPSA id fp2sm15885053pbb.36.2013.06.11.13.06.30 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 11 Jun 2013 13:06:31 -0700 (PDT)
Message-ID: <51B78312.1010108@gmail.com>
Date: Wed, 12 Jun 2013 08:05:38 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com>	<51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com>
In-Reply-To: <51B77E77.1030601@qti.qualcomm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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: Tue, 11 Jun 2013 20:06:33 -0000

Pete,

On 12/06/2013 07:45, Pete Resnick wrote:
> It's interesting to see that people are interpreting me to mean I want
> more text. I don't. I want less. Save your breath. There is no reason to
> send one line of support, and it only encourages the view that we're
> voting. Details below.

Just to test what you are saying, let me ask the following. I will
stipulate that a message that can be summarised accurately as "+1" doesn't
serve much purpose. How would you react to one that says something like:
"I've read the draft, and I've considered Joe Blow's objection, but I
still support publication of the draft" (*not" followed by a reasoned
rebuttal of Joe Blow's argument)?

   Brian

From dave@cridland.net  Tue Jun 11 13:24:11 2013
Return-Path: <dave@cridland.net>
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 DFD7B21F8B51 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 13:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.94
X-Spam-Level: 
X-Spam-Status: No, score=-1.94 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 dOVz0kT0FDxJ for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 13:24:10 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA4421F8459 for <ietf@ietf.org>; Tue, 11 Jun 2013 13:24:02 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id i4so4052169oah.38 for <ietf@ietf.org>; Tue, 11 Jun 2013 13:24:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2KBVgMTaHdIcymlbCXwi7nNisMhyKqRJ8+PW+dnqm+g=; b=SFFmM4SgO03XcMv+EIdOjzmEvgrog0pnY0COBYmv8uSNxVzLu8V7PhlxlhoQ1/dieg rUxi849F7/26HVO+dEq0DZRRzxKPeJvI7tEHae0Dh7EIJMeQkEMonKiC0OI/tBZfPaA1 rNsxcWAo0T3WET1bgdVteqCNtxsPbc2xbB9TI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=2KBVgMTaHdIcymlbCXwi7nNisMhyKqRJ8+PW+dnqm+g=; b=nc9Rc//N/jHz/8Qw1xusb6Qm21q4NciXCZAQmIk10WjSOcAsJnZvm5s3tYiyItEeaZ PXLrEPLF3XV1UYVOqgZPr+FPQ1dotRfNv6OsMUBYzlCpUQi8yXHEHGGqFlAn5f37mlPO c7OONcWRq9wnKqPXNcoFf8Y9n5WJGru7LdLUqigoNOi/AOkQ8lQjaO6HtUVlvgO2knzP yIqtRbhQ/Exqmb3rO3pnLcdxe9diUngi2SDjdj+4VDxLP7YgwDWN1U2V1N9KG1NgXHzO r8B7z4gLlUCRyu9eh/rTtqqu8Wschxvqt2WrEjNLIDir38E0v88BuENf3VHTc/e7lvrd zJoA==
MIME-Version: 1.0
X-Received: by 10.60.41.40 with SMTP id c8mr13407408oel.79.1370982240606; Tue, 11 Jun 2013 13:24:00 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Tue, 11 Jun 2013 13:24:00 -0700 (PDT)
In-Reply-To: <51B77E77.1030601@qti.qualcomm.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com>
Date: Tue, 11 Jun 2013 21:24:00 +0100
Message-ID: <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com>
Subject: Re: Content-free Last Call comments
From: Dave Cridland <dave@cridland.net>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=089e013a092671ed1e04dee6ad8b
X-Gm-Message-State: ALoCoQlyZSgGKdmR/uJgtd7krwO9XK32ZIuZhRS9aIiV2zlzbYNPyTsemwL2smUdRnj0clfNxnxA
Cc: "ietf@ietf.org Discussion" <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: Tue, 11 Jun 2013 20:24:12 -0000

--089e013a092671ed1e04dee6ad8b
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 11, 2013 at 8:45 PM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> It's interesting to see that people are interpreting me to mean I want
> more text. I don't. I want less. Save your breath.


Well, this thread is surely evidence that you don't always get what you
want.

But more seriously, what are you expecting Russ to do? What did you want
him to write?

If your answer is "Nothing", then how do you read IETF consensus for a
document that gets no response in its Last Call? The XSF's stance is often
"It got nothing in Last Call, it shouldn't advance", which seems reasonable
to me - I don't think defaulting to publication is right - certainly not in
every case.

My suggestion was simply to ask for what you want in the Last Call.

But I imagine you could also just start an endless thread on an already
overloaded list until someone guesses the answer.

Dave.

--089e013a092671ed1e04dee6ad8b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jun 11, 2013 at 8:45 PM, Pete Resnick <span dir=3D=
"ltr">&lt;<a href=3D"mailto:presnick@qti.qualcomm.com" target=3D"_blank">pr=
esnick@qti.qualcomm.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"=
><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">It&#39;s interesting to see that people are =
interpreting me to mean I want more text. I don&#39;t. I want less. Save yo=
ur breath.=A0</blockquote>
<div style><br></div><div style>Well, this thread is surely evidence that y=
ou don&#39;t always get what you want.</div><div style><br></div><div style=
>But more seriously, what are you expecting Russ to do? What did you want h=
im to write?</div>
<div style><br></div><div style>If your answer is &quot;Nothing&quot;, then=
 how do you read IETF consensus for a document that gets no response in its=
 Last Call? The XSF&#39;s stance is often &quot;It got nothing in Last Call=
, it shouldn&#39;t advance&quot;, which seems reasonable to me - I don&#39;=
t think defaulting to publication is right - certainly not in every case.</=
div>
<div style><br></div><div style>My suggestion was simply to ask for what yo=
u want in the Last Call.</div><div style><br></div><div style>But I imagine=
 you could also just start an endless thread on an already overloaded list =
until someone guesses the answer.</div>
<div style><br></div><div style>Dave.</div></div></div></div>

--089e013a092671ed1e04dee6ad8b--

From Ted.Lemon@nominum.com  Tue Jun 11 13:33:34 2013
Return-Path: <Ted.Lemon@nominum.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 C1AF621F8ADF for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 13:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.621
X-Spam-Level: 
X-Spam-Status: No, score=-106.621 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 AattzRJ7e33Z for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 13:33:28 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id EBFEF21F8825 for <ietf@ietf.org>; Tue, 11 Jun 2013 13:33:27 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUbeJl0ZCk96OvU8xI2dLi/iW2Had35Z6@postini.com; Tue, 11 Jun 2013 13:33:27 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6B7321B806F for <ietf@ietf.org>; Tue, 11 Jun 2013 13:33:27 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 62F2919005D; Tue, 11 Jun 2013 13:33:27 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 11 Jun 2013 13:33:27 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dave Cridland <dave@cridland.net>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkwIJIAgAFBKYCAAAqfAIAAAp+A
Date: Tue, 11 Jun 2013 20:33:26 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com>
In-Reply-To: <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751D16B0mbx01winnominum_"
MIME-Version: 1.0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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: Tue, 11 Jun 2013 20:33:34 -0000

--_000_8D23D4052ABE7A4490E77B1A012B6307751D16B0mbx01winnominum_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Jun 11, 2013, at 4:24 PM, Dave Cridland <dave@cridland.net<mailto:dave@c=
ridland.net>> wrote:
But more seriously, what are you expecting Russ to do? What did you want hi=
m to write?

If your answer is "Nothing", then how do you read IETF consensus for a docu=
ment that gets no response in its Last Call? The XSF's stance is often "It =
got nothing in Last Call, it shouldn't advance", which seems reasonable to =
me - I don't think defaulting to publication is right - certainly not in ev=
ery case.

My suggestion was simply to ask for what you want in the Last Call.

I have a modest suggestion for you: read the rest of the message from Pete =
that you just replied to, in which he answers each of the questions you ask=
ed in your reply.



--_000_8D23D4052ABE7A4490E77B1A012B6307751D16B0mbx01winnominum_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <39BA47EE8D1F3941A142E57144E68C88@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Jun 11, 2013, at 4:24 PM, Dave Cridland &lt;<a href=3D"mailto:dave@=
cridland.net">dave@cridland.net</a>&gt; wrote:</div>
<blockquote type=3D"cite">
<div style=3D"font-family: Optima; font-size: medium; font-style: normal; f=
ont-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
But more seriously, what are you expecting Russ to do? What did you want hi=
m to write?</div>
<div style=3D"font-family: Optima; font-size: medium; font-style: normal; f=
ont-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<br>
</div>
<div style=3D"font-family: Optima; font-size: medium; font-style: normal; f=
ont-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
If your answer is &quot;Nothing&quot;, then how do you read IETF consensus =
for a document that gets no response in its Last Call? The XSF's stance is =
often &quot;It got nothing in Last Call, it shouldn't advance&quot;, which =
seems reasonable to me - I don't think defaulting to
 publication is right - certainly not in every case.</div>
<div style=3D"font-family: Optima; font-size: medium; font-style: normal; f=
ont-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<br>
</div>
<div style=3D"font-family: Optima; font-size: medium; font-style: normal; f=
ont-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
My suggestion was simply to ask for what you want in the Last Call.</div>
</blockquote>
</div>
<br>
<div>I have a modest suggestion for you: read the rest of the message from =
Pete that you just replied to, in which he answers each of the questions yo=
u asked in your reply.</div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307751D16B0mbx01winnominum_--

From presnick@qti.qualcomm.com  Tue Jun 11 13:33:51 2013
Return-Path: <presnick@qti.qualcomm.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 6147921F99EF for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 13:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 CoK-Jn2a+CYx for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 13:33:39 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 5568421F8D6D for <ietf@ietf.org>; Tue, 11 Jun 2013 13:33:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1370982818; x=1402518818; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=7OCuv+HI84VDFxiF7N+PkJsrIXlnntzUiU5tFHVfTi4=; b=AaOKsxO/vP0jqcVPJRS4NbejnVxY1SBBV0PqoGCsVan/XHShn42vx1R4 s4OfUG4ZrqV65FZRysVOqsmh8ZRhdc6q9rNVqm1KrIpy5Qu+xckgB3hob R866z6d0viALsbRsDEf+HsG85iHhy3Ra9Xc1Ic9e7+7mIWviT50gfFUxc o=;
X-IronPort-AV: E=Sophos;i="4.87,847,1363158000"; d="scan'208";a="44642558"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth02.qualcomm.com with ESMTP; 11 Jun 2013 13:33:37 -0700
X-IronPort-AV: E=Sophos;i="4.87,847,1363158000"; d="scan'208";a="463207875"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 11 Jun 2013 13:33:37 -0700
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 11 Jun 2013 13:31:04 -0700
Message-ID: <51B78907.6070309@qti.qualcomm.com>
Date: Tue, 11 Jun 2013 15:31:03 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com>	<51B6710E.4040800@cs.tcd.ie>	<51B77E77.1030601@qti.qualcomm.com> <51B78312.1010108@gmail.com>
In-Reply-To: <51B78312.1010108@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: 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: Tue, 11 Jun 2013 20:33:51 -0000

On 6/11/13 3:05 PM, Brian E Carpenter wrote:
> Pete,
>
> On 12/06/2013 07:45, Pete Resnick wrote:
>    
>> It's interesting to see that people are interpreting me to mean I want
>> more text. I don't. I want less. Save your breath. There is no reason to
>> send one line of support, and it only encourages the view that we're
>> voting. Details below.
>>      
> Just to test what you are saying, let me ask the following.

Oooo...I love a test.

> How would you react to one that says something like:
> "I've read the draft, and I've considered Joe Blow's objection, but I
> still support publication of the draft" (*not" followed by a reasoned
> rebuttal of Joe Blow's argument)?
>    

I would be rather grumpy with such a message. If there's an outstanding 
(reasonable) objection to a document, I need to know why to consider 
that argument in the rough. I'd have to ask for more detail from the 
sender. If the response I get back is, "I figured it was obvious why Joe 
Blow was full of crap", I'd ask, "Then why did you bother posting?" If 
the sender happens to be an expert (and Joe Blow is not), I'm still not 
going to take it at face value that Joe Blow is wrong. If I did, Joe 
would be well within rights to appeal because his argument got blown off.

So, if you're saying something that is perfectly obvious, no need to say 
it. But if it's not perfectly obvious, I do want more text.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From dougb@dougbarton.us  Tue Jun 11 13:50:03 2013
Return-Path: <dougb@dougbarton.us>
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 6D0C821F9A21 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 13:50:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 ZzxOQ4BN-bnB for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 13:50:02 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 45F6021F9A0C for <ietf@ietf.org>; Tue, 11 Jun 2013 13:50:02 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id E723622B25 for <ietf@ietf.org>; Tue, 11 Jun 2013 20:50:01 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1370983802; bh=q9W8S/A9WsS7SIsyfOgP/6wis+K8twVoXaY/C1vtYAg=; h=Date:From:To:Subject:References:In-Reply-To; b=nLW8dhMvQ1rHPzzQ99xvvhYB9Ht8WpQ0Dd2QxAHVp328LCjchpV8Hz/eW8AP2lN/l RjKVu/wopxVn8ZDC1ECxlyRKCpVf6SQQn8+ZspVeO7tQsalS3ius+kRv2LkDnTs3Wh SSmpD8KaOU8pLc0siCl5Qs1nk2h4IgwqU70KXC3g=
Message-ID: <51B78D79.7010807@dougbarton.us>
Date: Tue, 11 Jun 2013 13:50:01 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Content-free Last Call comments
References: <20130611174332.79781.qmail@joyce.lan> <51B763C1.1050205@dougbarton.us> <8D23D4052ABE7A4490E77B1A012B6307751D1222@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751D1222@mbx-01.win.nominum.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Tue, 11 Jun 2013 20:50:03 -0000

On 06/11/2013 11:02 AM, Ted Lemon wrote:
> On Jun 11, 2013, at 1:52 PM, Doug Barton <dougb@dougbarton.us>
> wrote:
>> The flip side of that argument is that we don't want to assume
>> working groups are infallible, or more importantly not subject to
>> the groupthink phenomenon. Otherwise what is IETF LC for?
>
> The IETF last call is for catching things the working group missed,
> not for rehashing arguments that were beaten to death in the working
> group.

As I understand it cross-disciplinary review is also an important 
function of the IETF LC.

> It is certainly possible for a discussion in the working
> group to go one way, and then for the same discussion to come up in
> IETF last call and go the other way, because the experts on the topic
> were not included in the discussion, or because their advice was
> inappropriately ignored.

Right ... for example the recent issue in regards to the potential 
deprecation of the SPF DNS RRtype.

> This does happen; unfortunately, when it
> happens it often doesn't get caught in IETF last call anyway.

Then the process is faulty. :)

I should also point out that when I mentioned "groupthink" in my message 
I was not doing so in a snarky and/or throwaway manner. The phenomenon 
is very real, and IETF WGs are an ideal breeding ground for it on 
several levels. It's _very_ easy for a group of humans to get into a 
mutual confirmation bias feedback loop, and although we generally do 
better on that point than a lot of groups would in similar 
circumstances, having people from outside the WG review documents 
provides (or should provide) a much-needed sanity check. In many ways 
having people from outside the group provide a well thought out review 
is _more_ valuable than the process of creating the document within the 
WG itself (although obviously we need to give proper credit for that 
creation).

Doug

From dave@cridland.net  Tue Jun 11 14:27:32 2013
Return-Path: <dave@cridland.net>
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 0AA6421F99F6 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 14:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.946
X-Spam-Level: 
X-Spam-Status: No, score=-1.946 tagged_above=-999 required=5 tests=[AWL=0.031,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 lPzHOlVRgDw9 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 14:27:30 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 0941721F96EB for <ietf@ietf.org>; Tue, 11 Jun 2013 14:27:29 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id wo10so12496363obc.17 for <ietf@ietf.org>; Tue, 11 Jun 2013 14:27:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wPl+4tKoWaPmfIhwx6V2mUgz08JnSlInLY8yciI9p+8=; b=LeTSzLU+YfF15j2Q50f6F+02yqqx80KfzGVab11e8R/QU7SnF8GzkWJLZ899hGWl0B Dm1dqF78IiBwzFlrVlWq4BeFGblNN4TyGZx3d/VBV12QNEbvPCXlJm38qQMq3PQV9ldZ I6GlVl/toPEHubbWclkEjXV1IOdG4WgT/RRjc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=wPl+4tKoWaPmfIhwx6V2mUgz08JnSlInLY8yciI9p+8=; b=JvxWSj5TNhzFobsiRVTI2AfDoOLoC1I8cHiurwW6xoIN3QNq4ynsc/8ySfLM5/d9pn UpU3abVJMFaBrUzpzu5kJBwYWRIAqUx/NDzKGcysTnH6lbaAuRGmkzwWABCXjw74WK2z GqNSSntkWZXN14gBn8C6CrwMT8OasBcLIJuiSR3y7QNaD6riAArYcugDGm0yMOWxA5Uf 0oSrOQkdh+EE7qbh4dkIs4a3vuTmVG3fnmWxu9O/+bqssV/lQtzHdwO6Dh//qrshbu6O f2433NXcXo/bg3KhNoKLSSG4lyJgONbvOnn6O0iapdzmiV1vEggSc36RIUnQ7iQVLafI roNA==
MIME-Version: 1.0
X-Received: by 10.60.33.4 with SMTP id n4mr13027213oei.49.1370986049368; Tue, 11 Jun 2013 14:27:29 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Tue, 11 Jun 2013 14:27:29 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com>
Date: Tue, 11 Jun 2013 22:27:29 +0100
Message-ID: <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com>
Subject: Re: Content-free Last Call comments
From: Dave Cridland <dave@cridland.net>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=089e011619f67705c604dee790e6
X-Gm-Message-State: ALoCoQkKdq1OW81Brb5N59vhUR5F28i+YSq/LUiWSEyamvQdKiAXqj0wzTQuK1KL9Wjdsgnfyacz
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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: Tue, 11 Jun 2013 21:27:32 -0000

--089e011619f67705c604dee790e6
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 11, 2013 at 9:33 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

>  On Jun 11, 2013, at 4:24 PM, Dave Cridland <dave@cridland.net> wrote:
>
>  But more seriously, what are you expecting Russ to do? What did you want
> him to write?
>
>  If your answer is "Nothing", then how do you read IETF consensus for a
> document that gets no response in its Last Call? The XSF's stance is often
> "It got nothing in Last Call, it shouldn't advance", which seems reasonable
> to me - I don't think defaulting to publication is right - certainly not in
> every case.
>
>  My suggestion was simply to ask for what you want in the Last Call.
>
>
> I have a modest suggestion for you: read the rest of the message from Pete
> that you just replied to, in which he answers each of the questions you
> asked in your reply.
>
>

If he did, either I am sufficiently stupid I cannot make it out, or he did
so sufficiently obliquely that I can't see - depending on where you want to
place the blame. Either way, I've tried to parse out potential responses
(again), and the closest I can come (again) is that Pete seems to want
nothing from Russ in this instance, and indeed, in any instance from any
person except objections. This is not clear to me, however, and therefore
I'd appreciate some clarification, which is why I asked.

That in turn presumes we are defaulting to publication in all cases, and
that in turn seems problematic to me, because his answers become, in order:

a) Russ, and by extension anyone who supports the document's publication
for whatever reason, is expected to do nothing.

b) Russ, and by extension anyone who supports the document's publication
for whatever reason, should write nothing.

c) IETF-wide consensus is not judged here. IETF-wide apathy is IETF-wide
consensus.

My conclusion from that are:

1) Pete strongly supports publish-by-default.

2) Pete has his RFC 7000 sweepstake money on a much earlier date than I do.

Dave.

--089e011619f67705c604dee790e6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jun 11, 2013 at 9:33 PM, Ted Lemon <span dir=3D"lt=
r">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com" target=3D"_blank">Ted.Lemon=
@nominum.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word"><div class=3D"im">
<div>
<div>On Jun 11, 2013, at 4:24 PM, Dave Cridland &lt;<a href=3D"mailto:dave@=
cridland.net" target=3D"_blank">dave@cridland.net</a>&gt; wrote:</div>
<blockquote type=3D"cite">
<div style=3D"font-family:Optima;font-size:medium;font-style:normal;font-va=
riant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;te=
xt-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px">

But more seriously, what are you expecting Russ to do? What did you want hi=
m to write?</div>
<div style=3D"font-family:Optima;font-size:medium;font-style:normal;font-va=
riant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;te=
xt-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px">

<br>
</div>
<div style=3D"font-family:Optima;font-size:medium;font-style:normal;font-va=
riant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;te=
xt-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px">

If your answer is &quot;Nothing&quot;, then how do you read IETF consensus =
for a document that gets no response in its Last Call? The XSF&#39;s stance=
 is often &quot;It got nothing in Last Call, it shouldn&#39;t advance&quot;=
, which seems reasonable to me - I don&#39;t think defaulting to
 publication is right - certainly not in every case.</div>
<div style=3D"font-family:Optima;font-size:medium;font-style:normal;font-va=
riant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;te=
xt-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px">

<br>
</div>
<div style=3D"font-family:Optima;font-size:medium;font-style:normal;font-va=
riant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;te=
xt-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px">

My suggestion was simply to ask for what you want in the Last Call.</div>
</blockquote>
</div>
<br>
</div><div>I have a modest suggestion for you: read the rest of the message=
 from Pete that you just replied to, in which he answers each of the questi=
ons you asked in your reply.</div>
<div><br></div></div></blockquote><div><br></div><div><br></div><div style>=
If he did, either I am sufficiently stupid I cannot make it out, or he did =
so sufficiently obliquely that I can&#39;t see - depending on where you wan=
t to place the blame. Either way, I&#39;ve tried to parse out potential res=
ponses (again), and the closest I can come (again) is that Pete seems to wa=
nt nothing from Russ in this instance, and indeed, in any instance from any=
 person except objections. This is not clear to me, however, and therefore =
I&#39;d appreciate some clarification, which is why I asked.</div>
<div style><br></div><div style>That in turn presumes we are defaulting to =
publication in all cases, and that in turn seems problematic to me, because=
 his answers become, in order:</div><div style><br></div><div style>a) Russ=
, and by extension anyone who supports the document&#39;s publication for w=
hatever reason, is expected to do nothing.</div>
<div style><br></div><div style>b) Russ, and by extension anyone who suppor=
ts the document&#39;s publication for whatever reason, should write nothing=
.</div><div style><br></div><div style>c) IETF-wide consensus is not judged=
 here. IETF-wide apathy is IETF-wide consensus.</div>
<div style><br></div><div style>My conclusion from that are:</div><div styl=
e><br></div><div style>1) Pete strongly supports publish-by-default.</div><=
div style><br></div><div style>2) Pete has his RFC 7000 sweepstake money on=
 a much earlier date than I do.</div>
<div style><br></div><div style>Dave.</div></div></div></div>

--089e011619f67705c604dee790e6--

From dhc@dcrocker.net  Tue Jun 11 14:33:26 2013
Return-Path: <dhc@dcrocker.net>
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 ADA1121F9A33 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 14:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.307
X-Spam-Level: 
X-Spam-Status: No, score=-5.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4]
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 LkLItYsyt07J for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 14:33:21 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C538921F8904 for <ietf@ietf.org>; Tue, 11 Jun 2013 14:33:21 -0700 (PDT)
Received: from [10.2.4.14] ([64.9.249.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5BLXINC025405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Tue, 11 Jun 2013 14:33:21 -0700
Message-ID: <51B79798.9070507@dcrocker.net>
Date: Tue, 11 Jun 2013 14:33:12 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
CC: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Content-free Last Call comments
References: <20130611174332.79781.qmail@joyce.lan> <51B763C1.1050205@dougbarton.us> <8D23D4052ABE7A4490E77B1A012B6307751D1222@mbx-01.win.nominum.com> <51B78D79.7010807@dougbarton.us>
In-Reply-To: <51B78D79.7010807@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 11 Jun 2013 14:33:21 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Tue, 11 Jun 2013 21:33:26 -0000

On 6/11/2013 1:50 PM, Doug Barton wrote:
>
> As I understand it cross-disciplinary review is also an important
> function of the IETF LC.


This gets at the reality that the current IETF uses processing phases 
rather more robustly than we used to.  It certainly used to be that IETF 
LC was essentially a last chance for people with objections, but now 
it's a full round of broad reviews.  It is, therefore, a real vetting 
phase by the larger community.  As such, positive comments can be as 
valuable as negative, but of course only if they are backed with substance.

Possibly contrary to Pete's stated preference, I'll suggest that 
statements of pure support -- backed up with substantive commentary -- 
can be useful, given the low level of activity and involvement many 
working groups currently show.

To the extent that the IETF cares whether anyone beyond the authors care 
about the document, this shows that they do.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From mthornbu@adobe.com  Tue Jun 11 14:52:04 2013
Return-Path: <mthornbu@adobe.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 8707821F9A27 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 14:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ZMRMN8CiKJ0H for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 14:51:58 -0700 (PDT)
Received: from exprod6og124.obsmtp.com (exprod6og124.obsmtp.com [64.18.1.242]) by ietfa.amsl.com (Postfix) with ESMTP id EE36321F9A1D for <ietf@ietf.org>; Tue, 11 Jun 2013 14:51:54 -0700 (PDT)
Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob124.postini.com ([64.18.5.12]) with SMTP ID DSNKUbeb8RpqCL5zIZQobJK7wQLDaIaCq/bS@postini.com; Tue, 11 Jun 2013 14:51:55 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5BLmPD8029042; Tue, 11 Jun 2013 14:48:25 -0700 (PDT)
Received: from nahub01.corp.adobe.com (nahub01.corp.adobe.com [10.8.189.97]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5BLpi6A023554; Tue, 11 Jun 2013 14:51:44 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by nahub01.corp.adobe.com ([10.8.189.97]) with mapi; Tue, 11 Jun 2013 14:51:44 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 11 Jun 2013 14:51:39 -0700
Subject: RE: Last Call: <draft-thornburgh-adobe-rtmfp-07.txt> (Adobe's Secure Real-Time Media Flow Protocol) to Informational RFC
Thread-Topic: Last Call: <draft-thornburgh-adobe-rtmfp-07.txt> (Adobe's Secure Real-Time Media Flow Protocol) to Informational RFC
Thread-Index: Ac5iDsdOE9T0tj2JTVOxIWZ/6rLGngE3cnYA
Message-ID: <D9D602D39A98E34D9C43E965BEC7439825F201E3@nambx08.corp.adobe.com>
References: <20130528161229.25215.37302.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130605072309.0be62c30@resistor.net>
In-Reply-To: <6.2.5.6.2.20130605072309.0be62c30@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 11 Jun 2013 21:52:04 -0000

hi SM. thanks for your comments.  sorry for the delay in response; i was on=
 vacation and unable to reply.  replies inline.

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
M
> Sent: Wednesday, June 05, 2013 9:13 AM
>=20
> At 09:12 28-05-2013, The IESG wrote:
> >The IESG has received a request from an individual submitter to consider
> >the following document:
> >- 'Adobe's Secure Real-Time Media Flow Protocol'
> >   <draft-thornburgh-adobe-rtmfp-07.txt> as Informational RFC
> >
> >The IESG plans to make a decision in the next few weeks, and solicits
> >final comments on this action. Please send substantive comments to the
> >ietf@ietf.org mailing lists by 2013-06-25. Exceptionally, comments may b=
e
>=20
> The write-up mentions that:
>=20
>    "As a private protocol, no technical changes were performed on the
>     protocol itself, but the authors disclosed more details in
>     response to the WG discussions."
>=20
> I don't see why this specification requires IETF consensus as it is
> not possible to suggest any major changes.  The explanation given for
> the intended status is that the aspects of the protocol protected by
> IPR were not reviewed externally.

the intended status is Informational because the specification describes a =
protocol that was developed outside the IETF, the protocol is in widespread=
 use in the Internet today, and may be of interest to the Internet communit=
y.  the Shepherd write-up does not draw any connection (nor is there any co=
nnection) between the intended Informational status and the existence of IP=
R.  aspects of the protocol that are protected by IPR are disclosed in the =
specification and are (and have been) available for the review of the commu=
nity.  the relevant IPR was disclosed (IPR 1942) immediately after draft -0=
0 was submitted.

my understanding of the "A-D Sponsored" process for an Informational track =
document is that the IETF Last Call should serve as a final check with the =
IETF community that there are no important concerns that have been missed o=
r misunderstood. as this protocol and specification are not products of an =
IETF WG, technical changes to the protocol itself are not expected; however=
, the specification should be clear and complete enough that an independent=
 and interoperable implementation could be created from it.  i have receive=
d thorough and detailed feedback from several members of the community that=
 i believe has helped me improve the quality and clarity of the specificati=
on.

in the course of face-to-face discussion at IETF-86 in the TSVWG meeting, i=
 was prompted to disclose additional detail and supplementary information a=
bout the protocol, which i believe improves the clarity of the specificatio=
n.

> The summary is that there is a memo which is not a WG memo, which is
> supposed to have gained WG consensus, where some group is supposed to
> consider the IPR disclosure, and which is being Last-Called as an
> Individual Submission.  I would like to be considered as not part of
> the consensus.

the memo (and the protocol it describes) is not the product of a WG.  the p=
rotocol was presented in person at IETF-77 (in the TSV Area meeting) and IE=
TF-86 (in the TSVWG meeting), and feedback was solicited on the TSVWG and M=
MUSIC mailing lists.  at this time i am not aware of any unaddressed concer=
ns regarding this specification, with the exception of your following comme=
nt that i am about to address.

> Nits:
>=20
>    "At the time of writing, the Adobe Flash Player runtime is
>     installed on more than one billion end-user desktop computers."
>=20
> Shouldn't the memo be about the protocol?

agreed.  i included this statement at the suggestion of the Responsible (an=
d Sponsoring) Area Director, to help establish the breadth of deployment of=
 the protocol, and therefore the relevance of the specification in the RFC =
Series as an independent submission.  the Shepherd, A-D and i are discussin=
g your concern regarding this statement off-list.  possible solutions are: =
move this comment to the Shepherd write-up for the IESG's consideration, ch=
ange the wording to be more neutral, leave as-is or strike it completely.

> Regards,
> -sm

thanks.

-michael thornburgh


From Ted.Lemon@nominum.com  Tue Jun 11 14:55:02 2013
Return-Path: <Ted.Lemon@nominum.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 B030A21F99BA for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 14:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.621
X-Spam-Level: 
X-Spam-Status: No, score=-106.621 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 B6X5jExDfZJD for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 14:54:56 -0700 (PDT)
Received: from exprod7og129.obsmtp.com (exprod7og129.obsmtp.com [64.18.2.122]) by ietfa.amsl.com (Postfix) with ESMTP id 06BC321F94D3 for <ietf@ietf.org>; Tue, 11 Jun 2013 14:54:29 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob129.postini.com ([64.18.6.12]) with SMTP ID DSNKUbeclV0KvnRvz3kh3JqV/MK3XG4Sd5Q+@postini.com; Tue, 11 Jun 2013 14:54:30 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 764B91B81DB for <ietf@ietf.org>; Tue, 11 Jun 2013 14:54:29 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6C1E119005D; Tue, 11 Jun 2013 14:54:29 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 11 Jun 2013 14:54:23 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dave Cridland <dave@cridland.net>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkwIJIAgAFBKYCAAAqfAIAAAp+AgAAPHoCAAAeDAA==
Date: Tue, 11 Jun 2013 21:54:22 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com>
In-Reply-To: <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5F05C85A7E779D4F913D108C3C1F5C1E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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: Tue, 11 Jun 2013 21:55:02 -0000

On Jun 11, 2013, at 5:27 PM, Dave Cridland <dave@cridland.net> wrote:
> That in turn presumes we are defaulting to publication in all cases, and =
that in turn seems problematic to me, because his answers become, in order:
> a) Russ, and by extension anyone who supports the document's publication =
for whatever reason, is expected to do nothing.
> b) Russ, and by extension anyone who supports the document's publication =
for whatever reason, should write nothing.
> c) IETF-wide consensus is not judged here. IETF-wide apathy is IETF-wide =
consensus.

It is presumed that some degree of consensus to do the work of a working gr=
oup existed when that working group was chartered; otherwise it would not h=
ave been chartered.   When the working group reaches consensus to publish, =
therefore, it is assumed that the IETF has consensus to publish the documen=
t, because the IETF tasked the working group to go off and do its work, and=
 the working group did it.

Therefore, silence during IETF last call is not interpreted as apathy, but =
rather a lack of objection to the completion of a process that the IETF cho=
se to embark on and that the IETF has brought to completion, through the in=
strument of the working group that produced the document.

This is in fact how consensus is evaluated during IETF last call.   If you =
think it should be done differently, write up a document and get IETF conse=
nsus on it, and we can change the procedure to whatever you think it should=
 be.   Maybe it would be an improvement.


From elwynd@dial.pipex.com  Tue Jun 11 15:03:26 2013
Return-Path: <elwynd@dial.pipex.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 AEB8321F9A51 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 15:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 JdIYu88f0E8N for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 15:03:03 -0700 (PDT)
Received: from mk-outboundfilter-6.mail.uk.tiscali.com (mk-outboundfilter-6.mail.uk.tiscali.com [212.74.114.14]) by ietfa.amsl.com (Postfix) with ESMTP id 2F3C721F9A4B for <ietf@ietf.org>; Tue, 11 Jun 2013 15:03:03 -0700 (PDT)
X-Trace: 575756066/mk-outboundfilter-6.mail.uk.tiscali.com/PIPEX/$OFF_NET_AUTH_ACCEPTED/None/81.187.254.249/None/elwynd@dial.pipex.com
X-SBRS: None
X-RemoteIP: 81.187.254.249
X-IP-MAIL-FROM: elwynd@dial.pipex.com
X-SMTP-AUTH: elwynd@dial.pipex.com
X-Originating-Country: GB/UNITED KINGDOM
X-MUA: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsoIADiet1FRu/75/2dsb2JhbABZhna4XYJ0BAQBgReDFwEBBSMVQAEQCw4KAgIFFgsCAgkDAgECAUUGDQEHAQGIDahokT2BJo4MB4JMgRQDl0CGDIs2gxA
X-IronPort-AV: E=Sophos;i="4.87,847,1363132800"; d="scan'208";a="575756066"
X-IP-Direction: OUT
Received: from weee-pc2.folly.org.uk (HELO [81.187.254.249]) ([81.187.254.249]) by smtp.pipex.tiscali.co.uk with ESMTP; 11 Jun 2013 23:02:55 +0100
Message-ID: <51B79E8D.8000200@dial.pipex.com>
Date: Tue, 11 Jun 2013 23:02:53 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>
In-Reply-To: <51B63905.2020807@qti.qualcomm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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: Tue, 11 Jun 2013 22:03:28 -0000

On 10/06/13 21:37, Pete Resnick wrote:
> Russ, our IAB chair and former IETF chair, just sent a message to the 
> IETF list regarding a Last Call on draft-ietf-pkix-est. Here is the 
> entire contents of his message, save quoting the whole Last Call request:
>
> On 6/10/13 1:45 PM, Russ Housley wrote:
>> I have read the document, I a support publication on the standards 
>> track.
>>
>> Russ
>
Pete,

I write gen-art reviews.  A proportion of them at IETF Last Call, give 
or take a bunch of boilerplate, consist of the word 'Ready'*.

How do you distinguish the usefulness (or otherwise) of such a review 
from Russ' one liner?

/Elwyn

* and some of the others say 'Not ready' followed by some or many lines 
of comments.

From dave@cridland.net  Tue Jun 11 15:03:39 2013
Return-Path: <dave@cridland.net>
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 91E6721F9A51 for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 15:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.951
X-Spam-Level: 
X-Spam-Status: No, score=-1.951 tagged_above=-999 required=5 tests=[AWL=0.026,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 TOEzERSorbIq for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 15:03:37 -0700 (PDT)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3FB21F9A4B for <ietf@ietf.org>; Tue, 11 Jun 2013 15:03:36 -0700 (PDT)
Received: by mail-ob0-f180.google.com with SMTP id eh20so12153292obb.25 for <ietf@ietf.org>; Tue, 11 Jun 2013 15:03:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hrPycYCFX8cZg5VEz5XP1jhvlPMmbRjDLXdr792cAIk=; b=i9fEMVIXwdtP/71ggNBRFrTlOpB5Tunil9qUMlXg4OPDgxgPW6EYdkrX5/MqUdunnX AMbBxjueyvWvv8SUED099zVL+4qD5wXgdZSPTH7Pd0aUwOVPxb4TeajHVCFBzGfTg9gu GDa+NZ6NmrWIjAWpMqXgHx+sok8VFKH0SBTeI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=hrPycYCFX8cZg5VEz5XP1jhvlPMmbRjDLXdr792cAIk=; b=e1AK5PnKAYO52FqUoiZPSEoEi23JOrn9/WCOpbcA2+RLltmMi7DHaAqfJ2KlIPbC0V BQ4szJ4R8Zi3HfNhXKNDNyt35+SseHn5saXFb9mdoa84CptniRPUGRjl1Tf/uoMiq+zl wMgo/Uc0Cs6c4f8Qpa1XyMRQ2pJKOW9QxoA/2/JikCuIlcKyS5KM6wbrEM5z5LrwgLeQ tuKZPzkX2W2C8sqA/zNIulJx+QvE93vBPgnf80QjnV0sW/UZCPbY8oq81Y8cDzXKH1YJ xJ1zAk9o6nY4aiNPfr0Qyb0vRecbYzSjNNT32Fz+/SXsVuh+BiHWoeLQFQpRAgDHiQG1 yedw==
MIME-Version: 1.0
X-Received: by 10.182.86.6 with SMTP id l6mr13299748obz.6.1370988215497; Tue, 11 Jun 2013 15:03:35 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Tue, 11 Jun 2013 15:03:35 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com>
Date: Tue, 11 Jun 2013 23:03:35 +0100
Message-ID: <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com>
Subject: Re: Content-free Last Call comments
From: Dave Cridland <dave@cridland.net>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=089e0149c468938cca04dee8110e
X-Gm-Message-State: ALoCoQkIaILOsJDWHnP9exqKLc/51/rE443yJ6hlh+535zwPDzOgYbmp4CY5SoYV4niTsAok0LW0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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: Tue, 11 Jun 2013 22:03:39 -0000

--089e0149c468938cca04dee8110e
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 11, 2013 at 10:54 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> It is presumed that some degree of consensus to do the work of a working
> group existed when that working group was chartered; otherwise it would not
> have been chartered.   When the working group reaches consensus to publish,
> therefore, it is assumed that the IETF has consensus to publish the
> document, because the IETF tasked the working group to go off and do its
> work, and the working group did it.
>
> Therefore, silence during IETF last call is not interpreted as apathy, but
> rather a lack of objection to the completion of a process that the IETF
> chose to embark on and that the IETF has brought to completion, through the
> instrument of the working group that produced the document.
>
> This is in fact how consensus is evaluated during IETF last call.


That's interesting - judging by the messages on this thread, there doesn't
appear to be a strong consensus on this...


>   If you think it should be done differently, write up a document and get
> IETF consensus on it, and we can change the procedure to whatever you think
> it should be.   Maybe it would be an improvement.
>
>
... and how would we judge IETF consensus on a document that doesn't get
done under a charter (which would in turn have been granted consensus
without any IETF comments?)

--089e0149c468938cca04dee8110e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jun 11, 2013 at 10:54 PM, Ted Lemon <span dir=3D"ltr">&lt;<=
a href=3D"mailto:Ted.Lemon@nominum.com" target=3D"_blank">Ted.Lemon@nominum=
.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><span style=3D"color:rgb(3=
4,34,34)">It is presumed that some degree of consensus to do the work of a =
working group existed when that working group was chartered; otherwise it w=
ould not have been chartered. =A0 When the working group reaches consensus =
to publish, therefore, it is assumed that the IETF has consensus to publish=
 the document, because the IETF tasked the working group to go off and do i=
ts work, and the working group did it.</span><br>
</div>
<br>
Therefore, silence during IETF last call is not interpreted as apathy, but =
rather a lack of objection to the completion of a process that the IETF cho=
se to embark on and that the IETF has brought to completion, through the in=
strument of the working group that produced the document.<br>

<br>
This is in fact how consensus is evaluated during IETF last call.</blockquo=
te><div><br></div><div style>That&#39;s interesting - judging by the messag=
es on this thread, there doesn&#39;t appear to be a strong consensus on thi=
s...</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"> =A0 If you think it should be=
 done differently, write up a document and get IETF consensus on it, and we=
 can change the procedure to whatever you think it should be. =A0 Maybe it =
would be an improvement.<br>

<br>
</blockquote></div><br></div><div class=3D"gmail_extra" style>... and how w=
ould we judge IETF consensus on a document that doesn&#39;t get done under =
a charter (which would in turn have been granted consensus without any IETF=
 comments?)</div>
</div>

--089e0149c468938cca04dee8110e--

From Ted.Lemon@nominum.com  Tue Jun 11 15:20:39 2013
Return-Path: <Ted.Lemon@nominum.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 5B4B821F9A4A for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 15:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.62
X-Spam-Level: 
X-Spam-Status: No, score=-106.62 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 wTEIg2N3iWYW for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 15:20:31 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 7529821F9A2E for <ietf@ietf.org>; Tue, 11 Jun 2013 15:20:30 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUbeirgeWxSlRfTAhHIdSnZpDNtT/C6Hn@postini.com; Tue, 11 Jun 2013 15:20:30 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 071171B81DB for <ietf@ietf.org>; Tue, 11 Jun 2013 15:20:30 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F3E0119005D; Tue, 11 Jun 2013 15:20:29 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 11 Jun 2013 15:20:30 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dave Cridland <dave@cridland.net>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkwIJIAgAFBKYCAAAqfAIAAAp+AgAAPHoCAAAeDAIAAApOAgAAEuAA=
Date: Tue, 11 Jun 2013 22:20:28 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com> <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com>
In-Reply-To: <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751D1AB6mbx01winnominum_"
MIME-Version: 1.0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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: Tue, 11 Jun 2013 22:20:39 -0000

--_000_8D23D4052ABE7A4490E77B1A012B6307751D1AB6mbx01winnominum_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Jun 11, 2013, at 6:03 PM, Dave Cridland <dave@cridland.net<mailto:dave@c=
ridland.net>> wrote:
... and how would we judge IETF consensus on a document that doesn't get do=
ne under a charter (which would in turn have been granted consensus without=
 any IETF comments?)

I would expect that you'd start with a mailing list, see if there is intere=
st, come up with a proposal for a BOF, come up with a working group charter=
, get IESG review on the charter, then get IETF consensus on the charter, a=
nd then start working on the document.   That's how it's usually done.

BTW, the fact that a few people think the process ought to work differently=
 does not mean there is consensus for it to work differently.   Also, what =
there may not be consensus on among the people who have weighed in on the t=
opic is whether positive statements in favor of a document are relevant in =
IETF last call, but I don't really know how to reduce that to practice, bec=
ause in reality I think it is rare for a quorum of IETF participants to rea=
d a document as a consequence of a last call announcement.   Without that, =
I don't see how you can have any other last call process than the one we cu=
rrently have.


--_000_8D23D4052ABE7A4490E77B1A012B6307751D1AB6mbx01winnominum_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <C184621E29A75A42848863AEBA3FD24B@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Jun 11, 2013, at 6:03 PM, Dave Cridland &lt;<a href=3D"mailto:dave@=
cridland.net">dave@cridland.net</a>&gt; wrote:</div>
<blockquote type=3D"cite"><span style=3D"font-family: Optima; font-size: me=
dium; font-style: normal; font-variant: normal; font-weight: normal; letter=
-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto=
; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; w=
ord-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width=
: 0px; display: inline !important; float: none; ">...
 and how would we judge IETF consensus on a document that doesn't get done =
under a charter (which would in turn have been granted consensus without an=
y IETF comments?)</span></blockquote>
</div>
<br>
<div>I would expect that you'd start with a mailing list, see if there is i=
nterest, come up with a proposal for a BOF, come up with a working group ch=
arter, get IESG review on the charter, then get IETF consensus on the chart=
er, and then start working on the
 document. &nbsp; That's how it's usually done.</div>
<div><br>
</div>
<div>BTW, the fact that a few people think the process ought to work differ=
ently does not mean there is consensus for it to work differently. &nbsp; A=
lso, what there may not be consensus on among the people who have weighed i=
n on the topic is whether positive statements
 in favor of a document are relevant in IETF last call, but I don't really =
know how to reduce that to practice, because in reality I think it is rare =
for a quorum of IETF participants to read a document as a consequence of a =
last call announcement. &nbsp; Without
 that, I don't see how you can have any other last call process than the on=
e we currently have.</div>
<div><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307751D1AB6mbx01winnominum_--

From turners@ieca.com  Tue Jun 11 16:13:18 2013
Return-Path: <turners@ieca.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 75A1F21F9B8F for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 16:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.205
X-Spam-Level: 
X-Spam-Status: No, score=-102.205 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 MxqujSNFteYX for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 16:13:12 -0700 (PDT)
Received: from gateway16.websitewelcome.com (gateway16.websitewelcome.com [69.93.82.10]) by ietfa.amsl.com (Postfix) with ESMTP id 363F621F9B8E for <ietf@ietf.org>; Tue, 11 Jun 2013 16:13:12 -0700 (PDT)
Received: by gateway16.websitewelcome.com (Postfix, from userid 5007) id 4F6B552DD8110; Tue, 11 Jun 2013 18:12:48 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway16.websitewelcome.com (Postfix) with ESMTP id 3F92452DD80CD for <ietf@ietf.org>; Tue, 11 Jun 2013 18:12:48 -0500 (CDT)
Received: from [173.73.135.101] (port=50637 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1UmXkV-0001sn-EP; Tue, 11 Jun 2013 18:13:11 -0500
Message-ID: <51B7AF06.4060708@ieca.com>
Date: Tue, 11 Jun 2013 19:13:10 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-pkix-est-07.txt> (Enrollment over Secure Transport) to Proposed Standard
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130611000605.0b853d00@resistor.net>
In-Reply-To: <6.2.5.6.2.20130611000605.0b853d00@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (thunderfish.local) [173.73.135.101]:50637
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: 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: Tue, 11 Jun 2013 23:13:18 -0000

On 6/11/13 4:30 AM, SM wrote:
> At 07:45 10-06-2013, The IESG wrote:
>> The IESG has received a request from the Public-Key Infrastructure
>> (X.509) WG (pkix) to consider the following document:
>> - 'Enrollment over Secure Transport'
>>   <draft-ietf-pkix-est-07.txt> as Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-06-24. Exceptionally, comments may be
>
> There weren't any comments during the WGLC of draft-ietf-pkix-est-06.
> The AD review of draft-ietf-pkix-est-06 was posted to the mailing list
> and the only comments after that was "this version address my concerns".

PKIX is closing down; this is the final draft.  Has the wg lost a bit of 
its furor yes.  Mostly, the way things have worked in the recent past is 
that either people are for something and have some nice conversations 
about this or that improvement and wglc is quiet or people think the 
world is ending by publishing a draft and they object during authoring, 
wglc, and ietf lc.  This one falls in to the earlier bucket.

> I read the document.  It is about the use of an obsolete Proposed
> Standard or later versions of that specification.

This bit I don't agree with.  PKCS#10 is the way most PKI enrollments 
occur.  RFC 2986, which is where PKCS#10 is documented, is updated by 
RFC 5967 because the draft that contained the media-type registration 
was obsoleted.

This draft is a nod to the fact that PKCS#10 is the way it's done and 
it's one via the web (not email) with TLS as the secure transport (not 
S/MIME/CMS).  The kicker here is that it's actually been implemented and 
not just by the authors.

As for the TLS version, well I'm hoping 1.1 will be overtaken by events 
in short order but that compromise has been worked out and documented in 
a number of drafts.

>  The comments from
> three individuals who happen to be Area Directors creates a conundrum;
> should I give more weight to them or to a content-free comment?  I do
> not support the publication of this document as a Proposed Standard as
> it is doubtful that it has the consensus of the working group.

There has been discussion about this draft on the list albeit not much. 
  Definitely discussions at the meetings where it's been an agenda topic 
at IETF 82, 83, 85, and 86.

spt



From randy@psg.com  Tue Jun 11 18:13:33 2013
Return-Path: <randy@psg.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 5576A21F9B8C for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 18:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599]
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 0vG5CfMX6c7O for <ietf@ietfa.amsl.com>; Tue, 11 Jun 2013 18:13:32 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id E510B21F9B42 for <ietf@ietf.org>; Tue, 11 Jun 2013 18:13:32 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UmZcp-000H7a-J1; Wed, 12 Jun 2013 01:13:24 +0000
Date: Wed, 12 Jun 2013 03:13:20 +0200
Message-ID: <m2wqq0ku6n.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Content-free Last Call comments
In-Reply-To: <51B77602.80903@gmail.com>
References: <20130611174332.79781.qmail@joyce.lan> <51B763C1.1050205@dougbarton.us> <51B77602.80903@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <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, 12 Jun 2013 01:13:33 -0000

> Right.  We've had some issues with document quality, and I
> can think of several documents that sailed through WG last
> call and should not have.

there was a doc with which i had a small, but non trivial, issue.  the
author and the wg did not think it worthwhile.  i did not want to argue
endlessly, so i waited and raised it to the iesg at last call, and they
understood it instantly.  the author made the small change to the doc.
i said thank you.

i am sure we can make a constitutional crisis over this if we have too
much time on our hands.

randy

From dave@cridland.net  Wed Jun 12 01:43:49 2013
Return-Path: <dave@cridland.net>
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 4AEA921F9BF1 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 01:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.954
X-Spam-Level: 
X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[AWL=0.023,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 MkCa7y9kqylK for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 01:43:48 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 4474D21F9BEA for <ietf@ietf.org>; Wed, 12 Jun 2013 01:43:48 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id va7so12815202obc.41 for <ietf@ietf.org>; Wed, 12 Jun 2013 01:43:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7S81rd6SlSslyQIIn12dsA0F1APUZbowsxwCtjECXxs=; b=WghNUXIe3mOeGPzEv5fxRkKGx3oDP9Unk2aTiw1fdZ94rDV86TirtPqR4pdmqH7H0M MaSYBE9QXm4ypmzRYlUVirOaHFwXW0WMzg5sV1i+og6Mph9Sb4Q3wIOIN1oThOb+8Cau tKcNb1VTkSLQ+vYR7LehgPtl/BoGs75z6OGbg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=7S81rd6SlSslyQIIn12dsA0F1APUZbowsxwCtjECXxs=; b=KD3meUYPH8EOOTRs6oddQlRVKTa6vl9FNZr+FoceakLOz346vkr5gZjOGBuuXUIPg3 N1X99poBTvLvB+t9WmVmP+oKHc1wVna29EiSdT1Cm2S+I46Ko7lWhl9wIdKON63XFUyp ma9xi6M4cnlA1hn9jM46GfhJlkOtqCbvYFOfUuLFPy4Nu4/tplJeOapPr3Bck9ZSKZlZ iZL7+wjKJn6qT0k2jwJBuRaUMdaqQuOX+YamgR2rBo6ZQgazUmWZ13jyRFesK+kHB66D UzHrnerV2pDMEK9Q5gRj0dxEqpkgoCkpuq8ZmXcw2Ildj4BpQv5QZmkRBL78i1I9eajK X60w==
MIME-Version: 1.0
X-Received: by 10.60.119.65 with SMTP id ks1mr15024551oeb.43.1371026624067; Wed, 12 Jun 2013 01:43:44 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Wed, 12 Jun 2013 01:43:43 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com> <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com>
Date: Wed, 12 Jun 2013 09:43:43 +0100
Message-ID: <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com>
Subject: Re: Content-free Last Call comments
From: Dave Cridland <dave@cridland.net>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=047d7b3a9792e7cc0304def10278
X-Gm-Message-State: ALoCoQl4bl6kAv8xUav9FLd//SIhE3fAO19t4FYlQ6B1wkHryhtO5yMqROvL+ST1hIs3efuWTbY9
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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, 12 Jun 2013 08:43:49 -0000

--047d7b3a9792e7cc0304def10278
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 11, 2013 at 11:20 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

>  On Jun 11, 2013, at 6:03 PM, Dave Cridland <dave@cridland.net> wrote:
>
> ... and how would we judge IETF consensus on a document that doesn't get
> done under a charter (which would in turn have been granted consensus
> without any IETF comments?)
>
>
> I would expect that you'd start with a mailing list, see if there is
> interest, come up with a proposal for a BOF, come up with a working group
> charter, get IESG review on the charter, then get IETF consensus on the
> charter, and then start working on the document.   That's how it's usually
> done.
>
>
I think you misread entirely.

But anyway, let's assume we follow those steps.

I suspect the closest we get to getting an idea of IETF consensus is the
interest gauging at the beginning of the process, though interestingly this
is only positive interest - objections to doing the work at all aren't
really relevant here. The IETF consensus on the charter is handled by
Apathy Is Assent rules, so claiming that this consensus call becomes the
default is an interesting argument to make.

 BTW, the fact that a few people think the process ought to work
> differently does not mean there is consensus for it to work differently.
> Also, what there may not be consensus on among the people who have weighed
> in on the topic is whether positive statements in favor of a document are
> relevant in IETF last call, but I don't really know how to reduce that to
> practice, because in reality I think it is rare for a quorum of IETF
> participants to read a document as a consequence of a last call
> announcement.   Without that, I don't see how you can have any other last
> call process than the one we currently have.
>
>
OK, so we don't have voting but we do have a quorum? How wonderful. And
given that the majority of people are silent means they agree (with, mind,
everything - not just that they're not reading), so any number of people
are therefore "few".

But to loop around:

I strongly feel that positive statements have value, as they allow the
community to gauge the level of review and consensus, and I suspect that
human nature means that we get more reviews if people get to brag about it.
I suggest that if more than one bit of data is required, it's simply asked
for. Given that the text of IETF Last Call announcements is not governed by
any process RFC that I'm aware of (feel free to correct), I suggest simply
putting a set of optional questions there. I note this practise has served
the XSF very well. I do not think this needs an endless bikeshed discussion
on what questions; the IESG can pick what it wants to know.

If, on the other hand, only objections are sought, then the text (which
simply asks for "comments") also needs changing. And the GenArt, AppsDir,
and SecDir reviews should only be send when they have objections to
publication, of course.

If you feel that the only way to make either change is to form a working
group and publish an RFC to change something undocumented in the series,
then I think we're stranded in a bureaucratic quagmire with no chance of
escape, but I'll be happy to send "comments", as requested, nonetheless.

--047d7b3a9792e7cc0304def10278
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jun 11, 2013 at 11:20 PM, Ted Lemon <span dir=3D"ltr">&lt;<=
a href=3D"mailto:Ted.Lemon@nominum.com" target=3D"_blank">Ted.Lemon@nominum=
.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word"><div class=3D"im">
<div>
<div>On Jun 11, 2013, at 6:03 PM, Dave Cridland &lt;<a href=3D"mailto:dave@=
cridland.net" target=3D"_blank">dave@cridland.net</a>&gt; wrote:</div>
<blockquote type=3D"cite"><span style=3D"font-family:Optima;font-size:mediu=
m;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:n=
ormal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-trans=
form:none;white-space:normal;word-spacing:0px;display:inline!important;floa=
t:none">...
 and how would we judge IETF consensus on a document that doesn&#39;t get d=
one under a charter (which would in turn have been granted consensus withou=
t any IETF comments?)</span></blockquote>
</div>
<br>
</div><div>I would expect that you&#39;d start with a mailing list, see if =
there is interest, come up with a proposal for a BOF, come up with a workin=
g group charter, get IESG review on the charter, then get IETF consensus on=
 the charter, and then start working on the
 document. =A0 That&#39;s how it&#39;s usually done.</div>
<div><br></div></div></blockquote><div><br></div><div style>I think you mis=
read entirely.</div><div style><br></div><div style>But anyway, let&#39;s a=
ssume we follow those steps.</div><div style><br></div><div style>I suspect=
 the closest we get to getting an idea of IETF consensus is the interest ga=
uging at the beginning of the process, though interestingly this is only po=
sitive interest - objections to doing the work at all aren&#39;t really rel=
evant here. The IETF consensus on the charter is handled by Apathy Is Assen=
t rules, so claiming that this consensus call becomes the default is an int=
eresting argument to make.<br>
</div><div style><br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"wor=
d-wrap:break-word"><div>
</div>
<div>BTW, the fact that a few people think the process ought to work differ=
ently does not mean there is consensus for it to work differently. =A0 Also=
, what there may not be consensus on among the people who have weighed in o=
n the topic is whether positive statements
 in favor of a document are relevant in IETF last call, but I don&#39;t rea=
lly know how to reduce that to practice, because in reality I think it is r=
are for a quorum of IETF participants to read a document as a consequence o=
f a last call announcement. =A0 Without
 that, I don&#39;t see how you can have any other last call process than th=
e one we currently have.</div>
<div><br>
</div>
</div>

</blockquote></div><br></div><div class=3D"gmail_extra" style>OK, so we don=
&#39;t have voting but we do have a quorum? How wonderful. And given that t=
he majority of people are silent means they agree (with, mind, everything -=
 not just that they&#39;re not reading), so any number of people are theref=
ore &quot;few&quot;.</div>
<div class=3D"gmail_extra" style><br></div><div class=3D"gmail_extra" style=
>But to loop around:</div><div class=3D"gmail_extra" style><br></div><div c=
lass=3D"gmail_extra" style>I strongly feel that positive statements have va=
lue, as they allow the community to gauge the level of review and consensus=
, and I suspect that human nature means that we get more reviews if people =
get to brag about it. I suggest that if more than one bit of data is requir=
ed, it&#39;s simply asked for. Given that the text of IETF Last Call announ=
cements is not governed by any process RFC that I&#39;m aware of (feel free=
 to correct), I suggest simply putting a set of optional questions there. I=
 note this practise has served the XSF very well. I do not think this needs=
 an endless bikeshed discussion on what questions; the IESG can pick what i=
t wants to know.</div>
<div class=3D"gmail_extra" style><br></div><div class=3D"gmail_extra" style=
>If, on the other hand, only objections are sought, then the text (which si=
mply asks for &quot;comments&quot;) also needs changing. And the GenArt, Ap=
psDir, and SecDir reviews should only be send when they have objections to =
publication, of course.</div>
<div class=3D"gmail_extra" style><br></div><div class=3D"gmail_extra" style=
>If you feel that the only way to make either change is to form a working g=
roup and publish an RFC to change something undocumented in the series, the=
n I think we&#39;re stranded in a bureaucratic quagmire with no chance of e=
scape, but I&#39;ll be happy to send &quot;comments&quot;, as requested, no=
netheless.</div>
</div>

--047d7b3a9792e7cc0304def10278--

From jari.arkko@piuha.net  Wed Jun 12 02:28:19 2013
Return-Path: <jari.arkko@piuha.net>
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 6629B21F9C26 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 02:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.463
X-Spam-Level: 
X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=0.136, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 OKL6npOF6plA for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 02:28:14 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id EBECF21F9C25 for <ietf@ietf.org>; Wed, 12 Jun 2013 02:28:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C7F1D2CC60; Wed, 12 Jun 2013 12:28:11 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZoULuoC8uukO; Wed, 12 Jun 2013 12:28:11 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 13C462CC3C; Wed, 12 Jun 2013 12:28:11 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Content-free Last Call comments
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <m2ehc8ojcm.wl%randy@psg.com>
Date: Wed, 12 Jun 2013 12:28:10 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <099CEE49-B203-4DD7-A5FA-CB56A48726FF@piuha.net>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com> <51B710DD.5020805@dcrocker.net> <m2ehc8ojcm.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>, Elwyn Davies <elwynd@dial.pipex.com>, Pete Resnick <presnick@qti.qualcomm.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1503)
Cc: IETF Discussion <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, 12 Jun 2013 09:28:19 -0000

> perhaps we should go to the source of the problem and require a phd
> dissertation and defense from draft authors.

A couple of years ago I worked with someone who completed his PhD thesis =
on a topic faster than it took to publish the RFC on the same topic=85 =
that was my wake-up call for IETF process needing some work :-) Things =
have improved since then, though, but probably not enough.

But back to the topic. I, for one, would like to see responses on IETF =
last calls. It builds my confidence that we know enough about the topic =
to make an approval decision. Particularly when the input comes from =
people outside the working group. And I'd like to distinguish "everyone =
thinks this is fine" from "no one read the document".

And substance of the comments - be it positive or negative - is =
obviously important. But I find myself strangely between Stephen's =
opinion and Pete's opinion. Pete is of course right that blind "support" =
is bad and that we could easily guess wrong what the commenter meant, =
even when there is substance behind the support but the substance did =
not get explicitly articulated in the e-mail. But I can also see that =
there are cases where there's some context. Elwyn's mail illustrates an =
important example with Gen-ART reviewers. (Thank you by the way Elwyn =
and others for this great service. It is very much appreciated, and does =
improve RFC quality.)=20

Anyway, we know why these reviews are being done, and what the =
expectation is. The expectation is that a generalist reads the spec and =
determines if it is understandable, tries to spot possible errors, and =
so on. But at the same time, the reviewers are unlikely to be in a =
position to say, for instance, that they have implemented the spec or =
plan to deploy the technology. So at the end of the day, if the spec is =
fine, it will only say "Ready", We will interpret that as an Internet =
technology generalist outside the working group having read the document =
and indicating that it has no obvious problems. But there is no other =
implication - about the reviewer needing the work for himself or =
herself, for instance.

In Russ' case I took the message to mean that he reviewed it as an =
expert on the technology. It would probably have helped if he said =
whether he only reviewed it for correctness or if he was also making a =
statement about the technology being needed in his opinion. I would have =
appreciated his opinion on it. That being said, it feels kind of odd to =
explicitly say things if you have nothing to say about the matter. "I =
have read the document and it seems fine, but I am not implementing it =
and I don't know if it addresses a real need in the Internet." We tend =
to assume that if the commenter is not saying these things, it is =
because he has no statement about his implementation, for instance.

Jari


From john-ietf@jck.com  Wed Jun 12 02:44:20 2013
Return-Path: <john-ietf@jck.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 68DB821F99FD for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 02:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.144
X-Spam-Level: 
X-Spam-Status: No, score=-100.144 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, USER_IN_WHITELIST=-100]
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 E3cy2VcXGfQz for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 02:44:14 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9365821F99AF for <ietf@ietf.org>; Wed, 12 Jun 2013 02:44:14 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Umhb8-0009MK-FV; Wed, 12 Jun 2013 05:44:10 -0400
Date: Wed, 12 Jun 2013 05:44:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Thornburgh <mthornbu@adobe.com>, SM <sm@resistor.net>, ietf@ietf.org
Subject: RE: Last Call: <draft-thornburgh-adobe-rtmfp-07.txt> (Adobe's	Secure Real-Time Media Flow Protocol) to Informational RFC
Message-ID: <73DE8D6ECC5E9E17737AE8D9@JcK-HP8200.jck.com>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC7439825F201E3@nambx08.corp.adobe.com>
References: <20130528161229.25215.37302.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130605072309.0be62c30@resistor.net> <D9D602D39A98E34D9C43E965BEC7439825F201E3@nambx08.corp.adobe.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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, 12 Jun 2013 09:44:20 -0000

--On Tuesday, June 11, 2013 14:51 -0700 Michael Thornburgh
<mthornbu@adobe.com> wrote:

>...
>>    "At the time of writing, the Adobe Flash Player runtime is
>>     installed on more than one billion end-user desktop
>>     computers."
>> 
>> Shouldn't the memo be about the protocol?
> 
> agreed.  i included this statement at the suggestion of the
> Responsible (and Sponsoring) Area Director, to help establish
> the breadth of deployment of the protocol, and therefore the
> relevance of the specification in the RFC Series as an
> independent submission.  the Shepherd, A-D and i are
> discussing your concern regarding this statement off-list.
> possible solutions are: move this comment to the Shepherd
> write-up for the IESG's consideration, change the wording to
> be more neutral, leave as-is or strike it completely.

Michael, SM, and others,

I think the advantages to the community of having
widely-deployed protocols like this published for information
are considerable.  It seems to me that those advantages are
increasingly getting lost in our quest for consensus (or even
unanimity).  Perhaps we should be handling them all as
Independent Submissions where the community wouldn't even think
it had a "vote", but, as Michael points out, community review
often improves document quality.

For such a protocol, information about how widely deployed it is
and even the context in which it is used are important
information, nearly as important as the protocol specification
itself.  Without that information, it would be very hard to tell
a description of a widely-deployed protocol that it is useful
for the community to know about from a description of a fantasy
(or even the product of a fictitious standards body) that the
author hopes others will pick up and use.  By contrast, for
standards-track documents, that information is less important:
it changes more proportionally, the recommendation is based more
on engineering and other technical quality issues, and it is an
IETF recommendation.

So, assuming the document is accurate and clear, I think our
principles should favor publication and should favor publication
with the deployment comment included.

best,
    john


From dromasca@avaya.com  Wed Jun 12 04:17:45 2013
Return-Path: <dromasca@avaya.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 75AE821F9C41 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 04:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.456
X-Spam-Level: 
X-Spam-Status: No, score=-103.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 WOv+KPlOEv1T for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 04:17:40 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id DAAAA21F9C42 for <ietf@ietf.org>; Wed, 12 Jun 2013 04:17:39 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFAAhYuFHGmAcF/2dsb2JhbABWAxaCUiEwSb5ZfxZ0giMBAQEBAxIoMQ4MBAIBCA0EBAEBAQoUCQcyFAkIAgQBDQUIDA6HbAELnhybVxeOAYERIRAHBguCbmEDmGmFGYsAgw+BaAcCFx8
X-IronPort-AV: E=Sophos;i="4.87,851,1363147200"; d="scan'208";a="12781819"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 12 Jun 2013 07:17:37 -0400
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 12 Jun 2013 07:16:01 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0328.009; Wed, 12 Jun 2013 07:17:35 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Warren Kumari <warren@kumari.net>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: RE: [IETF] Content-free Last Call comments
Thread-Topic: [IETF] Content-free Last Call comments
Thread-Index: AQHOZsg5dYe8c0awDU++6NqxShCxFZkx7IqA
Date: Wed, 12 Jun 2013 11:17:35 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA19BA56@AZ-FFEXMB04.global.avaya.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <645B25A3-7974-431B-9723-25648F83D03D@kumari.net>
In-Reply-To: <645B25A3-7974-431B-9723-25648F83D03D@kumari.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <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, 12 Jun 2013 11:17:45 -0000

Hi,

I agree with Warren and disagree with Pete on this issue.=20

Of course, adding more arguments, being more verbose when expressing suppor=
t is very useful. However, I consider the brief comments like the one made =
by Russ useful - at least in determining consensus. I am actually encouragi=
ng such comments in the WGs I chair. I would like to add an argument, irres=
pective of who made the comment (which also counts IMO). Assuming a LC of s=
ome sorts (IETFLC, WGLC) gets only two negative comments. Would it not be u=
seful to know that it's (2 (negative) vs. 0 (positive)) or (2 (negative) vs=
. 10 (positive))? Indeed, we do not count votes in the IETF, but then we al=
so have a problem in interpreting silence, and for this purpose IMO what in=
 this thread is called 'content-free' actually has a lot of content on this=
 respect.=20

Regards,

Dan

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Warren Kumari
> Sent: Tuesday, June 11, 2013 8:22 PM
> To: Pete Resnick
> Cc: ietf@ietf.org
> Subject: Re: [IETF] Content-free Last Call comments
>=20
> [ Not sure if this is adding to the Signal or the Noise on the Discuss
> list, but it *will* help bump up my ranking on the "Weekly posting
> summary", which I use to justify my participation to my management.
> That's what it's for, isn't it?!* ] On Jun 10, 2013, at 4:37 PM, Pete
> Resnick <presnick@qti.qualcomm.com> wrote:
>=20
> > Russ, our IAB chair and former IETF chair, just sent a message to the
> IETF list regarding a Last Call on draft-ietf-pkix-est. Here is the
> entire contents of his message, save quoting the whole Last Call
> request:
> >
> > On 6/10/13 1:45 PM, Russ Housley wrote:
> >> I have read the document, I a support publication on the standards
> track.
> >>
> >> Russ
> >
> > A month ago, we had another very senior member of the community post
> just such a message (in that case directly to the IESG) in response to a
> different Last Call. I took that senior member of the community to task
> for it. But apparently Russ either disagrees with my complaint or didn't
> notice that discussion on the IESG list, so I think it's worth airing
> here in public:
> >
> > A statement such as the above is almost entirely useless to me as an
> IESG member trying to determine consensus. It is content-free.
>=20
> I disagree.
>=20
> >
> > We don't vote in the IETF, so a statement of support without a reason
> is meaningless. We should not be encouraging folks to send such things,
> and having the IAB chair do so is encouraging bad behavior. Had I not
> known Russ and his particular expertise, I would have no reason to take
> it into consideration *at all*. We should not have to determine the
> reputation of the poster to determine the weight of the message. Even
> given my background knowledge of who Russ is, I cannot tell from that
> message which one of the following Russ is saying:
> >
> > - This document precisely describes a protocol of which I have been an
> implementer, and I was able to independently develop an interoperable
> implementation from the document.
> > - This document is about a technology with which I have familiarity
> and I have reviewed the technical details. It's fine.
> > - I've seen objection X to the document and I think the objection is
> incorrect for such-and-so reasons.
> > - My company has a vested interest in this technology becoming a
> standard, and even though I know nothing about it, I support it becoming
> a standards track document.
> > - My Aunt Gertrude is the document editor and she said that she needs
> statements of support, so here I am.
> > - I have a running wager on when we're going to reach RFC 7000 and I
> want to increase my odds of winning.
> >
> > I take it I am supposed to presume from my friendship and knowledge of
> Russ that one of the first three is true and that the last three are
> not.
> > (Well, maybe the last one might be true.) But if instead of from "Russ
> Housely", the message was from "Foo Bar", I would have absolutely no way
> to distinguish among the above.
>=20
> Actually, yes.
>=20
> Russ has been participating in the IETF (and specifically in the area
> where he posted the above email) for a long time -- you know this,
> because you've also been participating.
> In *my opinion* he has shown himself to be diligent and sane. This means
> that *I* would give his comment and support great weight -- I'd *assume*
> he has read and understood the document, and is supporting it because
> #1, 2, 3 and / or 6. If Foo Bar had posted the comment, and in *my*
> opinion  Foo Bar is a total nutter, I would give his comment less, or
> possibly negative,  weight. Obviously your opinions of Russ and Foo may
> be opposite to mine -- you apply your own weighting to each comment --
> that's why we pay you the big bucks...
>=20
> If Foo Bar is new enough to the IETF and cannot reasonably expect
> everyone on the IESG (or in a WG or wherever) to know and have formed an
> opinion of him, then it is *Foo Bar's* responsibility to more fully
> support his comments.
>=20
> Do folk who actually *participate* actively and sanely get to assume
> that they have earned some standing and credibility? Yup. I view this as
> a feature, not a bug.
>=20
> If I go to my doctor and he tells me that I simply have a cold (and not,
> like I'm convinced, the plague), I should presumably weight his comments
> higher than those of my crazy next door neighbor (who, apparently,
> routinely communicates with beings from another dimension), yes?
>=20
> We want to reward merit and participation, not make the process so
> annoying that those who participate get annoyed and wander off.
>=20
> If anyone *opposes* a draft, I think that it behooves them to explain
> what the issue is, regardless of who they are. This is similar to at a
> restaurant -- when the waiter asks if you are enjoying your [steak|tofu]
> it's fine to say "Yes thanks, great", but if express displeasure you
> should be ready to explain what you didn't like.
>=20
>=20
> >
> > I think we should stop with these one-line statements of support. They
> don't add anything to the consensus call. I'm disappointed that Russ
> contributed to this pattern.
> >
> > Other opinions?
>=20
> My opinion is that the folk on the IETF / WG chairs / anyone evaluating
> information uses their opinion on the source of that information as
> input to it's weight. This is why we have people judging consensus (see
> http://tools.ietf.org/html/draft-resnick-on-consensus-01 :-P) and not
> voting / an algorithm.
>=20
> W
>=20
> >
> > pr
> >
> > --
> > Pete Resnick<http://www.qualcomm.com/~presnick/>
> > Qualcomm Technologies, Inc. - +1 (858)651-4478
> >
>=20
>=20
> [*]: :-P
> --
> "He who laughs last, thinks slowest."
>     -- Anonymous
>=20


From Martin.Stiemerling@neclab.eu  Wed Jun 12 04:38:13 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
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 3CA8221F99A7 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 04:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.025
X-Spam-Level: 
X-Spam-Status: No, score=-103.025 tagged_above=-999 required=5 tests=[AWL=0.574, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 QjZVqZltFI7L for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 04:38:08 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB3521F9A1D for <ietf@ietf.org>; Wed, 12 Jun 2013 04:38:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 98B891044D9; Wed, 12 Jun 2013 13:37:50 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLSHTWvWECTH; Wed, 12 Jun 2013 13:37:50 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 79C061044C3; Wed, 12 Jun 2013 13:37:40 +0200 (CEST)
Received: from [10.1.99.64] (10.1.99.64) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 12 Jun 2013 13:36:51 +0200
Message-ID: <51B85D94.1020008@neclab.eu>
Date: Wed, 12 Jun 2013 13:37:56 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-thornburgh-adobe-rtmfp-07.txt> (Adobe's Secure Real-Time Media Flow Protocol) to Informational RFC
References: <20130528161229.25215.37302.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130605072309.0be62c30@resistor.net>
In-Reply-To: <6.2.5.6.2.20130605072309.0be62c30@resistor.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.99.64]
Cc: 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, 12 Jun 2013 11:38:13 -0000

Hi SM,

On 06/05/2013 06:12 PM, SM wrote:
> At 09:12 28-05-2013, The IESG wrote:
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Adobe's Secure Real-Time Media Flow Protocol'
>>   <draft-thornburgh-adobe-rtmfp-07.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-06-25. Exceptionally, comments may be
>
> The write-up mentions that:
>
>    "As a private protocol, no technical changes were performed on the
>     protocol itself, but the authors disclosed more details in
>     response to the WG discussions."
>
> I don't see why this specification requires IETF consensus as it is not
> possible to suggest any major changes.  The explanation given for the
> intended status is that the aspects of the protocol protected by IPR
> were not reviewed externally.
>
> The summary is that there is a memo which is not a WG memo, which is
> supposed to have gained WG consensus, where some group is supposed to
> consider the IPR disclosure, and which is being Last-Called as an
> Individual Submission.  I would like to be considered as not part of the
> consensus.


The last call is not intended to gather IETF consensus about this draft 
but give the community an opportunity to see the draft and comment on it 
before it progress to the IESG. This draft is an AD sponsored draft.

As Michael also pointed out in his email: The draft has been brought to 
the attention of parts of the Transport Area.

The intention is to document the RTMFP protocol for the general public.

>
> Nits:
>
>    "At the time of writing, the Adobe Flash Player runtime is
>     installed on more than one billion end-user desktop computers."
>
> Shouldn't the memo be about the protocol?

The memo is about the protocol, but it is worth mentioning the 
deployment base.

Regards,

   Martin


>
> Regards,
> -sm

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From swmike@swm.pp.se  Wed Jun 12 04:38:23 2013
Return-Path: <swmike@swm.pp.se>
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 0AAAF21F9C20 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 04:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 DctGg0DYPmGX for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 04:38:22 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 6C55321F9C26 for <ietf@ietf.org>; Wed, 12 Jun 2013 04:38:22 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9518D9C; Wed, 12 Jun 2013 13:38:20 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 8817B9A for <ietf@ietf.org>; Wed, 12 Jun 2013 13:38:20 +0200 (CEST)
Date: Wed, 12 Jun 2013 13:38:20 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Content-free Last Call comments
In-Reply-To: <099CEE49-B203-4DD7-A5FA-CB56A48726FF@piuha.net>
Message-ID: <alpine.DEB.2.00.1306121337010.12285@uplift.swm.pp.se>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com> <51B710DD.5020805@dcrocker.net> <m2ehc8ojcm.wl%randy@psg.com> <099CEE49-B203-4DD7-A5FA-CB56A48726FF@piuha.net>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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, 12 Jun 2013 11:38:23 -0000

On Wed, 12 Jun 2013, Jari Arkko wrote:

> But back to the topic. I, for one, would like to see responses on IETF 
> last calls. It builds my confidence that we know enough about the topic 
> to make an approval decision. Particularly when the input comes from 
> people outside the working group. And I'd like to distinguish "everyone 
> thinks this is fine" from "no one read the document".

Should people who supported the document within the WG LC generally avoid 
voicing support in the IETF LC discussion?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From narten@us.ibm.com  Wed Jun 12 05:12:05 2013
Return-Path: <narten@us.ibm.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 EFE7821F9C3A for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 05:12:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 J-E9YOlnj3ts for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 05:11:59 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id BFFB121F9C38 for <ietf@ietf.org>; Wed, 12 Jun 2013 05:11:58 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Wed, 12 Jun 2013 08:11:57 -0400
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 12 Jun 2013 08:11:56 -0400
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id AF4FAC90026; Wed, 12 Jun 2013 08:11:54 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r5CCBtZl66191528; Wed, 12 Jun 2013 08:11:55 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r5CCBswl014065; Wed, 12 Jun 2013 08:11:54 -0400
Received: from cichlid.raleigh.ibm.com (sig-9-65-248-105.mts.ibm.com [9.65.248.105]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r5CCBoAV013881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jun 2013 08:11:52 -0400
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r5CCBnGA028599; Wed, 12 Jun 2013 08:11:49 -0400
Message-Id: <201306121211.r5CCBnGA028599@cichlid.raleigh.ibm.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: Deployment of standards compliant nameservers
In-reply-to: <20130521090727.GB17630@nic.fr>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr>
Comments: In-reply-to Stephane Bortzmeyer <bortzmeyer@nic.fr> message dated "Tue, 21 May 2013 11:07:27 +0200."
Date: Wed, 12 Jun 2013 08:11:49 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13061212-7182-0000-0000-000007484AD7
Cc: iesg@ietf.org, 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, 12 Jun 2013 12:12:05 -0000

[only now reviewing this thread...]

Stephane Bortzmeyer <bortzmeyer@nic.fr> writes:

> On Tue, May 21, 2013 at 10:26:39AM +1000,
>  Mark Andrews <marka@isc.org> wrote 
>  a message of 52 lines which said:

> > I'm not sure what the solution should be but regular audits of
> > delegated nameservers by infrastructure operator and removal of
> > delegations after a grace period

> Let's not reinvent the wheel: I suggest to first study the experience
> of the TLD which did exactly that. .fr had mandatory technical tests
> of the name servers almost from its inception, until december
> 2012. The tool used for the tests was Zonecheck
> <http://www.zonecheck.fr/>

> Although these tests certainly contributed to the good technical
> quality of the name servers, they were removed both for commercial
> reasons (a registry has to make money to pay its employees) and
> because it was easier to have the same rules for ccTLDs and gTLDs (and
> ICANN forbids these technical tests in gTLDs).

First I've heard that "ICANN forbids these technical tests in gTLDs",
and I doubt it's true. Just exactly what tests are you referring to?

It would also help if you could point to the actual policies or
contract language in the registry or registrar contracts that speak to
these restrictions you refer to.

Thomas



From Ted.Lemon@nominum.com  Wed Jun 12 05:12:15 2013
Return-Path: <Ted.Lemon@nominum.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 B0AA521F9C41 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 05:12:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.62
X-Spam-Level: 
X-Spam-Status: No, score=-106.62 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 MUWAvsxJ5kZy for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 05:12:09 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id C913111E80A2 for <ietf@ietf.org>; Wed, 12 Jun 2013 05:12:08 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUbhlmP6mXkCq4AFJDX4lFNuhIK69ks8T@postini.com; Wed, 12 Jun 2013 05:12:08 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2B4E81B81E0 for <ietf@ietf.org>; Wed, 12 Jun 2013 05:12:08 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 1E61019005D; Wed, 12 Jun 2013 05:12:08 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 12 Jun 2013 05:12:07 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dave Cridland <dave@cridland.net>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkwIJIAgAFBKYCAAAqfAIAAAp+AgAAPHoCAAAeDAIAAApOAgAAEuACAAK4igIAAOjkA
Date: Wed, 12 Jun 2013 12:12:07 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751D2941@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com> <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com> <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com>
In-Reply-To: <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751D2941mbx01winnominum_"
MIME-Version: 1.0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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, 12 Jun 2013 12:12:15 -0000

--_000_8D23D4052ABE7A4490E77B1A012B6307751D2941mbx01winnominum_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Jun 12, 2013, at 4:43 AM, Dave Cridland <dave@cridland.net<mailto:dave@c=
ridland.net>> wrote:
I suspect the closest we get to getting an idea of IETF consensus is the in=
terest gauging at the beginning of the process, though interestingly this i=
s only positive interest - objections to doing the work at all aren't reall=
y relevant here. The IETF consensus on the charter is handled by Apathy Is =
Assent rules, so claiming that this consensus call becomes the default is a=
n interesting argument to make.

Working group charters go by much less frequently than new drafts; the burd=
en of checking them is about as low as any comprehensive review burden in t=
he IETF can possibly get.   So if you don't comment on a charter when it go=
es by, and you don't comment on the work the working group does, you have o=
nly yourself to blame.   The IETF doesn't have members, so we can't say "on=
ly 10% of IETFers like this idea, so we won't bother with it."   We don't h=
ave voting, so we can't issue a ballot and count up the yeas and nays.   If=
 you want to limit the number of RFCs published, you need to voluntarily do=
 the work that is required to make that happen.   If you think there's a pr=
oblem with the charter, and you raise it on the IETF mailing list, there wi=
ll be no shortage of discussion.   Trust me on this.

OK, so we don't have voting but we do have a quorum? How wonderful. And giv=
en that the majority of people are silent means they agree (with, mind, eve=
rything - not just that they're not reading), so any number of people are t=
herefore "few".

Right.   We don't have members, so we can't have a quorum.   That's just no=
t how the IETF operates.   If you prefer to operate in an SDO that operates=
 that way, you can either change the IETF, or work in a different SDO.

I strongly feel that positive statements have value, as they allow the comm=
unity to gauge the level of review and consensus, and I suspect that human =
nature means that we get more reviews if people get to brag about it.

If the only reason you are doing a review is so you can brag about it, that=
 seems a bit useless to me.   But in any case, as you say, Pete made his po=
int, you don't agree with it, it's a matter of opinion, so we're bikesheddi=
ng.

FWIW, my reason for responding to these questions on ietf@ietf.org<mailto:i=
etf@ietf.org> is that before I became an AD, I actually didn't _know_ how I=
ETF consensus was determined, and had to do quite a bit of looking around t=
o figure it out when I suddenly needed to know.   So I thought it was worth=
 sharing; if in fact there are a lot of IETF participants who think this is=
 the wrong way to handle last call, you really ought to get together and do=
 a BOF.   That too is how the IETF thinks about things=97it is only a burea=
ucratic quagmire if you make it one.   Should it really be _easy_ to change=
 how the IETF evaluates consensus?


--_000_8D23D4052ABE7A4490E77B1A012B6307751D2941mbx01winnominum_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <93610D39AD54E646A180564D8F3E736D@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Jun 12, 2013, at 4:43 AM, Dave Cridland &lt;<a href=3D"mailto:dave@=
cridland.net">dave@cridland.net</a>&gt; wrote:</div>
<blockquote type=3D"cite"><span style=3D"font-family: Optima; font-size: me=
dium; font-style: normal; font-variant: normal; font-weight: normal; letter=
-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto=
; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; w=
ord-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width=
: 0px; display: inline !important; float: none; ">I
 suspect the closest we get to getting an idea of IETF consensus is the int=
erest gauging at the beginning of the process, though interestingly this is=
 only positive interest - objections to doing the work at all aren't really=
 relevant here. The IETF consensus
 on the charter is handled by Apathy Is Assent rules, so claiming that this=
 consensus call becomes the default is an interesting argument to make.</sp=
an></blockquote>
</div>
<br>
<div>Working group charters go by much less frequently than new drafts; the=
 burden of checking them is about as low as any comprehensive review burden=
 in the IETF can possibly get. &nbsp; So if you don't comment on a charter =
when it goes by, and you don't comment
 on the work the working group does, you have only yourself to blame. &nbsp=
; The IETF doesn't have members, so we can't say &quot;only 10% of IETFers =
like this idea, so we won't bother with it.&quot; &nbsp; We don't have voti=
ng, so we can't issue a ballot and count up the yeas
 and nays. &nbsp; If you want to limit the number of RFCs published, you ne=
ed to voluntarily do the work that is required to make that happen. &nbsp; =
If you think there's a problem with the charter, and you raise it on the IE=
TF mailing list, there will be no shortage
 of discussion. &nbsp; Trust me on this.</div>
<div><br>
</div>
<div>
<blockquote type=3D"cite">
<div class=3D"gmail_extra">OK, so we don't have voting but we do have a quo=
rum? How wonderful. And given that the majority of people are silent means =
they agree (with, mind, everything - not just that they're not reading), so=
 any number of people are therefore
 &quot;few&quot;.</div>
</blockquote>
</div>
<div>
<div class=3D"gmail_extra"><br>
</div>
</div>
<div class=3D"gmail_extra">Right. &nbsp; We don't have members, so we can't=
 have a quorum. &nbsp; That's just not how the IETF operates. &nbsp; If you=
 prefer to operate in an SDO that operates that way, you can either change =
the IETF, or work in a different SDO.</div>
<div class=3D"gmail_extra"><br>
</div>
<div class=3D"gmail_extra">
<blockquote type=3D"cite">I strongly feel that positive statements have val=
ue, as they allow the community to gauge the level of review and consensus,=
 and I suspect that human nature means that we get more reviews if people g=
et to brag about it.</blockquote>
<br>
</div>
<div class=3D"gmail_extra">If the only reason you are doing a review is so =
you can brag about it, that seems a bit useless to me. &nbsp; But in any ca=
se, as you say, Pete made his point, you don't agree with it, it's a matter=
 of opinion, so we're bikeshedding.</div>
<div class=3D"gmail_extra"><br>
</div>
<div class=3D"gmail_extra">FWIW, my reason for responding to these question=
s on <a href=3D"mailto:ietf@ietf.org">
ietf@ietf.org</a> is that before I became an AD, I actually didn't _know_ h=
ow IETF consensus was determined, and had to do quite a bit of looking arou=
nd to figure it out when I suddenly needed to know. &nbsp; So I thought it =
was worth sharing; if in fact there are
 a lot of IETF participants who think this is the wrong way to handle last =
call, you really ought to get together and do a BOF. &nbsp; That too is how=
 the IETF thinks about things=97it is only a bureaucratic quagmire if you m=
ake it one. &nbsp; Should it really be _easy_
 to change how the IETF evaluates consensus?</div>
<div class=3D"gmail_extra"><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307751D2941mbx01winnominum_--

From lear@cisco.com  Wed Jun 12 05:22:07 2013
Return-Path: <lear@cisco.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 C718521E804B for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 05:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 CNTsEdNVWzXn for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 05:22:02 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 8F54221F9BFD for <ietf@ietf.org>; Wed, 12 Jun 2013 05:22:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=980; q=dns/txt; s=iport; t=1371039722; x=1372249322; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=aNbuoB1FyDadrqBHFWZRiKL7lNSl7HAx+Vqda9rNBbo=; b=gckaPIeJnq7deBF0Su1Ia1THmX2yZIgYFMISoqwbSoSXrvFwP1X3XMGa IJGpl4kWBRGuPnvBONwawY8x0VKgQeCwjriJOohAlKCj85HhfKaJTGFN1 Q6ennnD2IljxRKOHqaGahmCHzoT6TiVKeSrE20vuJZGXHZNNUD/lanYkx Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgFAIJmuFGtJV2Z/2dsb2JhbABZgwmDbbtlgQAWdIIjAQEBBCNVARALDgoCAgUWCwICCQMCAQIBRQYNAQcBAReHc6hWkTiBJo4dB4JMgRQDl0CRQoMrIIEsBw
X-IronPort-AV: E=Sophos;i="4.87,851,1363132800"; d="scan'208";a="221854412"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP; 12 Jun 2013 12:22:02 +0000
Received: from rtp-vpn2-1546.cisco.com (rtp-vpn2-1546.cisco.com [10.82.246.12]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r5CCM0xV020911 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jun 2013 12:22:01 GMT
Message-ID: <51B867E7.2020107@cisco.com>
Date: Wed, 12 Jun 2013 08:21:59 -0400
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com>
In-Reply-To: <51B77E77.1030601@qti.qualcomm.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <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, 12 Jun 2013 12:22:08 -0000

On 6/11/13 3:45 PM, Pete Resnick wrote:
> It's interesting to see that people are interpreting me to mean I want
> more text. I don't. I want less. Save your breath. There is no reason
> to send one line of support, and it only encourages the view that
> we're voting. Details below.

And a lot of details they were.  I will point out that circumstances
probably matter.  For a working group document that has already received
some scrutiny, you've already addressed many questions, like whether the
work is important, whether it's right for the IETF to do, and whether
the solution is correct.  For AD sponsored, I would expect you'd
actually like a bit more.  Yes, you've answered some of these questions
in principle, but the rest of us haven't had our say.  In these
circumstances, I'd have to say that affirmative support with an eye
toward answering those questions (as well as nits et al) would probably
be useful for me to see as an individual.

Eliot


From ned+ietf@mauve.mrochek.com  Wed Jun 12 07:28:12 2013
Return-Path: <ned+ietf@mauve.mrochek.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 97E3721F9BB4 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 07:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 WuXJ0di+jyvM for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 07:28:04 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id EEB7621F9BB7 for <ietf@ietf.org>; Wed, 12 Jun 2013 07:27:31 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OUR5HS9KTS000PML@mauve.mrochek.com> for ietf@ietf.org; Wed, 12 Jun 2013 07:22:29 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OUMZ1UI6O0000054@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 12 Jun 2013 07:22:26 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OUR5HQDG62000054@mauve.mrochek.com>
Date: Wed, 12 Jun 2013 07:16:38 -0700 (PDT)
Subject: Re: Content-free Last Call comments
In-reply-to: "Your message dated Wed, 12 Jun 2013 09:43:43 +0100" <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com> <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com> <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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, 12 Jun 2013 14:28:12 -0000

Dave Cridland wrote:

> I strongly feel that positive statements have value, as they allow the
> community to gauge the level of review and consensus, and I suspect that
> human nature means that we get more reviews if people get to brag about it.

Agreed 100%.

But also consider the likely effect of calling certain comments "useless".

Discussions like this don't exactly fire me up with enthusiasm to expend 
additional time reviewing and commenting on documents not directly related to
what I do. And I rather doubt I'm alone in this.

				Ned

From dhc@dcrocker.net  Wed Jun 12 07:45:05 2013
Return-Path: <dhc@dcrocker.net>
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 75E0421F9ACB for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 07:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Level: 
X-Spam-Status: No, score=-6.392 tagged_above=-999 required=5 tests=[AWL=0.208,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 lH2yXPNOlNke for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 07:45:00 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 82C0B21F99BB for <ietf@ietf.org>; Wed, 12 Jun 2013 07:45:00 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5CEiuWU011310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Jun 2013 07:45:00 -0700
Message-ID: <51B88962.1000100@dcrocker.net>
Date: Wed, 12 Jun 2013 07:44:50 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <CAKHUCzy0DKRJ_EsSZsftdXwbgrQqKU8GZXn+CBg4vaZZCh5MaA@mail.gmail.com> <51B710DD.5020805@dcrocker.net> <m2ehc8ojcm.wl%randy@psg.com> <099CEE49-B203-4DD7-A5FA-CB56A48726FF@piuha.net>
In-Reply-To: <099CEE49-B203-4DD7-A5FA-CB56A48726FF@piuha.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 12 Jun 2013 07:45:00 -0700 (PDT)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 12 Jun 2013 14:45:05 -0000

On 6/12/2013 2:28 AM, Jari Arkko wrote:
> In Russ' case I took the message to mean that he reviewed it as an
> expert on the technology. It would probably have helped if he said
> whether he only reviewed it for correctness or if he was also making
> a statement about the technology being needed in his opinion. I would
> have appreciated his opinion on it. That being said, it feels kind of
> odd to explicitly say things if you have nothing to say about the
> matter.


The act of posting something means they feel that they do have something 
to say.  That's actually not the issue here.

The issue here is how fully the posting should explain itself.

When we write, we make assumptions about the reader.  Russ talking to 
you, Jari, permits an especially rich set of assumptions to be easy and 
correct.  You know each other.  For informal exchange, that's not only 
acceptable, it's essential.  The alternative is pathologically stilted 
and unworkably inefficient.

We often write things in the IETF -- including formal things -- as if 
they are only for folks we know.

But that's not really an appropriate model for a formal standards 
process.  When contributing to the formal parts of a standards process, 
we need to assume the writer and the reader don't know each other, 
because they usually don't.  The fact that some do is actually 
distracting.

Write for the record; the record does not know the background or intent 
or implications of the writer.  Neither will a random reader, now or 
later.  So make them explicit.

The fact that you, Jari, are still left with a guess about what Russ's 
comment fully meant should make obvious just how important it is for 
folks who post comments to provide context for their comment, where 
'context' means demonstrating an understanding of what is being 
commented on and fully explaining what our comment means.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From iab-chair@iab.org  Wed Jun 12 07:59:35 2013
Return-Path: <iab-chair@iab.org>
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 8C72C21F96D9; Wed, 12 Jun 2013 07:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 wJjZmiVsXlwH; Wed, 12 Jun 2013 07:59:34 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 992F821F9923; Wed, 12 Jun 2013 07:59:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 5F83B129734; Wed, 12 Jun 2013 07:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pQ7vPiOuXndL; Wed, 12 Jun 2013 07:59:33 -0700 (PDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) by c8a.amsl.com (Postfix) with ESMTPSA id C857A129730; Wed, 12 Jun 2013 07:59:32 -0700 (PDT)
Subject: Re: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 / IETF Relationship"
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-46--247535961
From: IAB Chair <iab-chair@iab.org>
In-Reply-To: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
Date: Wed, 12 Jun 2013 10:59:31 -0400
Message-Id: <F2043D47-5539-4CE3-9DD7-94E196DC9B56@iab.org>
References: <1C23C450-8A85-4003-BD53-B78CCE418F55@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <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, 12 Jun 2013 14:59:35 -0000

--Apple-Mail-46--247535961
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

The Call for Review has been extended to 4 July 2013.

Please send comment to iab (at) iab.org or enter a ticket in TRAC. 

A new ticket can be entered:
  - using http://trac.tools.ietf.org/group/iab/trac/newticket
  - select the component of /home/ietf/id/draft-iab-rfc4441rev-04.txt

On behalf of the IAB,
  Russ Housley
  IAB Chair


On Jun 5, 2013, at 2:50 PM, IAB Chair wrote:

> This is a call for review of "The IEEE 802 / IETF Relationship"
> prior to potential approval as an IAB stream RFC.
> 
> The document is available for inspection here:
> https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/
> 
> The Call for Review will last until 20 June 2013.
> Please send comments to iab@iab.org. 
> 
> On behalf of the IAB,
>   Russ Housley
>   IAB Chair
> 


--Apple-Mail-46--247535961
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The =
Call for Review has been extended to 4 July =
2013.<div><br></div><div>Please send comment to iab (at) <a =
href=3D"http://iab.org">iab.org</a> or enter a ticket in =
TRAC.&nbsp;</div><div><br></div><div>A new ticket can be =
entered:</div><div>&nbsp; - using&nbsp;<a =
href=3D"http://trac.tools.ietf.org/group/iab/trac/newticket">http://trac.t=
ools.ietf.org/group/iab/trac/newticket</a></div><div>&nbsp; - select the =
component of =
/home/ietf/id/draft-iab-rfc4441rev-04.txt<br><div><div><br></div><div>On =
behalf of the IAB,</div><div>&nbsp; Russ Housley</div><div>&nbsp; IAB =
Chair</div><div><br></div><div><br><div><div>On Jun 5, 2013, at 2:50 PM, =
IAB Chair wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; ">This is a call for =
review of "The IEEE 802 / IETF Relationship"<div>prior to potential =
approval as an IAB stream RFC.<br><br>The document is available for =
inspection here:<br><a =
href=3D"https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/">https://da=
tatracker.ietf.org/doc/draft-iab-rfc4441rev/</a><br>

<br>The Call for Review will last until 20 June 2013.<div>Please send =
comments to <a href=3D"mailto:iab@iab.org">iab@iab.org</a>. <br>
</div></div><div><br></div><div>On behalf of the IAB,</div><div>&nbsp; =
Russ Housley</div><div>&nbsp; IAB =
Chair</div><div><br></div></div></blockquote></div><br></div></div></div><=
/body></html>=

--Apple-Mail-46--247535961--

From sob@harvard.edu  Wed Jun 12 08:23:03 2013
Return-Path: <sob@harvard.edu>
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 C18A621E8053 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 08:23:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 9XYqKzkuaRMX for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 08:22:58 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 8DE7821F9ADE for <ietf@ietf.org>; Wed, 12 Jun 2013 08:22:58 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000000.university.harvard.edu [10.35.2.151]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 14D36E91F1; Wed, 12 Jun 2013 11:22:58 -0400 (EDT)
Received: from ENTWHUBT0000000.university.harvard.edu (10.32.8.201) by ENTWEDGE0000000.university.harvard.edu (10.35.2.151) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 12 Jun 2013 11:22:33 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.137]) by ENTWHUBT0000000.university.harvard.edu ([10.32.8.201]) with mapi id 14.02.0342.003; Wed, 12 Jun 2013 11:22:58 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: list list <ietf@ietf.org>
Subject: Fwd: New Version Notification for draft-bradner-rfc3979bis-05.txt
Thread-Topic: New Version Notification for draft-bradner-rfc3979bis-05.txt
Thread-Index: AQHOZ4BQD3mOA9csSkmeb0+wUPAs3g==
Date: Wed, 12 Jun 2013 15:22:56 +0000
Message-ID: <67F8B04D-2636-4446-9D1C-DCE0A1A2E0C5@harvard.edu>
References: <20130612152002.27844.95337.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.103.229.199]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C6C562ED7995EC489BA0A2CDC139E6E3@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 12 Jun 2013 15:23:03 -0000

this is an update to the 3979 bis ID that tries to deal with the comments o=
n the list since the last version

see the changes since section for the list of changes

thanks

Scott & Jorge

Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for draft-bradner-rfc3979bis-05.txt
> Date: June 12, 2013 11:20:02 AM EDT
> To: Scott O.Bradner <sob@harvard.edu>, Jorge Contreras <cntreras@gmail.co=
m>, Scott Bradner <sob@harvard.edu>
>=20
>=20
> A new version of I-D, draft-bradner-rfc3979bis-05.txt
> has been successfully submitted by Scott Bradner and posted to the
> IETF repository.
>=20
> Filename:	 draft-bradner-rfc3979bis
> Revision:	 05
> Title:		 Intellectual Property Rights in IETF Technology
> Creation date:	 2013-06-12
> Group:		 Individual Submission
> Number of pages: 18
> URL:             http://www.ietf.org/internet-drafts/draft-bradner-rfc397=
9bis-05.txt
> Status:          http://datatracker.ietf.org/doc/draft-bradner-rfc3979bis
> Htmlized:        http://tools.ietf.org/html/draft-bradner-rfc3979bis-05
> Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-bradner-rfc3979=
bis-05
>=20
> Abstract:
>   The IETF policies about Intellectual Property Rights (IPR), such as
>   patent rights, relative to technologies developed in the IETF are
>   designed to ensure that IETF working groups and participants have as
>   much information about any IPR constraints on a technical proposal as
>   possible.  The policies are intended to benefit the Internet
>   community and the public at large, while respecting the legitimate
>   rights of IPR holders.  This memo details the IETF policies
>   concerning IPR related to technology worked on within the IETF.  It
>   also describes the objectives that the policies are designed to meet.
>   This memo updates RFC 2026 and obsoletes RFC 3979 and RFC 4879.
>=20
>=20
>=20
>=20
> The IETF Secretariat
>=20


From bob.hinden@gmail.com  Wed Jun 12 08:33:54 2013
Return-Path: <bob.hinden@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 491EA11E80A2 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 08:33:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 XI7DlACx25VQ for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 08:33:53 -0700 (PDT)
Received: from mail-ve0-x22c.google.com (mail-ve0-x22c.google.com [IPv6:2607:f8b0:400c:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id B01B721F997C for <ietf@ietf.org>; Wed, 12 Jun 2013 08:33:53 -0700 (PDT)
Received: by mail-ve0-f172.google.com with SMTP id jz10so6995810veb.3 for <ietf@ietf.org>; Wed, 12 Jun 2013 08:33:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=iS6RLIGUeHlAi9XaBZl74xJxD4486nj8r3/r/u3MYnA=; b=vQFbuYZZgWC1sOy1fEVtXPfT+qzptaaUuJdnuSdb7B2XHpidPkoRiJfwVhNAcP00/6 PrvbBwA7JsoKrc1emVYIrYXtpmBFlTrM8MAc54KD991WQX0KKQu13IFzbQugASvtoYRC k5XhYA4bhKBBFOBecYgmHz1GlZL/rNtcibwOe9udAo273yJV6zw8Q5CGlWwHcvJAXeOx PHDHYkWg2Od5RQJzHg9YzgvJf6R6r7C3+d2CktA49JGN742I4xuCuBlnyxuPKpg3DD2Y DZvc/NOGDGoODU/LittC6b6OW+nMWwgatCAeSx2kbVvNHMsb9+5xssan8ck5hOYuW3yJ H/0Q==
X-Received: by 10.58.173.36 with SMTP id bh4mr10039745vec.9.1371051231718; Wed, 12 Jun 2013 08:33:51 -0700 (PDT)
Received: from ?IPv6:2601:9:4080:10:a4e2:cdd8:871a:8c25? ([2601:9:4080:10:a4e2:cdd8:871a:8c25]) by mx.google.com with ESMTPSA id sr7sm14982834vdc.2.2013.06.12.08.33.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Jun 2013 08:33:50 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Content-free Last Call comments
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <51B63905.2020807@qti.qualcomm.com>
Date: Wed, 12 Jun 2013 08:33:47 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C916195-0426-4484-A45E-87BEAC79884C@gmail.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1508)
Cc: Bob Hinden <bob.hinden@gmail.com>, 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, 12 Jun 2013 15:33:54 -0000

Pete,

On Jun 10, 2013, at 1:37 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> Russ, our IAB chair and former IETF chair, just sent a message to the =
IETF list regarding a Last Call on draft-ietf-pkix-est. Here is the =
entire contents of his message, save quoting the whole Last Call =
request:
>=20
> On 6/10/13 1:45 PM, Russ Housley wrote:
>> I have read the document, I a support publication on the standards =
track.
>>=20
>> Russ
>=20
> A month ago, we had another very senior member of the community post =
just such a message (in that case directly to the IESG) in response to a =
different Last Call. I took that senior member of the community to task =
for it. But apparently Russ either disagrees with my complaint or didn't =
notice that discussion on the IESG list, so I think it's worth airing =
here in public:
>=20
> A statement such as the above is almost entirely useless to me as an =
IESG member trying to determine consensus. It is content-free.

Please describe the context of your email.  Are you speaking for the =
IESG, yourself as an AD, or an individual?  Is this something the IESG =
has discussed?  Are you (or the IESG) creating rules for the community, =
that is, "thou should not send one sentence responses to IETF last =
calls"?  Same question when you "took that senior member of the =
community to task". =20

I read your email that you are trying to control how people respond to =
IETF last calls and if they don't respond to your liking you can take =
them to task.  Especially the "Russ either disagrees with my complaint=85"=
 text.

This may not have been your intent, but your original email and =
responses can be read that way. =20

Bob



From sm@resistor.net  Wed Jun 12 10:13:41 2013
Return-Path: <sm@resistor.net>
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 A1C4A21F9B1C for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 10:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.801
X-Spam-Level: 
X-Spam-Status: No, score=-101.801 tagged_above=-999 required=5 tests=[AWL=-0.598, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
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 KvmckTtobqBE for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 10:13:40 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C786421F9B42 for <ietf@ietf.org>; Wed, 12 Jun 2013 10:13:40 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5CHDT63027932; Wed, 12 Jun 2013 10:13:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1371057213; bh=d5/LQ81SmqCayqU7kEl3oXZ3JVf4J8ZE1GhJ1g/Aarw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=bthk1QbjjdPKFxAuI0+TrBxeQTMPEfDJ9RKSjznHIlNGgeTh2BpqK5De5iyByOcVS 7I0FgLDf53hEp9VPihrqIWXuLFTZ5uZELExRbeFG/A7KMpj3setFxeeXjMtfjLmQQY tHAu75+AE1MPDYoyyW8pCCNUhtMeHvIX4Uo0RlxI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1371057213; i=@resistor.net; bh=d5/LQ81SmqCayqU7kEl3oXZ3JVf4J8ZE1GhJ1g/Aarw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=q+7sAxtUt4kiZUlKiPqzEn14GtSFL0LwzLmc8IZZo6B5UOxBCH4JOg5kz1dDZYmMf knYSMz/s27/V3dHQnNoP8rTAgMZhzE94n52hnZ7fzrHXgKVL1PIO4tBFMoiaNKS5Pe folwsqIGa+vx+t3rKUrM7N4g4GmhyT1aePN79YJ0=
Message-Id: <6.2.5.6.2.20130612075255.073ecf28@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 12 Jun 2013 09:51:38 -0700
To: Dave Cridland <dave@cridland.net>
From: SM <sm@resistor.net>
Subject: Re: Content-free Last Call comments
In-Reply-To: <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.g mail.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com> <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com> <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: 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, 12 Jun 2013 17:13:41 -0000

Hi Dave,
At 01:43 12-06-2013, Dave Cridland wrote:
>I strongly feel that positive statements have=20
>value, as they allow the community to gauge the=20
>level of review and consensus, and I suspect=20
>that human nature means that we get more reviews=20
>if people get to brag about it. I suggest that=20
>if more than one bit of data is required, it's=20
>simply asked for. Given that the text of IETF=20
>Last Call announcements is not governed by any=20
>process RFC that I'm aware of (feel free to=20
>correct), I suggest simply putting a set of=20
>optional questions there. I note this practise=20
>has served the XSF very well. I do not think=20
>this needs an endless bikeshed discussion on=20
>what questions; the IESG can pick what it wants to know.
>
>If, on the other hand, only objections are=20
>sought, then the text (which simply asks for=20
>"comments") also needs changing. And the GenArt,=20
>AppsDir, and SecDir reviews should only be send=20
>when they have objections to publication, of course.
>
>If you feel that the only way to make either=20
>change is to form a working group and publish an=20
>RFC to change something undocumented in the=20
>series, then I think we're stranded in a=20
>bureaucratic quagmire with no chance of escape,=20
>but I'll be happy to send "comments", as requested, nonetheless.

An interesting point in the above is level of=20
review and consensus.  Here's what I know: there=20
is going to be apathy, there might be attempts by=20
a group to support a draft or even attempts to=20
silence critics, there might be someone new to=20
all this who might be commenting.  If it was my=20
decision to make (and it is not) I would take=20
those factors and some other points into=20
consideration in making a determination about a document.

As I have read your reviews I have an approximate=20
idea of the type of review you would do.  I read=20
the draft and I notice some obvious issues; I=20
downgrade your statement of support to a tweeter=20
comment.  I read the draft and I notice an=20
obvious issue; I consider your statement of support as good enough.

I have read the reviews from the IAB Chair.  I=20
read the draft and I notice that it is not=20
well-written; I downgrade the statement of=20
support of the IAB Chair to a tweeter comment.  I=20
read the draft and I notice that it is good to=20
go.  However, I don't find any comments about it=20
except for a statement of support from the IAB=20
Chair.  I don't say that there is=20
consensus.  Note that this is really a personal=20
decision; someone else might say that there is=20
consensus.  It's not a problem unless the IESG is=20
affected by the Abilene paradox.

The XSF is likely a group of people who can write=20
code.  The IETF is a bunch of people who might=20
discuss about content-free comments but won't=20
comment about the draft. :-)  Drawing up a set of=20
optional questions will generate a bottom-up=20
discussion and that would be against the values=20
which the IETF cherishes. :-)  There isn't=20
anything preventing an Area Director or someone=20
else from asking optional questions during a Last=20
Call.  Optional questions from an IETF=20
participant might be ignored if such activity=20
would turn a Last Call into the Tribunal del Santo Oficio de la Inquisici=F3=
n.

If you are doing an AppsDir review, for example, and you state:

    The draft is ready for publication as a Proposed Standard.

I presume that you can personally explain the meaning of that sentence.

If you are an individual responding to a Last=20
Call you can say anything you wish.  If your=20
message is littered with spelling mistakes or it=20
does not contain any substantive comment, it=20
won't bear much weight.  If your English writing=20
skills is not that good but your code is good the=20
message will bear more weight.  If your message=20
is to show your management that you are=20
participating in the IETF the message will not bear much weight.

It's simple enough.  I would send a message if I=20
believe that it can affect the decision.  It's up=20
to me to know what will influence the content and fate of the draft.

Regards,
-sm=20


From alexey.melnikov@isode.com  Wed Jun 12 11:38:07 2013
Return-Path: <alexey.melnikov@isode.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 69DEF21F997C for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 11:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 0ZHz2SCSjmAw for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 11:38:06 -0700 (PDT)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id A554121F997A for <ietf@ietf.org>; Wed, 12 Jun 2013 11:38:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1371062283; d=isode.com; s=selector; i=@isode.com; bh=pnyk8GSTKDnNxQH/wQXLJgXatFwA0+YDiQ6prytq99E=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=ggIG8jPqvd4hCyDTrem8N2+G8N2X6tFIQfbdzKS6p7IvjOVzlPQyMiqSMEuledJW/SIutx DymfypUP6jFvT4hGXBUZw3wFOn1nWPnEXGC5oEWbfOb80z3FlnRo9jE51nrmLdjEzcsCWV 22WtGg1NEk1jrYPASnSK59niQOulBvQ=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UbjACQATucNY@waldorf.isode.com>; Wed, 12 Jun 2013 19:38:02 +0100
Message-ID: <51B8C009.6050509@isode.com>
Date: Wed, 12 Jun 2013 19:38:01 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
To: ned+ietf@mauve.mrochek.com, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com> <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com> <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com> <01OUR5HQDG62000054@mauve.mrochek.com>
In-Reply-To: <01OUR5HQDG62000054@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org Discussion" <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, 12 Jun 2013 18:38:07 -0000

On 12/06/2013 15:16, ned+ietf@mauve.mrochek.com wrote:
> Dave Cridland wrote:
>> I strongly feel that positive statements have value, as they allow the
>> community to gauge the level of review and consensus, and I suspect that
>> human nature means that we get more reviews if people get to brag about it.
> Agreed 100%.
>
> But also consider the likely effect of calling certain comments "useless".
>
> Discussions like this don't exactly fire me up with enthusiasm to expend
> additional time reviewing and commenting on documents not directly related to
> what I do. And I rather doubt I'm alone in this.
You are not alone. I do occasional reviews of documents not directly 
related to what I do. But I hate paperworks. And if I would be required 
to fill in 10 pages questionnaire about why I think the document is in a 
good shape, I probably will stop doing such reviews altogether.


From stpeter@stpeter.im  Wed Jun 12 11:44:23 2013
Return-Path: <stpeter@stpeter.im>
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 6B60711E80E8 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 11:44:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 SI9THqCmybrC for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 11:44:19 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id EFE3D21E809C for <ietf@ietf.org>; Wed, 12 Jun 2013 11:44:18 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 3819441101; Wed, 12 Jun 2013 12:57:52 -0600 (MDT)
Message-ID: <51B8C17E.2090804@stpeter.im>
Date: Wed, 12 Jun 2013 12:44:14 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com> <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com> <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com> <01OUR5HQDG62000054@mauve.mrochek.com> <51B8C009.6050509@isode.com>
In-Reply-To: <51B8C009.6050509@isode.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ned+ietf@mauve.mrochek.com, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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, 12 Jun 2013 18:44:23 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/12/13 12:38 PM, Alexey Melnikov wrote:
> On 12/06/2013 15:16, ned+ietf@mauve.mrochek.com wrote:
>> Dave Cridland wrote:
>>> I strongly feel that positive statements have value, as they
>>> allow the community to gauge the level of review and consensus,
>>> and I suspect that human nature means that we get more reviews
>>> if people get to brag about it.
>> Agreed 100%.
>> 
>> But also consider the likely effect of calling certain comments 
>> "useless".
>> 
>> Discussions like this don't exactly fire me up with enthusiasm to
>> expend additional time reviewing and commenting on documents not
>> directly related to what I do. And I rather doubt I'm alone in
>> this.
> You are not alone. I do occasional reviews of documents not
> directly related to what I do. But I hate paperworks. And if I
> would be required to fill in 10 pages questionnaire about why I
> think the document is in a good shape, I probably will stop doing
> such reviews altogether.

Much as I love Pete, IMHO this thread started because in good
curmudgeonly style he needed something to grump at. In this instance,
I suggest we just keep doing what we've always been doing.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRuMF+AAoJEOoGpJErxa2pAkwQAK6dse/oJRAS/kNcjvaKvOvD
elHpEX54kil8v01wfiJ8/kd0fHSsKItR0m0r8b/YTkH/8I0+2dy+tG2F/gchI6uK
OrJsev4vFcSY2yZM/qh3QAWeJ2HbYDRjHKc7yMDrwAwS8zUPiNRTfecsw6p/lWNw
qj2H3R5bCIIkIR0dQO5NvWhaEj6Edy/40rwLe1pOOKo5EiMGhut0lQWUV6Dqy3u/
SJAy/dYRexXLuZDuYkI1hGUMBDCmspqnWVOe/bX6oQ3MuC1wTFyZXNntgOlsWOnu
QK7PkY9mNpSpd8KZ8Rt0LgMNEvsPKmNgggmD1Hx1RjBv5B/6SXPwKlT1jS3bZ2or
eCcdHPxLbTD06Ec1Ukg2vNiFe+kgVz5rXHe4GuBm7RQFvMTkq2jO5AF8MddKjtoi
wfW5ociPNQCqIjGkj+xM9CJS6aSQaQxUk0DPzxjwoUAYSIxcF4VIsB0uY/JUs5n0
41deCNgp26OAyvcxdTFW3pgD2vWX+BTA+H6w+0VzLd0msvousDi+tm5wPiQml3+y
Us6wSZwNrxdBgCp7Ce5BAyEaLFQ+LhtOqW3ElJv+AiNgKOujH5lhnNPfsd7jRWHF
Ca4m3XxhFsri+Hw9sr7D2PtUWWJZ4ntm32zfZVKRDM6SXXvUzpZoGAzzgwTOf2Zj
UTBku2xoH8Khfloa29y1
=79mX
-----END PGP SIGNATURE-----

From melinda.shore@gmail.com  Wed Jun 12 11:44:48 2013
Return-Path: <melinda.shore@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 0545C21E809A for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 11:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 U56b-vgp0CPy for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 11:44:47 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDDD21F90EF for <ietf@ietf.org>; Wed, 12 Jun 2013 11:44:47 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj3so5977493pad.28 for <ietf@ietf.org>; Wed, 12 Jun 2013 11:44:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/s/j7Znh/d0+igIwlK6aSGkruLG1ukE7o1YhiKdaCxs=; b=aS+bLRKKd/4p9FtRAqgP279F4wj0LdGo5VsXoJ2xpe4zlmUNTeZzzF6vEepcnpPH+l A6jeA0S6E/C8d+0bqTns8sOSuIfVoIvsfpIJiN4Z1T/AmaLZ//2RqnYbLKx0AlFyfsQv Od0rvNszbCoAbAi9JZxyPTuAlvNttPfABiE1IE1Ctz34Xp4e0hpFFQ9yL8c2jGDx3iXJ s4wXRaHXwNo7ehFP1yELUzCpL1mF/930Vi1CMPAj+R2NKCtcqY6UbYOjyQFzQbT5ZwZp jW9ZNAfXtheErr3nR3/oyC8oOPfazIN3/OpxE8KCR8pSAEagC9ROJv+VApmSfdzLG0ut WlMA==
X-Received: by 10.66.159.66 with SMTP id xa2mr25733011pab.36.1371062687022; Wed, 12 Jun 2013 11:44:47 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id cc15sm25869390pac.1.2013.06.12.11.44.45 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Jun 2013 11:44:46 -0700 (PDT)
Message-ID: <51B8C19C.7060800@gmail.com>
Date: Wed, 12 Jun 2013 10:44:44 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <645B25A3-7974-431B-9723-25648F83D03D@kumari.net> <9904FB1B0159DA42B0B887B7FA8119CA19BA56@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA19BA56@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 12 Jun 2013 18:44:48 -0000

On 6/12/13 3:17 AM, Romascanu, Dan (Dan) wrote:
> Hi,
> 
> I agree with Warren and disagree with Pete on this issue.
> 
> Of course, adding more arguments, being more verbose when expressing
> support is very useful. However, I consider the brief comments like
> the one made by Russ useful - at least in determining consensus. I am
> actually encouraging such comments in the WGs I chair. I would like
> to add an argument, irrespective of who made the comment (which also
> counts IMO). Assuming a LC of some sorts (IETFLC, WGLC) gets only two
> negative comments. Would it not be useful to know that it's (2
> (negative) vs. 0 (positive)) or (2 (negative) vs. 10 (positive))?
> Indeed, we do not count votes in the IETF, but then we also have a
> problem in interpreting silence, and for this purpose IMO what in
> this thread is called 'content-free' actually has a lot of content on
> this respect.

I think Pete is correct, in that the way we do last calls
tends to look like voting, which in turn suggests to participants
that we're voting.  "Are there any objections to <whatever>?"
is, I think, the real question at hand, although I can see where
that could tend to attract cranks and chronic kvetches.  Perhaps
something along the lines of "Does anybody have reasons this
document should not progress towards publication?" might do.

Melinda


From presnick@qti.qualcomm.com  Wed Jun 12 12:11:19 2013
Return-Path: <presnick@qti.qualcomm.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 2D8D621F9922 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 12:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 CnTfujcehdx4 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 12:11:14 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 24DE121F9925 for <ietf@ietf.org>; Wed, 12 Jun 2013 12:11:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1371064272; x=1402600272; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=9MnQfptssnMQZmUCf2kZl1plabmoFn3eqr173ak8/LY=; b=UJMkE/b24W84RbESdvM/fFOizlWWk4JfnT/Dv4rN4ApB+dT795K/wGGZ Jo/lCF9AqYtySvHwfVFQLDR2DWANBEJ64rkqPcOkHWFUy6cTBC3iFKVTV kV8IBqQUWzkRhGg7VrEYbEmE6v0J2QRYymQxA3FfLUL4NBBMDNEVMrsJ3 s=;
X-IronPort-AV: E=Sophos;i="4.87,854,1363158000"; d="scan'208";a="44802516"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 12 Jun 2013 12:11:11 -0700
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 12 Jun 2013 12:11:11 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 12 Jun 2013 12:11:11 -0700
Message-ID: <51B8C802.6040301@qti.qualcomm.com>
Date: Wed, 12 Jun 2013 14:12:02 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie>	<51B77E77.1030601@qti.qualcomm.com>	<CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com>	<CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com>	<CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com> <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com>
In-Reply-To: <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: "ietf@ietf.org Discussion" <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, 12 Jun 2013 19:11:19 -0000

After reading some of the criticisms, I wonder if folks who think 
they've been disagreeing with me are going to get to the end of this 
message and say, "Oh, if that's all he's on about, who cares?" But *I* 
of course think there is an important issue in here. Anyway, back into 
the breach. David's message seems like a good launching point.

On 6/12/13 3:43 AM, Dave Cridland wrote:

> The IETF consensus on the charter is handled by Apathy Is Assent 
> rules, so claiming that this consensus call becomes the default is an 
> interesting argument to make.

Partially tangential: We in the IETF use the phrase "consensus call" in, 
AFAICT, a unique (and IMO goofy) way. It implies that first we have a 
discussion, and then at the end of the discussion we engage in a short 
act we refer to as a "consensus call", the completion of which *creates* 
the consensus. That isn't a consensus call. That's just an anonymous and 
imprecisely counted vote. I think I've got a new section for my 
consensus document to work on: "Consensus isn't the destination; it's 
the journey." (I should get a job writing text for fortune cookies.)

But back to the topic at hand:

> I strongly feel that positive statements have value, as they allow the 
> community to gauge the level of review and consensus...

Reviews are good. We need to do them. They are of value. They should be 
encouraged. People should post the results of reviews. They should brag 
about them as they see fit. No argument there.

Public statements of negative reviews (with specific issues identified) 
are really important. If issues are identified that then go unanswered, 
that breaks consensus.

Public statements (even short ones) of positive reviews have value in 
that we want to know that reviews have taken place. That's useful. Mind 
you, such statements don't help you "gauge consensus": Sure, you *might* 
conclude that one more person is part of the consensus, but of course 
the number of people doesn't matter to the consensus, and the consensus 
hasn't moved at all -- you haven't resolved a new open issue. (There is 
a separate question about what to do when documents haven't gotten 
serious review prior to IETF Last Call and what that means for 
consensus. More on that in a moment.)

So, none of the above things get me torqued. Reviews: Good. Public 
statements of reviews: Good. Issues to be resolved: Good.

Here's what gets me torqued, that I think is useless, and starts people 
thinking that they are voting:

"I support publication of this document."
"I do not support publication of this document."

Even prefacing those with "I reviewed the document" doesn't help. (Of 
course the "I reviewed the document" part itself is potentially useful 
if the person bothers to tell us the result of the review, like "it's 
technically sound" or "it solves a problem that needs solving" or "it's 
technically crappy *and* here are the reasons why".) But the "I do/don't 
support this document" part is what gets my goat. It contains the 
apparent implication that someone is counting noses and that "support" 
matters. It shouldn't. What matters is that we as a community have 
worked this thing out, that it solves a problem that we have identified 
is real, and that nobody in the community has found serious fault in it.

It's not the shortness of the statement that's the problem (though 
sometimes, especially with negative reviews, it is a problem); it's 
treating the call for consensus as a vote that bugs me. It's not useful 
to simply "support" a document.

> If, on the other hand, only objections are sought, then the text 
> (which simply asks for "comments") also needs changing. And the 
> GenArt, AppsDir, and SecDir reviews should only be send when they have 
> objections to publication, of course.

Nope, I'm good with all that. In fact, the GenArt review says exactly 
what it should: It provides "generalist reviews for the General Area 
director (currently the IETF Chair), providing an additional set of eyes 
for documents as they are being considered for publication." It's not 
looking to "gauge consensus". It's looking for a review.

That said, I do believe that objections are *way* more important than 
comments saying, "It's fine". Once something has gone through a WG, the 
presumption is "It's fine." Additional eyes are good, but they're good 
precisely because they might find problems.

That brings us to one last thing which I mentioned above: What if 
documents *aren't* getting serious review prior to IETF Last Call? This 
goes back to our "tail heavy" discussion. The IETF used to be very good 
about getting lots of review (sometimes even cross-area review) *during* 
the consensus building process in the WG. We now have many instances 
where WGs are not really working toward consensus to solve a problem; 
they're doing reviews of a single person's idea of how to solve a 
problem. Even worse, we are seeing many individual submissions that are 
not the product of consensus building at all, and when that 4-week Last 
Call kicks in, we are at best getting reviews, but not building 
consensus around the need for the document. Solving that problem by 
tail-loading more reviews does not address the real issue.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From presnick@qti.qualcomm.com  Wed Jun 12 12:16:57 2013
Return-Path: <presnick@qti.qualcomm.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 B5FE321F9952 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 12:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 lue6CCXMVW76 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 12:16:53 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 7D49921F9977 for <ietf@ietf.org>; Wed, 12 Jun 2013 12:16:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1371064613; x=1402600613; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=cXujgiobsnGC59XtIB+35U0viGRpsQBe/O72z8iOzfQ=; b=KgvULXWDQk6+ouE2XtQ5L+6br30IhofAd5lxWXxArxQoYOcgv2ldaSK+ sNJ7/EkupNA4hNQXjKdYb8AXeQyXHApKPKYJ3FMjNcZHIVnhRvDLWkApw BvQRKkAWlKnVGxdHRkA+2a49E59lB++oSPEa6ydSnq3+LX9u57HU3G6gr s=;
X-IronPort-AV: E=Sophos;i="4.87,854,1363158000"; d="scan'208";a="56067538"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine02.qualcomm.com with ESMTP; 12 Jun 2013 12:16:53 -0700
X-IronPort-AV: E=Sophos;i="4.87,854,1363158000"; d="scan'208";a="552615644"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 12 Jun 2013 12:16:53 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 12 Jun 2013 12:16:52 -0700
Message-ID: <51B8C95A.1080208@qti.qualcomm.com>
Date: Wed, 12 Jun 2013 14:17:46 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com> <9C916195-0426-4484-A45E-87BEAC79884C@gmail.com>
In-Reply-To: <9C916195-0426-4484-A45E-87BEAC79884C@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: 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, 12 Jun 2013 19:16:57 -0000

On 6/12/13 10:33 AM, Bob Hinden wrote:
> Please describe the context of your email.  Are you speaking for the IESG, yourself as an AD, or an individual?

Oh, crap. And given that I'm usually the one giving people a hard time 
about *this* issue, I feel especially bad about not being clearer.

This is Pete, hatless individual talking. There are (as you've seen) 
IESG people, past and present who disagree with me. Nothing I've said is 
anything we've come to an IESG consensus around. Insofar as I think that 
only saying "I support this document" is a bogus thing to say, I am 
revealing something about how I behave as an AD in the face of such 
statements, and my further explanations that I value reviews and take 
them seriously also indicates my views as an AD, but that doesn't 
indicate some policy that I'm instituting with WGs for which I am 
responsible.

I am terribly sorry about not making this clear up front. My sincere 
apologies. I hope nobody took this as a other than my commentary.

Sheepishly,
pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From stpeter@stpeter.im  Wed Jun 12 12:31:53 2013
Return-Path: <stpeter@stpeter.im>
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 F037121E8089 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 12:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 z-uk3vfpSA8H for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 12:31:48 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 5D9D221E805F for <ietf@ietf.org>; Wed, 12 Jun 2013 12:31:47 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 38C7A41101; Wed, 12 Jun 2013 13:45:22 -0600 (MDT)
Message-ID: <51B8CCA0.5080503@stpeter.im>
Date: Wed, 12 Jun 2013 13:31:44 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com> <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com> <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com> <01OUR5HQDG62000054@mauve.mrochek.com> <51B8C009.6050509@isode.com> <51B8C17E.2090804@stpeter.im>
In-Reply-To: <51B8C17E.2090804@stpeter.im>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ned+ietf@mauve.mrochek.com, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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, 12 Jun 2013 19:31:53 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/12/13 12:44 PM, Peter Saint-Andre wrote:
> On 6/12/13 12:38 PM, Alexey Melnikov wrote:
>> On 12/06/2013 15:16, ned+ietf@mauve.mrochek.com wrote:
>>> Dave Cridland wrote:
>>>> I strongly feel that positive statements have value, as they 
>>>> allow the community to gauge the level of review and
>>>> consensus, and I suspect that human nature means that we get
>>>> more reviews if people get to brag about it.
>>> Agreed 100%.
>>> 
>>> But also consider the likely effect of calling certain
>>> comments "useless".
>>> 
>>> Discussions like this don't exactly fire me up with enthusiasm
>>> to expend additional time reviewing and commenting on documents
>>> not directly related to what I do. And I rather doubt I'm alone
>>> in this.
>> You are not alone. I do occasional reviews of documents not 
>> directly related to what I do. But I hate paperworks. And if I 
>> would be required to fill in 10 pages questionnaire about why I 
>> think the document is in a good shape, I probably will stop
>> doing such reviews altogether.
> 
> Much as I love Pete, IMHO this thread started because in good 
> curmudgeonly style he needed something to grump at. In this
> instance, I suggest we just keep doing what we've always been
> doing.

To clarify:

I reject kings, presidents, and voting. But I do believe in the delete
key.

If you think that these "+1" messages are useless, don't factor them
into your thinking about whether we have consensus.

If you think that these "+1" messages are actively harmful (e.g., by
leading to groupthink or poisoning our very understanding of what it
means for us to reach consensus), then proceed as Pete is proceeding.

I think these messages are useless, not harmful. But perhaps I have
more confidence in the inherent skepticism of your average IETF
participant than Pete does...

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRuMygAAoJEOoGpJErxa2p+FYP/iB8QDp6rQ8AdB+hcweMUWFF
lJ1zhGlI0KIaHFzvzLm68FUyjNv4373nRninqq1biS5Uj3wjKgm4Q1rM0kL46mM0
ETVkD916HB3u11nQd0akjtR22TO2I847Ka+HE+2waPUBfDHCaxD8vxPD7lbVI3J9
QlEgxhUobppvHfsKpWHHJaBd9EF+Q4r5dIAhQX3tt7xLi6bupm5X4byAljaFiw7+
JB3c+7xmu767+NFMe7/839fRfRnO8K15c2fkbheY0bHLH9qlwMoUr5DnvYchByXw
SrcZRnYZMaB5zvmYV0Q8TmHCGb3i9R+PIDbvIUL9p95ega8lDi9a5qKA/wN1lEdy
GgkJ1mY/WmhcSEVtYPnUk0ZnmM/ZBjcuZw4lS8h9bXr8LMfCOyp2z6WehrgRXPob
GNu2e5geD9ARJ0Y0f8etjj29Fh79LD+U1zEdH0UyMqu+AVJObX9U/+tIwixz7sa4
DR2zsf+OPGcOXWwGyEhE/WwPOFOCwEatdyBGU9g2mPIhnbPrNUwddfCvTFXsdNcZ
9e4ULnN+/xqictSyyoCBLXazNnAcbjssLhEz/Mw3yTtlOQk0UKKYUvxydFcmxY6l
bqheTm5a/3+VV1G6S4CflYeW4bWxKyiQSgo2N2+BSxrQFnzcFd3up3F3LhH6NYu8
f4MHTt0kpZp8MC2JAJjW
=7/LJ
-----END PGP SIGNATURE-----

From Ted.Lemon@nominum.com  Wed Jun 12 12:42:26 2013
Return-Path: <Ted.Lemon@nominum.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 BC85621F869A for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 12:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.609
X-Spam-Level: 
X-Spam-Status: No, score=-106.609 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 vcTmhKxmS-6y for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 12:42:20 -0700 (PDT)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id EBEC521E804C for <ietf@ietf.org>; Wed, 12 Jun 2013 12:42:19 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKUbjPG0a6Vx8Ku6q/5y6u5ZhdcAFv6zkC@postini.com; Wed, 12 Jun 2013 12:42:19 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 741AF1B81C2 for <ietf@ietf.org>; Wed, 12 Jun 2013 12:42:19 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6D9CE19005D; Wed, 12 Jun 2013 12:42:19 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 12 Jun 2013 12:42:19 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: AQHOZhpdrUZBwtQha0W/M1IcFh2tIpkwIJIAgAFBKYCAAAqfAIAAAp+AgAAPHoCAAAeDAIAAApOAgAAEuACAAK4igP//6rhggAC7U4CAAAG9AIAADUYAgAAC8wA=
Date: Wed, 12 Jun 2013 19:42:19 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751D3D50@mbx-01.win.nominum.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com> <CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com> <CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com> <CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com> <CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com> <01OUR5HQDG62000054@mauve.mrochek.com> <51B8C009.6050509@isode.com> <51B8C17E.2090804@stpeter.im> <51B8CCA0.5080503@stpeter.im>
In-Reply-To: <51B8CCA0.5080503@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <739B72BAB2361746A0BB3C54534E29AF@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ned+ietf@mauve.mrochek.com>" <ned+ietf@mauve.mrochek.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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, 12 Jun 2013 19:42:26 -0000

On Jun 12, 2013, at 3:31 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> I think these messages are useless, not harmful. But perhaps I have
> more confidence in the inherent skepticism of your average IETF
> participant than Pete does...

FWIW, until I read Pete's document on consensus, I thought that +1 statemen=
ts were part of the consensus process.   This was not a strongly held opini=
on=97it was just my understanding of how consensus operated, from having wa=
tched other working group chairs run their working groups.   I think the po=
int Pete is making is very important, because the consensus process Pete de=
scribes is more in keeping with how I think the IETF ought to operate than =
the process in which +1 counts for something.

(BTW, in case it wasn't obvious, I've been engaging in this discussion with=
 my AD and working group chair experience in the back of my mind, but my AD=
 hat off.)


From ted.ietf@gmail.com  Wed Jun 12 13:28:36 2013
Return-Path: <ted.ietf@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 3295421F9958 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 13:28:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 F93I0ZtMIbFo for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 13:28:35 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 5C31F21F88FB for <ietf@ietf.org>; Wed, 12 Jun 2013 13:28:35 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id u16so1978279iet.23 for <ietf@ietf.org>; Wed, 12 Jun 2013 13:28:35 -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=01uVeCIGrkIuK3xZyXEJX+S3pMDMlieaBADQ5d345oY=; b=JMnyFj57hy6vy0O0xf2YxCzDAABNZiujgshrvFnp527rpNu8JajAcQ5rThSUy/hHYK +GOq1W8qGjQRpqv4cv9HaTZs9bSGwEO0SW+Cz6njV/a7AkiXbxk4mDWVb4NtxenbeVFh ytihhYfUbjorRMa0X6KOR6DHSUFSLHWzFDxngLsj5gFgASNdL0KNPV5iYuqsz7fx7iZA TPZ+NRGK1mPhUNOxFmMDSRkZ0jl3ClZ2aweRjKE2yI1002lwLBR8F1VjvqRYpq7H8Uqg rRn4o0lWuNmB+Kt9viW31qn2AjOy/4V0GdozzgRHRVG3sJlP/A00rA7MXA3TsQAPhj/O auIg==
MIME-Version: 1.0
X-Received: by 10.50.23.8 with SMTP id i8mr4230882igf.42.1371068914981; Wed, 12 Jun 2013 13:28:34 -0700 (PDT)
Received: by 10.42.49.7 with HTTP; Wed, 12 Jun 2013 13:28:34 -0700 (PDT)
In-Reply-To: <51B8C19C.7060800@gmail.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <645B25A3-7974-431B-9723-25648F83D03D@kumari.net> <9904FB1B0159DA42B0B887B7FA8119CA19BA56@AZ-FFEXMB04.global.avaya.com> <51B8C19C.7060800@gmail.com>
Date: Wed, 12 Jun 2013 13:28:34 -0700
Message-ID: <CA+9kkMDWrsXOFL8oBvFgnsXcU1+pAmNYD-760EApT+m-YizpYg@mail.gmail.com>
Subject: Re: [IETF] Content-free Last Call comments
From: Ted Hardie <ted.ietf@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=089e01538794a3e4f504defadb29
Cc: 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, 12 Jun 2013 20:28:36 -0000

--089e01538794a3e4f504defadb29
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jun 12, 2013 at 11:44 AM, Melinda Shore <melinda.shore@gmail.com>wrote:

>
> I think Pete is correct, in that the way we do last calls
> tends to look like voting, which in turn suggests to participants
> that we're voting.  "Are there any objections to <whatever>?"
> is, I think, the real question at hand, although I can see where
> that could tend to attract cranks and chronic kvetches.  Perhaps
> something along the lines of "Does anybody have reasons this
> document should not progress towards publication?" might do.
>
>
So, back in the days when we were talking about the move from a 3-stage
process to a 2-stage process, I wrote draft-hardie-advance-mechanics.  That
described our then-extent process  this way:

   In practice, IETF document processing has evolved to a model which
   can be described as "objection based processing".  A document put
   forward by an author team advances from the relevant working group to
   IETF consideration after all objections from within the working group
   have been considered.  The IETF Last Call is, in practice, a way for
   the larger community to object to a document or elements within it.
   IESG document processing is, fundamentally, a process by which a
   sponsor resolves any objections raised by other area directors;
   though the term used is "discuss" and some delegation occurs (to
   document shepherds or review teams), the basic model is clear.
I don't think that true consensus is achieved by the lack of
objection, but the community
seems to have accepted it as "rough consensus".

Could we do better?  Absolutely.  We could, for example,  formalize
the third-party reviews
by other areas such that a demonstration that proposals were
acceptable in a broader Internet
context was fundamental (either at charter time, at working group
draft acceptance time,
at proposed  publication, periodically for advancement, or at all of
the above). That would
get voices known to have analysed it heard, and give us a lot more
confidence that the
proposal wasn't narrow in its examination of the impact of its work.

But this is a volunteer organization, and the practical truth is that
we don't have the volunteer
energy to do that or the funds to pay for it (or trust in anyone we'd
pay, as another issue).
So, bluntly, we should take what we get and use it as we can.  If Pete
can't figure out what
to make of a +1 by a 5 term IESG member and sitting IAB Chair, then
he'll have to evaluate
the document without that input.  He'll have to evaluate it on its
merits anyway, so it's
no big deal.  But  anything that discourages review, however, cursory,
is not really a good
thing.  Perhaps a note to the reviewer like:

"Thanks for taking the time.  It's good to know I can reach out to you
for more data, should
I be on the fence on this one".

(I'm thinking on heavy stock Crane paper, maybe in a cream, nicely
lettered.  Or, you know, as
a jotted email or IM.)

Even sent to a stranger, that would look nice and remind people that
we're not voting.

Just some thoughts on the topic,

Ted

--089e01538794a3e4f504defadb29
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 12, 2013 at 11:44 AM, Melinda Shore <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:melinda.shore@gmail.com" target=3D"_blank">melinda.shore@gmail=
.com</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<div class=3D"im"><br>
</div>I think Pete is correct, in that the way we do last calls<br>
tends to look like voting, which in turn suggests to participants<br>
that we&#39;re voting. =A0&quot;Are there any objections to &lt;whatever&gt=
;?&quot;<br>
is, I think, the real question at hand, although I can see where<br>
that could tend to attract cranks and chronic kvetches. =A0Perhaps<br>
something along the lines of &quot;Does anybody have reasons this<br>
document should not progress towards publication?&quot; might do.<br>
<span class=3D"HOEnZb"></span><br></blockquote><div><br>So, back in the day=
s when we were talking about the move from a 3-stage process to a 2-stage p=
rocess, I wrote draft-hardie-advance-mechanics.=A0 That described our then-=
extent process=A0 this way:<br>
<br><pre>   In practice, IETF document processing has evolved to a model wh=
ich
   can be described as &quot;objection based processing&quot;.  A document =
put
   forward by an author team advances from the relevant working group to
   IETF consideration after all objections from within the working group
   have been considered.  The IETF Last Call is, in practice, a way for
   the larger community to object to a document or elements within it.
   IESG document processing is, fundamentally, a process by which a
   sponsor resolves any objections raised by other area directors;
   though the term used is &quot;discuss&quot; and some delegation occurs (=
to
   document shepherds or review teams), the basic model is clear.
<br>I don&#39;t think that true consensus is achieved by the lack of object=
ion, but the community <br>seems to have accepted it as &quot;rough consens=
us&quot;.  <br><br>Could we do better?  Absolutely.  We could, for example,=
  formalize the third-party reviews <br>
by other areas such that a demonstration that proposals were acceptable in =
a broader Internet <br>context was fundamental (either at charter time, at =
working group draft acceptance time, <br>at proposed  publication, periodic=
ally for advancement, or at all of the above). That would <br>
get voices known to have analysed it heard, and give us a lot more confiden=
ce that the <br>proposal wasn&#39;t narrow in its examination of the impact=
 of its work.<br><br>But this is a volunteer organization, and the practica=
l truth is that we don&#39;t have the volunteer<br>
energy to do that or the funds to pay for it (or trust in anyone we&#39;d p=
ay, as another issue).  <br>So, bluntly, we should take what we get and use=
 it as we can.  If Pete can&#39;t figure out what <br>to make of a +1 by a =
5 term IESG member and sitting IAB Chair, then he&#39;ll have to evaluate <=
br>
the document without that input.  He&#39;ll have to evaluate it on its meri=
ts anyway, so it&#39;s <br>no big deal.  But  anything that discourages rev=
iew, however, cursory, is not really a good <br>thing.  Perhaps a note to t=
he reviewer like:<br>
<br>&quot;Thanks for taking the time.  It&#39;s good to know I can reach ou=
t to you for more data, should<br>I be on the fence on this one&quot;.<br><=
br>(I&#39;m thinking on heavy stock Crane paper, maybe in a cream, nicely l=
ettered.  Or, you know, as<br>
a jotted email or IM.)  <br><br>Even sent to a stranger, that would look ni=
ce and remind people that we&#39;re not voting.<br><br>Just some thoughts o=
n the topic,<br><br>Ted<br><br><br><br><br></pre></div></div>

--089e01538794a3e4f504defadb29--

From brian.e.carpenter@gmail.com  Wed Jun 12 13:37:36 2013
Return-Path: <brian.e.carpenter@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 5959111E80F8 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 13:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 cb71EuaylobH for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 13:37:35 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id C557C11E80E7 for <ietf@ietf.org>; Wed, 12 Jun 2013 13:37:35 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id lj1so4102144pab.31 for <ietf@ietf.org>; Wed, 12 Jun 2013 13:37:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wiaz68U3k5G7HMTbaKWZggznf4Gf4UyCx/YGW0OUNLM=; b=uPbDcWGvJ6dsGjFaeicFuL8OqlUtSBStZow3v6Rtlp7J0JQFHGWVAtQ8TXHWLK16Wr /Jds12vIm3Qg+WDydeLqWvrNBqR4m0g7whjChl+hsS3rexlCZbJTLmbvW1YYd/G1r5Gx rWyF16EMldbi91/T/AYTcBfnOEZTnuZEOAdCNZOPy7Rfagzof6OAgKfGb4V4+y50wkF+ bZrzd4afZnzsgP0Fy2n9m0MSwDGTkpLdlYB7dDfvcI6vRxPAknJa935uUK17r2+NJanB PiusI1uKqum3dh3BPOm2Wnqm13daqHq0zNd/fswA6TnwkIZNEN8TxFn+dP86GAId0jTe NCTQ==
X-Received: by 10.66.158.9 with SMTP id wq9mr25922715pab.189.1371069455037; Wed, 12 Jun 2013 13:37:35 -0700 (PDT)
Received: from [192.168.1.2] (153.235.252.27.dyn.cust.vf.net.nz. [27.252.235.153]) by mx.google.com with ESMTPSA id al2sm20350784pbc.25.2013.06.12.13.37.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Jun 2013 13:37:34 -0700 (PDT)
Message-ID: <51B8DC13.4000305@gmail.com>
Date: Thu, 13 Jun 2013 08:37:39 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com>	<51B6710E.4040800@cs.tcd.ie>	<51B77E77.1030601@qti.qualcomm.com> <51B78312.1010108@gmail.com> <51B78907.6070309@qti.qualcomm.com>
In-Reply-To: <51B78907.6070309@qti.qualcomm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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, 12 Jun 2013 20:37:36 -0000

'scuse front posting, but I'm going to outrageously summarise
Pete's point as "I want substance in all Last Call comments", or
alternatively "I will ignore +1 just as I will ignore -1".

That isn't unreasonable, but personally I would interpret "I've
read it and I think it's good work" as substantive, especially
if it comes from a known expert. YMMV

Regards
   Brian

On 12/06/2013 08:31, Pete Resnick wrote:
> On 6/11/13 3:05 PM, Brian E Carpenter wrote:
>> Pete,
>>
>> On 12/06/2013 07:45, Pete Resnick wrote:
>>   
>>> It's interesting to see that people are interpreting me to mean I want
>>> more text. I don't. I want less. Save your breath. There is no reason to
>>> send one line of support, and it only encourages the view that we're
>>> voting. Details below.
>>>      
>> Just to test what you are saying, let me ask the following.
> 
> Oooo...I love a test.
> 
>> How would you react to one that says something like:
>> "I've read the draft, and I've considered Joe Blow's objection, but I
>> still support publication of the draft" (*not" followed by a reasoned
>> rebuttal of Joe Blow's argument)?
>>    
> 
> I would be rather grumpy with such a message. If there's an outstanding
> (reasonable) objection to a document, I need to know why to consider
> that argument in the rough. I'd have to ask for more detail from the
> sender. If the response I get back is, "I figured it was obvious why Joe
> Blow was full of crap", I'd ask, "Then why did you bother posting?" If
> the sender happens to be an expert (and Joe Blow is not), I'm still not
> going to take it at face value that Joe Blow is wrong. If I did, Joe
> would be well within rights to appeal because his argument got blown off.
> 
> So, if you're saying something that is perfectly obvious, no need to say
> it. But if it's not perfectly obvious, I do want more text.
> 
> pr
> 

From presnick@qti.qualcomm.com  Wed Jun 12 13:43:03 2013
Return-Path: <presnick@qti.qualcomm.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 5EBB311E8109 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 13:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ohEYrOm2TPZD for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 13:42:59 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2E2E911E80F0 for <ietf@ietf.org>; Wed, 12 Jun 2013 13:42:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1371069779; x=1402605779; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=tdqeXEnx0+k1abJ3mZKgEP9+U+YTwF8QzfDGEXZKIoE=; b=oL4GweLMTeixQgWThElzrequOuKMS4zSFX8e3SpX0HnqybUhl9M66Ylu T4+kdAFH1OAp73juKsK7I/nnmmMP7Iwrp8unHiQ8PH1HF/FTT2igQfvDB J5lNZs0r8/+RFGQQrwgB+g1RdB6uk4FC0cVtiPVgatGoDfe5/tD7GYjNS s=;
X-IronPort-AV: E=Sophos;i="4.87,854,1363158000"; d="scan'208";a="44717888"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth01.qualcomm.com with ESMTP; 12 Jun 2013 13:42:43 -0700
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 12 Jun 2013 13:42:43 -0700
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 12 Jun 2013 13:42:42 -0700
Message-ID: <51B8DD3F.1000803@qti.qualcomm.com>
Date: Wed, 12 Jun 2013 15:42:39 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com>	<51B6710E.4040800@cs.tcd.ie>	<51B77E77.1030601@qti.qualcomm.com>	<51B78312.1010108@gmail.com> <51B78907.6070309@qti.qualcomm.com> <51B8DC13.4000305@gmail.com>
In-Reply-To: <51B8DC13.4000305@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: 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, 12 Jun 2013 20:43:03 -0000

On 6/12/13 3:37 PM, Brian E Carpenter wrote:
> 'scuse front posting, but I'm going to outrageously summarise
> Pete's point as "I want substance in all Last Call comments", or
> alternatively "I will ignore +1 just as I will ignore -1".
>    

Maybe not outrageous, but certainly wrong because...

> ...personally I would interpret "I've
> read it and I think it's good work" as substantive

I agree with that.

Confused now? Go back and look at my message of an hour and a half ago 
and see if you can tell why I agree. :-)

As I've said to other people, I like straw men. They make fine 
neighbors. They're quiet, and they don't smoke.

But if you're going to summarize (or summarise), best to do so accurately.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From sm@resistor.net  Wed Jun 12 14:21:46 2013
Return-Path: <sm@resistor.net>
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 2A6A111E80BA for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 14:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level: 
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 fVOucIX2NzEj for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 14:21:41 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F97211E80CC for <ietf@ietf.org>; Wed, 12 Jun 2013 14:21:38 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5CLLRLA010136; Wed, 12 Jun 2013 14:21:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1371072094; bh=LVSRID+YegughnbpiWmpbj0GSpglL9hirVCZ81+FtD8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=v6lm+VHyxNHxqc9wutjsjGLxdY4Y2S43V/SNNIOzQ79hYJ9nVURfUOFQndFBlyllp MCnH/8i/A/MwdDCcNtl4wYza7ZCiIEpM1HseH6IfC3PdIiV1pKrjZO8pflqACvm/2k LR+Sg+6gtDZbXki++B7mFYjf7T5wNePC7iOb66Lc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1371072094; i=@resistor.net; bh=LVSRID+YegughnbpiWmpbj0GSpglL9hirVCZ81+FtD8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JmcVL3MaN9zd9LZAU81ql+nr07P+TO7GN9Y9gVFMbSrRyeJIvvWkTQ155VqMXrBwt J9ROdsb3kVGDPAHawjafJRct0k7sSzuWPSNmPrbaVmRkTffRB12FNw97YnAaLHXvWY JphHnluaytdHhz1xB8dYnHrZOZ0iZVOsj7nryBFo=
Message-Id: <6.2.5.6.2.20130612135028.06e1e4b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 12 Jun 2013 14:10:03 -0700
To: Michael Thornburgh <mthornbu@adobe.com>, John C Klensin <john-ietf@jck.com>, Martin Stiemerling <martin.stiemerling@neclab.eu>
From: SM <sm@resistor.net>
Subject: RE: Last Call: <draft-thornburgh-adobe-rtmfp-07.txt> (Adobe's Secure Real-Time Media Flow Protocol) to Informational RFC
In-Reply-To: <D9D602D39A98E34D9C43E965BEC7439825F201E3@nambx08.corp.adob e.com>
References: <20130528161229.25215.37302.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130605072309.0be62c30@resistor.net> <D9D602D39A98E34D9C43E965BEC7439825F201E3@nambx08.corp.adobe.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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, 12 Jun 2013 21:21:46 -0000

Hi Michael,

I am adding my response to John and Martin at the end of this message.

At 14:51 11-06-2013, Michael Thornburgh wrote:
>the intended status is Informational because the specification 
>describes a protocol that was developed outside the IETF, the 
>protocol is in widespread use in the Internet today, and may be of 
>interest to the Internet community.  the Shepherd write-up does not 
>draw any connection (nor is there any connection) between the 
>intended Informational status and the existence of IPR.  aspects of 
>the protocol that are protected by IPR are disclosed in the 
>specification and are (and have been) available for the review of 
>the community.  the relevant IPR was disclosed (IPR 1942) 
>immediately after draft -00 was submitted.

Thanks for the explanation.  I don't have any problem with the IPR disclosure.

>my understanding of the "A-D Sponsored" process for an Informational 
>track document is that the IETF Last Call should serve as a final 
>check with the IETF community that there are no important concerns 
>that have been missed or misunderstood. as this protocol and 
>specification are not products of an IETF WG, technical changes to 
>the protocol itself are not expected; however, the specification 
>should be clear and complete enough that an independent and 
>interoperable implementation could be created from it.  i have 
>received thorough and detailed feedback from several members of the 
>community that i believe has helped me improve the quality and 
>clarity of the specification.

I'll comment about this in my response to Martin.

>in the course of face-to-face discussion at IETF-86 in the TSVWG 
>meeting, i was prompted to disclose additional detail and 
>supplementary information about the protocol, which i believe 
>improves the clarity of the specification.

Yes, I noticed that.

>the memo (and the protocol it describes) is not the product of a 
>WG.  the protocol was presented in person at IETF-77 (in the TSV 
>Area meeting) and IETF-86 (in the TSVWG meeting), and feedback was 
>solicited on the TSVWG and MMUSIC mailing lists.  at this time i am 
>not aware of any unaddressed concerns regarding this specification, 
>with the exception of your following comment that i am about to address.

I don't think that any technical concerns which might have been 
raised were not addressed.

>agreed.  i included this statement at the suggestion of the 
>Responsible (and Sponsoring) Area Director, to help establish the 
>breadth of deployment of the protocol, and therefore the relevance 
>of the specification in the RFC Series as an independent 
>submission.  the Shepherd, A-D and i are discussing your concern 
>regarding this statement off-list.  possible solutions are: move 
>this comment to the Shepherd write-up for the IESG's consideration, 
>change the wording to be more neutral, leave as-is or strike it completely.

My preference is to have something neutral but that can be ignored as 
it is nit.

At 02:44 12-06-2013, John C Klensin wrote:
>I think the advantages to the community of having
>widely-deployed protocols like this published for information
>are considerable.  It seems to me that those advantages are
>increasingly getting lost in our quest for consensus (or even
>unanimity).  Perhaps we should be handling them all as
>Independent Submissions where the community wouldn't even think
>it had a "vote", but, as Michael points out, community review
>often improves document quality.

Yes.

At 04:37 12-06-2013, Martin Stiemerling wrote:
>The last call is not intended to gather IETF consensus about this 
>draft but give the community an opportunity to see the draft and 
>comment on it before it progress to the IESG. This draft is an AD 
>sponsored draft.

I'll keep it short; the intended status is Informational, it's not 
worth spending too much time arguing about it. :-)

Regards,
-sm 


From l.wood@surrey.ac.uk  Wed Jun 12 14:56:09 2013
Return-Path: <l.wood@surrey.ac.uk>
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 16FEC11E8112 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 14:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.178
X-Spam-Level: 
X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[AWL=0.420,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=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 2f+vlwI3DNg0 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 14:55:59 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.171]) by ietfa.amsl.com (Postfix) with ESMTP id E13EF11E810C for <ietf@ietf.org>; Wed, 12 Jun 2013 14:55:58 -0700 (PDT)
Received: from [195.245.230.131:47931] by server-11.bemta-3.messagelabs.com id D9/33-05438-76EE8B15; Wed, 12 Jun 2013 21:55:51 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-78.messagelabs.com!1371074134!23070346!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20086 invoked from network); 12 Jun 2013 21:55:35 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-9.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 12 Jun 2013 21:55:35 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Wed, 12 Jun 2013 22:55:34 +0100
From: <l.wood@surrey.ac.uk>
To: <ietf@ietf.org>
Date: Wed, 12 Jun 2013 22:55:34 +0100
Subject: Renaming RFC
Thread-Topic: Renaming RFC
Thread-Index: AQHOZ7eRjouKx/TJbkaIj2DMb8l4yg==
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EAD@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 12 Jun 2013 21:56:09 -0000

RFC should be renamed to Resulted From Comments. It's now the endpoint of t=
he process; Request For Comments dated from when it was the start.

(Though RFCs through workgroups are arguably Resulted from Collaboration/Co=
nsensus/Chairing).

If you're going to alter the process in any way, start here.

Lloyd Wood
http://sat-net.com/L.Wood/



From l.wood@surrey.ac.uk  Wed Jun 12 14:58:44 2013
Return-Path: <l.wood@surrey.ac.uk>
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 C94E811E810E for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 14:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.22
X-Spam-Level: 
X-Spam-Status: No, score=-3.22 tagged_above=-999 required=5 tests=[AWL=0.378,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=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 UwZLnynN-T2l for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 14:58:40 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.168]) by ietfa.amsl.com (Postfix) with ESMTP id A33A121E812C for <ietf@ietf.org>; Wed, 12 Jun 2013 14:58:39 -0700 (PDT)
Received: from [195.245.230.131:52870] by server-8.bemta-3.messagelabs.com id CD/AC-25864-E0FE8B15; Wed, 12 Jun 2013 21:58:38 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-78.messagelabs.com!1371074318!30368614!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27199 invoked from network); 12 Jun 2013 21:58:38 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-6.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 12 Jun 2013 21:58:38 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Wed, 12 Jun 2013 22:58:37 +0100
From: <l.wood@surrey.ac.uk>
To: <presnick@qti.qualcomm.com>, <bob.hinden@gmail.com>
Date: Wed, 12 Jun 2013 22:56:05 +0100
Subject: RE: Content-free Last Call comments
Thread-Topic: Content-free Last Call comments
Thread-Index: Ac5noXjzNmtjA+i5QAeJYDk+e2rIEgAFiqt+
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EAE@EXMB01CMS.surrey.ac.uk>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <9C916195-0426-4484-A45E-87BEAC79884C@gmail.com>, <51B8C95A.1080208@qti.qualcomm.com>
In-Reply-To: <51B8C95A.1080208@qti.qualcomm.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 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, 12 Jun 2013 21:58:44 -0000

Are the IESG people who disagree with you speaking for the IESG, or for the=
mselves?

I've noticed a tendency for IESG weight to be (inadvertently?) thrown aroun=
d, lending more weight to comments than would otherwise be given.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Pete Resni=
ck [presnick@qti.qualcomm.com]
Sent: 12 June 2013 20:17
To: Bob Hinden
Cc: ietf@ietf.org
Subject: Re: Content-free Last Call comments

On 6/12/13 10:33 AM, Bob Hinden wrote:
> Please describe the context of your email.  Are you speaking for the IESG=
, yourself as an AD, or an individual?

Oh, crap. And given that I'm usually the one giving people a hard time
about *this* issue, I feel especially bad about not being clearer.

This is Pete, hatless individual talking. There are (as you've seen)
IESG people, past and present who disagree with me. Nothing I've said is
anything we've come to an IESG consensus around. Insofar as I think that
only saying "I support this document" is a bogus thing to say, I am
revealing something about how I behave as an AD in the face of such
statements, and my further explanations that I value reviews and take
them seriously also indicates my views as an AD, but that doesn't
indicate some policy that I'm instituting with WGs for which I am
responsible.

I am terribly sorry about not making this clear up front. My sincere
apologies. I hope nobody took this as a other than my commentary.

Sheepishly,
pr

--
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From stephen.farrell@cs.tcd.ie  Wed Jun 12 15:11:37 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
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 6891021F96D9 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 15:11:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 gdECqDTliHiD for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 15:11:32 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 66DC821F96A9 for <ietf@ietf.org>; Wed, 12 Jun 2013 15:11:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 27220BE80; Wed, 12 Jun 2013 23:11:01 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RPNtyYSjfL7y; Wed, 12 Jun 2013 23:10:58 +0100 (IST)
Received: from [10.87.48.12] (unknown [86.41.52.50]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1DA80BE54; Wed, 12 Jun 2013 23:10:58 +0100 (IST)
Message-ID: <51B8F1E7.4070203@cs.tcd.ie>
Date: Wed, 12 Jun 2013 23:10:47 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: l.wood@surrey.ac.uk
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <9C916195-0426-4484-A45E-87BEAC79884C@gmail.com>, <51B8C95A.1080208@qti.qualcomm.com> <290E20B455C66743BE178C5C84F12408223F494EAE@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EAE@EXMB01CMS.surrey.ac.uk>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: presnick@qti.qualcomm.com, bob.hinden@gmail.com, 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, 12 Jun 2013 22:11:37 -0000

On 06/12/2013 10:56 PM, l.wood@surrey.ac.uk wrote:
> 
> Are the IESG people who disagree with you speaking for the IESG, or for themselves?

That's really not clear already? In any case, I was disagreeing
with Pete as an individual since he was wrong regardless of hats.
He and I do that all the time and both find it amusing:-)

> I've noticed a tendency for IESG weight to be (inadvertently?) thrown around, lending more weight to comments than would otherwise be given.

I've not noticed that. Maybe I perceive things differently of
course, but people ought know not to take opinions any more or
less seriously just because someone's on some I* thing at the
moment.

S.

> 
> Lloyd Wood
> http://sat-net.com/L.Wood/
> 
> 
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Pete Resnick [presnick@qti.qualcomm.com]
> Sent: 12 June 2013 20:17
> To: Bob Hinden
> Cc: ietf@ietf.org
> Subject: Re: Content-free Last Call comments
> 
> On 6/12/13 10:33 AM, Bob Hinden wrote:
>> Please describe the context of your email.  Are you speaking for the IESG, yourself as an AD, or an individual?
> 
> Oh, crap. And given that I'm usually the one giving people a hard time
> about *this* issue, I feel especially bad about not being clearer.
> 
> This is Pete, hatless individual talking. There are (as you've seen)
> IESG people, past and present who disagree with me. Nothing I've said is
> anything we've come to an IESG consensus around. Insofar as I think that
> only saying "I support this document" is a bogus thing to say, I am
> revealing something about how I behave as an AD in the face of such
> statements, and my further explanations that I value reviews and take
> them seriously also indicates my views as an AD, but that doesn't
> indicate some policy that I'm instituting with WGs for which I am
> responsible.
> 
> I am terribly sorry about not making this clear up front. My sincere
> apologies. I hope nobody took this as a other than my commentary.
> 
> Sheepishly,
> pr
> 
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
> 
> 
> 

From presnick@qti.qualcomm.com  Wed Jun 12 17:54:37 2013
Return-Path: <presnick@qti.qualcomm.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 C473E21E8088 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 17:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 elDVmOtgNrfF for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 17:54:33 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 10B9521F8B98 for <ietf@ietf.org>; Wed, 12 Jun 2013 17:54:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1371084872; x=1402620872; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=R9Z9PnpdxSc7fFiV1LUk2SyIB8lRbMyfmqQ6r5vN2so=; b=dWSOmQLVdNV2N/Fo3fcU0pQMUqTwER6MOGViwSc6U2q3dqR8KaIeMF7V eVBWRBA8K1jigR9J0PQamo0uj4rAC/pmokdCiuFc6ViOduAEIuT2H4s0i 88ym52tNDRMi7u+I4RHcU2IvaC6eMhrfgMPChnTsv+nUIdfFrTmRZz/PZ 8=;
X-IronPort-AV: E=Sophos;i="4.87,855,1363158000"; d="scan'208";a="56064984"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 12 Jun 2013 17:54:22 -0700
X-IronPort-AV: E=Sophos;i="4.87,855,1363158000"; d="scan'208";a="489575502"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 12 Jun 2013 17:54:22 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 12 Jun 2013 17:54:21 -0700
Message-ID: <51B9183C.6090205@qti.qualcomm.com>
Date: Wed, 12 Jun 2013 19:54:20 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com>	<9C916195-0426-4484-A45E-87BEAC79884C@gmail.com>, <51B8C95A.1080208@qti.qualcomm.com>	<290E20B455C66743BE178C5C84F12408223F494EAE@EXMB01CMS.surrey.ac.uk> <51B8F1E7.4070203@cs.tcd.ie>
In-Reply-To: <51B8F1E7.4070203@cs.tcd.ie>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: bob.hinden@gmail.com, 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: Thu, 13 Jun 2013 00:54:37 -0000

On 6/12/13 5:10 PM, Stephen Farrell wrote:
> On 06/12/2013 10:56 PM, l.wood@surrey.ac.uk wrote:
>
>    
>> Are the IESG people who disagree with you speaking for the IESG, or for themselves?
>>      
> That's really not clear already? In any case, I was disagreeing
> with Pete as an individual since he was wrong regardless of hats.
> He and I do that all the time and both find it amusing:-)
>    

Indeed, Stephen's wrongness is clearly a personal wrongness and not 
because he is on the IESG. ;-)

Seriously though, Bob and I chatted about this a bit offline, and I see 
how I could be interpreted as saying something IESG-ish, and that was 
absolutely not my intention.

Importantly, I also have no interest in turning anything I've said here 
into some procedure or policy, even if I convince Stephen and others of 
the error of their ways. :-) This conversation is truly about a set of 
principles, that (in my very individual opinion that I hope others will 
share) we should be careful to not fall into the pattern of treating 
Last Calls as simple votes on a topic, that we should not use language 
that leads us (or more importantly newcomers) to believe that we are 
doing so, and that we should be more concerned about why we think a 
document is good or bad rather than the number (or reputation) of people 
who claim that it is. Sometimes we fall into the habit of assuming, "I 
know what Pete is talking when he says he supports a document, so 
everybody else will too." I think that's a bad habit. But this is 
(hopefully) something for the Tao, not something for RFC 2026.

>> I've noticed a tendency for IESG weight to be (inadvertently?) thrown around, lending more weight to comments than would otherwise be given.
>>      
> I've not noticed that. Maybe I perceive things differently of
> course, but people ought know not to take opinions any more or
> less seriously just because someone's on some I* thing at the
> moment.

Much as I would like what Stephen says to be true, I think Lloyd's 
probably right: People give more weight to opinions coming from people 
with dots on their name badges. I try to be careful because of that, but 
I wasn't careful enough this time.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From dwm@xpasc.com  Wed Jun 12 18:06:42 2013
Return-Path: <dwm@xpasc.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 4FA5821F9928 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 18:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level: 
X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[AWL=-0.431, BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 PomURk5f0-Ec for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 18:06:36 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 4EC3E21F9634 for <ietf@ietf.org>; Wed, 12 Jun 2013 18:06:36 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id CE3A440265 for <ietf@ietf.org>; Thu, 13 Jun 2013 01:06:35 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id r5D16ZGA032238 for <ietf@ietf.org>; Wed, 12 Jun 2013 18:06:35 -0700
Date: Wed, 12 Jun 2013 18:06:35 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: Content-free Last Call comments
In-Reply-To: <51B9183C.6090205@qti.qualcomm.com>
Message-ID: <alpine.LRH.2.01.1306121758010.30915@egate.xpasc.com>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com> <B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com> <51B63905.2020807@qti.qualcomm.com> <9C916195-0426-4484-A45E-87BEAC79884C@gmail.com>, <51B8C95A.1080208@qti.qualcomm.com> <290E20B455C66743BE178C5C84F12408223F494EAE@EXMB01CMS.surrey.ac.uk> <51B8F1E7.4070203@cs.tcd.ie> <51B9183C.6090205@qti.qualcomm.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.87-g7939dec
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: Thu, 13 Jun 2013 01:06:42 -0000

On Wed, 12 Jun 2013, Pete Resnick wrote:

> Much as I would like what Stephen says to be true, I think Lloyd's probably
> right: People give more weight to opinions coming from people with dots on
> their name badges. 

One has to be able to see the dots for it to possibly matter. Out here at
the end of the email connection, I have almost no clue who might have a
dot. I give weight to folks I've observed over time to provide thoughful
comments. Many have been ADs, etc. at some point. Unless a message
explicitly says "I'm writing in role as an AD", it doesn't matter. 

The exception would be the WG chairs and ADs associated with WGs I follow.

I'm well aware that any review comment I'd make would need to logically
explain my position because I'm relatively unknown.

Dave Morris


From randy_presuhn@mindspring.com  Wed Jun 12 18:51:32 2013
Return-Path: <randy_presuhn@mindspring.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 D4C4621F8FF3 for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 18:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 gsUKtK4fFHqz for <ietf@ietfa.amsl.com>; Wed, 12 Jun 2013 18:51:02 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id 66ECD21F8F61 for <ietf@ietf.org>; Wed, 12 Jun 2013 18:51:02 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=N0DgqFgkaS7fxGIozsGJXNGXrS54g6CVipU54FYxqvhKS5SmV1BFlfobRraXG+dZ; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.48] (helo=elwamui-rustique.atl.sa.earthlink.net) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Umwgn-0006g3-M3 for ietf@ietf.org; Wed, 12 Jun 2013 21:51:01 -0400
Received: from 76.254.49.35 by webmail.earthlink.net with HTTP; Wed, 12 Jun 2013 21:51:01 -0400
Message-ID: <19498732.1371088261656.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net>
Date: Wed, 12 Jun 2013 18:51:01 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: ietf@ietf.org
Subject: Re: Content-free Last Call comments
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888ba196d48fc2e3f0891d18168aa899d4229891c3128e228bf350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.48
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.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: Thu, 13 Jun 2013 01:51:32 -0000

Hi -

>From: Ted Lemon <Ted.Lemon@nominum.com>
>Sent: Jun 12, 2013 12:42 PM
>To: Peter Saint-Andre <stpeter@stpeter.im>
>Cc: "<ned+ietf@mauve.mrochek.com>" <ned+ietf@mauve.mrochek.com>, Alexey Me=
lnikov <alexey.melnikov@isode.com>, Pete Resnick <presnick@qti.qualcomm.com=
>, "ietf@ietf.org Discussion" <ietf@ietf.org>
>Subject: Re: Content-free Last Call comments
>
>On Jun 12, 2013, at 3:31 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
>> I think these messages are useless, not harmful. But perhaps I have
>> more confidence in the inherent skepticism of your average IETF
>> participant than Pete does...
>
>FWIW, until I read Pete's document on consensus, I thought that +1
>statements were part of the consensus process.   This was not a
>strongly held opinion=E2=80=94it was just my understanding of how
>consensus operated, from having watched other working group
>chairs run their working groups.   I think the point Pete is
>making is very important, because the consensus process Pete
>describes is more in keeping with how I think the IETF ought
>to operate than the process in which +1 counts for something.
...

As a former WG chair who's had to deal with some very rough
consensus calls...

Not "counting" a "+1" is more consistent with a classical definition
of consensus.  But, particularly at a WG level (less so, perhaps,
at the IETF level) "+1" is very helpful in determining whether
the previously mentioned "Abilene Paradox" should be of concern.

Randy

From joelja@bogus.com  Thu Jun 13 01:01:59 2013
Return-Path: <joelja@bogus.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 EC2CF21F9A33 for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 01:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 JLTNgO2eWfDL for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 01:01:58 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A7EC021F99BA for <ietf@ietf.org>; Thu, 13 Jun 2013 01:01:57 -0700 (PDT)
Received: from wifi-216-68.mtg.afnog.org (wifi-216-68.mtg.afnog.org [196.200.216.68]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r5D81oqq068788 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 13 Jun 2013 08:01:53 GMT (envelope-from joelja@bogus.com)
Message-ID: <51B97C6C.2030809@bogus.com>
Date: Thu, 13 Jun 2013 10:01:48 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Content-free Last Call comments
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com> <51B6710E.4040800@cs.tcd.ie>	<51B77E77.1030601@qti.qualcomm.com>	<CAKHUCzykXj1dO4KgOFFUsyhBk_W8Aj44PGogHyAGBrnvF7PTxw@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751D16B0@mbx-01.win.nominum.com>	<CAKHUCzw0e7OBWmF-DBGYDcF_1A3ORr3RcCXFooTDuEFLoBzA5A@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751D199C@mbx-01.win.nominum.com>	<CAKHUCzzxPJutz_fPdr18amQmLoptG0c10PUCvpXPN_po8AZcTg@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751D1AB6@mbx-01.win.nominum.com>	<CAKHUCzyE_RA8tnD93gW2Td_SsWvxowQTVL2LMH8Pex+tjt8dCw@mail.gmail.com>	<01OUR5HQDG62000054@mauve.mrochek.com> <51B8C009.6050509@isode.com>	<51B8C17E.2090804@stpeter.im> <51B8CCA0.5080503@stpeter.im> <8D23D4052ABE7A4490E77B1A012B6307751D3D50@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751D3D50@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 13 Jun 2013 08:01:57 +0000 (UTC)
Cc: "<ned+ietf@mauve.mrochek.com>" <ned+ietf@mauve.mrochek.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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: Thu, 13 Jun 2013 08:01:59 -0000

On 6/12/13 9:42 PM, Ted Lemon wrote:
> On Jun 12, 2013, at 3:31 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
>> I think these messages are useless, not harmful. But perhaps I have
>> more confidence in the inherent skepticism of your average IETF
>> participant than Pete does...
> FWIW, until I read Pete's document on consensus, I thought that +1 statements were part of the consensus process.   This was not a strongly held opinion—it was just my understanding of how consensus operated, from having watched other working group chairs run their working groups.   I think the point Pete is making is very important, because the consensus process Pete describes is more in keeping with how I think the IETF ought to operate than the process in which +1 counts for something.
+1 / -1

are conventions that crept in from other standards bodies, they don't 
have any particular place or meaning here, apart from what you can 
literally interpret them as e.g. the equivalent of hand raising in 
agreement or disagreement.
>
> (BTW, in case it wasn't obvious, I've been engaging in this discussion with my AD and working group chair experience in the back of my mind, but my AD hat off.)
>
>


From daedulus@btconnect.com  Thu Jun 13 02:30:24 2013
Return-Path: <daedulus@btconnect.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 5CDE821F91A3 for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 02:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 e9pnXWIVH1jW for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 02:30:07 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id E2D5121F9A76 for <ietf@ietf.org>; Thu, 13 Jun 2013 02:30:06 -0700 (PDT)
Received: from mail53-va3-R.bigfish.com (10.7.14.225) by VA3EHSOBE005.bigfish.com (10.7.40.25) with Microsoft SMTP Server id 14.1.225.23; Thu, 13 Jun 2013 09:30:05 +0000
Received: from mail53-va3 (localhost [127.0.0.1])	by mail53-va3-R.bigfish.com (Postfix) with ESMTP id A6636600CE	for <ietf@ietf.org>; Thu, 13 Jun 2013 09:30:05 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -13
X-BigFish: PS-13(z569dhz9371I542Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail53-va3 (localhost.localdomain [127.0.0.1]) by mail53-va3 (MessageSwitch) id 1371115803874185_1554; Thu, 13 Jun 2013 09:30:03 +0000 (UTC)
Received: from VA3EHSMHS019.bigfish.com (unknown [10.7.14.248])	by mail53-va3.bigfish.com (Postfix) with ESMTP id 91ACC420090; Thu, 13 Jun 2013 09:30:03 +0000 (UTC)
Received: from AMSPRD0711HT003.eurprd07.prod.outlook.com (157.56.250.181) by VA3EHSMHS019.bigfish.com (10.7.99.29) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 13 Jun 2013 09:29:56 +0000
Received: from DBXPRD0210HT002.eurprd02.prod.outlook.com (157.56.253.181) by pod51017.outlook.com (10.242.14.164) with Microsoft SMTP Server (TLS) id 14.16.324.0; Thu, 13 Jun 2013 09:29:42 +0000
Message-ID: <024001ce6818$a6a41cc0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <l.wood@surrey.ac.uk>, <ietf@ietf.org>
References: <290E20B455C66743BE178C5C84F12408223F494EAD@EXMB01CMS.surrey.ac.uk>
Subject: Re: Renaming RFC
Date: Thu, 13 Jun 2013 10:30:25 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.181]
X-FOPE-CRA-Verdict: 157.56.250.181$surrey.ac.uk%13189%4%btconnect.com%False%False%0$
X-OriginatorOrg: btconnect.com
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: Thu, 13 Jun 2013 09:30:24 -0000

----- Original Message -----
From: <l.wood@surrey.ac.uk>
To: <ietf@ietf.org>
Sent: Wednesday, June 12, 2013 10:55 PM
Subject: Renaming RFC



RFC should be renamed to Resulted From Comments. It's now the endpoint
of the process; Request For Comments dated from when it was the start.

<tp>

Fundamentally disagree.

Some SDOs produce standards as tablets of stone, and the world at large
is not even allowed to read them.

The IETF says this is the best we can do, can you help us make it
better, by making a request for comments.  For me, this is the reason
why the IETF succeeds, because it looks to engage the whole world, to do
yet better.

Tom Petch

</tp>

(Though RFCs through workgroups are arguably Resulted from
Collaboration/Consensus/Chairing).

If you're going to alter the process in any way, start here.

Lloyd Wood
http://sat-net.com/L.Wood/





From fgont@si6networks.com  Thu Jun 13 04:01:03 2013
Return-Path: <fgont@si6networks.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 50E3E21F9A49 for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 04:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 wOzk4LrYVFuQ for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 04:01:02 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id F0EC021F99FE for <ietf@ietf.org>; Thu, 13 Jun 2013 04:01:01 -0700 (PDT)
Received: from [2001:5c0:1400:a::693] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1Un5H2-0007hD-VR; Thu, 13 Jun 2013 13:01:01 +0200
Message-ID: <51B9A66C.10207@si6networks.com>
Date: Thu, 13 Jun 2013 13:01:00 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: ipv6hackers meeting in Berlin (July 28th, 2013)
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Thu, 13 Jun 2013 11:01:03 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Folks,

- From a couple of years now, we have had a mailing-list devoted to IPv6
hacking (i.e., testing, tools, low-level stuff, etc.). The
mailing-list ("charter", subscription options, etc.) is available at:
<http://lists.si6networks.com/listinfo/ipv6hackers/>.

We're planning to have our first in-person meeting on July 28th, 2013,
in Berlin (most likely in the afternoon, between lunch and the IETF
welcome reception). The venue would be either the IETF venue
(InterContinental Berlin), or some nearby hotel/room (to be confirmed
soon).

We're planning to have some presentations (which MUST be accompanied
with code :-) ), and might also have an IPv6 mini-hackathon (i.e.,
work on code, test implementations, try stuff).

In order to plan for the meeting, we'd need to have some indication of
how many people would attend, whether they would have stuff to
present, etc. So I've set up a very short on-line survey to help us
plan for the meeting.

If you're interested, please take 5 minutes to complete the survey at:
<https://www.surveymonkey.com/s/FFL386K>

Thanks!

Best regards,
- -- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJRuaZpAAoJEK4lDVUdTnSSkKQQAIWh/Mq05UuWxkgtExF4M3g4
+uHMsw4+RH1lWUn3Ti8RhVLCJuDVJZbhgOGDC8Z7+sHj5NxcQMWEjTAuOjiBkRXD
LG3U9DNGAkk5NxHXHqIRRa1o01PnN/+kSMlly+n+BnSvfMMYTaQ/raVP16wV/HoH
PMwt683Q2HHaTJKzb5iALYySToqPorgBTAA8Hd2Rz36U5+4WXra0shzAnNiaz+fy
aIstttyGzUzgara/8Hkbl07U2fYE+/qX6DRxjiXrFBpqjcXUuC4lBZpssp6rCNKG
Z1rGgMG5paLkJ229Mk8HY0c0dcBiNniksL4HcMjqpbvFjks0lIDhGlL7dvq1qO0e
W+1n8Z7VPkCWyX+KDz8vZt1/aP3f6DFa8lPomnw2KOL41a/ClR5pdib7nlsZFexE
1uX10PfpYf7z1kL044VCadHZnlLjACOLHk1xSqdYH9fRGOb3kuKJD0EdoHtHSr1q
TRpgCtArV9fk7O1ducXNbVfHK/B7+xCM5uzXOzpbYKPJ62OguL+hs5OnVbqylzhV
lPBW4QfVHoDPL8/OOYKDLGZcjxOmDiXGpmEH+5RqrF5K4KZqVwBahvS44ZetEYuO
WEWQZFtJOx/9DeTIcCxcUAsIpBpIEVJtRmtLF3aLyLUfMxbKuDehpzdC6n3P5hwV
mpg+egMOpHuoQx+DjhWJ
=KV2V
-----END PGP SIGNATURE-----

From rlb@ipv.sx  Thu Jun 13 07:06:56 2013
Return-Path: <rlb@ipv.sx>
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 D974121F9798 for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 07:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.303
X-Spam-Level: 
X-Spam-Status: No, score=-0.303 tagged_above=-999 required=5 tests=[AWL=0.122,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 T9-Il02OQZ53 for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 07:06:53 -0700 (PDT)
Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4D4C221F8763 for <ietf@ietf.org>; Thu, 13 Jun 2013 07:06:51 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id f4so7035418oah.7 for <ietf@ietf.org>; Thu, 13 Jun 2013 07:06:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=D0xJk+GwpilyJJdv7v6xvdU45GdkLTzF+LV00OW4wYI=; b=Pt4ugR1wK7a6MwON+VXDYAnFPcR+1WgW0nuVfEt4rVca3QqppAYvJcOll3I6+M1lBv O10rBASs2YijfwavHjSWZ3W+cD6aAEJRx7k2NvEt08lw1t0ufts7+eC/QfuwLWQjxHNR i+dZnEkSrQLcEUB7qpyzNPn7XBC0Sav6BiK1AWE1pqcuWy1b46hptEGgIayCEdD4xP5Z JGm26YyYi24rcpnH9KuDrrctzJlZa8m/FKlQCKmLHMHG3yFPNGMMpBP6RIM/ThLTTPy9 uYXn7PfGcxSEdAjdmG6VWYqu3rMCc80jlQ2D5F4DqfH/sKR9yBEE9lqUEhsP7L4kia+E ifrA==
MIME-Version: 1.0
X-Received: by 10.60.42.237 with SMTP id r13mr856948oel.61.1371132410685; Thu, 13 Jun 2013 07:06:50 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Thu, 13 Jun 2013 07:06:50 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <024001ce6818$a6a41cc0$4001a8c0@gateway.2wire.net>
References: <290E20B455C66743BE178C5C84F12408223F494EAD@EXMB01CMS.surrey.ac.uk> <024001ce6818$a6a41cc0$4001a8c0@gateway.2wire.net>
Date: Thu, 13 Jun 2013 10:06:50 -0400
Message-ID: <CAL02cgT11p1oy_wpYxKwHPHVm68xONU9U+SbuqaeCi9zTSygbg@mail.gmail.com>
Subject: Re: Renaming RFC
From: Richard Barnes <rlb@ipv.sx>
To: "t.p." <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=001a11c206aa476f9204df09a426
X-Gm-Message-State: ALoCoQlNdP2L4citq36DYwbBU6GJ+Itlfn89hUB2BjLoAGV8ZmtBb4I323XAwOyvVFaMfA1HWPwD
Cc: "ietf@ietf.org" <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: Thu, 13 Jun 2013 14:06:57 -0000

--001a11c206aa476f9204df09a426
Content-Type: text/plain; charset=ISO-8859-1

Cf. <http://tools.ietf.org/html/rfc5513>


On Thu, Jun 13, 2013 at 5:30 AM, t.p. <daedulus@btconnect.com> wrote:

> ----- Original Message -----
> From: <l.wood@surrey.ac.uk>
> To: <ietf@ietf.org>
> Sent: Wednesday, June 12, 2013 10:55 PM
> Subject: Renaming RFC
>
>
>
> RFC should be renamed to Resulted From Comments. It's now the endpoint
> of the process; Request For Comments dated from when it was the start.
>
> <tp>
>
> Fundamentally disagree.
>
> Some SDOs produce standards as tablets of stone, and the world at large
> is not even allowed to read them.
>
> The IETF says this is the best we can do, can you help us make it
> better, by making a request for comments.  For me, this is the reason
> why the IETF succeeds, because it looks to engage the whole world, to do
> yet better.
>
> Tom Petch
>
> </tp>
>
> (Though RFCs through workgroups are arguably Resulted from
> Collaboration/Consensus/Chairing).
>
> If you're going to alter the process in any way, start here.
>
> Lloyd Wood
> http://sat-net.com/L.Wood/
>
>
>
>
>

--001a11c206aa476f9204df09a426
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Cf. &lt;<a href=3D"http://tools.ietf.org/html/rfc5513">htt=
p://tools.ietf.org/html/rfc5513</a>&gt;<br></div><div class=3D"gmail_extra"=
><br><br><div class=3D"gmail_quote">On Thu, Jun 13, 2013 at 5:30 AM, t.p. <=
span dir=3D"ltr">&lt;<a href=3D"mailto:daedulus@btconnect.com" target=3D"_b=
lank">daedulus@btconnect.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">----- Original Message ---=
--<br>
From: &lt;<a href=3D"mailto:l.wood@surrey.ac.uk">l.wood@surrey.ac.uk</a>&gt=
;<br>
To: &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br>
Sent: Wednesday, June 12, 2013 10:55 PM<br>
Subject: Renaming RFC<br>
<br>
<br>
<br>
RFC should be renamed to Resulted From Comments. It&#39;s now the endpoint<=
br>
of the process; Request For Comments dated from when it was the start.<br>
<br>
</div>&lt;tp&gt;<br>
<br>
Fundamentally disagree.<br>
<br>
Some SDOs produce standards as tablets of stone, and the world at large<br>
is not even allowed to read them.<br>
<br>
The IETF says this is the best we can do, can you help us make it<br>
better, by making a request for comments. =A0For me, this is the reason<br>
why the IETF succeeds, because it looks to engage the whole world, to do<br=
>
yet better.<br>
<br>
Tom Petch<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
&lt;/tp&gt;<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
(Though RFCs through workgroups are arguably Resulted from<br>
Collaboration/Consensus/Chairing).<br>
<br>
If you&#39;re going to alter the process in any way, start here.<br>
<br>
Lloyd Wood<br>
<a href=3D"http://sat-net.com/L.Wood/" target=3D"_blank">http://sat-net.com=
/L.Wood/</a><br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div>

--001a11c206aa476f9204df09a426--

From barryleiba.mailing.lists@gmail.com  Thu Jun 13 08:32:36 2013
Return-Path: <barryleiba.mailing.lists@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 2210221F86D5 for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 08:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.107
X-Spam-Level: 
X-Spam-Status: No, score=-102.107 tagged_above=-999 required=5 tests=[AWL=-0.130, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 ltTYxPXdozKk for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 08:32:34 -0700 (PDT)
Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 59F3421F962D for <ietf@ietf.org>; Thu, 13 Jun 2013 08:32:34 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id pa12so7750435veb.39 for <ietf@ietf.org>; Thu, 13 Jun 2013 08:32:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=WVPsrE3QiaEDTvmc4j6YOYS+xfo5n+BUkTQD7iRzwd4=; b=fidpjorpro+IDe23zQnbpFIUNMeoznxzwrmDm+pDYV3sCDxeoAUKhG4LoHov/O/cxu tcV57RH3GmMohTGfN4HZN4FrDaOShbKuvhPztwcF2KbC6lFORyyA1dOx7WOvIYlTjYke H9cI7gYF5rURzIObjVDt3mFcVMw0exjrRp90vcZ0gPj30VnCgombWMdHfw6V5o8GKYSC o9fPq576zC1cRTddrfsIKZQ+aIe+F+9iwCM9iGmybmafZP7Af1j4d1+t5vTSYRSoorSb JtZFF9U9qjMsPC/p1qBP5wVh3IVpA4bID+s5ED8T6JkY3OReY4fHYfi34l2sSXPYDo2U AgRg==
MIME-Version: 1.0
X-Received: by 10.52.34.7 with SMTP id v7mr472315vdi.96.1371137553557; Thu, 13 Jun 2013 08:32:33 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.234.105 with HTTP; Thu, 13 Jun 2013 08:32:33 -0700 (PDT)
In-Reply-To: <19498732.1371088261656.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net>
References: <19498732.1371088261656.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net>
Date: Thu, 13 Jun 2013 17:32:33 +0200
X-Google-Sender-Auth: sROmWKb5mGIK8FNJQOFKMniVvPA
Message-ID: <CAC4RtVA6XMgwspZJ=txCG8NA_OVdGutrJughu_F9LuxTiG24eg@mail.gmail.com>
Subject: Re: Content-free Last Call comments
From: Barry Leiba <barryleiba@computer.org>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Content-Type: multipart/alternative; boundary=20cf307c9e9ed16c6104df0ad672
Cc: "ietf@ietf.org" <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: Thu, 13 Jun 2013 15:32:36 -0000

--20cf307c9e9ed16c6104df0ad672
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Without agreeing with or disagreeing with Pete, I'll point out that Pete
was talking about IETF last call.  It's perfectly reasonable for a WG
participant who has been actively involved to say, "This one is ready.
 Ship it," and Pete isn't saying otherwise.  In that case there is context
that helps.

Barry

On Wednesday, June 12, 2013, Randy Presuhn wrote:

> Hi -
>
> >From: Ted Lemon <Ted.Lemon@nominum.com <javascript:;>>
> >Sent: Jun 12, 2013 12:42 PM
> >To: Peter Saint-Andre <stpeter@stpeter.im <javascript:;>>
> >Cc: "<ned+ietf@mauve.mrochek.com <javascript:;>>" <
> ned+ietf@mauve.mrochek.com <javascript:;>>, Alexey Melnikov <
> alexey.melnikov@isode.com <javascript:;>>, Pete Resnick <
> presnick@qti.qualcomm.com <javascript:;>>, "ietf@ietf.org <javascript:;>D=
iscussion" <
> ietf@ietf.org <javascript:;>>
> >Subject: Re: Content-free Last Call comments
> >
> >On Jun 12, 2013, at 3:31 PM, Peter Saint-Andre <stpeter@stpeter.im<javas=
cript:;>>
> wrote:
> >> I think these messages are useless, not harmful. But perhaps I have
> >> more confidence in the inherent skepticism of your average IETF
> >> participant than Pete does...
> >
> >FWIW, until I read Pete's document on consensus, I thought that +1
> >statements were part of the consensus process.   This was not a
> >strongly held opinion=97it was just my understanding of how
> >consensus operated, from having watched other working group
> >chairs run their working groups.   I think the point Pete is
> >making is very important, because the consensus process Pete
> >describes is more in keeping with how I think the IETF ought
> >to operate than the process in which +1 counts for something.
> ...
>
> As a former WG chair who's had to deal with some very rough
> consensus calls...
>
> Not "counting" a "+1" is more consistent with a classical definition
> of consensus.  But, particularly at a WG level (less so, perhaps,
> at the IETF level) "+1" is very helpful in determining whether
> the previously mentioned "Abilene Paradox" should be of concern.
>
> Randy
>

--20cf307c9e9ed16c6104df0ad672
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Without agreeing with or disagreeing with Pete, I&#39;ll point out that Pet=
e was talking about IETF last call. =A0It&#39;s perfectly reasonable for a =
WG participant who has been actively involved to say, &quot;This one is rea=
dy. =A0Ship it,&quot; and Pete isn&#39;t saying otherwise. =A0In that case =
there is context that helps.<div>
<br></div><div>Barry<span></span><br><br>On Wednesday, June 12, 2013, Randy=
 Presuhn  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi -<br>
<br>
&gt;From: Ted Lemon &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;=
cvml&#39;, &#39;Ted.Lemon@nominum.com&#39;)">Ted.Lemon@nominum.com</a>&gt;<=
br>
&gt;Sent: Jun 12, 2013 12:42 PM<br>
&gt;To: Peter Saint-Andre &lt;<a href=3D"javascript:;" onclick=3D"_e(event,=
 &#39;cvml&#39;, &#39;stpeter@stpeter.im&#39;)">stpeter@stpeter.im</a>&gt;<=
br>
&gt;Cc: &quot;&lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#=
39;, &#39;ned+ietf@mauve.mrochek.com&#39;)">ned+ietf@mauve.mrochek.com</a>&=
gt;&quot; &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;,=
 &#39;ned+ietf@mauve.mrochek.com&#39;)">ned+ietf@mauve.mrochek.com</a>&gt;,=
 Alexey Melnikov &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvm=
l&#39;, &#39;alexey.melnikov@isode.com&#39;)">alexey.melnikov@isode.com</a>=
&gt;, Pete Resnick &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;c=
vml&#39;, &#39;presnick@qti.qualcomm.com&#39;)">presnick@qti.qualcomm.com</=
a>&gt;, &quot;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;,=
 &#39;ietf@ietf.org&#39;)">ietf@ietf.org</a> Discussion&quot; &lt;<a href=
=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;ietf@ietf.org&#=
39;)">ietf@ietf.org</a>&gt;<br>

&gt;Subject: Re: Content-free Last Call comments<br>
&gt;<br>
&gt;On Jun 12, 2013, at 3:31 PM, Peter Saint-Andre &lt;<a href=3D"javascrip=
t:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;stpeter@stpeter.im&#39;)">st=
peter@stpeter.im</a>&gt; wrote:<br>
&gt;&gt; I think these messages are useless, not harmful. But perhaps I hav=
e<br>
&gt;&gt; more confidence in the inherent skepticism of your average IETF<br=
>
&gt;&gt; participant than Pete does...<br>
&gt;<br>
&gt;FWIW, until I read Pete&#39;s document on consensus, I thought that +1<=
br>
&gt;statements were part of the consensus process. =A0 This was not a<br>
&gt;strongly held opinion=97it was just my understanding of how<br>
&gt;consensus operated, from having watched other working group<br>
&gt;chairs run their working groups. =A0 I think the point Pete is<br>
&gt;making is very important, because the consensus process Pete<br>
&gt;describes is more in keeping with how I think the IETF ought<br>
&gt;to operate than the process in which +1 counts for something.<br>
...<br>
<br>
As a former WG chair who&#39;s had to deal with some very rough<br>
consensus calls...<br>
<br>
Not &quot;counting&quot; a &quot;+1&quot; is more consistent with a classic=
al definition<br>
of consensus. =A0But, particularly at a WG level (less so, perhaps,<br>
at the IETF level) &quot;+1&quot; is very helpful in determining whether<br=
>
the previously mentioned &quot;Abilene Paradox&quot; should be of concern.<=
br>
<br>
Randy<br>
</blockquote></div>

--20cf307c9e9ed16c6104df0ad672--

From joelja@bogus.com  Thu Jun 13 08:39:40 2013
Return-Path: <joelja@bogus.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 AF65B21F9944 for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 08:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8oIeipqs00Nm for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 08:39:40 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 268E121F8B51 for <ietf@ietf.org>; Thu, 13 Jun 2013 08:39:40 -0700 (PDT)
Received: from wifi-216-68.mtg.afnog.org (wifi-216-68.mtg.afnog.org [196.200.216.68]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r5DFdXeV073628 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 13 Jun 2013 15:39:36 GMT (envelope-from joelja@bogus.com)
Message-ID: <51B9E7B4.5080404@bogus.com>
Date: Thu, 13 Jun 2013 17:39:32 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com>
In-Reply-To: <51A37E8A.9010506@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 13 Jun 2013 15:39:37 +0000 (UTC)
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: Thu, 13 Jun 2013 15:39:40 -0000

I am told that draft has been revved again in response to discussion on 
the list.

http://www.ietf.org/rfcdiff?url2=draft-jabley-dnsext-eui48-eui64-rrtypes-05

Please direct your attention to the security considerations section. If 
it turns out that informational documentation of the two RR-Type 
assignments remains controversial, I will likely withdraw my sponsorship 
of this draft.

Thanks
joel


On 5/27/13 5:40 PM, joel jaeggli wrote:
> On 5/20/13 6:44 AM, The IESG wrote:
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Resource Records for EUI-48 and EUI-64 Addresses in the DNS'
>>    <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> as Proposed Standard
>
> I would direct the attention of the commentors to draft 04
>
> http://www.ietf.org/internet-drafts/draft-jabley-dnsext-eui48-eui64-rrtypes-04.txt 
>
>
> Which addresses concerns expressed in IETF last call over the intended 
> status.
>
> It also incorporates edits proposed by John Klensin in his review.
>
> Notes: from the author:
>
>  - changed intended status to informational
>
>  - incorporation of John's suggestions in the Terminology section, to 
> indicate that we're using 2119 keywords even though this is not a 
> standards track document
>
>  - added a couple of sentences to the security considerations sections 
> to underscore the fact that this document specifies optional 
> mechanisms that people might well not use if privacy considerations 
> dictate otherwise
>
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-06-17. Exceptionally, comments 
>> may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     48-bit Extended Unique Identifiers (EUI-48) and 64-bit Extended
>>     Unique Identifiers (EUI-64) are address formats specified by the 
>> IEEE
>>     for use in various layer-2 networks, e.g. ethernet.
>>
>>     This document defines two new DNS resource record types, EUI48 and
>>     EUI64, for encoding ethernet addresses in the DNS.
>>
>
>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-jabley-dnsext-eui48-eui64-rrtypes/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-jabley-dnsext-eui48-eui64-rrtypes/ballot/ 
>>
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>


From randy@psg.com  Thu Jun 13 08:55:29 2013
Return-Path: <randy@psg.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 04A9821F9815 for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 08:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599]
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 u+SGoR6IWcRD for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 08:55:28 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id C16D821F9967 for <ietf@ietf.org>; Thu, 13 Jun 2013 08:55:27 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Un9rx-0001cF-B2; Thu, 13 Jun 2013 15:55:26 +0000
Date: Thu, 13 Jun 2013 17:55:22 +0200
Message-ID: <m2obbaovit.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
In-Reply-To: <51B9E7B4.5080404@bogus.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <51B9E7B4.5080404@bogus.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: 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: Thu, 13 Jun 2013 15:55:29 -0000

> I am told that draft has been revved again in response to discussion on 
> the list.
> 
> http://www.ietf.org/rfcdiff?url2=draft-jabley-dnsext-eui48-eui64-rrtypes-05
> 
> Please direct your attention to the security considerations section. If 
> it turns out that informational documentation of the two RR-Type 
> assignments remains controversial, I will likely withdraw my sponsorship 
> of this draft.

the addition of 

    This document recommends that EUI-48 or EUI-64 addresses SHOULD NOT
    be published in the public DNS.

alleviates my worst fears.  though i wish it was a MUST NOT, i will not
insist.

thanks joe and joel.

randy

From housley@vigilsec.com  Thu Jun 13 09:04:44 2013
Return-Path: <housley@vigilsec.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 2EBF921F8BB7 for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 09:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 syxfXpv3lmHN for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 09:04:39 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id F2C6321F8617 for <ietf@ietf.org>; Thu, 13 Jun 2013 09:04:38 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 8B55CF2408A; Thu, 13 Jun 2013 12:04:57 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id gojPIMmSF8rn; Thu, 13 Jun 2013 12:04:09 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id C0403F2407E; Thu, 13 Jun 2013 12:04:56 -0400 (EDT)
Subject: Re: Renaming RFC
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EAD@EXMB01CMS.surrey.ac.uk>
Date: Thu, 13 Jun 2013 12:04:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC97A628-7F58-441D-A825-30EFDA8B202F@vigilsec.com>
References: <290E20B455C66743BE178C5C84F12408223F494EAD@EXMB01CMS.surrey.ac.uk>
To: <l.wood@surrey.ac.uk> <l.wood@surrey.ac.uk>
X-Mailer: Apple Mail (2.1085)
Cc: RFC Interest <rfc-interest@rfc-editor.org>, IETF <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: Thu, 13 Jun 2013 16:04:44 -0000

I think this suggestion should be discussed on rfc-interest, not this =
mail list.

Russ


On Jun 12, 2013, at 5:55 PM, <l.wood@surrey.ac.uk> <l.wood@surrey.ac.uk> =
wrote:

>=20
> RFC should be renamed to Resulted =46rom Comments. It's now the =
endpoint of the process; Request For Comments dated from when it was the =
start.
>=20
> (Though RFCs through workgroups are arguably Resulted from =
Collaboration/Consensus/Chairing).
>=20
> If you're going to alter the process in any way, start here.
>=20
> Lloyd Wood
> http://sat-net.com/L.Wood/
>=20
>=20


From jari.arkko@piuha.net  Thu Jun 13 09:07:37 2013
Return-Path: <jari.arkko@piuha.net>
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 627E121F9A1F; Thu, 13 Jun 2013 09:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 D3e8ie6I1Bz6; Thu, 13 Jun 2013 09:07:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4575A21F925A; Thu, 13 Jun 2013 09:07:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7F0EC2CC56; Thu, 13 Jun 2013 19:07:21 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0rA1p9X8DA4y; Thu, 13 Jun 2013 19:07:21 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id AAADB2CC61; Thu, 13 Jun 2013 19:07:20 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [Gen-art] Gen-ART review of draft-eastlake-rfc5342bis-03
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712980CA213@MX15A.corp.emc.com>
Date: Thu, 13 Jun 2013 19:07:19 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4DC72F40-E427-4F50-9CA9-73F5C89F2E2C@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712980CA206@MX15A.corp.emc.com> <CAF4+nEER=JdeKV6PU_8m2jJ8O182WHcsQ-ayODUTCp1jRx-X+w@mail.gmail.com> <8D3D17ACE214DC429325B2B98F3AE712980CA213@MX15A.corp.emc.com>
To: David Black <david.black@emc.com>
X-Mailer: Apple Mail (2.1503)
Cc: General Area Review Team <gen-art@ietf.org>, joe.abley@icann.org, 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: Thu, 13 Jun 2013 16:07:37 -0000

> I'm concerned about readers who aren't as
> cognizant of and comfortable/familiar with the relationships among
> OUIs and the identifiers based on them as people like you and me.

Thanks your review, David. The Gen-ART reviews are important for me in =
helping decide if the documents may have issues where I need to dig in =
deeper.

In this case I agree with the issue you raise and think it is a mistake =
that should be corrected. I see that Barry has already raised a discuss =
about that, however. I am balloting a No-Objection based on your review.

Jari



From narten@us.ibm.com  Thu Jun 13 21:53:17 2013
Return-Path: <narten@us.ibm.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 2CD4E21F9B16 for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 21:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.372
X-Spam-Level: 
X-Spam-Status: No, score=-109.372 tagged_above=-999 required=5 tests=[AWL=-1.228, BAYES_00=-2.599, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 WKI4ArGHfhlE for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2013 21:53:10 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 220D721F9AF9 for <ietf@ietf.org>; Thu, 13 Jun 2013 21:53:10 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 14 Jun 2013 00:53:08 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 14 Jun 2013 00:53:07 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 386BA38C8047 for <ietf@ietf.org>; Fri, 14 Jun 2013 00:53:06 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r5E4r6DG301554 for <ietf@ietf.org>; Fri, 14 Jun 2013 00:53:06 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r5E4r6Je028067 for <ietf@ietf.org>; Fri, 14 Jun 2013 01:53:06 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r5E4r62r028052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 14 Jun 2013 01:53:06 -0300
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r5E4r52B002839 for <ietf@ietf.org>; Fri, 14 Jun 2013 00:53:05 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r5E4r4q7002802 for ietf@ietf.org; Fri, 14 Jun 2013 00:53:04 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201306140453.r5E4r4q7002802@rotala.raleigh.ibm.com>
Date: Fri, 14 Jun 2013 00:53:04 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13061404-7182-0000-0000-00000753D15A
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: Fri, 14 Jun 2013 04:53:17 -0000

Total of 158 messages in the last 7 days.
 
script run at: Fri Jun 14 00:53:03 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.13% |   16 |  9.82% |   124800 | ted.lemon@nominum.com
  5.06% |    8 |  6.98% |    88757 | dave@cridland.net
  4.43% |    7 |  4.80% |    61022 | presnick@qti.qualcomm.com
  3.80% |    6 |  3.80% |    48351 | sm@resistor.net
  3.80% |    6 |  3.54% |    45049 | l.wood@surrey.ac.uk
  3.16% |    5 |  4.16% |    52840 | abdussalambaryun@gmail.com
  3.80% |    6 |  3.04% |    38633 | dhc@dcrocker.net
  3.16% |    5 |  2.73% |    34740 | brian.e.carpenter@gmail.com
  3.16% |    5 |  2.56% |    32572 | melinda.shore@gmail.com
  3.16% |    5 |  2.00% |    25369 | randy@psg.com
  2.53% |    4 |  2.37% |    30074 | narten@us.ibm.com
  1.90% |    3 |  2.47% |    31426 | magnus.westerlund@ericsson.com
  2.53% |    4 |  1.77% |    22553 | dwm@xpasc.com
  1.90% |    3 |  2.14% |    27243 | andy@yumaworks.com
  1.90% |    3 |  1.70% |    21617 | joelja@bogus.com
  1.90% |    3 |  1.61% |    20461 | stpeter@stpeter.im
  1.27% |    2 |  1.68% |    21373 | elwynd@folly.org.uk
  1.27% |    2 |  1.62% |    20640 | dromasca@avaya.com
  1.27% |    2 |  1.62% |    20584 | david.black@emc.com
  1.27% |    2 |  1.50% |    19051 | tjc@ecs.soton.ac.uk
  1.27% |    2 |  1.43% |    18119 | d3e3e3@gmail.com
  1.27% |    2 |  1.34% |    16981 | stephen.farrell@cs.tcd.ie
  1.27% |    2 |  1.26% |    15973 | sob@harvard.edu
  1.27% |    2 |  1.20% |    15292 | turners@ieca.com
  0.63% |    1 |  1.80% |    22839 | jdrake@juniper.net
  1.27% |    2 |  1.15% |    14594 | ulrich@herberg.name
  1.27% |    2 |  1.11% |    14169 | bob.hinden@gmail.com
  1.27% |    2 |  1.11% |    14096 | rpelletier@isoc.org
  1.27% |    2 |  1.10% |    14014 | john-ietf@jck.com
  1.27% |    2 |  1.09% |    13798 | jari.arkko@piuha.net
  1.27% |    2 |  1.06% |    13454 | mcr+ietf@sandelman.ca
  1.27% |    2 |  1.00% |    12670 | mansaxel@besserwisser.org
  0.63% |    1 |  1.62% |    20647 | yi.jiazi@gmail.com
  1.27% |    2 |  0.99% |    12579 | dougb@dougbarton.us
  1.27% |    2 |  0.96% |    12163 | housley@vigilsec.com
  0.63% |    1 |  1.27% |    16099 | lars@netapp.com
  0.63% |    1 |  0.98% |    12438 | ted.ietf@gmail.com
  0.63% |    1 |  0.86% |    10985 | barryleiba@computer.org
  0.63% |    1 |  0.81% |    10259 | doug.mtview@gmail.com
  0.63% |    1 |  0.80% |    10208 | conte@isoc.org
  0.63% |    1 |  0.79% |    10055 | warren@kumari.net
  0.63% |    1 |  0.76% |     9637 | mthornbu@adobe.com
  0.63% |    1 |  0.73% |     9336 | ogier@earthlink.net
  0.63% |    1 |  0.67% |     8536 | rlb@ipv.sx
  0.63% |    1 |  0.67% |     8463 | mnot@mnot.net
  0.63% |    1 |  0.59% |     7508 | iab-chair@iab.org
  0.63% |    1 |  0.59% |     7458 | martin.stiemerling@neclab.eu
  0.63% |    1 |  0.58% |     7344 | carlosm3011@gmail.com
  0.63% |    1 |  0.56% |     7178 | glenzorn@gmail.com
  0.63% |    1 |  0.56% |     7122 | msk@blackops.org
  0.63% |    1 |  0.55% |     6963 | marka@isc.org
  0.63% |    1 |  0.53% |     6792 | daedulus@btconnect.com
  0.63% |    1 |  0.52% |     6659 | alexey.melnikov@isode.com
  0.63% |    1 |  0.52% |     6606 | lear@cisco.com
  0.63% |    1 |  0.52% |     6584 | randy_presuhn@mindspring.com
  0.63% |    1 |  0.51% |     6541 | arturo.servin@gmail.com
  0.63% |    1 |  0.51% |     6495 | fgont@si6networks.com
  0.63% |    1 |  0.50% |     6378 | juliao@braga.eti.br
  0.63% |    1 |  0.48% |     6084 | peter@akayla.com
  0.63% |    1 |  0.48% |     6076 | johnl@taugh.com
  0.63% |    1 |  0.48% |     6055 | stbryant@cisco.com
  0.63% |    1 |  0.47% |     5965 | elwynd@dial.pipex.com
  0.63% |    1 |  0.47% |     5916 | adrian@olddog.co.uk
  0.63% |    1 |  0.46% |     5880 | amorris@amsl.com
  0.63% |    1 |  0.46% |     5847 | ned+ietf@mauve.mrochek.com
  0.63% |    1 |  0.43% |     5509 | cabo@tzi.org
  0.63% |    1 |  0.42% |     5331 | swmike@swm.pp.se
  0.63% |    1 |  0.36% |     4587 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |  158 |100.00% |  1271437 | Total


From daedulus@btconnect.com  Fri Jun 14 01:27:49 2013
Return-Path: <daedulus@btconnect.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 0743121F9B8F for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2013 01:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 p5KMMipkRiqu for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2013 01:27:43 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0249.outbound.messaging.microsoft.com [213.199.154.249]) by ietfa.amsl.com (Postfix) with ESMTP id 194C421F9B57 for <ietf@ietf.org>; Fri, 14 Jun 2013 01:27:42 -0700 (PDT)
Received: from mail152-db9-R.bigfish.com (10.174.16.236) by DB9EHSOBE026.bigfish.com (10.174.14.89) with Microsoft SMTP Server id 14.1.225.23; Fri, 14 Jun 2013 08:27:41 +0000
Received: from mail152-db9 (localhost [127.0.0.1])	by mail152-db9-R.bigfish.com (Postfix) with ESMTP id 1399CE0090; Fri, 14 Jun 2013 08:27:41 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zzbb2dI98dI9371Ic89bh542I1432I1418Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail152-db9 (localhost.localdomain [127.0.0.1]) by mail152-db9 (MessageSwitch) id 1371198459520475_6816; Fri, 14 Jun 2013 08:27:39 +0000 (UTC)
Received: from DB9EHSMHS019.bigfish.com (unknown [10.174.16.244])	by mail152-db9.bigfish.com (Postfix) with ESMTP id 707D82A007E; Fri, 14 Jun 2013 08:27:39 +0000 (UTC)
Received: from AMSPRD0711HT001.eurprd07.prod.outlook.com (157.56.250.181) by DB9EHSMHS019.bigfish.com (10.174.14.29) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 14 Jun 2013 08:27:38 +0000
Received: from pc6 (86.135.128.129) by pod51017.outlook.com (10.242.14.162) with Microsoft SMTP Server (TLS) id 14.16.324.0; Fri, 14 Jun 2013 08:27:36 +0000
Message-ID: <004701ce68d9$238a9640$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <20130610144518.18776.77082.idtracker@ietfa.amsl.com>	<B3BA7D5C-2B90-4A82-9CAE-6757754A01E9@vigilsec.com>	<51B63905.2020807@qti.qualcomm.com><51B6710E.4040800@cs.tcd.ie> <51B77E77.1030601@qti.qualcomm.com>
Subject: Re: Content-free Last Call comments
Date: Fri, 14 Jun 2013 09:28:07 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.135.128.129]
Content-Transfer-Encoding: quoted-printable
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: ietf <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: Fri, 14 Jun 2013 08:27:49 -0000

----- Original Message -----
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
Cc: <ietf@ietf.org>
Sent: Tuesday, June 11, 2013 8:45 PM
Subject: Re: Content-free Last Call comments


It's interesting to see that people are interpreting me to mean I want
more text. I don't. I want less. Save your breath. There is no reason to
send one line of support, and it only encourages the view that we're
voting. Details below.

<tp>

Seems to me that there are more points of view on this thread than there
are members of the IESG, in which case, to help followers of this list,
perhaps they, when instigating a Last Call, should do as some WG Chairs
do when instigating WG Last Call, spell out that expressions of support
from those that have read it are welcome - or not, as the case may be.
Thus the AD might add that any e-mail containing "+1" in the body will
be filtered into a spam trap and discarded without being read.

Tom Petch

</tp>







Specifically on Stephen's message:

On 6/10/13 7:36 PM, Stephen Farrell wrote:
> I think you err when you say this:
>
>
>> A statement such as the above is almost entirely useless to me as an
>> IESG member trying to determine consensus. It is content-free.
>>
> In fact, you do know Russ. If you did not, then the above would be
> far closer to correct. But in reality you do know a lot more than
> you claim below. With overwhelming probability, your choice #2
> applies and I'm very surprised you don't also think that. If it
> made a significant difference and I wasn't sure I'd ask Russ to
> clarify. For me, I read Russ' mail and I concluded he meant #2.
> And I'm confident in that conclusion.
>
> So I'm really bemused when you say that you don't know how to
> interpret Russ' mail.
>

Let's separate out a few issues. There's what the message means itself,
there's its usefulness and how much weight it should be given, and then
there's what's problematic about it. I think you've conflated a few
things.

As you know, on the earlier message I called out on the IESG list, I
guessed wrong that the sender was claiming choice #3 (that is, I
thought, incorrectly, that the sender disagreed with a recent argument
against publication, but simply didn't explain why). In fact in that
case, not only wasn't it choice #4, it was also neither choice #1 (an
implementer claiming implementation) nor choice #2 (an expert on the
topic), my other two guesses, but rather a generally smart IETFer who
thought the work seemed like a good idea. So I'm a little disinclined to
guess on motives. In the case of Russ's message, I did guess it was
choice #2, but I wasn't really sure.

But let's separate what Russ meant from the weight it should be given.
The message was that a person (let's presume with some expertise in the
area) had read it. So what? Didn't this document go through a WG?
Weren't a good bunch of experts already reading and reviewing this
document? If this was during the WG discussion and the chairs solicited
some final check reviews, *maybe* the message could have some use. But
during IETF Last Call? Even if the message was sent because it was
trying to say, "I'm an expert on this stuff and it looks technically
sound", is that going to change anything that the IESG should do about
the document? I just think at Last Call, these statements of support are
either harmless-but-useless or they are nefarious.

> Declaring that mail problematic also seems quite purist to me.
>

I always find it amusing that when Stephen and I disagree, it's almost
always because he presumes I want purity (and usually a new process),
which I don't, and it seems to me that he wants no rules-of-thumb at all
and that everything should be on a case-by-case basis. (I guess that
means that I'm into purity, where Stephen has no principles. ;-) ) I
think general principles are a fine thing, and we should try to stick to
them, but I've got no interest in purity.

The single piece of mail isn't problematic at all. As I said, probably
harmless but useless. But the overall impression it gives *is*
problematic. It encourages the view that we are voting, that a simple
statement of support is important to our process. (What really set my
hair on end was the "I support publication" bit. That always sounds like
a vote for a new RFC. From Russ, I have a pretty good idea that he
didn't mean it that way, but it's a poor formulation and not what we
should be encouraging.) It also indicates that during Last Call, we want
to hear that a document is getting reviewed. I would like to presume
that documents get serious reviews in the WG, and that Last Call time is
for people who haven't been participating in the WG to do a final check,
letting us know if there's something *wrong*. If the document wasn't
getting good review in the WG and needs statements of support at Last
Call time, something has seriously failed earlier in the process. The
chair or responsible AD should have been saying early on, "Dear Expert,
can you please have a read over this document and see if it's sane."
Last Call is the wrong time for that to happen. This just encourages
more of the tail-heavy process that we discussed earlier.

> At the same time I agree we do not want a procession of +1 mails.
>

Right. And having senior members of the community doing so will
encourage such behavior in the future.

> But then we won't get that for this draft. And if we did get that
> for any draft, some IETF participants (probably incl. you and I)
> would notice that and query it or object.

I'd rather have all of us crusty folks model good behavior rather than
having to complain about bad behavior later, especially when we'll get
responses like, "But the chair did it." We've already seen a couple of
comments to my message from non-crusty-folks indicating that any +1 is
just dandy. Blech.

> Lastly, I think evaluating IETF LC messages only in terms
> of how they help the IESG evaluate consensus or not is wrong.
> Those messages are for and from the IETF community. So if
> e.g. some renowned NFS person who's hardly known to the IESG
> were to have sent an equivalent message, that might have been
> quite good input that Martin or Spencer could have translated for
> you. And that's just fine. And it would be fine if Russ' mail
> had been directed not at the IESG but at some other part of the
> community.
>

So this is the most interesting argument. But I would say that requiring
this kind of interpretation/translation is problematic as a general rule
when the messages are going to the IETF list in response to a Last Call.
If a renowned NFS person is doing a review of an NFS document, I think
that's great. And I think that's helpful to Martin or Spencer. But if
all they're going to say is, "I don't have any concerns", it doesn't
seem to me to be that useful a piece of info on the IETF list at Last
Call time. Again, at best it encourages the idea that just because =DCber
NFS person endorses the document, that weighs in its favor. The
important thing to hear at Last Call time are objections, not
endorsements. As a note to the IESG saying, "Just in case you didn't
think this got review from the right people before, I, =DCber NFS person,
hereby say that I reviewed it and have no problem with it", that has
some content, but it does indicate that we are waiting until too late in
the process to be thinking about such things.

> So bottom line, I think you're wrong, Russ' mail was not content-free.
>

Yeah, you haven't convinced me.

> PS: Yes, this is a not-very-good academic accusing an employee
> of an industrial behemoth of excess purity. Go figure:-)

I'll note that I hide in a small R&D corner of my industrial behemoth,
mostly teaching classes to other engineers. You, on the other hand,
probably still write code. :-)

pr

--
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478




From ford@isoc.org  Fri Jun 14 01:43:10 2013
Return-Path: <ford@isoc.org>
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 2EE2221F9C50 for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2013 01:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.657
X-Spam-Level: 
X-Spam-Status: No, score=-102.657 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, GB_I_INVITATION=-2, SARE_RMML_Stock4=1.54, USER_IN_WHITELIST=-100]
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 jRf7ptXT2Kjy for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2013 01:43:03 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0158.outbound.protection.outlook.com [207.46.163.158]) by ietfa.amsl.com (Postfix) with ESMTP id 7D46A21F9BFF for <ietf@ietf.org>; Fri, 14 Jun 2013 01:43:03 -0700 (PDT)
Received: from [192.168.0.9] (81.2.115.113) by BN1PR06MB183.namprd06.prod.outlook.com (10.242.215.17) with Microsoft SMTP Server (TLS) id 15.0.702.21; Fri, 14 Jun 2013 08:43:01 +0000
From: Matthew Ford <ford@isoc.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 14 Jun 2013 09:42:43 +0100
Subject: Reducing Internet Latency Workshop
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Message-ID: <29C57024-B48B-4797-9AEE-D654719253C4@isoc.org>
MIME-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Originating-IP: [81.2.115.113]
X-ClientProxiedBy: DBXPR04CA006.eurprd04.prod.outlook.com (10.255.191.154) To BN1PR06MB183.namprd06.prod.outlook.com (10.242.215.17)
X-Forefront-Antispam-Report: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:0; SRVR:BN1PR06MB183; H:[192.168.0.9]; LANG:en; 
X-OriginatorOrg: isoc.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: Fri, 14 Jun 2013 08:43:10 -0000

Possibly of interest. (Short) Position paper deadline is 23rd June.

Regards,
Mat

Workshop on Reducing Internet Latency
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
25 - 26 September 2013
London, England

Latency tends to have been sacrificed in favour of headline bandwidth in =
the way the Internet has been built. This two-day invitation-only =
workshop aims to galvanise action to fix that. All layers of the stack =
are in scope.
Latency is an increasingly important topic for networking researchers =
and Internet practitioners alike. Data from Google, Microsoft, Amazon =
and others indicate that latency increases for interactive Web =
applications result in less usage and less revenue from sales or =
advertising income. Whether trying to provide platforms for Web =
applications, high-frequency stock trading, multi-player online gaming =
or 'cloud' services of any kind, latency is a critical factor in =
determining end-user satisfaction and the success of products in the =
marketplace. Consequently, latency and variation in latency are key =
performance metrics for services these days.

But latency reduction is not just about increasing revenues for big =
business. Matt Mullenweg of WordPress motivates work on latency =
reduction well when he says, "My theory here is when an interface is =
faster, you feel good. And ultimately what that comes down to is you =
feel in control. The [application] isn=92t controlling me, I=92m =
controlling it. Ultimately that feeling of control translates to =
happiness in everyone. In order to increase the happiness in the world, =
we all have to keep working on this."

Invitations to attend the workshop will depend on receipt of a position =
paper. In a spirit of co- ordination across the industry, submissions =
are encouraged from developers and network operators as well as the =
research and standards communities.

A wide range of latency related topics are in scope including, but not =
limited to:
- surveys of latency across all layers
- analyses of sources of latency and severity/variability
- the cost of latency problems to society and the economy, or the value =
of fixing it
- principles for latency reduction across the stack
- solutions to reduce latency, including cross-layer
- deployment considerations for latency reducing technology
- benchmarking, accreditation, measurement and market comparison =
practices

Submissions
-----------
This is an invitation-only workshop. Prospective participants must =
submit short (up to 2 pages) position papers outlining their views on a =
specific aspect of the overall scope. The emphasis here is on relevance =
and brevity - you do not need to write a lot of text, just demonstrate =
that you have thought about the problem space and have something =
interesting to say on the topic.

Please send position papers in PDF format to: latency@isoc.org

Participant numbers will be limited to focus on discussion and =
identifying actions rather than slideware.
Accepted position papers will be made public. A report on the workshop =
will be published after participants have agreed the content. Therefore, =
it will be possible to state views during the workshop without them =
being publicly attributed.

Important Dates
---------------
Position paper submission deadline: 23 June 2013
Paper acceptance notification: 28 June 2013
Workshop dates: 9am, Wednesday 25th =96 5pm, Thursday 26th September =
2013

Program committee
-----------------
Mat Ford, Internet Society, co-chair
Bob Briscoe, BT, co-chair
Gorry Fairhurst, University of Aberdeen
Arvind Jain, Google
Jason Livingood, Comcast
Andrew McGregor, Google

Workshop venue and other details
--------------------------------
Venue: Hilton London Paddington Hotel, 146 Praed Street, LONDON W2 1EE, =
UK
Registration fee: There is no registration fee for the workshop.
Recommended accommodation: Hilton London Paddington, registration link =
will be supplied to accepted participants.

The workshop is sponsored by the Internet Society, the RITE project, =
Simula Research Labs and the TimeIn project.
The Internet Society will host a workshop dinner on the Wednesday =
evening.=

From joelja@bogus.com  Fri Jun 14 07:00:09 2013
Return-Path: <joelja@bogus.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 3B7BB21F9ABB; Fri, 14 Jun 2013 07:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level: 
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8LEj7p1+oqzy; Fri, 14 Jun 2013 07:00:08 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2635521F9A5C; Fri, 14 Jun 2013 07:00:08 -0700 (PDT)
Received: from wifi-216-68.mtg.afnog.org (wifi-216-68.mtg.afnog.org [196.200.216.68]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r5EE02sO088272 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 14 Jun 2013 14:00:06 GMT (envelope-from joelja@bogus.com)
Message-ID: <51BB21E0.6010606@bogus.com>
Date: Fri, 14 Jun 2013 16:00:00 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: Last Call: <draft-ietf-ipfix-protocol-rfc5101bis-08.txt> (Specification of the IP Flow Information eXport (IPFIX) Protocol for the Exchange of Flow Information) to Internet Standard
References: <20130614132444.5422.99013.idtracker@ietfa.amsl.com>
In-Reply-To: <20130614132444.5422.99013.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 14 Jun 2013 14:00:07 +0000 (UTC)
Cc: ipfix@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: Fri, 14 Jun 2013 14:00:09 -0000

The last call is being rerun to capture an import change to the 
rfc5101bis namely the requested status for "Specification of the IP Flow 
Information eXport (IPFIX) Protocol for the Exchange of Flow 
Information" Internet Standard rather than proposed.

Thank you
Joel

On 6/14/13 3:24 PM, The IESG wrote:
> The IESG has received a request from the IP Flow Information Export WG
> (ipfix) to consider the following document:
> - 'Specification of the IP Flow Information eXport (IPFIX) Protocol for
>     the Exchange of Flow Information'
>    <draft-ietf-ipfix-protocol-rfc5101bis-08.txt> as Internet Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-28. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document specifies the IP Flow Information Export (IPFIX)
>     protocol that serves for transmitting Traffic Flow information over
>     the network. In order to transmit Traffic Flow information from an
>     Exporting Process to a Collecting Process, a common representation of
>     flow data and a standard means of communicating them is required.
>     This document describes how the IPFIX Data and Template Records are
>     carried over a number of transport protocols from an IPFIX Exporting
>     Process to an IPFIX Collecting Process. This document obsoletes RFC
>     5101.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-ipfix-protocol-rfc5101bis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-ipfix-protocol-rfc5101bis/ballot/
>
>
> The following IPR Declarations may be related to this I-D:
>
>     http://datatracker.ietf.org/ipr/1927/
>
>
>


From housley@vigilsec.com  Fri Jun 14 13:23:53 2013
Return-Path: <housley@vigilsec.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 132D521F9CC3; Fri, 14 Jun 2013 13:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level: 
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 RfgaREJGLlGQ; Fri, 14 Jun 2013 13:23:48 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id E8E5A21F9B82; Fri, 14 Jun 2013 13:23:47 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 8BB39F2407D; Fri, 14 Jun 2013 16:23:51 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id o1kzzxD7pdlj; Fri, 14 Jun 2013 16:23:44 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id BC3DFF24078; Fri, 14 Jun 2013 16:23:50 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Gen-ART Review of draft-ietf-manet-rfc6622-bis-02
Date: Fri, 14 Jun 2013 16:23:45 -0400
Message-Id: <90D2B755-F68F-4C58-A645-84E4445C73BE@vigilsec.com>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IETF Gen-ART <gen-art@ietf.org>, manet@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: Fri, 14 Jun 2013 20:23:53 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-manet-rfc6622-bis-02
Reviewer: Russ Housley
Review Date: 2013-06-15
IETF LC End Date: 2013-06-27
IESG Telechat date: Unknown

Summary:  The document is almost ready for publication as a
standards track RFC.  I raise one major concern, and once it
is resolved, the document will be ready.

Major Concern:

In Section 12.2.3, is there any difference in processing when the
source IP address is IPv4 as opposed to IPv6?  Obviously, the two have
a different length.  Off the top of my head I cannot find a way for an
attacker to exploit one party using IPv4 in the ICV calculation and the
other party using IPv6.  Since the IPv6 address is 12 octets longer
than the IPv4 address, there may be some opportunity for an attacker.
Anyway, concerns like this are usually thwarted by including the length
of the overall hash function input as the first octet or two of the
value-to-be-hashed.  Such a value does not need to be transmitted.
Each party knows how many octets it passed to the hash function.


Minor Concerns:  

I find Section 1.1 a bit confusing.  I think it should start by saying
that RFC 6622 defined two ICV TLV extension types (0 and 1).  This
document repeats those definitions and adds a third ICV TLV extension
type (2).


Section 5 says:

  An ICV TLV with type extension = 2 specifies a modified version of
  this definition.
 
This is unclear.  I believe that an ICV TLV with type extension = 2 is
an update to ICV TLV with type extension = 1.  It would be good to
introduce the need for this update.  I suggest:

  An ICV TLV with type extension = 2 is the same as an ICV TLV with
  type extension = 1, except that the integrity protection also covers
  the source address of the IP datagram carrying the packet, message,
  or address block.

If you accept this suggestion, the following paragraph should also be
revised.  I suggest:

  Specifically, with type extension = 1 or type extension = 2, the
  <value> field contains the result of combining a cryptographic
  function and a hash function.  The <value> field contains multiple
  sub-fields indicating which hash function and cryptographic function
  have been used as specified in Section 12.


From adrian@olddog.co.uk  Mon Jun 17 10:51:35 2013
Return-Path: <adrian@olddog.co.uk>
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 8FE7321F9CBF for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 10:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level: 
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599]
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 cGphgll+c4-U for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 10:51:35 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 1D3A121F9CB5 for <ietf@ietf.org>; Mon, 17 Jun 2013 10:51:34 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5HHpXRb017210 for <ietf@ietf.org>; Mon, 17 Jun 2013 18:51:33 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5HHpWau017199 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Mon, 17 Jun 2013 18:51:33 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: New non-WG malign list : Network Service Chaining (NSC)
Date: Mon, 17 Jun 2013 18:51:32 +0100
Message-ID: <02a901ce6b83$4e22bbb0$ea683310$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5rgz8KIpl429SoSZ+5N4KbdHLRiA==
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Mon, 17 Jun 2013 17:51:35 -0000

There is a new non-working group mailing list for discussion of Network Service
Chaining (NSC)

The web page for users is:

    https://www.ietf.org/mailman/listinfo/nsc

There is also an email-based interface for users. You can get info about using
it by sending a message with just the word `help' as subject or in the body, to:

    nsc-request@ietf.org

The mailing list is configured with a public archive which can be found at: 

   http://www.ietf.org/mail-archive/web/nsc

The purpose of the list
 
  Network services are widely deployed and essential in many networks. The
  services provide a range of functions such as security, WAN acceleration, and
  server load balancing. Service functions that form part of the overall service
  may be physically located at different points in the network infrastructure
such
  as the wide area network, data center, campus, and so forth.
 
  New data center network and Internet cloud architectures require more flexible
  network service deployment models. Additionally, the transition to virtual
  platforms requires an agile service insertion model that supports elastic
  service delivery, the movement of service functions and application workloads
in
  the network and the ability to easily bind service policy to granular
  information such as per-subscriber state.
 
  Service chaining is a broad term used to describe a common model for
delivering
  multiple services in a specific order. Service chaining de-couples service
  delivery from the underlying network topology and creates a dynamic services
  plane that addresses the requirements of cloud and virtual application
delivery.
  Traffic that requires service chaining is classified, and context is shared
  between the network and the services.
 
  This list is for discussion of aspects of Network Service Chaining (NSC) that
  impact upon the IETF's work, the applicability of IETF protocols to NSC, as
well
  as new protocols and changes to IETF protocols that might be required.
 
  A BoF has been proposed for NSC in Berlin. This list also serves to discuss
that
  BoF proposal. See the proposal at http://trac.tools.ietf.org/bof/trac/
 
Thanks,
Adrian


From melinda.shore@gmail.com  Mon Jun 17 11:42:51 2013
Return-Path: <melinda.shore@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 AF82721F9DC9 for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 11:42:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 pmVlIljSUcOW for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 11:42:51 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 139FA21F9DB7 for <ietf@ietf.org>; Mon, 17 Jun 2013 11:42:51 -0700 (PDT)
Received: by mail-pa0-f43.google.com with SMTP id hz11so3155870pad.30 for <ietf@ietf.org>; Mon, 17 Jun 2013 11:42:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=1cTUcwms4E/0ddAI8R9O96kFUT8hGdGlryy4uX3SR9U=; b=hb9U4gJWEFfuLOgSK4d+kqD3tn1V2dVuDKjsruRtPBVeq/qMXa9M/lj5rv748iSG8L TFaKsnsUB4YNCNl1rq3zBZ5Bh8jshnV1NQTCiS+z0KNXMjnyqrbF0qvKPs/ta/5Oz4IN z3guByviwLlhPEghPz9pJVJILjxO/4r0pNcMFYQ4nZTQ7DTCICYZQNcR6FnAwP5PJ1Ym gcCyjmtm/iJZW+Fi1/nx+SeUtdizSkZA/d6zx8CChKcDG3gh6OcfWEvHsNx6rKPZI0Jd 99WV8GMLxkquONnVfvRywyC4dbmMI5uQ3DEOxx1G1W1nyMxhhkyuRqyPsnusSyXluwDE 2dYg==
X-Received: by 10.68.175.68 with SMTP id by4mr14104675pbc.53.1371494570846; Mon, 17 Jun 2013 11:42:50 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id ix3sm14731456pbc.37.2013.06.17.11.42.48 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 17 Jun 2013 11:42:49 -0700 (PDT)
Message-ID: <51BF58A7.4010008@gmail.com>
Date: Mon, 17 Jun 2013 10:42:47 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: New non-WG malign list : Network Service Chaining (NSC)
References: <02a901ce6b83$4e22bbb0$ea683310$@olddog.co.uk>
In-Reply-To: <02a901ce6b83$4e22bbb0$ea683310$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Mon, 17 Jun 2013 18:42:51 -0000

How about a new non-malign WG list?

Melinda


From paul.hoffman@vpnc.org  Mon Jun 17 12:40:16 2013
Return-Path: <paul.hoffman@vpnc.org>
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 316E721E8063 for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 12:40:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 FHTc3BMyrIuf for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 12:40:15 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id E1D6721E8084 for <ietf@ietf.org>; Mon, 17 Jun 2013 12:40:14 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5HJeB2v045367 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 17 Jun 2013 12:40:12 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: New non-WG malign list : Network Service Chaining (NSC)
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51BF58A7.4010008@gmail.com>
Date: Mon, 17 Jun 2013 12:40:11 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <A0E2EF02-8902-4D69-B3D6-65CBF1625BE9@vpnc.org>
References: <02a901ce6b83$4e22bbb0$ea683310$@olddog.co.uk> <51BF58A7.4010008@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: 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: Mon, 17 Jun 2013 19:40:16 -0000

On Jun 17, 2013, at 11:42 AM, Melinda Shore <melinda.shore@gmail.com> wrote:

> How about a new non-malign WG list?

Haven't seen one of those in the IETF in quite some time.

From doug.mtview@gmail.com  Mon Jun 17 12:58:18 2013
Return-Path: <doug.mtview@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 DE62E21F8C38; Mon, 17 Jun 2013 12:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 AxoCO+B3pN5t; Mon, 17 Jun 2013 12:58:18 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id DBF6621F89EB; Mon, 17 Jun 2013 12:58:17 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id um15so3110956pbc.10 for <multiple recipients>; Mon, 17 Jun 2013 12:58:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=whFG7Gy303A9uBB3/fvih3vMqhBthClUPXCawL0eNHM=; b=wlAIQcHjRQndfRfPo2T67aRD2ANgzEaj/TVM2LwhkYffGVETTQt1qhSv1isBzjYa+E 2zK/21EMwgnTo9+AD9WKX7xnEtOJtH1Dyxb+dcn6HeiwLtm+XNAHj4+osCbcETuHY+5+ Hm4eh1kpSjszXarsGx+UPl3ox9TVtE1iWoR2XGpFJx7e2zk9GC10P/HDsSBqFsu6otew ERCPg4wep0wnWrMk1GNGpkVxCjyMYZdtYtqitpfBaHfir6485UrqgmmAbiceq/qFSziI Z0XKNZCebkegikHqmlbsTqmK/lJkfnwGzjP0xN7vPqeizA4Fx0tP7AlZmCW3dfjBo1lL 9jNg==
X-Received: by 10.68.139.33 with SMTP id qv1mr14122294pbb.93.1371499097581; Mon, 17 Jun 2013 12:58:17 -0700 (PDT)
Received: from ?IPv6:2601:9:3180:3e:25e8:1bfc:c9d8:6b1? ([2601:9:3180:3e:25e8:1bfc:c9d8:6b1]) by mx.google.com with ESMTPSA id fn9sm16113439pab.2.2013.06.17.12.58.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 17 Jun 2013 12:58:16 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_E256A67C-79E2-49C6-AB07-957D4D12A5CD"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Review of: draft-otis-dkim-harmful
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <tslfvwxjo8q.fsf@mit.edu>
Date: Mon, 17 Jun 2013 12:58:13 -0700
Message-Id: <32E83DDA-8DCF-43EA-BC4B-5E7586DC450F@gmail.com>
References: <51907325.7050600@dcrocker.net> <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com> <51ADB6E6.5030300@dcrocker.net> <tslfvwxjo8q.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1508)
Cc: Barry Leiba <barryleiba@computer.org>, IETF Discussion <ietf@ietf.org>, Dave Rand <dave_rand@trendmicro.com>, iesg IESG <iesg@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: Mon, 17 Jun 2013 19:58:19 -0000

--Apple-Mail=_E256A67C-79E2-49C6-AB07-957D4D12A5CD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 4, 2013, at 7:16 PM, Sam Hartman <hartmans-ietf@mit.edu> wrote:
> So, I'd like to encourage Doug to refine his work, fix errors of
> precision, but to say I think this is worth writing down.

Dear Sam,

Thank you for your interest.  I have updated the draft and, and as =
requested by Dave Crocker, included references to prior statements by =
Dave Crocker and Barry Leiba made public subsequent to the conclusion of =
the WG DKIM specification in response to comments about the phishing =
threat DKIM permits.  In reviewing some of Dave Crocker's responses, it =
appears differences between "validated the SDID" and "authenticated the =
SDID" could use some clarification since this is awkwardly described in =
RFC6376 section 6.3. =20

Quoting the abstract of RFC5863 co-authored by Dave Crocker, "DKIM's =
authentication of email identity can assist in the global control of =
"spam" and "phishing".  This document provides implementation, =
deployment, operational, and migration considerations for DKIM."=20

Section 5.4 "Inbound Mail Filtering" of RFC5863 states:=20
,---
   DKIM is frequently employed in a mail filtering strategy to avoid
   performing content analysis on email originating from trusted
   sources.  Messages that carry a valid DKIM signature from a trusted
   source can be whitelisted, avoiding the need to perform computation
   and hence energy-intensive content analysis to determine the
   disposition of the message.
'---
This is exactly how DKIM is being used and why DKIM is harmful!

Additional information is being acquired, but will not alter conclusions =
reached.
http://tools.ietf.org/html/draft-otis-dkim-harmful-03

Regards,
Douglas Otis

=20


--Apple-Mail=_E256A67C-79E2-49C6-AB07-957D4D12A5CD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jun 4, 2013, at 7:16 PM, Sam Hartman &lt;<a =
href=3D"mailto:hartmans-ietf@mit.edu">hartmans-ietf@mit.edu</a>&gt; =
wrote:</div><blockquote type=3D"cite">So, I'd like to encourage Doug to =
refine his work, fix errors of<br>precision, but to say I think this is =
worth writing down.<br></blockquote><br></div><div>Dear =
Sam,</div><div><br></div><div>Thank you for your interest. &nbsp;I have =
updated the draft and, and&nbsp;as requested by Dave =
Crocker,&nbsp;included references to prior statements by Dave Crocker =
and Barry Leiba made public subsequent to the conclusion of the WG DKIM =
specification in response to comments about the phishing threat DKIM =
permits. &nbsp;In reviewing some of Dave Crocker's responses, it appears =
differences between "validated the SDID" and "authenticated the SDID" =
could use some clarification since this is awkwardly described in =
RFC6376 section 6.3. &nbsp;</div><div><br></div><div>Quoting the =
abstract of RFC5863 co-authored by Dave Crocker, "DKIM's authentication =
of email identity can assist in the global&nbsp;control of "spam" and =
"phishing". &nbsp;This document provides&nbsp;implementation, =
deployment, operational, and migration considerations&nbsp;for =
DKIM."&nbsp;</div><div><br></div><div>Section&nbsp;5.4 "Inbound Mail =
Filtering"&nbsp;of RFC5863 states:&nbsp;</div><div>,---</div><div>&nbsp; =
&nbsp;DKIM is frequently employed in a mail filtering strategy to =
avoid</div><div>&nbsp; &nbsp;performing content analysis on email =
originating from trusted</div><div>&nbsp; &nbsp;sources. &nbsp;Messages =
that carry a valid DKIM signature from a trusted</div><div>&nbsp; =
&nbsp;source can be whitelisted, avoiding the need to perform =
computation</div><div>&nbsp; &nbsp;and hence energy-intensive content =
analysis to determine the</div><div>&nbsp; &nbsp;disposition of the =
message.</div><div>'---</div><div>This is exactly how DKIM is being used =
and why DKIM is harmful!</div><div><br></div><div>Additional information =
is being acquired, but will not alter conclusions reached.</div><div><a =
href=3D"http://tools.ietf.org/html/draft-otis-dkim-harmful-03">http://tool=
s.ietf.org/html/draft-otis-dkim-harmful-03</a></div><div><br></div><div>Re=
gards,</div><div>Douglas =
Otis</div><div><br></div><div>&nbsp;</div><br></body></html>=

--Apple-Mail=_E256A67C-79E2-49C6-AB07-957D4D12A5CD--

From prvs=18809eb668=suresh.krishnan@ericsson.com  Mon Jun 17 13:03:08 2013
Return-Path: <prvs=18809eb668=suresh.krishnan@ericsson.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 C5CB821F9AE2 for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 13:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 F5i8PPAS9CGv for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 13:03:02 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 1773721F9A8C for <ietf@ietf.org>; Mon, 17 Jun 2013 13:03:02 -0700 (PDT)
X-AuditID: c6180641-b7f0e6d0000015f1-d6-51bf6b74e76f
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 95.74.05617.47B6FB15; Mon, 17 Jun 2013 22:03:01 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0328.009; Mon, 17 Jun 2013 16:03:00 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Diversity: Call for community input
Thread-Topic: Diversity: Call for community input
Thread-Index: Ac5qwFpJ4lDSIIxHToKBGdZqcuFe4g==
Date: Mon, 17 Jun 2013 20:03:00 +0000
Message-ID: <E87B771635882B4BA20096B589152EF626959D@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_E87B771635882B4BA20096B589152EF626959Deusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLLMWRmVeSWpSXmKPExsUyuXSPt25p9v5Ag54NghbPNs5ncWD0WLLk J1MAYxS3TVJiSVlwZnqevl0Cd8aaN69YCx54V5z+oNXAOMOpi5GTQ0LAROLWkT9MELaYxIV7 69m6GLk4hASOMkq8fraMFcJZziix6sQ3ZpAqNqCODTs/g3WICChLHJh5gxXEFhbQkTjy7Dor RNxQYvquPewQtp7E/c6PYDaLgKrE9l+LwWxeAW+JbZteg81hBNr8/dQaMJtZQFzi1pP5UBcJ SCzZc54ZwhaVePn4HyuErSyx5Ml+Foj6fIlZf64xQswUlDg58wnLBEahWUhGzUJSNgtJGURc R2LB7k9sELa2xLKFr5lh7DMHHjMhiy9gZF/FyFFanFqWm25kuIkRGPrHJNgcdzAu+GR5iFGa g0VJnPf9qV2BQgLpiSWp2ampBalF8UWlOanFhxiZODhBBJdUA2OpXmg+d5dKlqNTdBBf4Gaz WkGX92eMlv8WttUwn2gi9e9X4d++XTUrEjInfTbWzjrMGLnqu7fYKo053qzcehOlbVbZaFSH C+k+eNnbsXkXh2PN1xeZB9TX3Ju++4uWxt6uRHN2lm1+37RuO8wx7czf0zLvnf5+qbcMs9Zb zb/xoSR8565HdkosxRmJhlrMRcWJALv60+NQAgAA
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: Mon, 17 Jun 2013 20:03:08 -0000

--_000_E87B771635882B4BA20096B589152EF626959Deusaamb107ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

The diversity design team is working on mechanisms to increase
the range of perspectives within the IETF, while maintaining high
standards of quality.

Our goal is to help improve the composition and dynamic of the
IETF, by finding ways to incorporate a wide range of perspectives
within the IETF, and specifically in the IETF management teams.
One way of achieving this is to ensure that participants differ
along many different personal, social, and professional
attributes. The expectation is that the greater range of
perspectives leads to considering issues more deeply and with
more sensitivity.

Community feedback is the most important input that helps us
determine the aspects are currently working well in the IETF in
this regard and those that are not. We cannot properly execute
the task of proposing new mechanisms or modifying existing
mechanisms to further these goals without **your** participation
and feedback.

We would like to help the IETF management make choices that
maximize the IETF's ability to include and encourage all
interested participants, and maximize their contributions to IETF
work.

On that basis, we are seeking input from people based on their
personal experiences about

* actions and activities that have worked well to improve the
  inclusiveness of the IETF process

* actions and activitiets that have not worked well to improve
  the inclusiveness of the IETF process

* actions and activities that have worked *against* inclusiveness
  of the IETF process

If you have experience with other technology based organisations
that have broad consultation practices, we would also like to
hear about examples of actions taken that work well to include
participation from diverse communities

Please provide us your input by sending an email to the diversity
design team at diversity-dt@ietf.org . You can provide
**anonymous** feedback by contacting either of the design team
leads Suresh Krishnan <suresh.krishnan@ericsson.com> and Kathleen
Moriarty <kathleen.moriarty@emc.com> who will anonymize it for
the rest of the members.

Thanks
Suresh Krishnan & Kathleen Moriarty
for the diversity design team

Design team members
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Narelle Clark
Dave Crocker
Aaron Yi Ding
Lars Eggert
SM
Monique Morrow
Hugo Salgado
Arturo Servin
Margaret Wasserman
Scott Weeks

--_000_E87B771635882B4BA20096B589152EF626959Deusaamb107ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-CA" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The diversity design team is working on mechanisms t=
o increase<o:p></o:p></p>
<p class=3D"MsoNormal">the range of perspectives within the IETF, while mai=
ntaining high<o:p></o:p></p>
<p class=3D"MsoNormal">standards of quality.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Our goal is to help improve the composition and dyna=
mic of the<o:p></o:p></p>
<p class=3D"MsoNormal">IETF, by finding ways to incorporate a wide range of=
 perspectives<o:p></o:p></p>
<p class=3D"MsoNormal">within the IETF, and specifically in the IETF manage=
ment teams.<o:p></o:p></p>
<p class=3D"MsoNormal">One way of achieving this is to ensure that particip=
ants differ<o:p></o:p></p>
<p class=3D"MsoNormal">along many different personal, social, and professio=
nal<o:p></o:p></p>
<p class=3D"MsoNormal">attributes. The expectation is that the greater rang=
e of<o:p></o:p></p>
<p class=3D"MsoNormal">perspectives leads to considering issues more deeply=
 and with<o:p></o:p></p>
<p class=3D"MsoNormal">more sensitivity.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Community feedback is the most important input that =
helps us<o:p></o:p></p>
<p class=3D"MsoNormal">determine the aspects are currently working well in =
the IETF in<o:p></o:p></p>
<p class=3D"MsoNormal">this regard and those that are not. We cannot proper=
ly execute<o:p></o:p></p>
<p class=3D"MsoNormal">the task of proposing new mechanisms or modifying ex=
isting<o:p></o:p></p>
<p class=3D"MsoNormal">mechanisms to further these goals without **your** p=
articipation<o:p></o:p></p>
<p class=3D"MsoNormal">and feedback.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We would like to help the IETF management make choic=
es that<o:p></o:p></p>
<p class=3D"MsoNormal">maximize the IETF's ability to include and encourage=
 all<o:p></o:p></p>
<p class=3D"MsoNormal">interested participants, and maximize their contribu=
tions to IETF<o:p></o:p></p>
<p class=3D"MsoNormal">work.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">On that basis, we are seeking input from people base=
d on their<o:p></o:p></p>
<p class=3D"MsoNormal">personal experiences about<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">* actions and activities that have worked well to im=
prove the<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; inclusiveness of the IETF process<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">* actions and activitiets that have not worked well =
to improve<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; the inclusiveness of the IETF process<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">* actions and activities that have worked *against* =
inclusiveness<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; of the IETF process<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If you have experience with other technology based o=
rganisations<o:p></o:p></p>
<p class=3D"MsoNormal">that have broad consultation practices, we would als=
o like to<o:p></o:p></p>
<p class=3D"MsoNormal">hear about examples of actions taken that work well =
to include<o:p></o:p></p>
<p class=3D"MsoNormal">participation from diverse communities<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please provide us your input by sending an email to =
the diversity<o:p></o:p></p>
<p class=3D"MsoNormal">design team at diversity-dt@ietf.org . You can provi=
de<o:p></o:p></p>
<p class=3D"MsoNormal">**anonymous** feedback by contacting either of the d=
esign team<o:p></o:p></p>
<p class=3D"MsoNormal">leads Suresh Krishnan &lt;suresh.krishnan@ericsson.c=
om&gt; and Kathleen<o:p></o:p></p>
<p class=3D"MsoNormal">Moriarty &lt;kathleen.moriarty@emc.com&gt; who will =
anonymize it for<o:p></o:p></p>
<p class=3D"MsoNormal">the rest of the members.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks<o:p></o:p></p>
<p class=3D"MsoNormal">Suresh Krishnan &amp; Kathleen Moriarty<o:p></o:p></=
p>
<p class=3D"MsoNormal">for the diversity design team<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Design team members<o:p></o:p></p>
<p class=3D"MsoNormal">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Narelle Clark<o:p></o:p></p>
<p class=3D"MsoNormal">Dave Crocker<o:p></o:p></p>
<p class=3D"MsoNormal">Aaron Yi Ding<o:p></o:p></p>
<p class=3D"MsoNormal">Lars Eggert<o:p></o:p></p>
<p class=3D"MsoNormal">SM<o:p></o:p></p>
<p class=3D"MsoNormal">Monique Morrow<o:p></o:p></p>
<p class=3D"MsoNormal">Hugo Salgado<o:p></o:p></p>
<p class=3D"MsoNormal">Arturo Servin<o:p></o:p></p>
<p class=3D"MsoNormal">Margaret Wasserman<o:p></o:p></p>
<p class=3D"MsoNormal">Scott Weeks<o:p></o:p></p>
</div>
</body>
</html>

--_000_E87B771635882B4BA20096B589152EF626959Deusaamb107ericsso_--

From paul.hoffman@vpnc.org  Mon Jun 17 16:42:19 2013
Return-Path: <paul.hoffman@vpnc.org>
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 F10A921F9E70 for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 16:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 H4F8dKk5-jqC for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 16:42:15 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8AAA821F9E6B for <ietf@ietf.org>; Mon, 17 Jun 2013 16:42:14 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5HNgC1Z052123 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Mon, 17 Jun 2013 16:42:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Hugh Daniel has passed away
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20130604230415.GY8399@mip.aaaaa.org>
Date: Mon, 17 Jun 2013 16:42:11 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <FDB4C180-7D98-421E-8664-F4D2D549A50C@vpnc.org>
References: <alpine.LFD.2.10.1306041741030.898@bofh.nohats.ca> <20130604230415.GY8399@mip.aaaaa.org>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1508)
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: Mon, 17 Jun 2013 23:42:19 -0000

Memorials planned:

http://www.chuqui.com/2013/06/hugh-daniel-memorial-info/



From carlosm3011@gmail.com  Mon Jun 17 19:52:22 2013
Return-Path: <carlosm3011@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 4C73621F9C2B for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 19:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 lJYmEi3OEm7s for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 19:52:14 -0700 (PDT)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 86ECD21F9C22 for <ietf@ietf.org>; Mon, 17 Jun 2013 19:52:09 -0700 (PDT)
Received: by mail-la0-f48.google.com with SMTP id lx15so3018671lab.7 for <ietf@ietf.org>; Mon, 17 Jun 2013 19:52:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Q2rFkkzVfq5cFdSF5hWNA+apVNfNjMbd/DAakbYuZjs=; b=RQLr9P5TnK7NsHUY1DrjL+61/vyqQqwNlO72bz9fchiq7IfRpRIn4VmybaFfPKdSCq LV9qaVUgF+K/DE9V8GtDMYcZo6XoDOmSg6sHElOWzD59zHcXC8kafieCsn4Xb/TQnbhX K9+tyOQ3Nal73pNXQa18pvKo21B1evjscUzlMHovBjVuxNfhWKwmguyrISzBahqpt3vR 1QyxgpaektJT2P998cvgD+zXLMCAkksgdhlZPzGBlkB6cQpGA28/5XzRfYK+qcSh/6++ WH/TRrQ7hs7keoen5g4FxAAaIF34QctDq96B8R5hjD/cL7HCtoggmi+IMFytLSlcGudl G4Rg==
MIME-Version: 1.0
X-Received: by 10.112.16.74 with SMTP id e10mr105152lbd.46.1371523928389; Mon, 17 Jun 2013 19:52:08 -0700 (PDT)
Received: by 10.112.205.70 with HTTP; Mon, 17 Jun 2013 19:52:08 -0700 (PDT)
In-Reply-To: <A0E2EF02-8902-4D69-B3D6-65CBF1625BE9@vpnc.org>
References: <02a901ce6b83$4e22bbb0$ea683310$@olddog.co.uk> <51BF58A7.4010008@gmail.com> <A0E2EF02-8902-4D69-B3D6-65CBF1625BE9@vpnc.org>
Date: Mon, 17 Jun 2013 23:52:08 -0300
Message-ID: <CA+z-_EWpEvtWm1mvkyBtK6aFGXC9Oc3Vx-XaWunKCDSk_b417g@mail.gmail.com>
Subject: Re: New non-WG malign list : Network Service Chaining (NSC)
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=001a11c3fdb68d7d2a04df64cc4e
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
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: Tue, 18 Jun 2013 02:52:22 -0000

--001a11c3fdb68d7d2a04df64cc4e
Content-Type: text/plain; charset=ISO-8859-1

Not only that, they may also contain nuts.

:D


On Mon, Jun 17, 2013 at 4:40 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On Jun 17, 2013, at 11:42 AM, Melinda Shore <melinda.shore@gmail.com>
> wrote:
>
> > How about a new non-malign WG list?
>
> Haven't seen one of those in the IETF in quite some time.
>



-- 
--
=========================
Carlos M. Martinez-Cagnazzo
http://cagnazzo.name
=========================

--001a11c3fdb68d7d2a04df64cc4e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Not only that, they may also contain nuts.<div><br></div><=
div style>:D</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gm=
ail_quote">On Mon, Jun 17, 2013 at 4:40 PM, Paul Hoffman <span dir=3D"ltr">=
&lt;<a href=3D"mailto:paul.hoffman@vpnc.org" target=3D"_blank">paul.hoffman=
@vpnc.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Jun 17, 2013, at 11:42 =
AM, Melinda Shore &lt;<a href=3D"mailto:melinda.shore@gmail.com">melinda.sh=
ore@gmail.com</a>&gt; wrote:<br>

<br>
&gt; How about a new non-malign WG list?<br>
<br>
</div>Haven&#39;t seen one of those in the IETF in quite some time.<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>--<br>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Ca=
rlos M. Martinez-Cagnazzo<br><a href=3D"http://cagnazzo.name" target=3D"_bl=
ank">http://cagnazzo.name</a><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
</div>

--001a11c3fdb68d7d2a04df64cc4e--

From chris.dearlove@baesystems.com  Tue Jun 18 02:16:08 2013
Return-Path: <chris.dearlove@baesystems.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 4312821F9B20; Tue, 18 Jun 2013 02:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.261
X-Spam-Level: 
X-Spam-Status: No, score=-10.261 tagged_above=-999 required=5 tests=[AWL=0.338, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 8RnWvMIyioE8; Tue, 18 Jun 2013 02:16:04 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 7FCF621F8904; Tue, 18 Jun 2013 02:16:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,887,1363132800"; d="scan'208";a="347486685"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 18 Jun 2013 10:15:56 +0100
X-IronPort-AV: E=Sophos;i="4.87,887,1363132800"; d="scan'208";a="19264460"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasmds017.greenlnk.net with ESMTP; 18 Jun 2013 10:15:55 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.180]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.02.0328.009; Tue, 18 Jun 2013 10:15:55 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
Subject: RE: Gen-ART Review of draft-ietf-manet-rfc6622-bis-02
Thread-Topic: Gen-ART Review of draft-ietf-manet-rfc6622-bis-02
Thread-Index: AQHOaT0eFhzEQVZMPEinJ81AQTFy/Jk7MyUg
Date: Tue, 18 Jun 2013 09:15:54 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D250921AA@GLKXM0002V.GREENLNK.net>
References: <90D2B755-F68F-4C58-A645-84E4445C73BE@vigilsec.com>
In-Reply-To: <90D2B755-F68F-4C58-A645-84E4445C73BE@vigilsec.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: IETF Gen-ART <gen-art@ietf.org>, "manet@ietf.org" <manet@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: Tue, 18 Jun 2013 09:16:08 -0000

Comments below, marked >>>. I think (though I need my co-authors to agree o=
f course) that a draft with these revisions (and any others we need) will b=
e appropriate following any other IETF LC comments.

-- =

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Rus=
s Housley
Sent: 14 June 2013 21:24
To: IETF
Cc: IETF Gen-ART; manet@ietf.org
Subject: Gen-ART Review of draft-ietf-manet-rfc6622-bis-02

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-manet-rfc6622-bis-02
Reviewer: Russ Housley
Review Date: 2013-06-15
IETF LC End Date: 2013-06-27
IESG Telechat date: Unknown

Summary:  The document is almost ready for publication as a
standards track RFC.  I raise one major concern, and once it
is resolved, the document will be ready.

Major Concern:

In Section 12.2.3, is there any difference in processing when the
source IP address is IPv4 as opposed to IPv6?  Obviously, the two have
a different length.  Off the top of my head I cannot find a way for an
attacker to exploit one party using IPv4 in the ICV calculation and the
other party using IPv6.  Since the IPv6 address is 12 octets longer
than the IPv4 address, there may be some opportunity for an attacker.
Anyway, concerns like this are usually thwarted by including the length
of the overall hash function input as the first octet or two of the
value-to-be-hashed.  Such a value does not need to be transmitted.
Each party knows how many octets it passed to the hash function.

>>> As it happens, this value is present in the packet header, but not in t=
he message header, and we do not want to introduce a difference between the=
m. In addition, being after the address might not work.
>>> Like you, I can't see how to exploit and still maintain a legal structu=
re following, but attackers can be very resourceful. and I don't see that t=
his can be guaranteed.
>>> Thus, this appears a good suggestion, with minimal computational overhe=
ad and no over the air overhead.


Minor Concerns:  =


I find Section 1.1 a bit confusing.  I think it should start by saying
that RFC 6622 defined two ICV TLV extension types (0 and 1).  This
document repeats those definitions and adds a third ICV TLV extension
type (2).

>>> OK.

Section 5 says:

  An ICV TLV with type extension =3D 2 specifies a modified version of
  this definition.
 =

This is unclear.  I believe that an ICV TLV with type extension =3D 2 is
an update to ICV TLV with type extension =3D 1.  It would be good to
introduce the need for this update.  I suggest:

  An ICV TLV with type extension =3D 2 is the same as an ICV TLV with
  type extension =3D 1, except that the integrity protection also covers
  the source address of the IP datagram carrying the packet, message,
  or address block.

>>> Might tweak that a little, but OK.

If you accept this suggestion, the following paragraph should also be
revised.  I suggest:

  Specifically, with type extension =3D 1 or type extension =3D 2, the
  <value> field contains the result of combining a cryptographic
  function and a hash function.  The <value> field contains multiple
  sub-fields indicating which hash function and cryptographic function
  have been used as specified in Section 12.

>>> Essentially moving detail from this paragraph to previous one.


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From prvs=3881e1e3e5=magnus.westerlund@ericsson.com  Tue Jun 18 04:41:57 2013
Return-Path: <prvs=3881e1e3e5=magnus.westerlund@ericsson.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 1BCA221F9BFF; Tue, 18 Jun 2013 04:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.083
X-Spam-Level: 
X-Spam-Status: No, score=-106.083 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 GQo9H494EDTZ; Tue, 18 Jun 2013 04:41:51 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF4F21F9BD9; Tue, 18 Jun 2013 04:41:50 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-10-51c0477cc1fc
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id F5.63.15700.C7740C15; Tue, 18 Jun 2013 13:41:49 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Tue, 18 Jun 2013 13:41:49 +0200
Message-ID: <51C047BC.1050207@ericsson.com>
Date: Tue, 18 Jun 2013 13:42:52 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Gen-art last call review: draft-ietf-mmusic-rfc2326bis-34
References: <51AFB3FF.7000009@nostrum.com>
In-Reply-To: <51AFB3FF.7000009@nostrum.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHLMWRmVeSWpSXmKPExsUyM+JvrW6t+4FAg/NfOC2u7Z7CZHH11WcW i2cb57NYTF3+mMXi2pxGNgdWjyVLfjJ5zNr5hMXjy+XPbAHMUdw2SYklZcGZ6Xn6dgncGV+n TGUqeLOXseLCs2fsDYxPpjF2MXJySAiYSFx4dYwJwhaTuHBvPVsXIxeHkMApRom172YyQjjL GSXe71rNClLFK6Atsf5BD1g3i4CqxJEdE8G62QQsJG7+aGQDsUUFgiWObN/MAlEvKHFy5hMw W0RAQ+LakiXsIEOZBSYzSszbcAmsQVjATWLGsY3sILaQgJbEww/nwBo4gZZNXX0B6jxJiS0v 2sFqmAUMJI4smsMKYctLNG+dzQzRqy3R0NTBOoFRaBaS3bOQtMxC0rKAkXkVI3tuYmZOernh JkZgcB/c8lt3B+OpcyKHGKU5WJTEeT+c2hUoJJCeWJKanZpakFoUX1Sak1p8iJGJgxNEcEk1 MCbJ+Eyo92Lc7ZoV6LQh/MT6k+t3pzNJ7Npz5s33Wev9VzVcDEqSWHqqdq3Ho5aShItz2zZs kCm9Iii3OnmNPs/y+CCmeM4Jf3rfBHoZPulKt5hgIrI8N+0uu9iJypdt4QYK977Jr36hUmBY +klSRnWDs82Zve1XCo2n6DH/OqaU43HW4mZYkxJLcUaioRZzUXEiAAs+RylBAgAA
Cc: draft-ietf-mmusic-rfc2326bis@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, mmusic@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: Tue, 18 Jun 2013 11:41:57 -0000

Hi Robert,

Thanks for the massive review. A number of really good comments in here.
Below you will find my answers, comments, questions and in most cases
clarifications what I see us doing with your comment. These covers your
major and minor comments. The nits we will simply implement as we see
fit, if we have questions we will comeback with those.

WG, there are a number of issues in here that would be greatly helped by
your input!

On 2013-06-05 23:56, Robert Sparks wrote:
> Document: draft-ietf-mmusic-rfc2326bis-34
> Reviewer: Robert Sparks
> Review Date: 05-Jun-2013
> IETF LC End Date: 04-Jun-2013
> IESG Telechat date: not yet on a telechat
>
>
> The document is very long, and the structure is unusual - much of the
> definition of the protocol itself is in the appendices. You are missing
> an opportunity to make this document much shorter (thereby likely
> increasing its effectiveness). Much of the jump in from RFC2326 was
> importing the description of headers and responses from HTTP, tailoring
> them to RTSP. That was a good exercise in that it highlights some issues
> that would otherwise be non-obvious (and raises a few questions below).
> But you followed the style from HTTP perhaps too closely - much shorter
> descriptions without examples might have done the job better. Overall,
> separating exposition and examples from the protocol definition would
> make it much easier for an implementer to find the definition of the
> protocol, and use the document as a reference when diagnosing a failure
> to interoperate.

Agree, it would be differently structure if we wrote it from scratch
today. But it is an document that is 10 years in the making with dual
heritage in RFC 2326 and RFC 2068.

>
> Major Issues
>
> I'm not seeing what instructs an RTSP element on how to find the server
> it would try to open a connection to given an rtsp or rtsps URI? Are you
> assuming it would be doing A or AAAA DNS lookups? 

Yes, using A or AAAA DNS records are assumed. No problem making that
explicit.

Should this protocol
> use NAPTR/SRV? 

Potentially, but as everyone have been using A records for all these
years, I think it is not worth defining it at this stage.

The document should be explicit. On a related note, (and
> maybe I missed this), but where do you talk about what an element should
> check in the server's certificate when connecting over TLS? Are you
> assuming a common name match? Or are you expecting some SubjectAltName
> processing?

This draft says in Section 19.2 the following regarding this:

   RTSP MUST follow the same guidelines with
   regards to TLS [RFC5246] usage as specified for HTTP, see [RFC2818].

Where section 3.1 (Server Identity) of RFC 2818 contains the following:

   If a subjectAltName extension of type dNSName is present, that MUST
   be used as the identity. Otherwise, the (most specific) Common Name
   field in the Subject field of the certificate MUST be used.

Isn't that clear enough on that matter?

>
> The document should say more about when connection reuse is appropriate,
> particularly when the connections happened because of an rtsps uri. Two
> different names might resolve to the same IP address - reusing a
> connection formed when looking at the first name (and verifying the
> server's cert) is dangerous. A new connection needs to be formed (and
> verified) instead.

I want to check my understanding of the issue you are seeing here. So a
client looks ups foo.example.org, gets an ip address A and establishes
an TCP/TLS connection and verifies that there are a SubjectAltName that
matches foo.example.org works. Then client is going to open
bar.example.com and looks up that address and gets the same IP address A.
Client matches A against existing connections and simply sends a request to
bar.example.com. Thus bypassing the certificate verification.

If we clarify that in the process of opening rtsps://bar.example.com the
client MUST verify that the server certificate for the TLS connection it
considers re-using has an SubjectAltName of bar.example.com, does that
resolve your concerns. If not, please explain the concern further.


>
> The text talks about the option to queue S->C requests if there isn't a
> connection to the client available. Ostensibly, this means the request
> can go down some future connection. It's not clear how the server can
> tell the right client connected. In particular, when using rtsps, how do
> you prevent a malicious client from getting such a queued message that
> wasn't meant for him?


Okay, this security issue I have totally missed but it is clearly
serious. I don't see any easy way of fixing this. Thus I would suggest
that we simply make it clear that a server MUST NOT queue the S->C RTSP
message, independent if they are requests PLAY_NOTIFY and TEARDOWN or
responses to client requests.


>
> Given that the text talks about queuing S-C requests, it should
> explicitly call out whether a server can queue a response if the
> connection the associated request arrived on is no longer available. I
> think what you want to say is that such a response must not be queued,
> and must be dropped.

Agreed, lets mandate that they are dropped.


>
> There are several places in the text that talk about using a 503
> response with a Retry-After header to push back on traffic from an
> element (the first is section 10.7).
> * It's not clear what the subject of a 503 is. Is it intended to be
> scoped to requests to the resource in the RURI of the associated
> request? Is it intended to be scoped to the domain in that resource? Or
> is it, like in SIP, intended to be scoped to the server issuing the
> response, independent of what the RURI contained?

Very good question. It is far from obvious what the best choice is. And
I think even talking only about URI related scope may not be the best.

The case I have in mind is if a proxy that has several already
established RTSP sessions over a persistent connection. When a client
connected to the proxy requests to establish a new session the server
may have insufficient resource to handle the SETUP request and send a
503 answer. However if another client already having an RTSP session for
the same resource want to terminate that session it would be strange to
refuse to process the message as it will actually free up resources.

This makes me believe that you need to have a RTSP Session scope for any
request carrying a Session-ID and a general server, or host name scope
for non-associated that doesn't prevent established sessions to try.

Thoughts on this?


> * If the intent is that the 503 talks about the server, then you should
> clarify that a proxy doesn't simply forward 503 responses (after
> rewriting CSeqs), and should probably have a response of its own.
> Otherwise, clients that might be talking to two different servers
> through one proxy would lose access to both of them when one of the
> servers 503ed.

If we us a host and session scope then this issue would not be present.
However, if the proxy is actually overloaded that still needs its own
552 Proxy Unavailable response with the same scope rules as for the 503,
but where unassociated requests concerns sending to the proxy at all.

>
> Section 4.9.1 lists values the Seek-Style header can take, but 18.45
> lists a completely different set (which most of the rest of the document
> uses). Should 4.9.1 be changed to use the values in 18.45? Are the right
> strings being used in sections 13.4.4 through 13.4.6? Those appear to be
> using strings from 4.9.1.

Yes, clearly an inconsistency issue that needs to be resolved.

>
> The document will not stand if you delete some of the appendices. They
> aren't supplementary material. Please consider restructuring the
> normative sections back into the main document, or clearly identifying
> which ones define protocol and which are background information.

I would like to characterize this differently. I think you will have a
working protocol of RTSP, but you can't use it for anything. This as you
will have no media transport (C), no media description protocol (D), and
no parameters format (F). But, these appendixes are replaceable with
other protocol solutions.

The Introduction section (1) says:

                                 The appendixes describe and define some
   functionalities that are not part of the core RTSP specification, but
   which are still important to enable some usages.  Among them, the RTP
   usage is defined in Appendix C and the SDP usage with RTSP is defined
   in Appendix D, which are two mandatory appendixes.

I note that we should add F to this list.

I think we should be clear in each of this appendices that if one
support Foo for the purpose of bar then this appendix defines
normatively how one does it.


>
> Section 15 talks about a "transparent' proxy, but there is no
> description in this document of what protocol such a thing should
> follow. What bad thing happens if you remove all mention of
> "transparent" proxies from the document? As far as I can tell, that
> won't affect the protocol definition at all.

Not really, there is no definition of transparent proxies currently.
There is one security concern that make require some word smithing if we
remove transparent proxies.

>From my perspective a transparent proxy is something that hijacks a TCP
connection towards an RTSP server to be a proxy between client and
server. Further is not detectable from the client's or the servers
perspective, but still may modify RTSP messages within the bounds of the
RTSP protocol.

But, in reality as we have proxies that are visible we should focus on
those and forget this bastard version.

>
> The list of steps for establishing an SRTP cryptographic context in
> C.1.4.1 says "This specification does not specify an explicit method for
> indicating this SRTP cryptographic context establishment method, but
> future specifications may." in the context of looking at the SDP. SDP
> _has_ methods of indicating what keying mechanism is used with SRTP -
> are you talking about something different? 

I think you are considering the methods for keying SRTP that are
Offer/Answer dependent. The only RTSP SDP using method that exist is the
one defined in RFC 4567, which we are explicit on not using.

Why doesn't this section say
> something like "the use of SRTP with RTSP is only defined with MIKEY
> with keys established as defined in this section. Future documents may
> talk about how an RTSP implementation might treat SDP that indicates
> some other key mechanism be used"? 

Yes, that is appears better, but we will have to make it clear that is
is regarding RTSP 2.0. Must also think if RFC 4567 needs to be worked
into that sentence.

Could you provide an example in the
> document of an RTSP message carrying SDP reflecting the use of SRTP as
> defined in this document?

The point is that the only difference is that he RTP profile is SAVP/RTP
or SAVPF/RTP in the SDP. Thus making such an SDP isn't difficult.
Question is if it provides a benefit?



> Minor Issues
>
> The document uses the notion of a "control connection" (it appears first
> in section 2.5) without defining what that is, or what kind of
> connections you might have that aren't control connections.

The "control connection" is the connection established for sending RTSP
messages on it. I agree it is undefined and could likely be replaced by
the "RTSP connection" or "connection for RTSP messages"

>
> The update to the registration of the rtsp and rtsps schema call out
> that there are changes that can result in interoperability issues. It
> doesn't say what the issues are, or who might encounter them. I can
> infer that the point is that there might be problems if a URI following
> this updated registration were to be processed by an RTSP 1.0
> implementation (or any other application that relied on the previous
> definition). It would be better to say that explicitly, and talk about
> how a previous implementation is likely to act when presented with a URI
> that exercised these new changes.

I have gotten these comment elsewhere and have prepared a text update
for section 4.2:

   The details of the syntax of "rtsp" and "rtsps" URIs has been changed
   from RTSP 1.0.  These changes are:

   o  Support for IPV6 literal in host part and future IP literals
      through RFC 3986 defined mechanism.

   o  A new relative format to use in the RTSP protocol elements that is
      not required to start with "/".

   Neither should have any significant impact on interoperability.  If
   one is required to use IPv6 literals to reach an RTSP server, then
   that RTSP server must be IPv6 capable, and RTSP 1.0 is not a fully
   IPv6 capable protocol.  If an RTSP 1.0 client attempts to process the
   URI it will not match the allowed syntax and be considered invalid
   and processing will be stopped.  This is clearly a failure to reach
   the resource, however it is not a signification issue as RTSP 2.0
   support was needed anyway in both server and client.  Thus failure
   will only occur in a later step when there is a RTSP version
   mismatch between client and server.  The second change will only
   occur in RTSP messages, that are explicitly identified as being RTSP
   2.0 messages, thus a RTSP 1.0 only agent will not be required to
   parse this variant.

Clear enough?

The above is Edited In.

 (It's not clear to me that all of the
> thread at www.ietf.org—msg01567.html
> <http://www.ietf.org/mail-archive/web/uri-review/current/msg01567.html>
> concluded - I see how the fragments question ended, but what about
> things like the addition of IPV6 literals? In particular, I'm not
> finding a response where Ted Hardie agreed that the potential for
> interoperability failure had been adequately addressed).

I talked to him in person about this just after the discussion to better
understand his comments. If we want a confirmation I think we need to
loop him into a discussion regarding this particular issue.

I provided a clarification to the designated URI reviewer which accepted
the request.

>
>
> I think you've said something different than you mean in 5.4 item 1. I
> think you mean to say that an RTSP implementation would ignore any body
> that happened to come in message that MUST NOT contain one. What you've
> said is that the part of the parser that's doing framing has to stop
> framing at the end of the headers, and that such an errant body would be
> parsed as a separate message. As written this would keep someone from
> using an Internet Message Format parser since it would have to ignore
> any Content-Length that might have appeared, even though it wasn't
> supposed to.

Yes, it is clearly sufficient to ignore the body, and likely much better
from an error handling consideration.

We will propose a text change.


>
> In section 10.4, it looks like a server can keep an RTSP transaction
> pending forever if it sends 100 responses often enough. I assume the
> client's recourse if it doesn't want to remain involved is to close the
> connection. If that's right, it's worth calling it out explicitly in
> this section.

This is likely a good suggestion, and works fine if the client simply
wants to abort the request and is anyway abandoning the RTSP session.
However, the question is what to do if just the request becomes
irrelevant and instead want to do something else with the RTSP session.
A single client may abandon the connection, open a new one and issue a
request, to a potentially undetermined session state. Yet another
complexity is what a proxy does that has multiple RTSP sessions on the
same server. Here the rules for processing in order the different
requests and their relation to answers in the same order.

This makes me want to weaken the recommendation on re-using an
connection for multiple RTSP sessions.


>
> Somewhere, probably in section 15.2, you should be explicit that a proxy
> that is multiplexing requests MUST keep the requests in the same order
> as they are folded together. You can infer that, or things simply break,
> but saying it explicitly would be better.

Probably, as a clarification to what is already present in section 18.19
(CSeq header)

   Proxies that aggregate several sessions on the same transport will
   have to ensure that the requests sent towards a particular server
   have a joint sequence number space, i.e., they will regularly need to
   renumber the CSeq header field in requests (from proxy to server) and
   responses (from server to proxy) to fulfill the rules for the header.
   The proxy MUST increase the CSeq by one for each request it
   transmits, without regard of different sessions.


>
> Both GET_PARAMETER and SET_PARAMETER are listed as keep-alive methods in
> 10.5, but the note in section 13 on table 7 only uses that as a reason
> for requiring SET_PARAMETER. Why doesn't it also apply to GET_PARAMETER?
> And why is this only required at servers? "Required" in this section
> means Mandatory to Implement, I think. If that's right, it should be
> made explicit. If that's not right, what does it mean?

Yes, required is Required to implement in the server. The GET_PARAMETER
is not required as only one method for keep-alive is necessary. Thus,
the ones that needs to use GET/SET_PARAMETER for keep-alive will have to
choose SET_PARAMETER.

It is only required at the server, as it is in the client implementation
choice of how to ensure keep-alive works. As this is also dependent on
the media transport support one has, the client may not need a method
based keep-alive.

Clarifying "Required" should be straightforward.

>
> Section 13.8 makes a good argument for always putting parameters to be
> retrieved in a body. Why are you keeping the complexity of also allowing
> them in headers?

Some arguments are probably lost in the passage of time. However, the
headers specified to be suitable for inclusion in a GET_PARAMETER
requests are used for providing these information also in other methods,
thus we have not wanted to duplicate the representation of this
information in both a body and a header form.

>
> Section 13.10: "That should not provide any benefit." is not clear - can
> you expand it a little?

   If the REDIRECT request times out following the rules in Section 10.4
   the server MAY terminate the session or transport connection that
   would be redirected by the request.  This is a safeguard against
   misbehaving clients that refuse to respond to a REDIRECT request.
   That should not provide any benefit.

The intention here is to make clear that there shouldn't be an incentive
in the protocol to not acknowledge a REDIRECT request and instead simply
go on as it wasn't received or seen. Thus, we want to make clear that
the server may simply terminate the session in those cases.

I propose we change this sentence to:

Thus, removing any incentive to not acknowledge the reception of a
REDIRECT request.

Edited In

>
> In Section 13.10 you talk about clients _sending_ media (search for
> "send or receive media"). Do you mean anything more than possibly RTCP?
> Can you make that clear in the section?

You mean this sentence:

   After a REDIRECT request has been processed, a client that wants to
   continue to send or receive media for the resource identified by the
   Request-URI will have to establish a new session with the designated
   host.

The mentioning of send media is likely a RECORD reference. In this case
I don't see any issue with removing it.

Edited In

>
> Section 15.2's second paragraph appears to be the only place the proxy
> rewriting of CSeq in order to multiplex requests is defined, and it is
> very loose. It would be easy for a reader to fail to recognize this as
> an interoperability requirement. Please consider expanding how this is
> specified when addressing the comment about above about keeping requests
> in relative order when multiplexing.

There are text in Section 18.19 CSeq also. But I do think I agree that
this should be clarified.

>
> You follow the principle of saying a client should treat a response with
> an unknown response code, the same as it would treat the x00 of that
> class (e.g. 400 for an unknown 4xx). However, you do not define what a
> response code of 300 means. How is a client supposed to handle an
> unknown 3xx response?

Sorry, I don't quite get this comment. Section 17.3 says:

   If a 3rr response is received for a request in relation to
   an established session, the client SHOULD send a TEARDOWN request for
   the session, and MAY reestablish the session using the resource
   indicated by the Location.

   If the Location header is used in a response it MUST contain an
   absolute URI pointing out the media resource the client is redirected
   to, the URI MUST NOT only contain the host name.

As explained above unknown 3XX codes will be 3rr codes, as 304 isn't
unknown.

If you don't believe this is sufficient can you please be more explicit
about the issue?

>
> As written, a client and server can use HTTP Basic authentication over
> TCP that is not protected with TLS. Consider restricting it's use to TLS
> only. Are you sure you don't need to say anything RTSP specific about
> DIGEST computations (I don't think you need to go as far as SIP did
> talking about DIGEST, but I'm surprised you haven't run into issues
> relying only on 2617 literally.

Are you referring to Section 19.1 here?

Yes, I would not have any issue with requiring Basic to be combined with
TLS. I think that is appropriate.

When it comes to DIGEST, are you referring to section 22.4 in RFC 3261?

That section indicates that some clarifications are likely needed.

>
>
> How does 411 Length Required for this protocol make sense? Given that
> you've restricted the protocol to TCP and require the Content-Length
> header to be present if there is a body, in what circumstance would a
> server need to send a 411?

It really should occur for malformed messages, which we could use 400 as
response. So yes, 411 could be removed.

>
>
> Section 18.19 requires senders to increment CSeq by 1. We have a
> reliable transport with no request retransmission, so there should never
> be gaps at the receiver. Should the receiver check and react some way if
> there are gaps? I think you should explicitly tell them not to even
> look. If you agree, why is incrementing by one important as long as you
> are always strictly increasing?

I agree that for TCP or other reliable transports the receiver
SHOULD/SHALL ignore gaps. For any future specification of an unreliable
transport of RTSP messages this would be needed. As noted in Appendix G,
CSeq is retained for future support of unreliable transport.

>
> You call out several places where RTCP is essential to allow RTSP using
> RTP to work correctly, yet section C.1.2 sets up conditions where RTCP
> MUST NOT be sent. Why are you allowing those instead of treating the
> conditions you describe as errors?

Good question. I think it is a case we must ensure that you can
negotiate and configure your desired way, without really considering if
it should be allowed at all. I think mandating usage of RTCP with RTP
for RTSP 2.0 would be good. But, I think that needs to be verified with
the WG.

cheers


Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From mehmet.ersue@nsn.com  Tue Jun 18 06:18:50 2013
Return-Path: <mehmet.ersue@nsn.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 205D421F9EC2 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 06:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 1GfRul7W3YQv for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 06:18:45 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id B021921F9EBC for <ietf@ietf.org>; Tue, 18 Jun 2013 06:18:44 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r5IDIgPR006931 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 18 Jun 2013 15:18:42 +0200
Received: from DEMUHTC002.nsn-intra.net ([10.159.42.33]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r5IDIeqC016521 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Jun 2013 15:18:42 +0200
Received: from DEMUHTC009.nsn-intra.net (10.159.42.40) by DEMUHTC002.nsn-intra.net (10.159.42.33) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 18 Jun 2013 15:18:38 +0200
Received: from DEMUMBX005.nsn-intra.net ([169.254.5.149]) by DEMUHTC009.nsn-intra.net ([10.159.42.40]) with mapi id 14.03.0123.003; Tue, 18 Jun 2013 15:18:38 +0200
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: ext Melinda Shore <melinda.shore@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: New non-WG malign list : Network Service Chaining (NSC)
Thread-Topic: New non-WG malign list : Network Service Chaining (NSC)
Thread-Index: Ac5rgz8KIpl429SoSZ+5N4KbdHLRiP//7OaA//6rjnA=
Date: Tue, 18 Jun 2013 13:18:36 +0000
Message-ID: <E4DE949E6CE3E34993A2FF8AE79131F8108981@DEMUMBX005.nsn-intra.net>
References: <02a901ce6b83$4e22bbb0$ea683310$@olddog.co.uk> <51BF58A7.4010008@gmail.com>
In-Reply-To: <51BF58A7.4010008@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.159.42.114]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 428
X-purgate-ID: 151667::1371561522-00002EAE-6C112AE0/0-0/0-0
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: Tue, 18 Jun 2013 13:18:50 -0000

I assume "non-malign non-WG maillist" would be appropriate in this case.

Cheers,=20
Mehmet=20


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of e=
xt Melinda
> Shore
> Sent: Monday, June 17, 2013 8:43 PM
> To: ietf@ietf.org
> Subject: Re: New non-WG malign list : Network Service Chaining (NSC)
>=20
> How about a new non-malign WG list?
>=20
> Melinda


From hartmans@painless-security.com  Tue Jun 18 07:19:16 2013
Return-Path: <hartmans@painless-security.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 5177C21F9F12; Tue, 18 Jun 2013 07:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 QWb5-QCOOfSL; Tue, 18 Jun 2013 07:19:10 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 6240121F9EE1; Tue, 18 Jun 2013 07:19:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id BC2032013A; Tue, 18 Jun 2013 10:15:09 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bd8b3jpw8fH3; Tue, 18 Jun 2013 10:15:08 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 18 Jun 2013 10:15:08 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 525ED80046; Tue, 18 Jun 2013 10:18:50 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: "Black\, David" <david.black@emc.com>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com>
Date: Tue, 18 Jun 2013 10:18:50 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> (David Black's message of "Mon, 17 Jun 2013 22:39:28 -0400")
Message-ID: <tsl38sfbiyd.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <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: Tue, 18 Jun 2013 14:19:16 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:

    Black,> The next to last paragraph on p.3 begins with this sentence:

    Black,>    For these reasons, channel binding MUST be implemented by
    Black,> peers, EAP servers and AAA servers in environments where EAP
    Black,> authentication is used to access application layer services.

    Black,> It appear that this "MUST" requirement applies to all uses
    Black,> of EAP, including network access authentication, not just
    Black,> application layer access authentication.  If so, that's not
    Black,> immediately obvious from the text, and an additional
    Black,> sentence should be added to make this clearer.  If not, the
    Black,> above sentence needs to exclude network access
    Black,> authentication from that requirement.


I know you're correct that AAA servers and EAP servers need to implement
channel binding for network access in such environments.
I'm not sure whether peers only doing network access SHOULD implement
channel binding or MUST implement channel binding.

Practically speaking, it will be a while before peers implement channel
binding for network access.
The sorts of attacks that result without channel binding are attacks
where a peer thinks it is doing network access authentication but what
it's really doing is helping an attacker access an application.
If all the application access peers support channel binding, then you
could potentially require the eap-lower-layer attribute or similar for
application authentication and work securely in environments where peers
for network access have not been updated yet.
It's also kind of tempting to stick our head in the sand and just add
the clarification that "yes, we mean network access too."

--Sam

From rjsparks@nostrum.com  Tue Jun 18 07:21:36 2013
Return-Path: <rjsparks@nostrum.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 9E0FD21F949F; Tue, 18 Jun 2013 07:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.277
X-Spam-Level: 
X-Spam-Status: No, score=-102.277 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 PZmQ3PEWLTCW; Tue, 18 Jun 2013 07:21:34 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6C8E621F9133; Tue, 18 Jun 2013 07:21:32 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5IELLtJ024140 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Tue, 18 Jun 2013 09:21:22 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <51C06CDC.9050804@nostrum.com>
Date: Tue, 18 Jun 2013 09:21:16 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: Gen-art last call review: draft-ietf-mmusic-rfc2326bis-34
References: <51AFB3FF.7000009@nostrum.com> <51C047BC.1050207@ericsson.com>
In-Reply-To: <51C047BC.1050207@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Cc: draft-ietf-mmusic-rfc2326bis@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, mmusic@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: Tue, 18 Jun 2013 14:21:37 -0000

Hi Magnus -

Thanks for your careful treatment of these comments - I think you're on 
a good path with all the suggestions below.
Responses to questions and a few comments inline:

On 6/18/13 6:42 AM, Magnus Westerlund wrote:
> Hi Robert,
>
> Thanks for the massive review. A number of really good comments in here.
> Below you will find my answers, comments, questions and in most cases
> clarifications what I see us doing with your comment. These covers your
> major and minor comments. The nits we will simply implement as we see
> fit, if we have questions we will comeback with those.
>
> WG, there are a number of issues in here that would be greatly helped by
> your input!
>
> On 2013-06-05 23:56, Robert Sparks wrote:
>> Document: draft-ietf-mmusic-rfc2326bis-34
>> Reviewer: Robert Sparks
>> Review Date: 05-Jun-2013
>> IETF LC End Date: 04-Jun-2013
>> IESG Telechat date: not yet on a telechat
>>
>>
>> The document is very long, and the structure is unusual - much of the
>> definition of the protocol itself is in the appendices. You are missing
>> an opportunity to make this document much shorter (thereby likely
>> increasing its effectiveness). Much of the jump in from RFC2326 was
>> importing the description of headers and responses from HTTP, tailoring
>> them to RTSP. That was a good exercise in that it highlights some issues
>> that would otherwise be non-obvious (and raises a few questions below).
>> But you followed the style from HTTP perhaps too closely - much shorter
>> descriptions without examples might have done the job better. Overall,
>> separating exposition and examples from the protocol definition would
>> make it much easier for an implementer to find the definition of the
>> protocol, and use the document as a reference when diagnosing a failure
>> to interoperate.
> Agree, it would be differently structure if we wrote it from scratch
> today. But it is an document that is 10 years in the making with dual
> heritage in RFC 2326 and RFC 2068.
>
>> Major Issues
>>
>> I'm not seeing what instructs an RTSP element on how to find the server
>> it would try to open a connection to given an rtsp or rtsps URI? Are you
>> assuming it would be doing A or AAAA DNS lookups?
> Yes, using A or AAAA DNS records are assumed. No problem making that
> explicit.
>
> Should this protocol
>> use NAPTR/SRV?
> Potentially, but as everyone have been using A records for all these
> years, I think it is not worth defining it at this stage.
>
> The document should be explicit. On a related note, (and
>> maybe I missed this), but where do you talk about what an element should
>> check in the server's certificate when connecting over TLS? Are you
>> assuming a common name match? Or are you expecting some SubjectAltName
>> processing?
> This draft says in Section 19.2 the following regarding this:
>
>     RTSP MUST follow the same guidelines with
>     regards to TLS [RFC5246] usage as specified for HTTP, see [RFC2818].
>
> Where section 3.1 (Server Identity) of RFC 2818 contains the following:
>
>     If a subjectAltName extension of type dNSName is present, that MUST
>     be used as the identity. Otherwise, the (most specific) Common Name
>     field in the Subject field of the certificate MUST be used.
>
> Isn't that clear enough on that matter?
Yes - I was worried that I might have missed it before.
>
>> The document should say more about when connection reuse is appropriate,
>> particularly when the connections happened because of an rtsps uri. Two
>> different names might resolve to the same IP address - reusing a
>> connection formed when looking at the first name (and verifying the
>> server's cert) is dangerous. A new connection needs to be formed (and
>> verified) instead.
> I want to check my understanding of the issue you are seeing here. So a
> client looks ups foo.example.org, gets an ip address A and establishes
> an TCP/TLS connection and verifies that there are a SubjectAltName that
> matches foo.example.org works. Then client is going to open
> bar.example.com and looks up that address and gets the same IP address A.
> Client matches A against existing connections and simply sends a request to
> bar.example.com. Thus bypassing the certificate verification.
>
> If we clarify that in the process of opening rtsps://bar.example.com the
> client MUST verify that the server certificate for the TLS connection it
> considers re-using has an SubjectAltName of bar.example.com, does that
> resolve your concerns. If not, please explain the concern further.
You understood what I intended, and your resolution looks sufficient.
>
>
>> The text talks about the option to queue S->C requests if there isn't a
>> connection to the client available. Ostensibly, this means the request
>> can go down some future connection. It's not clear how the server can
>> tell the right client connected. In particular, when using rtsps, how do
>> you prevent a malicious client from getting such a queued message that
>> wasn't meant for him?
>
> Okay, this security issue I have totally missed but it is clearly
> serious. I don't see any easy way of fixing this. Thus I would suggest
> that we simply make it clear that a server MUST NOT queue the S->C RTSP
> message, independent if they are requests PLAY_NOTIFY and TEARDOWN or
> responses to client requests.
Works for me. Does this mean you are removing cross-connection queueing 
altogether?
>
>
>> Given that the text talks about queuing S-C requests, it should
>> explicitly call out whether a server can queue a response if the
>> connection the associated request arrived on is no longer available. I
>> think what you want to say is that such a response must not be queued,
>> and must be dropped.
> Agreed, lets mandate that they are dropped.
>
>
>> There are several places in the text that talk about using a 503
>> response with a Retry-After header to push back on traffic from an
>> element (the first is section 10.7).
>> * It's not clear what the subject of a 503 is. Is it intended to be
>> scoped to requests to the resource in the RURI of the associated
>> request? Is it intended to be scoped to the domain in that resource? Or
>> is it, like in SIP, intended to be scoped to the server issuing the
>> response, independent of what the RURI contained?
> Very good question. It is far from obvious what the best choice is. And
> I think even talking only about URI related scope may not be the best.
>
> The case I have in mind is if a proxy that has several already
> established RTSP sessions over a persistent connection. When a client
> connected to the proxy requests to establish a new session the server
> may have insufficient resource to handle the SETUP request and send a
> 503 answer. However if another client already having an RTSP session for
> the same resource want to terminate that session it would be strange to
> refuse to process the message as it will actually free up resources.
>
> This makes me believe that you need to have a RTSP Session scope for any
> request carrying a Session-ID and a general server, or host name scope
> for non-associated that doesn't prevent established sessions to try.
>
> Thoughts on this?
That seems like it might work - exploring the idea should get some
WG cycles.
>
>
>> * If the intent is that the 503 talks about the server, then you should
>> clarify that a proxy doesn't simply forward 503 responses (after
>> rewriting CSeqs), and should probably have a response of its own.
>> Otherwise, clients that might be talking to two different servers
>> through one proxy would lose access to both of them when one of the
>> servers 503ed.
> If we us a host and session scope then this issue would not be present.
> However, if the proxy is actually overloaded that still needs its own
> 552 Proxy Unavailable response with the same scope rules as for the 503,
> but where unassociated requests concerns sending to the proxy at all.
If you build one of these, please be sure to highlight the impact of the
other sessions already established, and call out the potential for
problems if you forward one as a Proxy, as opposed to generating your
own based on the situation.
>
>> Section 4.9.1 lists values the Seek-Style header can take, but 18.45
>> lists a completely different set (which most of the rest of the document
>> uses). Should 4.9.1 be changed to use the values in 18.45? Are the right
>> strings being used in sections 13.4.4 through 13.4.6? Those appear to be
>> using strings from 4.9.1.
> Yes, clearly an inconsistency issue that needs to be resolved.
>
>> The document will not stand if you delete some of the appendices. They
>> aren't supplementary material. Please consider restructuring the
>> normative sections back into the main document, or clearly identifying
>> which ones define protocol and which are background information.
> I would like to characterize this differently. I think you will have a
> working protocol of RTSP, but you can't use it for anything. This as you
> will have no media transport (C), no media description protocol (D), and
> no parameters format (F). But, these appendixes are replaceable with
> other protocol solutions.
>
> The Introduction section (1) says:
>
>                                   The appendixes describe and define some
>     functionalities that are not part of the core RTSP specification, but
>     which are still important to enable some usages.  Among them, the RTP
>     usage is defined in Appendix C and the SDP usage with RTSP is defined
>     in Appendix D, which are two mandatory appendixes.
>
> I note that we should add F to this list.
>
> I think we should be clear in each of this appendices that if one
> support Foo for the purpose of bar then this appendix defines
> normatively how one does it.
Makes my head swim, but maybe it's must me.

fwiw - I'm still worried that there are information in Appendix B that's 
not captured in the main text, but I can't find easy things to point to. 
Elwyn seems more comfortable that everything is covered.
>
>
>> Section 15 talks about a "transparent' proxy, but there is no
>> description in this document of what protocol such a thing should
>> follow. What bad thing happens if you remove all mention of
>> "transparent" proxies from the document? As far as I can tell, that
>> won't affect the protocol definition at all.
> Not really, there is no definition of transparent proxies currently.
> There is one security concern that make require some word smithing if we
> remove transparent proxies.
>
> >From my perspective a transparent proxy is something that hijacks a TCP
> connection towards an RTSP server to be a proxy between client and
> server. Further is not detectable from the client's or the servers
> perspective, but still may modify RTSP messages within the bounds of the
> RTSP protocol.
>
> But, in reality as we have proxies that are visible we should focus on
> those and forget this bastard version.
>
>> The list of steps for establishing an SRTP cryptographic context in
>> C.1.4.1 says "This specification does not specify an explicit method for
>> indicating this SRTP cryptographic context establishment method, but
>> future specifications may." in the context of looking at the SDP. SDP
>> _has_ methods of indicating what keying mechanism is used with SRTP -
>> are you talking about something different?
> I think you are considering the methods for keying SRTP that are
> Offer/Answer dependent. The only RTSP SDP using method that exist is the
> one defined in RFC 4567, which we are explicit on not using.
>
> Why doesn't this section say
>> something like "the use of SRTP with RTSP is only defined with MIKEY
>> with keys established as defined in this section. Future documents may
>> talk about how an RTSP implementation might treat SDP that indicates
>> some other key mechanism be used"?
> Yes, that is appears better, but we will have to make it clear that is
> is regarding RTSP 2.0. Must also think if RFC 4567 needs to be worked
> into that sentence.
>
> Could you provide an example in the
>> document of an RTSP message carrying SDP reflecting the use of SRTP as
>> defined in this document?
> The point is that the only difference is that he RTP profile is SAVP/RTP
> or SAVPF/RTP in the SDP. Thus making such an SDP isn't difficult.
> Question is if it provides a benefit?
I think it would be worth the extra space it would take up.
>
>
>
>> Minor Issues
>>
>> The document uses the notion of a "control connection" (it appears first
>> in section 2.5) without defining what that is, or what kind of
>> connections you might have that aren't control connections.
> The "control connection" is the connection established for sending RTSP
> messages on it. I agree it is undefined and could likely be replaced by
> the "RTSP connection" or "connection for RTSP messages"
>
>> The update to the registration of the rtsp and rtsps schema call out
>> that there are changes that can result in interoperability issues. It
>> doesn't say what the issues are, or who might encounter them. I can
>> infer that the point is that there might be problems if a URI following
>> this updated registration were to be processed by an RTSP 1.0
>> implementation (or any other application that relied on the previous
>> definition). It would be better to say that explicitly, and talk about
>> how a previous implementation is likely to act when presented with a URI
>> that exercised these new changes.
> I have gotten these comment elsewhere and have prepared a text update
> for section 4.2:
>
>     The details of the syntax of "rtsp" and "rtsps" URIs has been changed
>     from RTSP 1.0.  These changes are:
>
>     o  Support for IPV6 literal in host part and future IP literals
>        through RFC 3986 defined mechanism.
>
>     o  A new relative format to use in the RTSP protocol elements that is
>        not required to start with "/".
>
>     Neither should have any significant impact on interoperability.  If
>     one is required to use IPv6 literals to reach an RTSP server, then
>     that RTSP server must be IPv6 capable, and RTSP 1.0 is not a fully
>     IPv6 capable protocol.  If an RTSP 1.0 client attempts to process the
>     URI it will not match the allowed syntax and be considered invalid
>     and processing will be stopped.  This is clearly a failure to reach
>     the resource, however it is not a signification issue as RTSP 2.0
>     support was needed anyway in both server and client.  Thus failure
>     will only occur in a later step when there is a RTSP version
>     mismatch between client and server.  The second change will only
>     occur in RTSP messages, that are explicitly identified as being RTSP
>     2.0 messages, thus a RTSP 1.0 only agent will not be required to
>     parse this variant.
>
> Clear enough?
Maybe. In the last sentence, are you saying you would never see a relative
URL in a request URI? If you're not already saying that explicitly in 
the document
(you might be) please consider doing so. Saying it that way in this text 
would
also help.
>
> The above is Edited In.
>
>   (It's not clear to me that all of the
>> thread at www.ietf.org—msg01567.html
>> <http://www.ietf.org/mail-archive/web/uri-review/current/msg01567.html>
>> concluded - I see how the fragments question ended, but what about
>> things like the addition of IPV6 literals? In particular, I'm not
>> finding a response where Ted Hardie agreed that the potential for
>> interoperability failure had been adequately addressed).
> I talked to him in person about this just after the discussion to better
> understand his comments. If we want a confirmation I think we need to
> loop him into a discussion regarding this particular issue.
I suggest the shepherd/AD double-check with him if he doesn't jump into 
this thread before.
>
> I provided a clarification to the designated URI reviewer which accepted
> the request.
>
>>
>> I think you've said something different than you mean in 5.4 item 1. I
>> think you mean to say that an RTSP implementation would ignore any body
>> that happened to come in message that MUST NOT contain one. What you've
>> said is that the part of the parser that's doing framing has to stop
>> framing at the end of the headers, and that such an errant body would be
>> parsed as a separate message. As written this would keep someone from
>> using an Internet Message Format parser since it would have to ignore
>> any Content-Length that might have appeared, even though it wasn't
>> supposed to.
> Yes, it is clearly sufficient to ignore the body, and likely much better
> from an error handling consideration.
>
> We will propose a text change.
>
>
>> In section 10.4, it looks like a server can keep an RTSP transaction
>> pending forever if it sends 100 responses often enough. I assume the
>> client's recourse if it doesn't want to remain involved is to close the
>> connection. If that's right, it's worth calling it out explicitly in
>> this section.
> This is likely a good suggestion, and works fine if the client simply
> wants to abort the request and is anyway abandoning the RTSP session.
> However, the question is what to do if just the request becomes
> irrelevant and instead want to do something else with the RTSP session.
> A single client may abandon the connection, open a new one and issue a
> request, to a potentially undetermined session state. Yet another
> complexity is what a proxy does that has multiple RTSP sessions on the
> same server. Here the rules for processing in order the different
> requests and their relation to answers in the same order.
>
> This makes me want to weaken the recommendation on re-using an
> connection for multiple RTSP sessions.
Are there also considerations here wrt pipelining?
>
>
>> Somewhere, probably in section 15.2, you should be explicit that a proxy
>> that is multiplexing requests MUST keep the requests in the same order
>> as they are folded together. You can infer that, or things simply break,
>> but saying it explicitly would be better.
> Probably, as a clarification to what is already present in section 18.19
> (CSeq header)
>
>     Proxies that aggregate several sessions on the same transport will
>     have to ensure that the requests sent towards a particular server
>     have a joint sequence number space, i.e., they will regularly need to
>     renumber the CSeq header field in requests (from proxy to server) and
>     responses (from server to proxy) to fulfill the rules for the header.
>     The proxy MUST increase the CSeq by one for each request it
>     transmits, without regard of different sessions.
>
>
>> Both GET_PARAMETER and SET_PARAMETER are listed as keep-alive methods in
>> 10.5, but the note in section 13 on table 7 only uses that as a reason
>> for requiring SET_PARAMETER. Why doesn't it also apply to GET_PARAMETER?
>> And why is this only required at servers? "Required" in this section
>> means Mandatory to Implement, I think. If that's right, it should be
>> made explicit. If that's not right, what does it mean?
> Yes, required is Required to implement in the server. The GET_PARAMETER
> is not required as only one method for keep-alive is necessary. Thus,
> the ones that needs to use GET/SET_PARAMETER for keep-alive will have to
> choose SET_PARAMETER.
>
> It is only required at the server, as it is in the client implementation
> choice of how to ensure keep-alive works. As this is also dependent on
> the media transport support one has, the client may not need a method
> based keep-alive.
>
> Clarifying "Required" should be straightforward.
>
>> Section 13.8 makes a good argument for always putting parameters to be
>> retrieved in a body. Why are you keeping the complexity of also allowing
>> them in headers?
> Some arguments are probably lost in the passage of time. However, the
> headers specified to be suitable for inclusion in a GET_PARAMETER
> requests are used for providing these information also in other methods,
> thus we have not wanted to duplicate the representation of this
> information in both a body and a header form.
>
>> Section 13.10: "That should not provide any benefit." is not clear - can
>> you expand it a little?
>     If the REDIRECT request times out following the rules in Section 10.4
>     the server MAY terminate the session or transport connection that
>     would be redirected by the request.  This is a safeguard against
>     misbehaving clients that refuse to respond to a REDIRECT request.
>     That should not provide any benefit.
>
> The intention here is to make clear that there shouldn't be an incentive
> in the protocol to not acknowledge a REDIRECT request and instead simply
> go on as it wasn't received or seen. Thus, we want to make clear that
> the server may simply terminate the session in those cases.
>
> I propose we change this sentence to:
>
> Thus, removing any incentive to not acknowledge the reception of a
> REDIRECT request.
>
> Edited In
>
>> In Section 13.10 you talk about clients _sending_ media (search for
>> "send or receive media"). Do you mean anything more than possibly RTCP?
>> Can you make that clear in the section?
> You mean this sentence:
>
>     After a REDIRECT request has been processed, a client that wants to
>     continue to send or receive media for the resource identified by the
>     Request-URI will have to establish a new session with the designated
>     host.
>
> The mentioning of send media is likely a RECORD reference. In this case
> I don't see any issue with removing it.
>
> Edited In
>
>> Section 15.2's second paragraph appears to be the only place the proxy
>> rewriting of CSeq in order to multiplex requests is defined, and it is
>> very loose. It would be easy for a reader to fail to recognize this as
>> an interoperability requirement. Please consider expanding how this is
>> specified when addressing the comment about above about keeping requests
>> in relative order when multiplexing.
> There are text in Section 18.19 CSeq also. But I do think I agree that
> this should be clarified.
>
>> You follow the principle of saying a client should treat a response with
>> an unknown response code, the same as it would treat the x00 of that
>> class (e.g. 400 for an unknown 4xx). However, you do not define what a
>> response code of 300 means. How is a client supposed to handle an
>> unknown 3xx response?
> Sorry, I don't quite get this comment. Section 17.3 says:
>
>     If a 3rr response is received for a request in relation to
>     an established session, the client SHOULD send a TEARDOWN request for
>     the session, and MAY reestablish the session using the resource
>     indicated by the Location.
>
>     If the Location header is used in a response it MUST contain an
>     absolute URI pointing out the media resource the client is redirected
>     to, the URI MUST NOT only contain the host name.
>
> As explained above unknown 3XX codes will be 3rr codes, as 304 isn't
> unknown.
>
> If you don't believe this is sufficient can you please be more explicit
> about the issue?
Sure. It might be quickest if you look at the table of contents.
Note that you define 100 in 17.1.1, 200 in 17.2.1, 400 in 17.4.1, 500 in 
17.5.1, but you do not define 300 anywhere - you jump straight to 301.
Please add a section defining it, or declaring that you will never see a 
literal 300 on the wire, but if you did you would do (what you quote 
above) and nothing else.

>
>> As written, a client and server can use HTTP Basic authentication over
>> TCP that is not protected with TLS. Consider restricting it's use to TLS
>> only. Are you sure you don't need to say anything RTSP specific about
>> DIGEST computations (I don't think you need to go as far as SIP did
>> talking about DIGEST, but I'm surprised you haven't run into issues
>> relying only on 2617 literally.
> Are you referring to Section 19.1 here?
Yes
>
> Yes, I would not have any issue with requiring Basic to be combined with
> TLS. I think that is appropriate.
>
> When it comes to DIGEST, are you referring to section 22.4 in RFC 3261?
Yes
>
> That section indicates that some clarifications are likely needed.
>
>>
>> How does 411 Length Required for this protocol make sense? Given that
>> you've restricted the protocol to TCP and require the Content-Length
>> header to be present if there is a body, in what circumstance would a
>> server need to send a 411?
> It really should occur for malformed messages, which we could use 400 as
> response. So yes, 411 could be removed.
>
>>
>> Section 18.19 requires senders to increment CSeq by 1. We have a
>> reliable transport with no request retransmission, so there should never
>> be gaps at the receiver. Should the receiver check and react some way if
>> there are gaps? I think you should explicitly tell them not to even
>> look. If you agree, why is incrementing by one important as long as you
>> are always strictly increasing?
> I agree that for TCP or other reliable transports the receiver
> SHOULD/SHALL ignore gaps. For any future specification of an unreliable
> transport of RTSP messages this would be needed. As noted in Appendix G,
> CSeq is retained for future support of unreliable transport.
>
>> You call out several places where RTCP is essential to allow RTSP using
>> RTP to work correctly, yet section C.1.2 sets up conditions where RTCP
>> MUST NOT be sent. Why are you allowing those instead of treating the
>> conditions you describe as errors?
> Good question. I think it is a case we must ensure that you can
> negotiate and configure your desired way, without really considering if
> it should be allowed at all. I think mandating usage of RTCP with RTP
> for RTSP 2.0 would be good. But, I think that needs to be verified with
> the WG.
Ack
>
> cheers
>
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>


From john-ietf@jck.com  Tue Jun 18 07:31:03 2013
Return-Path: <john-ietf@jck.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 DC22321F9452 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 07:31:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.424
X-Spam-Level: 
X-Spam-Status: No, score=-102.424 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 s2IScVXrhs+o for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 07:30:58 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5176921F92B8 for <ietf@ietf.org>; Tue, 18 Jun 2013 07:30:42 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UowvX-000NoQ-VH; Tue, 18 Jun 2013 10:30:32 -0400
Date: Tue, 18 Jun 2013 10:30:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: Steve Crocker <Steve@shinkuro.com>, Olivier MJ Crepin-Leblond <ocl@gih.com>
Subject: Re: IETF,	ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt>	(The Internet Numbers Registry System) to Informational RFC)
Message-ID: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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: Tue, 18 Jun 2013 14:31:04 -0000

--On Tuesday, May 21, 2013 09:42 +0100 Steve Crocker
<Steve@shinkuro.com> wrote:

> Like the IETF, ICANN is also an open organization.  ICANN
> meetings are free, and a veritable ocean of documents are
> published regularly, many in multiple languages to increase
> availability.
> 
> ICANN is purposefully organized to include participation from
> a range of communities, e.g. business, civil society,
> governments, and the technical community. 
>...
> The roster of topics active within ICANN at any given time is
> fully documented and publicized, and I invite anyone who is
> interested to participate.  We listen to everyone, and we
> publish tentative results, tentative policies, etc. for
> everyone to critique.


--On Tuesday, May 21, 2013 12:25 +0200 Olivier MJ Crepin-Leblond
<ocl@gih.com> wrote:

> Quite frankly, I used to have the same feeling... until very
> recently. With Steve at the wheel, things have improved a lot.
>...
> Today, it's still not
> perfect, but you cannot fix a bus by shooting it - work on it
> instead, to fix it. I believe it's fixable.

Steve and Olivier,

As I think you both know, I've made personal decisions to avoid
saying what I'm about to say in places as public as the IETF
list and have been largely successful in that for the last
decade.  I've been deliberating about the balance of advantages
and disadvantages of responding to your notes; hence the delay
in doing so.  I've worked happily and successfully with both of
you on various Internet issues and have no doubts about either
your integrity or your commitment to a better Internet, with the
latter more or less the way the IETF would understand.  That
shared background and assumptions combined with your very
optimistic postings seem to call for comment.

Olivier, certainly there has been change at ICANN over the last
several years.  You comment implies to me that you think things
are monotonically improving; I don't believe that although I do
believe that, if one starts from selected examples and times,
huge improvements are easy to document.   I'll address the issue
of public input and what happens to it below.

As a fairly trivial example, while issues are publicized (as
Steve notes), they are publicized on a web site that seems much
harder to find anything on, unless one is spending enough time
working on ICANN issues for it to feel familiar with its
organization, than it was a few years ago.  I recommend trying
the experiment of pretending you don't know the site and then
trying to get quickly to information on the status, open issues,
and decisions already made about any particular substantive
issue in which you might be interested.

Steve, participation in ICANN is certainly not free, any more
than participation in the IETF is free.  ICANN doesn't charge a
meeting registration fee, but its meetings tend to be in more
exotic places that are more costly to get to and/or stay at than
IETF's choices (and some of us still whine about the IETF ones,
especially when IAOC considers "mid $200 range" to be acceptable
for hotels and when the combination of the IETF meeting
schedule, associated meetings, and plane connections can easily
require a six or seven day stay).  

My not entirely subjective impression is that participating in
ICANN, f2f, is considerably more expensive in an average year
than it is for IETF.   More important, while I think the IETF's
remote participation mechanisms could still use a lot of
improvement, they do tend to work and our "decisions on mailing
lists" rules and provisions for very public appeals and
responses provide a lot of protection when they don't work.  By
contrast, ICANN's remote participation mechanisms for meetings
often don't work (probably an unfortunate side-effect of some of
the places ICANN chooses to meet) and a very large fraction of
the key decision-making meetings and discussions don't even
pretend to be publicly or remotely accessible.  

But the more important issue, at least from my perspective, is
that two things keep reappearing and have either gotten worse or
remained the same in recent years.  They are:

(1) While ICANN accepts input from anyone who is interested,
there is very little evidence that any of that input has any
influence on results unless it comes from a well-established
constituency group.   There is little evidence that either the
Board or Staff actually consider any of the public input and
considerable evidence (from examination of proposals before and
after the public review) that they do not.  It is also possible
that they consider all such comments and justifiably conclude
that all of them are completely bogus or uninformed, but I just
can't believe that.  That might be less of an issue were those
established constituency groups really representative of the
Internet community but, especially in the domain name space, the
influential groups seems to be entirely those with a vested
interest in the marketing and sales of domain names.  Even in
the address space, there is little evidence that anyone but the
NRO/RIRs and their associated entities can really be heard at a
level that has an influence on policy.  I'm sure they consider
their processes adequate to reflect all legitimate input and
therefore that the closed circle of influence is a good thing;
perhaps they are right. Consequently, what "bottom up" seems to
mean in the ICANN environment is that only ICANN-recognized and
established presumptive representatives of the "bottom" have any
voice in the system with "that proposal or objection didn't
arrive via the bottom up process" sometimes being used as an
excuse to ignore input.

(2) The established mechanism for dealing with a moderately
contentious issue is to appoint a committee of volunteers to
study it.  The mechanism for even more contentious or complex
issues is to appoint many committees either serially or in
parallel.  Those committees typically produce reports that tend
to run into the hundreds of pages.  I don't know whether that is
because they don't have time to write shorter reports or because
they don't think the subject matter can be covered in more
concise reports, but the pattern is clear,   When those
committees cannot agree or discover the the issues are, in fact,
contentious, they typically recommend the creation of more
committees.  

Those committees are time-consuming enough that their design has
another effect: only those with a very strong commitment to the
work and resources to back that commitment up can participate in
practice.   Those people usually turn out to be those with a
vested interest in particular results, interests that are
dominated by those with an organizational interest in buying and
selling names.  Others who might be willing to invest personal
resources to participate in the best interests of the Internet
are typically driven out of active participation in the process,
if not initially than by the sequence and multitude of
committees and inability to even figure out where the leverage
points lie, much less participate everywhere that is necessary.

The many, many years in which one "whois" or "registry database"
committee followed another, each one addressing somewhat
overlapping aspects of the issues, but with no ability to get
any of them to address IDN or "multilingual" registrations in a
serious way (at least until very recently) is symptomatic of the
problem but I believe only one example among many.  In the
meantime, staff (I believe trying sincerely to fill the vacuum)
charges ahead with their own approaches.  Those approaches end
up either binding ICANN without even a sign of a legitimate
policy development process or, because they don't have community
support, going nowhere after considerable resources have been
wasted.

The result of the many committees is collections of long and
complex reports that often avoid asking, much less answering,
actual critical questions.  Because of the length, number, and
complexity of the reports almost no one actually reads them,
much less gets a complete picture of the systems and issues
involved.  Staff apparently sees their mandate in organizing,
overseeing, and presenting the resulting studies as "how do we
make this work and minimize the risks".  A result is that one of
the questions that rarely or never gets asked, especially if
there is a loud or well-resourced constituency for some action,
is whether the action is a good idea for the Internet at all
rather than how to do it and mitigate the damage.

The Board doesn't seem to be inclined and able to fix any of
this.  I don't know whether that is because too much of its
composition is the wrong people with the wrong knowledge and
skills, it isn't getting adequate information or an adequate and
comprehensive understanding of the issues about which it is
supposedly setting directions and policies, because it has come
to care more about ICANN's success (however measured) than that
of the Internet, of for other reasons.  However, the result
seems to be that the same patterns keep repeating themselves
years after year with little real change.

I'm not at all sure how to fix these problems, at least without
a reorganization of ICANN that is at least as significant as the
2.0 one.  But I'm fairly sure that the sort of complacency that
I interpret from the notes partially quoted above is an
impediment to even serious thinking about the issues.

I hope there is some way to do better in the future.

best regards,
    john


From christopher.morrow@gmail.com  Tue Jun 18 08:57:37 2013
Return-Path: <christopher.morrow@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 C060B21F9B29 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 08:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.1
X-Spam-Level: 
X-Spam-Status: No, score=-103.1 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 SAG2EtO1iaIt for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 08:57:30 -0700 (PDT)
Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176]) by ietfa.amsl.com (Postfix) with ESMTP id 1C98D21F9B2D for <ietf@ietf.org>; Tue, 18 Jun 2013 08:57:29 -0700 (PDT)
Received: by mail-lb0-f176.google.com with SMTP id z5so3704268lbh.21 for <ietf@ietf.org>; Tue, 18 Jun 2013 08:57:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=szi9nEK+bFCL3+rOA+MueuhoIoPOxOCtLvwkFMHaoZw=; b=rcwEm9YNTu4rUbCIx+D9rHntCxaKkHXM+NGSuHXLhZKNOY/FLzNvs4J4ayVw/lbH+S 6CfV48JFfY+8lbrZ6JIF8VuuNgTsIEPExz21C2q+9m1L0MP26EKhPckZqCTl8GcniCdq pMBj8rofQWLh8Dk+vHitQO45uxwvxRrqwf0JDpmH0uUJS84vvQUP+oAeGuaIrMTopONo kCG3S9iCzHSs8/JLJc8tr6YfVM0t47dGK7saJpG0nGOY+BalhjbU2wWzDYPbNpgvnTlw lPwmyMwqooMPg56VXjYNVgAY+8TjgLFp5N1eTab4TLzg77LMglmj/IWzrXipdX4k26O0 VT5A==
MIME-Version: 1.0
X-Received: by 10.152.27.40 with SMTP id q8mr9397222lag.75.1371571048853; Tue, 18 Jun 2013 08:57:28 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.152.22.196 with HTTP; Tue, 18 Jun 2013 08:57:28 -0700 (PDT)
In-Reply-To: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com>
Date: Tue, 18 Jun 2013 11:57:28 -0400
X-Google-Sender-Auth: RTJyjtj-nEWGEYb6-trBfz8V4UY
Message-ID: <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: Christopher Morrow <morrowc.lists@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
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: Tue, 18 Jun 2013 15:57:37 -0000

Did this LC end?
or stated differently: "What's the status of this draft LC?"

I'm not such a fan of the draft, mostly because it appears to remove
some principles that some RIR folk hold up in their policy discussions
as important... while not having a backstop in said policies to
replace the originals from 2050.

That can be fixed though... provided those communities see fit to keep
the principles in place. Mostly then my 'not such a fan' is a timing
problem I suppose, which is what prompted this LC query.

-chris


On Tue, Jun 18, 2013 at 10:30 AM, John C Klensin <john-ietf@jck.com> wrote:
>
>
> --On Tuesday, May 21, 2013 09:42 +0100 Steve Crocker
> <Steve@shinkuro.com> wrote:
>
>> Like the IETF, ICANN is also an open organization.  ICANN
>> meetings are free, and a veritable ocean of documents are
>> published regularly, many in multiple languages to increase
>> availability.
>>
>> ICANN is purposefully organized to include participation from
>> a range of communities, e.g. business, civil society,
>> governments, and the technical community.
>>...
>> The roster of topics active within ICANN at any given time is
>> fully documented and publicized, and I invite anyone who is
>> interested to participate.  We listen to everyone, and we
>> publish tentative results, tentative policies, etc. for
>> everyone to critique.
>
>
> --On Tuesday, May 21, 2013 12:25 +0200 Olivier MJ Crepin-Leblond
> <ocl@gih.com> wrote:
>
>> Quite frankly, I used to have the same feeling... until very
>> recently. With Steve at the wheel, things have improved a lot.
>>...
>> Today, it's still not
>> perfect, but you cannot fix a bus by shooting it - work on it
>> instead, to fix it. I believe it's fixable.
>
> Steve and Olivier,
>
> As I think you both know, I've made personal decisions to avoid
> saying what I'm about to say in places as public as the IETF
> list and have been largely successful in that for the last
> decade.  I've been deliberating about the balance of advantages
> and disadvantages of responding to your notes; hence the delay
> in doing so.  I've worked happily and successfully with both of
> you on various Internet issues and have no doubts about either
> your integrity or your commitment to a better Internet, with the
> latter more or less the way the IETF would understand.  That
> shared background and assumptions combined with your very
> optimistic postings seem to call for comment.
>
> Olivier, certainly there has been change at ICANN over the last
> several years.  You comment implies to me that you think things
> are monotonically improving; I don't believe that although I do
> believe that, if one starts from selected examples and times,
> huge improvements are easy to document.   I'll address the issue
> of public input and what happens to it below.
>
> As a fairly trivial example, while issues are publicized (as
> Steve notes), they are publicized on a web site that seems much
> harder to find anything on, unless one is spending enough time
> working on ICANN issues for it to feel familiar with its
> organization, than it was a few years ago.  I recommend trying
> the experiment of pretending you don't know the site and then
> trying to get quickly to information on the status, open issues,
> and decisions already made about any particular substantive
> issue in which you might be interested.
>
> Steve, participation in ICANN is certainly not free, any more
> than participation in the IETF is free.  ICANN doesn't charge a
> meeting registration fee, but its meetings tend to be in more
> exotic places that are more costly to get to and/or stay at than
> IETF's choices (and some of us still whine about the IETF ones,
> especially when IAOC considers "mid $200 range" to be acceptable
> for hotels and when the combination of the IETF meeting
> schedule, associated meetings, and plane connections can easily
> require a six or seven day stay).
>
> My not entirely subjective impression is that participating in
> ICANN, f2f, is considerably more expensive in an average year
> than it is for IETF.   More important, while I think the IETF's
> remote participation mechanisms could still use a lot of
> improvement, they do tend to work and our "decisions on mailing
> lists" rules and provisions for very public appeals and
> responses provide a lot of protection when they don't work.  By
> contrast, ICANN's remote participation mechanisms for meetings
> often don't work (probably an unfortunate side-effect of some of
> the places ICANN chooses to meet) and a very large fraction of
> the key decision-making meetings and discussions don't even
> pretend to be publicly or remotely accessible.
>
> But the more important issue, at least from my perspective, is
> that two things keep reappearing and have either gotten worse or
> remained the same in recent years.  They are:
>
> (1) While ICANN accepts input from anyone who is interested,
> there is very little evidence that any of that input has any
> influence on results unless it comes from a well-established
> constituency group.   There is little evidence that either the
> Board or Staff actually consider any of the public input and
> considerable evidence (from examination of proposals before and
> after the public review) that they do not.  It is also possible
> that they consider all such comments and justifiably conclude
> that all of them are completely bogus or uninformed, but I just
> can't believe that.  That might be less of an issue were those
> established constituency groups really representative of the
> Internet community but, especially in the domain name space, the
> influential groups seems to be entirely those with a vested
> interest in the marketing and sales of domain names.  Even in
> the address space, there is little evidence that anyone but the
> NRO/RIRs and their associated entities can really be heard at a
> level that has an influence on policy.  I'm sure they consider
> their processes adequate to reflect all legitimate input and
> therefore that the closed circle of influence is a good thing;
> perhaps they are right. Consequently, what "bottom up" seems to
> mean in the ICANN environment is that only ICANN-recognized and
> established presumptive representatives of the "bottom" have any
> voice in the system with "that proposal or objection didn't
> arrive via the bottom up process" sometimes being used as an
> excuse to ignore input.
>
> (2) The established mechanism for dealing with a moderately
> contentious issue is to appoint a committee of volunteers to
> study it.  The mechanism for even more contentious or complex
> issues is to appoint many committees either serially or in
> parallel.  Those committees typically produce reports that tend
> to run into the hundreds of pages.  I don't know whether that is
> because they don't have time to write shorter reports or because
> they don't think the subject matter can be covered in more
> concise reports, but the pattern is clear,   When those
> committees cannot agree or discover the the issues are, in fact,
> contentious, they typically recommend the creation of more
> committees.
>
> Those committees are time-consuming enough that their design has
> another effect: only those with a very strong commitment to the
> work and resources to back that commitment up can participate in
> practice.   Those people usually turn out to be those with a
> vested interest in particular results, interests that are
> dominated by those with an organizational interest in buying and
> selling names.  Others who might be willing to invest personal
> resources to participate in the best interests of the Internet
> are typically driven out of active participation in the process,
> if not initially than by the sequence and multitude of
> committees and inability to even figure out where the leverage
> points lie, much less participate everywhere that is necessary.
>
> The many, many years in which one "whois" or "registry database"
> committee followed another, each one addressing somewhat
> overlapping aspects of the issues, but with no ability to get
> any of them to address IDN or "multilingual" registrations in a
> serious way (at least until very recently) is symptomatic of the
> problem but I believe only one example among many.  In the
> meantime, staff (I believe trying sincerely to fill the vacuum)
> charges ahead with their own approaches.  Those approaches end
> up either binding ICANN without even a sign of a legitimate
> policy development process or, because they don't have community
> support, going nowhere after considerable resources have been
> wasted.
>
> The result of the many committees is collections of long and
> complex reports that often avoid asking, much less answering,
> actual critical questions.  Because of the length, number, and
> complexity of the reports almost no one actually reads them,
> much less gets a complete picture of the systems and issues
> involved.  Staff apparently sees their mandate in organizing,
> overseeing, and presenting the resulting studies as "how do we
> make this work and minimize the risks".  A result is that one of
> the questions that rarely or never gets asked, especially if
> there is a loud or well-resourced constituency for some action,
> is whether the action is a good idea for the Internet at all
> rather than how to do it and mitigate the damage.
>
> The Board doesn't seem to be inclined and able to fix any of
> this.  I don't know whether that is because too much of its
> composition is the wrong people with the wrong knowledge and
> skills, it isn't getting adequate information or an adequate and
> comprehensive understanding of the issues about which it is
> supposedly setting directions and policies, because it has come
> to care more about ICANN's success (however measured) than that
> of the Internet, of for other reasons.  However, the result
> seems to be that the same patterns keep repeating themselves
> years after year with little real change.
>
> I'm not at all sure how to fix these problems, at least without
> a reorganization of ICANN that is at least as significant as the
> 2.0 one.  But I'm fairly sure that the sort of complacency that
> I interpret from the notes partially quoted above is an
> impediment to even serious thinking about the issues.
>
> I hope there is some way to do better in the future.
>
> best regards,
>     john
>

From david.black@emc.com  Mon Jun 17 19:39:51 2013
Return-Path: <david.black@emc.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 B425F21F9CA1; Mon, 17 Jun 2013 19:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 OD3-PUlgH65b; Mon, 17 Jun 2013 19:39:47 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D7E8B21F9C57; Mon, 17 Jun 2013 19:39:46 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5I2djDB011711 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Jun 2013 22:39:45 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 17 Jun 2013 22:39:31 -0400
Received: from mxhub32.corp.emc.com (mxhub32.corp.emc.com [128.222.70.172]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5I2dUJF026235; Mon, 17 Jun 2013 22:39:31 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub32.corp.emc.com ([128.222.70.172]) with mapi; Mon, 17 Jun 2013 22:39:30 -0400
From: "Black, David" <david.black@emc.com>
To: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, "jsalowey@cisco.com" <jsalowey@cisco.com>, General Area Review Team <gen-art@ietf.org>
Date: Mon, 17 Jun 2013 22:39:28 -0400
Subject: Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Topic: Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcg==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 18 Jun 2013 09:14:54 -0700
Cc: "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>
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: Tue, 18 Jun 2013 02:39:51 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-abfab-eapapplicability-03
Reviewer: David L. Black
Review Date: June 17, 2003
IETF LC End Date: June 17, 2003

Summary:
This draft is on the right track but has open issues, described in the revi=
ew.

This draft updates the applicability statement for EAP to include usage
for application layer access via EAP over GSSAPI.  Additional security
requirements are introduced for environments in which EAP is used for
that purpose.

I found one open issue, which is minor, and may be editorial

Major issues: None

Minor issues: One

The next to last paragraph on p.3 begins with this sentence:

   For these reasons, channel binding MUST be implemented by peers, EAP
   servers and AAA servers in environments where EAP authentication is
   used to access application layer services.

It appear that this "MUST" requirement applies to all uses of EAP,
including network access authentication, not just application layer access
authentication.  If so, that's not immediately obvious from the text, and
an additional sentence should be added to make this clearer.  If not,
the above sentence needs to exclude network access authentication from
that requirement.

Nits/editorial comments:

The same paragraph (p.3) continues with:

   In addition, channel
   binding MUST default to being required by peers for non-network
   authentication.  If the EAP server is aware that authentication is
   for something other than a network service, it too MUST default to
   requiring channel binding.

What is meant by "non-network authentication" and "other than a network
service"?  If those mean "other than for network access authentication"
as the term "network access authentication" is used in section 1 and
RFC 3748, that meaning should be clarified.

idnits 2.12.17 generated this comment:

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
     have content which was first submitted before 10 November 2008.  If yo=
u
     have contacted all the original authors and they are all willing to gr=
ant
     the BCP78 rights to the IETF Trust, then this is fine, and you can ign=
ore
     this comment.  If not, you may need to add the pre-RFC5378 disclaimer.=
=20
     (See the Legal Provisions document at
     http://trustee.ietf.org/license-info for more information.)

idnits appears to be confused ;-).  The -00 version of this draft is from 2=
012,
and this draft does not contain sufficient material from RFC 3748 that woul=
d
raise that concern, so this comment should be ok to ignore.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From david.black@emc.com  Tue Jun 18 07:43:47 2013
Return-Path: <david.black@emc.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 3AF5911E80DF; Tue, 18 Jun 2013 07:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 AOw19EIogZJb; Tue, 18 Jun 2013 07:43:42 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 427E321E8053; Tue, 18 Jun 2013 07:43:38 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IEhaPN032387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jun 2013 10:43:37 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 18 Jun 2013 10:43:06 -0400
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IEh5dK006895; Tue, 18 Jun 2013 10:43:05 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub26.corp.emc.com ([10.254.110.182]) with mapi; Tue, 18 Jun 2013 10:43:05 -0400
From: "Black, David" <david.black@emc.com>
To: Sam Hartman <hartmans@painless-security.com>
Date: Tue, 18 Jun 2013 10:43:03 -0400
Subject: RE: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5sLtL2MQaEvFULRLupG53n6IyQQgAAT1zw
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129826522D@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu>
In-Reply-To: <tsl38sfbiyd.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 18 Jun 2013 09:14:54 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <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: Tue, 18 Jun 2013 14:43:47 -0000

Sam,

I was concerned that something along these lines was lurking in here :-(.

I think this is the crucial "running code" consideration to start from:

> Practically speaking, it will be a while before peers implement channel
> binding for network access.

Assuming that network access does not use channel binding, how does one
avoid the proxy attack on network access authentication via application
access authentication when the latter is introduced?

For environments where EAP is used for network access authentication,
the suggestion of a "MUST use" requirement for channel binding with=20
application access authentication sounds like the right approach:

> If all the application access peers support channel binding, then you
> could potentially require the eap-lower-layer attribute or similar for
> application authentication and work securely in environments where peers
> for network access have not been updated yet.

Is that plausible and reasonable in practice?

This would be in addition to the "MUST implement" requirements for AAA
servers, EAP serves and peers doing application access:

> I know you're correct that AAA servers and EAP servers need to implement
> channel binding for network access in such environments.

Thanks,
--David


> -----Original Message-----
> From: Sam Hartman [mailto:hartmans@painless-security.com]
> Sent: Tuesday, June 18, 2013 10:19 AM
> To: Black, David
> Cc: stefan.winter@restena.lu; jsalowey@cisco.com; General Area Review Tea=
m;
> abfab@ietf.org; ietf@ietf.org
> Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-=
03
>=20
> >>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
>=20
>     Black,> The next to last paragraph on p.3 begins with this sentence:
>=20
>     Black,>    For these reasons, channel binding MUST be implemented by
>     Black,> peers, EAP servers and AAA servers in environments where EAP
>     Black,> authentication is used to access application layer services.
>=20
>     Black,> It appear that this "MUST" requirement applies to all uses
>     Black,> of EAP, including network access authentication, not just
>     Black,> application layer access authentication.  If so, that's not
>     Black,> immediately obvious from the text, and an additional
>     Black,> sentence should be added to make this clearer.  If not, the
>     Black,> above sentence needs to exclude network access
>     Black,> authentication from that requirement.
>=20
>=20
> I know you're correct that AAA servers and EAP servers need to implement
> channel binding for network access in such environments.
> I'm not sure whether peers only doing network access SHOULD implement
> channel binding or MUST implement channel binding.
>=20
> Practically speaking, it will be a while before peers implement channel
> binding for network access.
> The sorts of attacks that result without channel binding are attacks
> where a peer thinks it is doing network access authentication but what
> it's really doing is helping an attacker access an application.
> If all the application access peers support channel binding, then you
> could potentially require the eap-lower-layer attribute or similar for
> application authentication and work securely in environments where peers
> for network access have not been updated yet.
> It's also kind of tempting to stick our head in the sand and just add
> the clarification that "yes, we mean network access too."
>=20
> --Sam


From drc@virtualized.org  Tue Jun 18 09:15:18 2013
Return-Path: <drc@virtualized.org>
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 BCB8911E80E8 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 09:15:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 KvQssEy8Y0G6 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 09:15:12 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 31DF921E80AA for <ietf@ietf.org>; Tue, 18 Jun 2013 09:15:10 -0700 (PDT)
Received: from [10.0.1.19] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 4BA4D1712A; Tue, 18 Jun 2013 16:15:08 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Back to] Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: David Conrad <drc@virtualized.org>
In-Reply-To: <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com>
Date: Tue, 18 Jun 2013 09:15:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <333C0971-E28F-4F0C-B1DE-A09E75A07763@virtualized.org>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf <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: Tue, 18 Jun 2013 16:15:18 -0000

Chris,

On Jun 18, 2013, at 8:57 AM, Christopher Morrow =
<morrowc.lists@gmail.com> wrote:
> I'm not such a fan of the draft, mostly because it appears to remove
> some principles that some RIR folk hold up in their policy discussions
> as important... while not having a backstop in said policies to
> replace the originals from 2050.

Which principles are you referencing?

Thanks,
-drc


From hallam@gmail.com  Tue Jun 18 09:52:38 2013
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 5C21B21F9AE2 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 09:52:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.48
X-Spam-Level: 
X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119,  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 I6PdOAwWkzxF for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 09:52:36 -0700 (PDT)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 9EBC511E80C5 for <ietf@ietf.org>; Tue, 18 Jun 2013 09:52:28 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id q56so3657492wes.31 for <ietf@ietf.org>; Tue, 18 Jun 2013 09:52:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=eS87ETFCZiwgpJ/ht/HQaQp+KXf0SNGmVi66ueJ2Ggk=; b=dUNhAph2e6UoewN12fPJBDqxBLu66brh3FkH5EGHH9LQLEP3+CvK5oXIwBTmmJKeHX Pj62ooRvFmrRIjpqvtwN6rXkfJiEwFlZP0toVn97DeKdMlzQzI7GdjzNjTdD0Rq3pCkt dGb9NF5AZv2/HlWoWeNBJnEjpRpHuJHrUB6LPTjhAlo9exGqMSHV0E4eLB7KZeoWNBuH 3bMSke0krisg+bc3oJCwHfb4kjbeRUlHaS9xcJe6mqfj5at0jqnASqZXNPxQkFl2UawV GRckqNcBquaVQyODokTtO9bNVWXwLoZ6oib7G01gQPoAQ/Hpe6U+sN6T33aGIg7HRozF b5PA==
MIME-Version: 1.0
X-Received: by 10.180.9.242 with SMTP id d18mr8132677wib.18.1371574347731; Tue, 18 Jun 2013 09:52:27 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Tue, 18 Jun 2013 09:52:27 -0700 (PDT)
Date: Tue, 18 Jun 2013 12:52:27 -0400
Message-ID: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>
Subject: IETF Diversity
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c2228cc79d0704df708932
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: Tue, 18 Jun 2013 16:52:38 -0000

--001a11c2228cc79d0704df708932
Content-Type: text/plain; charset=ISO-8859-1

I am rather disappointed that there hasn't been any followup to the
diversity discussion that took place at the plenary.

I do applications and I do security and so having a diverse range of input
is critical if the final product is going to be useful. There are no gender
or cultural issues in packet routing that I am aware of. But once we get to
the application layer they become central.

We seem to have interminable discussions about how to help some
hypothetical dissident in (pick your authoritarian state). But I can't
remember the last time we discussed Internet stalking which has been an
issue women have been complaining about since I started getting involved in
IETF. This is just one security issues that has a big gender bias and it is
a problem that I think can be usefully addressed in an open consensus
seeking organization.

It does not take 100 people to write a specification but it does take a
large number of people to adequately gather requirements. Taking
requirements from 100 people from almost the same background and
perspective is not very productive. I am aware that I have a limited
personal perspective which is why I actively seek out other perspectives.

At the plenary I pointed out that there have been women involved in IETF
ever since I started in IETF over 20 years ago now. Yet we have an IAB and
an IESG with only one female member who is not ex-officio (according to
their Web sites)

That situation should be something that has the IETF management worried but
I can't see much sign of that. The IETF is unlikely to die but it can lose
influence beyond the IP and DNS core. Sooner or later someone is going to
work out how to establish an applications standards process that is gender
and culture inclusive. And  we know from experience that in our environment
there can be a remarkably small time between the idea and establishing an
institution.

Minecraft was launched in 2011 and they had 4,500 people at their first
international conference that year, they are now about to have their third.
So they went from having nothing to having a larger participant community
than the IETF in a matter of months.

The IETF is a community known for valuing consensus rather than seeking
diverse views. I see a real risk that the consensus being built here is a
false consensus built by excluding opposing views rather than a real
consensus built on reconciling them. Bringing opposing views to this forum
is invariably a thankless task. The assumption is that if you can't hack it
here well that is your fault and your problem. Case in point,  each time I
get something wrong in RFC2HTML and I get the error message 'You Lose', my
natural response is 'why the heck am I bothering wasting my time here'.

I do not think that gender is the only diversity problem in IETF but it is
one that can be measured and the IETF is conspicuously failing. We also
have a rather severe age problem, twenty years ago EKR and myself were
among the youngest participants in most discussions and setting aside the
grad students the same is usually true today.


The perspective is going to need to change. Rather than looking for ways to
encourage a few token women to work their way up through the existing
selection regime we need to look at what sort of selection and
participation and representation structures will encourage diversity.


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

--001a11c2228cc79d0704df708932
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am rather disappointed that there hasn&#39;t been any fo=
llowup to the diversity discussion that took place at the plenary.<div><br>=
</div><div>I do applications and I do security and so having a diverse rang=
e of input is critical if the final product is going to be useful. There ar=
e no gender or cultural issues in packet routing that I am aware of. But on=
ce we get to the application layer they become central.</div>
<div><br></div><div>We seem to have interminable discussions about how to h=
elp some hypothetical dissident in (pick your authoritarian state). But I c=
an&#39;t remember the last time we discussed Internet stalking which has be=
en an issue women have been complaining about since I started getting invol=
ved in IETF. This is just one security issues that has a big gender bias an=
d it is a problem that I think can be usefully addressed in an open consens=
us seeking organization.</div>
<div><br></div><div style>It does not take 100 people to write a specificat=
ion but it does take a large number of people to adequately gather requirem=
ents. Taking requirements from 100 people from almost the same background a=
nd perspective is not very productive. I am aware that I have a limited per=
sonal perspective which is why I actively seek out other perspectives.=A0</=
div>
<div style><br></div><div style>At the plenary I pointed out that there hav=
e been women involved in IETF ever since I started in IETF over 20 years ag=
o now. Yet we have an IAB and an IESG with only one female member who is no=
t ex-officio (according to their Web sites)</div>
<div style><br></div><div style>That situation should be something that has=
 the IETF management worried but I can&#39;t see much sign of that. The IET=
F is unlikely to die but it can lose influence beyond the IP and DNS core. =
Sooner or later someone is going to work out how to establish an applicatio=
ns standards process that is gender and culture inclusive. And =A0we know f=
rom experience that in our environment there can be a remarkably small time=
 between the idea and establishing an institution.=A0</div>
<div style><br></div><div style>Minecraft was launched in 2011 and they had=
 4,500 people at their first international conference that year, they are n=
ow about to have their third. So they went from having nothing to having a =
larger participant community than the IETF in a matter of months.</div>
<div style><br></div><div style>The IETF is a community known for valuing c=
onsensus rather than seeking diverse views. I see a real risk that the cons=
ensus being built here is a false consensus built by excluding opposing vie=
ws rather than a real consensus built on reconciling them. Bringing opposin=
g views to this forum is invariably a thankless task. The assumption is tha=
t if you can&#39;t hack it here well that is your fault and your problem. C=
ase in point, =A0each time I get something wrong in RFC2HTML and I get the =
error message &#39;You Lose&#39;, my natural response is &#39;why the heck =
am I bothering wasting my time here&#39;.</div>
<div><br></div><div><div style>I do not think that gender is the only diver=
sity problem in IETF but it is one that can be measured and the IETF is con=
spicuously failing. We also have a rather severe age problem, twenty years =
ago EKR and myself were among the youngest participants in most discussions=
 and setting aside the grad students the same is usually true today.</div>
<div><br></div><div><br></div><div style>The perspective is going to need t=
o change. Rather than looking for ways to encourage a few token women to wo=
rk their way up through the existing selection regime we need to look at wh=
at sort of selection and participation and representation structures will e=
ncourage diversity.</div>
<div style><br></div><div><br></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c2228cc79d0704df708932--

From jari.arkko@piuha.net  Tue Jun 18 09:54:20 2013
Return-Path: <jari.arkko@piuha.net>
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 9496011E80DF for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 09:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 XvvNOo3WyZkQ for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 09:54:15 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5D7B121E8095 for <ietf@ietf.org>; Tue, 18 Jun 2013 09:54:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C68892CC66; Tue, 18 Jun 2013 19:54:09 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Km8dh74NmwPr; Tue, 18 Jun 2013 19:54:09 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4C2B32CC53; Tue, 18 Jun 2013 19:54:09 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com>
Date: Tue, 18 Jun 2013 19:54:10 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>, John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1503)
Cc: ietf <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: Tue, 18 Jun 2013 16:54:20 -0000

Chris: The last call on RFC 2050 bis has ended. The draft will be =
shortly on the IESG telechat, up for an approval decision and/or =
suggestion for changes. I personally think it is ready to move forward. =
That is not to say that we wouldn't take comments, if you have some.

As for the rest of the discussion - I'm sure there are things to be =
improved in ICANN. I'd suggest though that some of the feedback might be =
better placed in an ICANN discussion than on IETF list. And is not like =
there'd be nothing to improve on our side :-) Lets focus on IETF aspects =
here. For what it is worth, I have limited experience about ICANN, but =
it has all been very positive.

Jari


From stpeter@stpeter.im  Tue Jun 18 10:09:20 2013
Return-Path: <stpeter@stpeter.im>
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 A3F6A21F9B7F for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 10:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 u87F--nTlA7g for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 10:09:15 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 72B4B21F9B7D for <ietf@ietf.org>; Tue, 18 Jun 2013 10:09:15 -0700 (PDT)
Received: from sjc-vpn5-823.cisco.com (unknown [128.107.239.235]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C40F741189; Tue, 18 Jun 2013 11:23:08 -0600 (MDT)
Message-ID: <51C09437.5040006@stpeter.im>
Date: Tue, 18 Jun 2013 11:09:11 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IETF Diversity
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>
In-Reply-To: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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: Tue, 18 Jun 2013 17:09:20 -0000

On 6/18/13 10:52 AM, Phillip Hallam-Baker wrote:
> I am rather disappointed that there hasn't been any followup to the
> diversity discussion that took place at the plenary.

Speak for yourself. Some of us are taking concrete actions (e.g.,
recruiting people for document shepherd and WG chair roles) instead of
pontificating at the mic.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From john-ietf@jck.com  Tue Jun 18 10:09:58 2013
Return-Path: <john-ietf@jck.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 810A921E805D for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 10:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 unvc7dJU1g+k for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 10:09:52 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9A00521E8090 for <ietf@ietf.org>; Tue, 18 Jun 2013 10:09:52 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UozPi-000O83-SE; Tue, 18 Jun 2013 13:09:50 -0400
Date: Tue, 18 Jun 2013 13:09:45 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>, Christopher Morrow <morrowc.lists@gmail.com>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
Message-ID: <4CF0E73F6EEFC35F39F2E616@JcK-HP8200.jck.com>
In-Reply-To: <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf <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: Tue, 18 Jun 2013 17:09:58 -0000

--On Tuesday, June 18, 2013 19:54 +0300 Jari Arkko
<jari.arkko@piuha.net> wrote:

> Chris: The last call on RFC 2050 bis has ended. The draft will
> be shortly on the IESG telechat, up for an approval decision
> and/or suggestion for changes. I personally think it is ready
> to move forward. That is not to say that we wouldn't take
> comments, if you have some.

Jari,

For the record, I still believe that 2050bis should be
published.  Regardless of what I think of some of the things it
says, I think it is reasonably reflective of reality and that
reality is always worth documenting.

> As for the rest of the discussion - I'm sure there are things
> to be improved in ICANN. I'd suggest though that some of the
> feedback might be better placed in an ICANN discussion than on
> IETF list. And is not like there'd be nothing to improve on
> our side :-) Lets focus on IETF aspects here. For what it is
> worth, I have limited experience about ICANN, but it has all
> been very positive.

As to my more general comments, they were not really addressed
to 2050bis and I have no desire to start a discussion of them
here.  However, some assertions about how well ICANN is working
were made on this list by people who do not usually participate
actively in IETF's technical work.  In part because some ICANN
decisions and behaviors does affect the fate of IETF protocols
and the state of the Internet generally, I concluded after a lot
of consideration that those assertions should be responded to on
this list.  I would welcome a discussion (definitely somewhere
else) about that difference in perceptions if it were possible
that it would bring about either improved understanding or
changes that would make the various decision-making processes
that affect the Internet more open and/or more based on a
general understanding of Internet technical reality.  That would
include an offlist discussion of why your perceptions and mine
may differ should you find such a discussion useful.

best,
   john



From jsalowey@cisco.com  Tue Jun 18 10:10:26 2013
Return-Path: <jsalowey@cisco.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 80E8611E80F0; Tue, 18 Jun 2013 10:10:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 PjsZs7F81wtv; Tue, 18 Jun 2013 10:10:21 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id AEC3921F9B7D; Tue, 18 Jun 2013 10:10:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3564; q=dns/txt; s=iport; t=1371575421; x=1372785021; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+hlGh+C++SrXDUQzquKhgpIyxvVI+lyR41mFbWx3p6c=; b=gfzZQRI498ui8ajAaKuqPEDxRMrYTYCIBzj/rw9Irytkm90faOGjIf5B HjIX8Y5eewwOL3Q0Kb5OhVBKlZOYJgyQxVOgXON/h/OpS4TqYPC7kApuo vzBHWMz5JXYkKJuAWQBwpw9obPjZfu9QTvfMnj1nb/uAWEa+msI9ueyBS c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAAaUwFGtJXG//2dsb2JhbABPCoMJer8PgQIWdIIjAQEBAwE6PwULAgEIIhQQMiUBAQQOBQiIAAa7Eo1/gQkCMQeDAGEDqQSDD4FqJBo
X-IronPort-AV: E=Sophos;i="4.87,890,1363132800"; d="scan'208";a="224374188"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-3.cisco.com with ESMTP; 18 Jun 2013 17:10:20 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r5IHAKcY000945 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Jun 2013 17:10:20 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Tue, 18 Jun 2013 12:10:19 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Sam Hartman <hartmans@painless-security.com>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQA=
Date: Tue, 18 Jun 2013 17:10:19 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu>
In-Reply-To: <tsl38sfbiyd.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.248.222]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4F7AA199DE677B4EBAFAEF02DB1C2F7F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "abfab@ietf.org" <abfab@ietf.org>, "Black, David" <david.black@emc.com>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <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: Tue, 18 Jun 2013 17:10:26 -0000

On Jun 18, 2013, at 7:18 AM, Sam Hartman <hartmans@painless-security.com>
 wrote:

>>>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
>=20
>    Black,> The next to last paragraph on p.3 begins with this sentence:
>=20
>    Black,>    For these reasons, channel binding MUST be implemented by
>    Black,> peers, EAP servers and AAA servers in environments where EAP
>    Black,> authentication is used to access application layer services.
>=20
>    Black,> It appear that this "MUST" requirement applies to all uses
>    Black,> of EAP, including network access authentication, not just
>    Black,> application layer access authentication.  If so, that's not
>    Black,> immediately obvious from the text, and an additional
>    Black,> sentence should be added to make this clearer.  If not, the
>    Black,> above sentence needs to exclude network access
>    Black,> authentication from that requirement.
>=20
>=20
> I know you're correct that AAA servers and EAP servers need to implement
> channel binding for network access in such environments.
> I'm not sure whether peers only doing network access SHOULD implement
> channel binding or MUST implement channel binding.
>=20
> Practically speaking, it will be a while before peers implement channel
> binding for network access.
> The sorts of attacks that result without channel binding are attacks
> where a peer thinks it is doing network access authentication but what
> it's really doing is helping an attacker access an application.
> If all the application access peers support channel binding, then you
> could potentially require the eap-lower-layer attribute or similar for
> application authentication and work securely in environments where peers
> for network access have not been updated yet.

[Joe]  I'm trying to get a handle on the attack mechanism here.   In this a=
ttack a valid network service is trying to spoof an application service?  S=
ince it knows the MSK it can do this if the channel-binding of the lower-la=
yer into the EAP conversation is not enforced.  If the AAA server always en=
forces channel bindings for applications then it will catch the spoofing at=
tempt.   The reverse case may also be an issue where an application service=
 is trying to spoof a network service.   In this case, if the AAA server va=
lidates that the application channel binding is not present then it can pre=
vent the spoofing.  However the server MUST understand channel bindings eve=
n if the peers do not.   I think the document did try to capture this in th=
e following sentence:

"If the EAP server is aware that authentication is
   for something other than a network service, it too MUST default to
   requiring channel binding."

I think we could state this a bit better as something like:

"In environments where EAP is used for applications authentication and netw=
ork access authentication all EAP servers MUST understand channel bindings =
and require that application bindings MUST be present in application authen=
tication and that application bindings MUST be absent in network authentica=
tion.   All network access EAP peer implementations SHOULD support channel =
binding to explicitly identify the reason for authentication.  Any new usag=
e of EAP MUST support channel bindings to prevent confusion with network ac=
cess usage. "=20



> It's also kind of tempting to stick our head in the sand and just add
> the clarification that "yes, we mean network access too."
>=20
> --Sam


From jari.arkko@piuha.net  Tue Jun 18 10:18:10 2013
Return-Path: <jari.arkko@piuha.net>
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 2A4FE11E80E2 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 10:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 sRNhWurFGD4q for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 10:17:58 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6019111E80DF for <ietf@ietf.org>; Tue, 18 Jun 2013 10:17:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AA29D2CC66; Tue, 18 Jun 2013 20:17:57 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q_RmLWtgp8Ag; Tue, 18 Jun 2013 20:17:57 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id ED9AD2CC53; Tue, 18 Jun 2013 20:17:56 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Diversity
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>
Date: Tue, 18 Jun 2013 20:17:57 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5AD378E-0497-42C2-A6BA-BCBFCC9F9691@piuha.net>
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: 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: Tue, 18 Jun 2013 17:18:10 -0000

Phillip,

For the record, there have been several ongoing efforts. First, there is =
a diversity design team. We expect some results from them before =
IETF-87, lets deal with those when they come. Second, the IAOC has =
looked hard at the possibilities for reaching further out in the =
geographical world - you must have seen the big discussion about South =
America a while ago. I expect some news from the IAOC on this front =
soon. Third, we have worked with ISOC and others to look at how we could =
expand outreach efforts, be it geography, new types of participants, or =
other factors. Fourth, I think many of us have had the topic in our =
minds in our daily work, e.g., when looking at competence profiles for =
tasks, etc. See Peter's mail.

All in all, I'd of course be happier if we had made a big change and =
impact immediately. But the reality is that these types of changes are =
hard and take some time. But there is definitely efforts on the way. =
Those will have effects, long term.

That being said, I don't think we've done enough. Do you have =
suggestions on what additional things we could do? (Or you, or others on =
the list?)

Jari


From jari.arkko@piuha.net  Tue Jun 18 10:36:32 2013
Return-Path: <jari.arkko@piuha.net>
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 BDBB121F9B1C for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 10:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 D+WWGk8O+7oi for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 10:36:27 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6022621F996F for <ietf@ietf.org>; Tue, 18 Jun 2013 10:36:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E03C22CC66; Tue, 18 Jun 2013 20:36:25 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5iNpnSet4C8j; Tue, 18 Jun 2013 20:36:25 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 608802CC53; Tue, 18 Jun 2013 20:36:25 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <4CF0E73F6EEFC35F39F2E616@JcK-HP8200.jck.com>
Date: Tue, 18 Jun 2013 20:36:26 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <21E3F837-F6A5-4EBC-B9AB-858CABB50874@piuha.net>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <4CF0E73F6EEFC35F39F2E616@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1503)
Cc: ietf <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: Tue, 18 Jun 2013 17:36:32 -0000

John,

> For the record, I still believe that 2050bis should be
> published.  Regardless of what I think of some of the things it
> says, I think it is reasonably reflective of reality and that
> reality is always worth documenting.

Thanks.

> As to my more general comments, they were not really addressed
> to 2050bis and I have no desire to start a discussion of them
> here.  However, some assertions about how well ICANN is working
> were made on this list by people who do not usually participate
> actively in IETF's technical work.  In part because some ICANN
> decisions and behaviors does affect the fate of IETF protocols
> and the state of the Internet generally,

Ok. Understood.

> I would welcome a discussion (definitely somewhere
> else) about that difference in perceptions =85 That would
> include an offlist discussion of why your perceptions and mine
> may differ should you find such a discussion useful.

Fair enough. Hopefully some of that could be fed into ICANN as well.

(I should probably have indicated that my experience is very limited. I =
didn't want to indicate that there are no challenges - I know there =
are.)

Jari


From jsalowey@cisco.com  Tue Jun 18 10:47:10 2013
Return-Path: <jsalowey@cisco.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 9523A11E80DF; Tue, 18 Jun 2013 10:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 eRUCxIPRbfch; Tue, 18 Jun 2013 10:47:05 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id E391C11E80EC; Tue, 18 Jun 2013 10:47:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2198; q=dns/txt; s=iport; t=1371577625; x=1372787225; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Tl0W1XPlBj7Q7T8U4EZPVfIrpXaWB8G9FYDbLyRLqJI=; b=cZvKpaWkdEdheb+GuYb9/qy3lsQVZaaLVXj3eSSn3Hw+I37mNtYzLHxo NXMu5jlhPexVFY2tLTsZIlCdzuUA5yRaZDZb7S1vY1dO11A3Rglkyfptn 2H9TWvQGiFQNm6cd/oc58A2Q+wWE9OT2NQ9Bcn2nE4nXtIDtcun2ixFAS U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FALecwFGtJV2d/2dsb2JhbABPCoMJer8PgQIWdIIkAQEEOj8QAgEIIhQQMiUBAQQODYgGuwuNf4EJAjEHgwBhA6kEgw+CKA
X-IronPort-AV: E=Sophos;i="4.87,890,1363132800"; d="scan'208";a="224169702"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 18 Jun 2013 17:47:04 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r5IHl4iY016128 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Jun 2013 17:47:04 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.02.0318.004; Tue, 18 Jun 2013 12:47:04 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Black, David" <david.black@emc.com>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQAAClxl4P//t2GA
Date: Tue, 18 Jun 2013 17:47:03 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.248.222]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6D250E7F34578C4DB2BC1DE691351E73@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <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: Tue, 18 Jun 2013 17:47:10 -0000

>>=20
>> I think we could state this a bit better as something like:
>>=20
>> "In environments where EAP is used for applications authentication and n=
etwork
>> access authentication all EAP servers MUST understand channel bindings a=
nd
>> require that application bindings MUST be present in application
>> authentication and that application bindings MUST be absent in network
>> authentication.   All network access EAP peer implementations SHOULD sup=
port
>> channel binding to explicitly identify the reason for authentication.  A=
ny new
>> usage of EAP MUST support channel bindings to prevent confusion with net=
work
>> access usage. "
>=20
> That text is an improvement, and it's headed in the same direction as Sam=
's
> comment - "application bindings MUST be present in application authentica=
tion"
> is a "MUST use" requirement, not just a "MUST implement" requirement.
>=20
> OTOH, I'm not clear on what "application bindings" means, as that term's =
not
> in the current draft.  Specifically, I'm a bit unclear on "application bi=
ndings
> MUST be absent in network authentication" - does that mean that channel
> binding must be absent, or that channel binding is optional, but if chann=
el
> binding is present, it MUST NOT be an "application binding", whatever tha=
t is?
>=20

[Joe] Good points, the text can be more specific:

"In environments where EAP is used for purposes other than network access a=
uthentication all EAP servers MUST enforce channel bindings.  For applicati=
on authentication, the EAP server MUST require that the correct EAP lower-l=
ayer attribute be present in the channel binding data.   For network access=
 authentication, the EAP server MUST require that if channel bindings are p=
resent they MUST contain the correct EAP lower-layer attribute.   All netwo=
rk access EAP peer implementations SHOULD use channel bindings including th=
e EAP lower-layer attribute to explicitly identify the reason for authentic=
ation.  Any new usage of EAP MUST use channel bindings including the EAP lo=
wer-layer attribute to prevent confusion with network access usage. "

Does this help?

Thanks,

Joe


From abdussalambaryun@gmail.com  Tue Jun 18 11:03:04 2013
Return-Path: <abdussalambaryun@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 B1B1921F998A for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, 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 xHuY0RN6r4EN for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:03:03 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 50E8621F961F for <ietf@ietf.org>; Tue, 18 Jun 2013 11:03:03 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id xb12so4163505pbc.12 for <ietf@ietf.org>; Tue, 18 Jun 2013 11:03:03 -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=0f/3LX1Sw4jAxOPB8dsO91EtScjGX/NF5aAVeBa2MIo=; b=T/gbM3tL2OWAtkaMNaT4U/ywFIlrwyECtQOnIDt/FGg1N/2pvO/At7Hm4D8ir8BTTl KSDi6PRmyE0Fd58a23miH4IoeTKSaUhU3OdILCVsx6AsdsPllqZ9QpRMvqZ869CGDTz9 dMrUWFBgyO7GLhhn77hLms3+RVRIFXwhu/LIoFbk0MMLbmcRQWbletXFXu0QNWytefiT ZUB4tlwhivW3d4pzRmSqWt7/hNHMx62ZiET44Ab2BypLu31u7SPSsh+jV0IuH0s8lkma leZe+kgAmcN15IZkkyQ7cnL6QiZvrsScJ9ixC7Rxij8p+5Z+7lPANwsrJpRWCJA+eWm5 V62g==
MIME-Version: 1.0
X-Received: by 10.68.219.42 with SMTP id pl10mr18322391pbc.24.1371578582937; Tue, 18 Jun 2013 11:03:02 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Tue, 18 Jun 2013 11:03:02 -0700 (PDT)
In-Reply-To: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>
Date: Tue, 18 Jun 2013 20:03:02 +0200
Message-ID: <CADnDZ8_e2Tn9XPZ0ZTk7Hhc+7TC9erXcrM6gxVmnp3rG7fgGHA@mail.gmail.com>
Subject: Re: IETF Diversity
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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: Tue, 18 Jun 2013 18:03:04 -0000
X-List-Received-Date: Tue, 18 Jun 2013 18:03:04 -0000

On 6/18/13, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> I am rather disappointed that there hasn't been any followup to the
> diversity discussion that took place at the plenary.
>

I thought there are some people following/working this up, and made
some progress. However, I agree that I seen no progress
written/reported to us,

> I do applications and I do security and so having a diverse range of input
> is critical if the final product is going to be useful. There are no gender
> or cultural issues in packet routing that I am aware of. But once we get to
> the application layer they become central.

I agree that at that layer you will face the community.

>
> It does not take 100 people to write a specification but it does take a
> large number of people to adequately gather requirements. Taking
> requirements from 100 people from almost the same background and
> perspective is not very productive. I am aware that I have a limited
> personal perspective which is why I actively seek out other perspectives.

I mentioned similar idea of that before, and I agree IETF needs
diversity to progress.

>
> At the plenary I pointed out that there have been women involved in IETF
> ever since I started in IETF over 20 years ago now. Yet we have an IAB and
> an IESG with only one female member who is not ex-officio (according to
> their Web sites)
>
> That situation should be something that has the IETF management worried but
> I can't see much sign of that.

I suggested also that we need more women in management, so I support
that, however, majority men may not want that, so what can we do!!!!

> The IETF is unlikely to die but it can lose
> influence beyond the IP and DNS core. Sooner or later someone is going to
> work out how to establish an applications standards process that is gender
> and culture inclusive. And  we know from experience that in our environment
> there can be a remarkably small time between the idea and establishing an
> institution.

It is good if IETF realise that it can loose, so it will work harder.
The IETF is mostly doing its meetings in North America so its culture
is closer to North America culture.

>
> Minecraft was launched in 2011 and they had 4,500 people at their first
> international conference that year, they are now about to have their third.
> So they went from having nothing to having a larger participant community
> than the IETF in a matter of months.

I think that is good news, and that IETF should realise how did that
happen, and realise what is wrong in IETF. I suggested before that
IETF encourages participants, and gave many responses but still I was
feeling ignored.

>
> The IETF is a community known for valuing consensus rather than seeking
> diverse views. I see a real risk that the consensus being built here is a
> false consensus built by excluding opposing views rather than a real
> consensus built on reconciling them.

I already mentioned that before, I found out that many say we want
consensus when they don't have good engineering reason, and when there
is no consensus they go back to technical reasons.

> Bringing opposing views to this forum
> is invariably a thankless task. The assumption is that if you can't hack it
> here well that is your fault and your problem. Case in point,  each time I
> get something wrong in RFC2HTML and I get the error message 'You Lose', my
> natural response is 'why the heck am I bothering wasting my time here'.

We waste time only if management don't listen to the
minorities/diversed of the community.

>
> I do not think that gender is the only diversity problem in IETF but it is
> one that can be measured and the IETF is conspicuously failing. We also
> have a rather severe age problem, twenty years ago EKR and myself were
> among the youngest participants in most discussions and setting aside the
> grad students the same is usually true today.

I agree,

>
>
> The perspective is going to need to change. Rather than looking for ways to
> encourage a few token women to work their way up through the existing
> selection regime we need to look at what sort of selection and
> participation and representation structures will encourage diversity.
>

I think it is very easy to encourage people, and very easy to
discourage people, the difficult part is to maintain people encouraged
and liking to continue participating in the IETF. Many people in life
hate CHANGE, so that is another difficulty, the IETF should get use to
CHANGE.


Thanks for your input it makes a greater impact than my inputs maybe
because my english.

AB

From hallam@gmail.com  Tue Jun 18 11:08:41 2013
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 09D0D21F9B94 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=0.104,  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 lVYJh8reLbQ2 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:08:39 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 8D6E821F9B91 for <ietf@ietf.org>; Tue, 18 Jun 2013 11:08:39 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id n11so3820385wgh.9 for <ietf@ietf.org>; Tue, 18 Jun 2013 11:08:36 -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=B4UIgZeSwnM1kD6mrdiGGuUd0jAmA16TegNbOliNtWc=; b=yUjUox+cEYKDvWG3xiyIz0uDHBbfmxB0YtqWEVhQEI231mk9pvCovRN3DZVjEW7NKf T02MEjJtFQgRrru07Ah26v7bh8xmY0hxTER0DzoSp9TCICOCqg6PVDWuz897BSbuRj+J LLS6H+eDY6i63nAQahSJBO8vRd9HqFMiLhqsuYkAyd0JCtOu0r89WW0E4XKX/j+3+ljb 1nYiBAp8nyw0Q6UuTpCxrmnN0NtDr0vppjXaAf+xhJxvcC63mlC0VDYM1HY0EzdZaeQ/ uYkuAX8BvfN3biDSGV9bwTWWbe2ms08WGYlcXv5k01zXLU8JOjgrJYFECHvwPekhyPr/ ztkg==
MIME-Version: 1.0
X-Received: by 10.194.240.201 with SMTP id wc9mr10041620wjc.1.1371578916024; Tue, 18 Jun 2013 11:08:36 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Tue, 18 Jun 2013 11:08:35 -0700 (PDT)
In-Reply-To: <51C09437.5040006@stpeter.im>
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <51C09437.5040006@stpeter.im>
Date: Tue, 18 Jun 2013 14:08:35 -0400
Message-ID: <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com>
Subject: Re: IETF Diversity
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=089e013d1bea12436904df719a9c
Cc: 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: Tue, 18 Jun 2013 18:08:41 -0000

--089e013d1bea12436904df719a9c
Content-Type: text/plain; charset=ISO-8859-1

When I make a statement at the microphone and then have multiple people
come to thank me afterwards for making that point I don't consider it
pontificating.

I do however consider your own response to be an example of the type of
exclusionary behavior that I was talking about. Dismissing those concerns
as 'pontificating' does not help matters. And you have no idea what actions
I have taken to attempt to recruit people to get involved.

The issue was raised in the IETF plenary I would have expected mention of a
followup mailing list to be made here on the ietf discussion list.




On Tue, Jun 18, 2013 at 1:09 PM, Peter Saint-Andre <stpeter@stpeter.im>wrote:

> On 6/18/13 10:52 AM, Phillip Hallam-Baker wrote:
> > I am rather disappointed that there hasn't been any followup to the
> > diversity discussion that took place at the plenary.
>
> Speak for yourself. Some of us are taking concrete actions (e.g.,
> recruiting people for document shepherd and WG chair roles) instead of
> pontificating at the mic.
>
> Peter
>
> --
> Peter Saint-Andre
> https://stpeter.im/
>
>
>


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

--089e013d1bea12436904df719a9c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">When I make a statement at the microphone and then have mu=
ltiple people come to thank me afterwards for making that point I don&#39;t=
 consider it pontificating.<div><br></div><div style>I do however consider =
your own response to be an example of the type of exclusionary behavior tha=
t I was talking about. Dismissing those concerns as &#39;pontificating&#39;=
 does not help matters. And you have no idea what actions I have taken to a=
ttempt to recruit people to get involved.=A0</div>
<div style><br></div><div style>The issue was raised in the IETF plenary I =
would have expected mention of a followup mailing list to be made here on t=
he ietf discussion list.=A0</div><div style><br></div><div style><br></div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue,=
 Jun 18, 2013 at 1:09 PM, Peter Saint-Andre <span dir=3D"ltr">&lt;<a href=
=3D"mailto:stpeter@stpeter.im" target=3D"_blank">stpeter@stpeter.im</a>&gt;=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 6/18/13 10:52 AM, Phill=
ip Hallam-Baker wrote:<br>
&gt; I am rather disappointed that there hasn&#39;t been any followup to th=
e<br>
&gt; diversity discussion that took place at the plenary.<br>
<br>
</div>Speak for yourself. Some of us are taking concrete actions (e.g.,<br>
recruiting people for document shepherd and WG chair roles) instead of<br>
pontificating at the mic.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Peter<br>
<br>
--<br>
Peter Saint-Andre<br>
<a href=3D"https://stpeter.im/" target=3D"_blank">https://stpeter.im/</a><b=
r>
<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><=
br>
</div>

--089e013d1bea12436904df719a9c--

From christopher.morrow@gmail.com  Tue Jun 18 11:15:00 2013
Return-Path: <christopher.morrow@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 1879821F99BE for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 1tR7Zof+fTa1 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:14:55 -0700 (PDT)
Received: from mail-lb0-f173.google.com (mail-lb0-f173.google.com [209.85.217.173]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD2211E80F6 for <ietf@ietf.org>; Tue, 18 Jun 2013 11:14:51 -0700 (PDT)
Received: by mail-lb0-f173.google.com with SMTP id v1so3916656lbd.32 for <ietf@ietf.org>; Tue, 18 Jun 2013 11:14:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=NvZ/1W4L0pZnE7VQd66oE9qJ3IQdMHj04qdoxFN08GM=; b=r2XzIT7IjIV5saKZNoj92VopB8RSDuviDR9ZPJhyUX/5r32Z2GsZfYhcUIzFpptZOs XNTq6w5KwP+lOkiLG55uHr1QVmRKeCzRFf9wn8SJKSguhNR1g347zi3tueoteO6sQnW7 nFDr0NQUvldk0kw7fVJPo3MZzMj+9vPtbgUXkRvm3m88t4wjio+50y0/AWTpcPqTkpya Fv+Lf7EdbQKPgow6yMDj2rEjHVp43DIRrIw9a0vhdQbkePrNGDz99BLq0jO8ssVp3RXd 3YAtDAyeUN8jOCdPbbBFbOdOhydH1a6ltTCFudYQIIAuB5JZh8bqKExWCyi28rtWR3Zw EAGg==
MIME-Version: 1.0
X-Received: by 10.112.156.42 with SMTP id wb10mr1599663lbb.62.1371579291055; Tue, 18 Jun 2013 11:14:51 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.152.22.196 with HTTP; Tue, 18 Jun 2013 11:14:50 -0700 (PDT)
In-Reply-To: <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
Date: Tue, 18 Jun 2013 14:14:50 -0400
X-Google-Sender-Auth: tljEHp-zEzSz-rUoJS8Kw1EJFa0
Message-ID: <CAL9jLaZK6H8r-tizX+RhmZPYzOViJF5rr91QtURX8nGysORYSw@mail.gmail.com>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: John C Klensin <john-ietf@jck.com>, ietf <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: Tue, 18 Jun 2013 18:15:00 -0000

On Tue, Jun 18, 2013 at 12:54 PM, Jari Arkko <jari.arkko@piuha.net> wrote:
> Chris: The last call on RFC 2050 bis has ended. The draft will be shortly=
 on the IESG telechat, up for an approval decision and/or suggestion for ch=
anges. I personally think it is ready to move forward. That is not to say t=
hat we wouldn't take comments, if you have some.
>

ok, cool... my  only comment was on the timing issue... which I doubt
will get fixed before pub time, and isn't a show-stopper though ...
will make the conversation at the RIR level a bit more challenging for
some folks I imagine.

-chris

From dhc@dcrocker.net  Tue Jun 18 11:20:26 2013
Return-Path: <dhc@dcrocker.net>
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 2B06D21E805D for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.533
X-Spam-Level: 
X-Spam-Status: No, score=-6.533 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 EjNVmkuWkzgV for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:20:21 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2947D21F9AAA for <ietf@ietf.org>; Tue, 18 Jun 2013 11:20:21 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5IIKHmT025457 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 18 Jun 2013 11:20:20 -0700
Message-ID: <51C0A4D2.9020106@dcrocker.net>
Date: Tue, 18 Jun 2013 11:20:02 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IETF Diversity
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <A5AD378E-0497-42C2-A6BA-BCBFCC9F9691@piuha.net>
In-Reply-To: <A5AD378E-0497-42C2-A6BA-BCBFCC9F9691@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 18 Jun 2013 11:20:20 -0700 (PDT)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Tue, 18 Jun 2013 18:20:26 -0000

On 6/18/2013 10:17 AM, Jari Arkko wrote:
>     Second, the IAOC has
> looked hard at the possibilities for reaching further out in the
> geographical world


Jari,

The only action that's been cited has been holding a meeting in that 
region.  A number of us have posted comments suggesting that this is 
unlikely to be an effective recruiting technique; a few also offered 
thoughts of other approaches.  I won't rehash the rationales that have 
been offered.

If other avenues of recruiting are being explored by the IAOC, what are 
they?

If the only avenue being considered is a meeting in the region, it would 
be helpful to see some response to the concerns raised about this as a 
recruiting tool.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From christopher.morrow@gmail.com  Tue Jun 18 11:21:22 2013
Return-Path: <christopher.morrow@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 51C1521F972E for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 02eSIan3TaQz for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:21:21 -0700 (PDT)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id ABEF811E80EE for <ietf@ietf.org>; Tue, 18 Jun 2013 11:21:09 -0700 (PDT)
Received: by mail-la0-f54.google.com with SMTP id ec20so3747781lab.41 for <ietf@ietf.org>; Tue, 18 Jun 2013 11:21:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0QSeArNaMBULKqltfa1BQ1/XDODY9IobGVW942cpHBA=; b=ybNpVQJzd+YHhgtTL0cvVDufD7O3+cXhHgNeDVIg6JwvlyMY459dmpDQhXatUny2PZ I0tKnY6yXifUG8+dZG1C1CVOkQR91fV1Isezw2yVHKNhyhh7qs8wmIyni1FNyxVQNoSz BYjCYuaM7GAZQCE8AKJb/S68/fvScQ4APpBmzG5lh7egQAIq/UmTdUS3unUSl6SpYSQQ iz6CbpP/ezz+K3GYl/uDQoGtzGHoIE56hiLJUPOXG6diKn5IBemDZL/8haxoO7FCzLlf fdiFNbfibnYtmktqBMjMIRGvZiCLSAR3YntjFywLXEAn5WdYLysy31VQAdJ48nBkX9tF Jz+A==
MIME-Version: 1.0
X-Received: by 10.112.146.97 with SMTP id tb1mr1654063lbb.26.1371579668335; Tue, 18 Jun 2013 11:21:08 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.152.22.196 with HTTP; Tue, 18 Jun 2013 11:21:08 -0700 (PDT)
In-Reply-To: <333C0971-E28F-4F0C-B1DE-A09E75A07763@virtualized.org>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <333C0971-E28F-4F0C-B1DE-A09E75A07763@virtualized.org>
Date: Tue, 18 Jun 2013 14:21:08 -0400
X-Google-Sender-Auth: mgYPOc4UOpy-IELp_Z45Ut1OYYs
Message-ID: <CAL9jLaaBf1gzSk5oTMQuAg4uNxtUuyKdHfLD+BuZfm0BpGLAjA@mail.gmail.com>
Subject: Re: [Back to] Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: Christopher Morrow <morrowc.lists@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <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: Tue, 18 Jun 2013 18:21:22 -0000

On Tue, Jun 18, 2013 at 12:15 PM, David Conrad <drc@virtualized.org> wrote:
> Chris,
>
> On Jun 18, 2013, at 8:57 AM, Christopher Morrow <morrowc.lists@gmail.com> wrote:
>> I'm not such a fan of the draft, mostly because it appears to remove
>> some principles that some RIR folk hold up in their policy discussions
>> as important... while not having a backstop in said policies to
>> replace the originals from 2050.
>
> Which principles are you referencing?

at least needs-based allocations...

So, I should be clear that I don't 'like' that 'the ietf has dictated'
to the community some actions they must take with respect to
allocation policy that the RIR communities are supposed to agree upon
amongst their individual selves (perhaps coordinated, perhaps not). So
I understand why these things (and actually agree with) the removal of
these things.

I think though there could be perceived a situation where 'oops, no
more rules!!' because the RIRs (arin's community at least) hasn't
pushed for these items explicitly in their policy manual. (arin has
some of this via linkages to 2050 in their PDP.. but not in the
community-built nrpm)

It's worth noting, to me at least, that the 'no rules!' bit could be
viewed as a good thing, and could be a method to pull back as a
community and gather some data on how the system reacts. Additonally,
it could be the case that the community really does not want this sort
of restriction in place in the name of 'making the move to ipv6 happen
more quickly and more completely' (a-la burning your ships upon
landing in the 'new world').

as a summary:
  1) happy to see the principles / restrictions imposed from 'above'
on the RIR's removed
  2) happy to see the doc move forward
  3) interested to see how the communities at the RIR level deal with this
  4) sad a bit that the ARIN community (at least) didn't move to put
in place protections/restrictions/garter-belts/suspenders/etc before
this doc is published.

-chris

>
> Thanks,
> -drc
>

From hartmans@painless-security.com  Tue Jun 18 11:39:23 2013
Return-Path: <hartmans@painless-security.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 D58BD11E80F7; Tue, 18 Jun 2013 11:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 SvRUC7f+lfIX; Tue, 18 Jun 2013 11:39:18 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id A88AE11E80F8; Tue, 18 Jun 2013 11:39:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 36D902013A; Tue, 18 Jun 2013 14:35:24 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xAFbtdoguduW; Tue, 18 Jun 2013 14:35:23 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 18 Jun 2013 14:35:23 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 2DA9980047; Tue, 18 Jun 2013 14:39:05 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: "Joseph Salowey \(jsalowey\)" <jsalowey@cisco.com>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com>
Date: Tue, 18 Jun 2013 14:39:05 -0400
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com> (Joseph Salowey's message of "Tue, 18 Jun 2013 17:47:03 +0000")
Message-ID: <tsl38sf9sc6.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "abfab@ietf.org" <abfab@ietf.org>, "Black, David" <david.black@emc.com>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <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: Tue, 18 Jun 2013 18:39:24 -0000

Joe, eap-lower-layer is not required for application authentication if
there's some other attribute that's specific to the lower layer.  For
example Moonshot sends gss-acceptor-service-name but does not currently
send eap-lower-layer, and doing that seems consistent with the
requirements of the channel binding spec.

Adding a requirement for eap-lower-layer all the time would be new, but
might be reasonable.

--Sam

From stpeter@stpeter.im  Tue Jun 18 11:42:31 2013
Return-Path: <stpeter@stpeter.im>
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 C3D3A21E8096 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 VsUAx0ADcQp1 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:42:26 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B7F6F11E80F7 for <ietf@ietf.org>; Tue, 18 Jun 2013 11:42:15 -0700 (PDT)
Received: from sjc-vpn5-823.cisco.com (unknown [128.107.239.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B75A341189; Tue, 18 Jun 2013 12:56:09 -0600 (MDT)
Message-ID: <51C0AA04.4020508@stpeter.im>
Date: Tue, 18 Jun 2013 12:42:12 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IETF Diversity
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com>
In-Reply-To: <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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: Tue, 18 Jun 2013 18:42:31 -0000

On 6/18/13 12:08 PM, Phillip Hallam-Baker wrote:
> When I make a statement at the microphone and then have multiple people
> come to thank me afterwards for making that point I don't consider it
> pontificating.
> 
> I do however consider your own response to be an example of the type of
> exclusionary behavior that I was talking about. Dismissing those
> concerns as 'pontificating' does not help matters. And you have no idea
> what actions I have taken to attempt to recruit people to get involved. 

No, I don't. I'm happy to hear that you're getting busy from the ground
up, instead of waiting for official action.

> The issue was raised in the IETF plenary I would have expected mention
> of a followup mailing list to be made here on the ietf discussion list. 

Fair enough.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From stephen.farrell@cs.tcd.ie  Tue Jun 18 11:51:36 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
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 DDCD921E8050 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 1tiogSZpZqkK for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 11:51:32 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 934F621F9936 for <ietf@ietf.org>; Tue, 18 Jun 2013 11:51:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 26FF4BE98; Tue, 18 Jun 2013 19:50:56 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sVsNnBMWpw+X; Tue, 18 Jun 2013 19:50:54 +0100 (IST)
Received: from [172.30.0.172] (stat-217-145-38-54.xdsl.toledo.be [217.145.38.54]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 088FBBE97; Tue, 18 Jun 2013 19:50:53 +0100 (IST)
Message-ID: <51C0AC0C.70002@cs.tcd.ie>
Date: Tue, 18 Jun 2013 19:50:52 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: IETF Diversity
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <51C0AA04.4020508@stpeter.im>
In-Reply-To: <51C0AA04.4020508@stpeter.im>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Phillip Hallam-Baker <hallam@gmail.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: Tue, 18 Jun 2013 18:51:37 -0000

On 06/18/2013 07:42 PM, Peter Saint-Andre wrote:
> On 6/18/13 12:08 PM, Phillip Hallam-Baker wrote:
>
>> The issue was raised in the IETF plenary I would have expected mention
>> of a followup mailing list to be made here on the ietf discussion list. 
> 
> Fair enough.

Not quite. My local ietf@ietf.org folder has 392 messages that
match a search for "diversity" all but of few of which are since
this March, e.g. most recently before this thread [1].

There is a lot of noise on this list so I can understand that
threads might be missed but its not true to say there's been
nothing on here.

S.

[1] http://www.ietf.org/mail-archive/web/ietf/current/msg80076.html


> 
> Peter
> 

From randy@psg.com  Tue Jun 18 12:07:18 2013
Return-Path: <randy@psg.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 BAC9011E80F7 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 12:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599]
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 FgsmfhgQ7Osm for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 12:07:18 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5065D11E80EE for <ietf@ietf.org>; Tue, 18 Jun 2013 12:07:18 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Up1FM-0006I0-GN; Tue, 18 Jun 2013 19:07:16 +0000
Date: Wed, 19 Jun 2013 04:07:14 +0900
Message-ID: <m24ncv1bml.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt>	(The Internet Numbers Registry System) to Informational RFC)
In-Reply-To: <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <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: Tue, 18 Jun 2013 19:07:18 -0000

> As for the rest of the discussion - I'm sure there are things to be
> improved in ICANN. I'd suggest though that some of the feedback might
> be better placed in an ICANN discussion than on IETF list.

when that feedback is that the icann does not really listen to feedback,
i think there is a problem with this approach.  the examples of earwax
are rife.

randy

From dhc@dcrocker.net  Tue Jun 18 12:07:59 2013
Return-Path: <dhc@dcrocker.net>
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 CE46811E80FE for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 12:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.536
X-Spam-Level: 
X-Spam-Status: No, score=-6.536 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 brxvKKczTMhQ for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 12:07:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E944E11E80FF for <ietf@ietf.org>; Tue, 18 Jun 2013 12:07:45 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5IJ7gGj026478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Tue, 18 Jun 2013 12:07:45 -0700
Message-ID: <51C0AFEF.9020904@dcrocker.net>
Date: Tue, 18 Jun 2013 12:07:27 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: IETF Diversity
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <51C0AA04.4020508@stpeter.im>
In-Reply-To: <51C0AA04.4020508@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 18 Jun 2013 12:07:45 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Tue, 18 Jun 2013 19:07:59 -0000

>> The issue was raised in the IETF plenary I would have expected mention
>> of a followup mailing list to be made here on the ietf discussion list.
>
> Fair enough.



I'm probably misunderstanding something basic here, because I thought 
there already was/is a list established:

    Diversity open mailing list

    https://www.ietf.org/mailman/listinfo/diversity


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jsalowey@cisco.com  Tue Jun 18 13:00:26 2013
Return-Path: <jsalowey@cisco.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 C373021E80B6; Tue, 18 Jun 2013 13:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 gr57FFocfblg; Tue, 18 Jun 2013 13:00:20 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id DE6D921E80BD; Tue, 18 Jun 2013 13:00:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=868; q=dns/txt; s=iport; t=1371585620; x=1372795220; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=eB/jRNm4UWz/7giJ74P44658v9HNsMtyBDBq+TrXiwM=; b=fhA1BWL/N24VkIc2NpKZ1I1UCQWOE7NnH0BjelSKH0U4FPGh91MolZKp ep8B7XujsZ9rA6TgXNeVWZvNafK9Y5nB8TReZ6chOrjolQcXpSbOSQwL2 egt1ykf1chuVSiNydT1cXq17JGr6Z0VALC6Up8cyOtgUQusPHtfMBs3Ht Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al4FACS7wFGtJXHA/2dsb2JhbABZgwl6gjq8VYEEFnSCIwEBAQMBOj8FCwIBCCIUEDIlAgQOBQiIAAa6fI8IAjEHgwBhA6kEgw+BaAc5
X-IronPort-AV: E=Sophos;i="4.87,891,1363132800"; d="scan'208";a="224230285"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 18 Jun 2013 20:00:19 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r5IK0J4d013814 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Jun 2013 20:00:19 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Tue, 18 Jun 2013 15:00:18 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Sam Hartman <hartmans@painless-security.com>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: AQHObFMc5Vr98eb9RParuraCHgwUcpk8OBOA
Date: Tue, 18 Jun 2013 20:00:17 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628CFBE45@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com> <tsl38sf9sc6.fsf@mit.edu>
In-Reply-To: <tsl38sf9sc6.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.248.222]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3E45AE4402E8FD46832FA550ED86D443@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "abfab@ietf.org" <abfab@ietf.org>, "Black, David" <david.black@emc.com>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <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: Tue, 18 Jun 2013 20:00:26 -0000

On Jun 18, 2013, at 11:39 AM, Sam Hartman <hartmans@painless-security.com>
 wrote:

> Joe, eap-lower-layer is not required for application authentication if
> there's some other attribute that's specific to the lower layer.  For
> example Moonshot sends gss-acceptor-service-name but does not currently
> send eap-lower-layer, and doing that seems consistent with the
> requirements of the channel binding spec.
>=20
> Adding a requirement for eap-lower-layer all the time would be new, but
> might be reasonable.
>=20

[Joe] Ah yes, I remember this.  It would be simpler to just use eap lower-l=
ayer attribute.  I think we could massage the text to say something like "e=
ap lower-layer layer attribute or equivalent attribute indicating the EAP l=
ower layer in use" .   Let me see what I can do with the text David provide=
d. =20


> --Sam


From prvs=68814591e7=suresh.krishnan@ericsson.com  Tue Jun 18 13:23:06 2013
Return-Path: <prvs=68814591e7=suresh.krishnan@ericsson.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 B061E21E8083 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 13:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 c174FZuwdEeZ for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 13:22:59 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 29EE321F9CCE for <ietf@ietf.org>; Tue, 18 Jun 2013 13:22:58 -0700 (PDT)
X-AuditID: c6180641-b7f0e6d0000015f1-4a-51c0c198d7b4
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id FE.C9.05617.891C0C15; Tue, 18 Jun 2013 22:22:49 +0200 (CEST)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC004.ericsson.se (147.117.188.84) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 18 Jun 2013 16:22:48 -0400
Received: from [164.48.125.25] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 18 Jun 2013 16:22:47 -0400
Message-ID: <51C0C0F4.70701@ericsson.com>
Date: Tue, 18 Jun 2013 16:20:04 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IETF Diversity
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com>
In-Reply-To: <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrLLMWRmVeSWpSXmKPExsUyuXRPiO7MgwcCDRo+sVtcXX6cyeLZxvks Fsf29DM7MHvsnHWX3WPJkp9MHnP3vGAOYI7itklKLCkLzkzP07dL4M6Y9tivYBV7xeqmhUwN jK9Zuxg5OSQETCQ+d6xmg7DFJC7cWw9kc3EICRxllNh/8iQzSEJIYA+jxNYecYjEVkaJZw8a gbo5OHgFNCVa2lVAalgEVCVaL5wDG8QGNHTDzs9MILaoQJjEh2VLwGxeAUGJkzOfsIDYIgLa Ekf3bQE7glkgSmLFjG1gu4QFpCXanr1jgdi1mVFiyYqJYEWcAoESH1rXQV0qKbHlRTs7RLOe xJSrLYwQtrzE9rdzoI7WlNi65jvrBEbhWUh2z0LSMgtJywJG5lWMHKXFqWW56UaGmxiBoX1M gs1xB+OCT5aHGKU5WJTEed+f2hUoJJCeWJKanZpakFoUX1Sak1p8iJGJgxNEcEk1MGouuOWs Uv970uvFWbzz375b156QLyHy69qm071HrfarNvqx71ytvCHs+Acjrx9bTs86sXSj1oU3CvIi 7Ae4tpedNDgv/7ZbMO7Mfqf7v27FzYjavy1pguvpmcufyuYcvenxMlb+PeNxmZr2496xHK4/ 2bscT158Kpz94PmfkMuJR18I7zK4tFNQiaU4I9FQi7moOBEA97lL3UACAAA=
Cc: 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: Tue, 18 Jun 2013 20:23:06 -0000

Hi Phil,

On 06/18/2013 02:08 PM, Phillip Hallam-Baker wrote:
> When I make a statement at the microphone and then have multiple people
> come to thank me afterwards for making that point I don't consider it
> pontificating.
> 
> I do however consider your own response to be an example of the type of
> exclusionary behavior that I was talking about. Dismissing those
> concerns as 'pontificating' does not help matters. And you have no idea
> what actions I have taken to attempt to recruit people to get involved. 
> 
> The issue was raised in the IETF plenary I would have expected mention
> of a followup mailing list to be made here on the ietf discussion list. 

Apologies. The announcement of the diversity list was sent to the IETF
announcement list and not the discussion list. The diversity list can be
found here as Dave C. mentioned.

https://www.ietf.org/mailman/listinfo/diversity

Thanks
Suresh



From david.black@emc.com  Tue Jun 18 10:28:44 2013
Return-Path: <david.black@emc.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 A1C5811E80E3; Tue, 18 Jun 2013 10:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hFsFab+5vvBv; Tue, 18 Jun 2013 10:28:39 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4725111E80E6; Tue, 18 Jun 2013 10:28:38 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IHSaXR016150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jun 2013 13:28:37 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Tue, 18 Jun 2013 13:28:19 -0400
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IHSIKd002504; Tue, 18 Jun 2013 13:28:18 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Tue, 18 Jun 2013 13:28:17 -0400
From: "Black, David" <david.black@emc.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
Date: Tue, 18 Jun 2013 13:28:17 -0400
Subject: RE: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQAAClxl4A==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com>
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 18 Jun 2013 14:56:53 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <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: Tue, 18 Jun 2013 17:28:44 -0000

> [Joe]  I'm trying to get a handle on the attack mechanism here.   In this
> attack a valid network service is trying to spoof an application service?
> Since it knows the MSK it can do this if the channel-binding of the lower=
-
> layer into the EAP conversation is not enforced.  If the AAA server alway=
s
> enforces channel bindings for applications then it will catch the spoofin=
g
> attempt.   The reverse case may also be an issue where an application ser=
vice
> is trying to spoof a network service.

While both cases appear to be relevant, my concern started from the reverse
case - here's the draft's text describing the attack:

   One
   potentially serious attack exists when channel binding is not
   required and EAP authentication is introduced into an existing non-
   network service.  A device can be created that impersonates a Network
   Access Service to peers, but actually proxies the authentication to
   the new application service that accepts EAP authentications.  This
   may decrease the security of this service even for users who
   previously used non-EAP means of authentication to the service.

> In this case, if the AAA server
> validates that the application channel binding is not present then it can
> prevent the spoofing.  However the server MUST understand channel binding=
s
> even if the peers do not.   I think the document did try to capture this =
in
> the following sentence:
>=20
> "If the EAP server is aware that authentication is
>    for something other than a network service, it too MUST default to
>    requiring channel binding."
>=20
> I think we could state this a bit better as something like:
>=20
> "In environments where EAP is used for applications authentication and ne=
twork
> access authentication all EAP servers MUST understand channel bindings an=
d
> require that application bindings MUST be present in application
> authentication and that application bindings MUST be absent in network
> authentication.   All network access EAP peer implementations SHOULD supp=
ort
> channel binding to explicitly identify the reason for authentication.  An=
y new
> usage of EAP MUST support channel bindings to prevent confusion with netw=
ork
> access usage. "

That text is an improvement, and it's headed in the same direction as Sam's
comment - "application bindings MUST be present in application authenticati=
on"
is a "MUST use" requirement, not just a "MUST implement" requirement.

OTOH, I'm not clear on what "application bindings" means, as that term's no=
t
in the current draft.  Specifically, I'm a bit unclear on "application bind=
ings
MUST be absent in network authentication" - does that mean that channel
binding must be absent, or that channel binding is optional, but if channel
binding is present, it MUST NOT be an "application binding", whatever that =
is?

Thanks,
--David

> -----Original Message-----
> From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]
> Sent: Tuesday, June 18, 2013 1:10 PM
> To: Sam Hartman
> Cc: Black, David; stefan.winter@restena.lu; General Area Review Team;
> abfab@ietf.org; ietf@ietf.org
> Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-=
03
>=20
>=20
> On Jun 18, 2013, at 7:18 AM, Sam Hartman <hartmans@painless-security.com>
>  wrote:
>=20
> >>>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
> >
> >    Black,> The next to last paragraph on p.3 begins with this sentence:
> >
> >    Black,>    For these reasons, channel binding MUST be implemented by
> >    Black,> peers, EAP servers and AAA servers in environments where EAP
> >    Black,> authentication is used to access application layer services.
> >
> >    Black,> It appear that this "MUST" requirement applies to all uses
> >    Black,> of EAP, including network access authentication, not just
> >    Black,> application layer access authentication.  If so, that's not
> >    Black,> immediately obvious from the text, and an additional
> >    Black,> sentence should be added to make this clearer.  If not, the
> >    Black,> above sentence needs to exclude network access
> >    Black,> authentication from that requirement.
> >
> >
> > I know you're correct that AAA servers and EAP servers need to implemen=
t
> > channel binding for network access in such environments.
> > I'm not sure whether peers only doing network access SHOULD implement
> > channel binding or MUST implement channel binding.
> >
> > Practically speaking, it will be a while before peers implement channel
> > binding for network access.
> > The sorts of attacks that result without channel binding are attacks
> > where a peer thinks it is doing network access authentication but what
> > it's really doing is helping an attacker access an application.
> > If all the application access peers support channel binding, then you
> > could potentially require the eap-lower-layer attribute or similar for
> > application authentication and work securely in environments where peer=
s
> > for network access have not been updated yet.
>=20
> [Joe]  I'm trying to get a handle on the attack mechanism here.   In this
> attack a valid network service is trying to spoof an application service?
> Since it knows the MSK it can do this if the channel-binding of the lower=
-
> layer into the EAP conversation is not enforced.  If the AAA server alway=
s
> enforces channel bindings for applications then it will catch the spoofin=
g
> attempt.   The reverse case may also be an issue where an application ser=
vice
> is trying to spoof a network service.   In this case, if the AAA server
> validates that the application channel binding is not present then it can
> prevent the spoofing.  However the server MUST understand channel binding=
s
> even if the peers do not.   I think the document did try to capture this =
in
> the following sentence:
>=20
> "If the EAP server is aware that authentication is
>    for something other than a network service, it too MUST default to
>    requiring channel binding."
>=20
> I think we could state this a bit better as something like:
>=20
> "In environments where EAP is used for applications authentication and ne=
twork
> access authentication all EAP servers MUST understand channel bindings an=
d
> require that application bindings MUST be present in application
> authentication and that application bindings MUST be absent in network
> authentication.   All network access EAP peer implementations SHOULD supp=
ort
> channel binding to explicitly identify the reason for authentication.  An=
y new
> usage of EAP MUST support channel bindings to prevent confusion with netw=
ork
> access usage. "
>=20
>=20
>=20
> > It's also kind of tempting to stick our head in the sand and just add
> > the clarification that "yes, we mean network access too."
> >
> > --Sam
>=20


From david.black@emc.com  Tue Jun 18 12:35:26 2013
Return-Path: <david.black@emc.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 74DA421E80C1; Tue, 18 Jun 2013 12:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 qwUFxhG5gcMO; Tue, 18 Jun 2013 12:35:21 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5A18B21E80C0; Tue, 18 Jun 2013 12:35:17 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IJZGCe028823 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jun 2013 15:35:16 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Tue, 18 Jun 2013 15:34:57 -0400
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IJYhuw023324; Tue, 18 Jun 2013 15:34:55 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub26.corp.emc.com ([10.254.110.182]) with mapi; Tue, 18 Jun 2013 15:34:45 -0400
From: "Black, David" <david.black@emc.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
Date: Tue, 18 Jun 2013 15:34:44 -0400
Subject: RE: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQAAClxl4P//t2GAgAA80uA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71298265300@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com>
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 18 Jun 2013 14:56:53 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <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: Tue, 18 Jun 2013 19:35:26 -0000

> [Joe] Good points, the text can be more specific:
>=20
> "In environments where EAP is used for purposes other than network access
> authentication all EAP servers MUST enforce channel bindings.  For applic=
ation
> authentication, the EAP server MUST require that the correct EAP lower-la=
yer
> attribute be present in the channel binding data.   For network access
> authentication, the EAP server MUST require that if channel bindings are
> present they MUST contain the correct EAP lower-layer attribute.   All ne=
twork
> access EAP peer implementations SHOULD use channel bindings including the=
 EAP
> lower-layer attribute to explicitly identify the reason for authenticatio=
n.
> Any new usage of EAP MUST use channel bindings including the EAP lower-la=
yer
> attribute to prevent confusion with network access usage. "

This is looking good, modulo Sam's comment on EAP lower-layer vs. something
else that I'll leave to you and he to sort out.  I have a suggested rewrite=
,
mostly to clarify MUST vs. SHOULD requirements for support vs. usage, and
to reformat into a structured bullet list of requirements (this is not
intended to change any requirements from what you wrote):

"In environments where EAP is used for purposes other than network access
authentication:

	o All EAP servers and all application access EAP peers MUST
		support channel bindings.  All network access EAP peers
		SHOULD support channel bindings.

	o Channel binding MUST be used for all application authentication.
		The EAP server MUST require that the correct EAP lower-layer
		attribute be present in the channel binding data for
		application authentication.

	o Channel binding SHOULD be used for all network access authentication,
		and when channel binding data is present, the EAP server MUST
		require that it contain the correct EAP lower-layer attribute
		to explicitly identify the reason for authentication.

	o Any new usage of EAP MUST use channel bindings including the
		EAP lower-layer attribute to prevent confusion with network
		access usage."

Thanks,
--David


> -----Original Message-----
> From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]
> Sent: Tuesday, June 18, 2013 1:47 PM
> To: Black, David
> Cc: stefan.winter@restena.lu; General Area Review Team; abfab@ietf.org;
> ietf@ietf.org
> Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-=
03
>=20
> >>
> >> I think we could state this a bit better as something like:
> >>
> >> "In environments where EAP is used for applications authentication and=
 network
> >> access authentication all EAP servers MUST understand channel bindings=
 and
> >> require that application bindings MUST be present in application
> >> authentication and that application bindings MUST be absent in network
> >> authentication.   All network access EAP peer implementations SHOULD s=
upport
> >> channel binding to explicitly identify the reason for authentication. =
 Any new
> >> usage of EAP MUST support channel bindings to prevent confusion with n=
etwork
> >> access usage. "
> >
> > That text is an improvement, and it's headed in the same direction as S=
am's
> > comment - "application bindings MUST be present in application authenti=
cation"
> > is a "MUST use" requirement, not just a "MUST implement" requirement.
> >
> > OTOH, I'm not clear on what "application bindings" means, as that term'=
s not
> > in the current draft.  Specifically, I'm a bit unclear on "application =
bindings
> > MUST be absent in network authentication" - does that mean that channel
> > binding must be absent, or that channel binding is optional, but if cha=
nnel
> > binding is present, it MUST NOT be an "application binding", whatever t=
hat
> is?
> >
>=20
> [Joe] Good points, the text can be more specific:
>=20
> "In environments where EAP is used for purposes other than network access
> authentication all EAP servers MUST enforce channel bindings.  For applic=
ation
> authentication, the EAP server MUST require that the correct EAP lower-la=
yer
> attribute be present in the channel binding data.   For network access
> authentication, the EAP server MUST require that if channel bindings are
> present they MUST contain the correct EAP lower-layer attribute.   All ne=
twork
> access EAP peer implementations SHOULD use channel bindings including the=
 EAP
> lower-layer attribute to explicitly identify the reason for authenticatio=
n.
> Any new usage of EAP MUST use channel bindings including the EAP lower-la=
yer
> attribute to prevent confusion with network access usage. "
>=20
> Does this help?
>=20
> Thanks,
>=20
> Joe
>=20


From hallam@gmail.com  Tue Jun 18 15:23:43 2013
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 9FBAD11E8115 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 15:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093,  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 hmk2m4Pn7rt8 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 15:23:41 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 890F311E8113 for <ietf@ietf.org>; Tue, 18 Jun 2013 15:23:41 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id y10so58645wgg.4 for <ietf@ietf.org>; Tue, 18 Jun 2013 15:23:36 -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=Lm4cS/e6DCmYgHPz/lBlbAn2Visyf+EKzyLzINSiOD4=; b=WtLQgNUzbDonR4L7MMKrCCuKeDThAEqpPNGtz/owmW2LRDSZEjwFuXuWFsP5Mhk+VG CG1t28dT1vuQ5pZfD0sbswqblLGgHtSptqhHjqiahu6ivHI55CExCN2drl9c/E3b4jep 5mCyPi9i3pYLWJ+Y81KT/G5gBZ5TFurahUewFdm7YKgMGIvOu2SgiZ9r6PRk0s21UQ6w HZkAxJUoHIBLbd8OT4Xe/n0UDQmBcN6DkIcNld5Vzaqyqefa9eue+Y7f8S2hqJI3F2C8 Maomd2T1AGktLd6e88oyMrG+a65fu+4ci4eq3EmAlyiVRCc+HgnGIQQbzCXtiamOIDbT C9GA==
MIME-Version: 1.0
X-Received: by 10.180.206.77 with SMTP id lm13mr8841669wic.18.1371594216811; Tue, 18 Jun 2013 15:23:36 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Tue, 18 Jun 2013 15:23:36 -0700 (PDT)
In-Reply-To: <51C0AC0C.70002@cs.tcd.ie>
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <51C0AA04.4020508@stpeter.im> <51C0AC0C.70002@cs.tcd.ie>
Date: Tue, 18 Jun 2013 18:23:36 -0400
Message-ID: <CAMm+Lwjjh64bq8PMLhUNbL0YtPRN7_8eGR_rEELfqbRz_MTtrw@mail.gmail.com>
Subject: Re: IETF Diversity
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=001a11c380ae11b30104df752aef
Cc: 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: Tue, 18 Jun 2013 22:23:43 -0000

--001a11c380ae11b30104df752aef
Content-Type: text/plain; charset=ISO-8859-1

I am getting my ietf@ietf.org on my gmail account.

I have no filters that delete mail, no mails with 'ietf' in them in my spam
folder and no copies of 80% of the mails to this list.


On Tue, Jun 18, 2013 at 2:50 PM, Stephen Farrell
<stephen.farrell@cs.tcd.ie>wrote:

>
>
> On 06/18/2013 07:42 PM, Peter Saint-Andre wrote:
> > On 6/18/13 12:08 PM, Phillip Hallam-Baker wrote:
> >
> >> The issue was raised in the IETF plenary I would have expected mention
> >> of a followup mailing list to be made here on the ietf discussion list.
> >
> > Fair enough.
>
> Not quite. My local ietf@ietf.org folder has 392 messages that
> match a search for "diversity" all but of few of which are since
> this March, e.g. most recently before this thread [1].
>
> There is a lot of noise on this list so I can understand that
> threads might be missed but its not true to say there's been
> nothing on here.
>
> S.
>
> [1] http://www.ietf.org/mail-archive/web/ietf/current/msg80076.html
>
>
> >
> > Peter
> >
>



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

--001a11c380ae11b30104df752aef
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am getting my <a href=3D"mailto:ietf@ietf.org">ietf@ietf=
.org</a> on my gmail account.<div><br></div><div style>I have no filters th=
at delete mail, no mails with &#39;ietf&#39; in them in my spam folder and =
no copies of 80% of the mails to this list.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue,=
 Jun 18, 2013 at 2:50 PM, Stephen Farrell <span dir=3D"ltr">&lt;<a href=3D"=
mailto:stephen.farrell@cs.tcd.ie" target=3D"_blank">stephen.farrell@cs.tcd.=
ie</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
<br>
On 06/18/2013 07:42 PM, Peter Saint-Andre wrote:<br>
&gt; On 6/18/13 12:08 PM, Phillip Hallam-Baker wrote:<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt; The issue was raised in the IETF plenary I=
 would have expected mention<br>
&gt;&gt; of a followup mailing list to be made here on the ietf discussion =
list.<br>
&gt;<br>
&gt; Fair enough.<br>
<br>
</div>Not quite. My local <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a=
> folder has 392 messages that<br>
match a search for &quot;diversity&quot; all but of few of which are since<=
br>
this March, e.g. most recently before this thread [1].<br>
<br>
There is a lot of noise on this list so I can understand that<br>
threads might be missed but its not true to say there&#39;s been<br>
nothing on here.<br>
<br>
S.<br>
<br>
[1] <a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg80076.h=
tml" target=3D"_blank">http://www.ietf.org/mail-archive/web/ietf/current/ms=
g80076.html</a><br>
<br>
<br>
&gt;<br>
&gt; Peter<br>
&gt;<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Website: <a =
href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div>

--001a11c380ae11b30104df752aef--

From dwm@xpasc.com  Tue Jun 18 15:50:35 2013
Return-Path: <dwm@xpasc.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 DD56321E809B for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 15:50:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.071
X-Spam-Level: 
X-Spam-Status: No, score=-3.071 tagged_above=-999 required=5 tests=[AWL=-1.764, BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 fFs1VYeAzESw for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 15:50:30 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 8A75811E80E1 for <ietf@ietf.org>; Tue, 18 Jun 2013 15:50:26 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 4DEDC3F7D5 for <ietf@ietf.org>; Tue, 18 Jun 2013 22:50:24 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id r5IMoORH027496 for <ietf@ietf.org>; Tue, 18 Jun 2013 15:50:24 -0700
Date: Tue, 18 Jun 2013 15:50:24 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: IETF Diversity
In-Reply-To: <CAMm+Lwjjh64bq8PMLhUNbL0YtPRN7_8eGR_rEELfqbRz_MTtrw@mail.gmail.com>
Message-ID: <alpine.LRH.2.01.1306181548310.26747@egate.xpasc.com>
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <51C0AA04.4020508@stpeter.im> <51C0AC0C.70002@cs.tcd.ie> <CAMm+Lwjjh64bq8PMLhUNbL0YtPRN7_8eGR_rEELfqbRz_MTtrw@mail.gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.87-g7939dec
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: Tue, 18 Jun 2013 22:50:36 -0000

On Tue, 18 Jun 2013, Phillip Hallam-Baker wrote:

> I am getting my ietf@ietf.org on my gmail account.
> 
> I have no filters that delete mail, no mails with 'ietf' in them in my spam
> folder and no copies of 80% of the mails to this list.

That reads like you are missing 80% of the email distributed via this
list? That somehow, you are missing many emails w/o your filters
being responsible?

From aservin@lacnic.net  Tue Jun 18 19:24:08 2013
Return-Path: <aservin@lacnic.net>
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 0587521F99A6 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 19:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.226
X-Spam-Level: 
X-Spam-Status: No, score=0.226 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HOST_EQ_STATIC=1.172]
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 nxf2cXrjBguD for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 19:23:57 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 08D8321F999A for <ietf@ietf.org>; Tue, 18 Jun 2013 19:23:56 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (110-170-171-184.static.asianet.co.th [110.170.171.184]) by mail.lacnic.net.uy (Postfix) with ESMTP id B7FE830848D; Tue, 18 Jun 2013 23:23:29 -0300 (UYT)
Message-ID: <51C1162B.4040606@lacnic.net>
Date: Wed, 19 Jun 2013 09:23:39 +0700
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: IETF Diversity
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <A5AD378E-0497-42C2-A6BA-BCBFCC9F9691@piuha.net> <51C0A4D2.9020106@dcrocker.net>
In-Reply-To: <51C0A4D2.9020106@dcrocker.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: 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, 19 Jun 2013 02:24:08 -0000

Dave,

    We created an IETF-TF in LACNOG; as you we also think that only a
meeting is not enough and along with ISOC, ccTLDs, LACNIC and other
organizations we are trying to encourage and prepare more people to
participate in the IETF by sending comments, reviewing documents and
writing RFCs. There are some specific actions that we are doing to
fulfill that goal (I can give more details if somebody is wanted to know).

    As Jari pointed out, the results are not immidiately but we are
working on that.

    If interested, anybody can subscribe at:

https://mail.lacnic.net/mailman/listinfo/ietf-lac

Regards,
as


On 6/19/13 1:20 AM, Dave Crocker wrote:
> On 6/18/2013 10:17 AM, Jari Arkko wrote:
>>     Second, the IAOC has
>> looked hard at the possibilities for reaching further out in the
>> geographical world
>
>
> Jari,
>
> The only action that's been cited has been holding a meeting in that
> region.  A number of us have posted comments suggesting that this is
> unlikely to be an effective recruiting technique; a few also offered
> thoughts of other approaches.  I won't rehash the rationales that have
> been offered.
>
> If other avenues of recruiting are being explored by the IAOC, what
> are they?
>
> If the only avenue being considered is a meeting in the region, it
> would be helpful to see some response to the concerns raised about
> this as a recruiting tool.
>
>
> d/
>


From yding@cs.helsinki.fi  Tue Jun 18 23:13:56 2013
Return-Path: <yding@cs.helsinki.fi>
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 2C00421F9D7B for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 23:13:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 7v-hb-mh2IG0 for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 23:13:51 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76BFD21F9D72 for <ietf@ietf.org>; Tue, 18 Jun 2013 23:13:50 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Wed Jun 19 09:13:33 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type; s=dkim20130528; bh=EwAX/T2pwZuqKbO/Ey TA4AK9ozIorUXN2dN96KuYrgI=; b=H+/HNbOGzPXq7b4XUxqQ8lIMpws/wTRbZv M/gt/qTENIqYne+nPe4W2W7bnN8glrlrO03NjfGxPpwx8efifXtWMzQIJh+jhkB5 JHMiWS/sz3SJ3eKOnnQ/2P/reFsyaODxexSf/uzNjYCXep58FJSLuV5bPcDFk4ZX oaZ88E/KE=
Received: from [192.168.1.100] (host-94-101-2-100.igua.fi [94.101.2.100]) (AUTH: PLAIN yding, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Wed, 19 Jun 2013 09:13:33 +0300 id 00068AB4.51C14C0D.0000783F
Message-ID: <51C14C06.1060207@cs.helsinki.fi>
Date: Wed, 19 Jun 2013 09:13:26 +0300
From: Aaron Yi DING <yding@cs.helsinki.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IETF Diversity
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com>
In-Reply-To: <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000906050807020607080502"
Cc: 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, 19 Jun 2013 06:13:56 -0000

This is a multi-part message in MIME format.
--------------000906050807020607080502
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 18/06/13 21:08, Phillip Hallam-Baker wrote:
> When I make a statement at the microphone and then have multiple 
> people come to thank me afterwards for making that point I don't 
> consider it pontificating.
>


sorry, just point it out, sometimes you said it right, but that does not 
guarantee you are always right. to correct and make it clearer, "when 
... made a statement, ... people came to thank"  for past experience, no 
present tense please.

no further comment, since I actually appreciate what you said and the 
intention, as you described below.

-- Aaron

> I do however consider your own response to be an example of the type 
> of exclusionary behavior that I was talking about. Dismissing those 
> concerns as 'pontificating' does not help matters. And you have no 
> idea what actions I have taken to attempt to recruit people to get 
> involved.
>
> The issue was raised in the IETF plenary I would have expected mention 
> of a followup mailing list to be made here on the ietf discussion list.
>
>
>
>
> On Tue, Jun 18, 2013 at 1:09 PM, Peter Saint-Andre <stpeter@stpeter.im 
> <mailto:stpeter@stpeter.im>> wrote:
>
>     On 6/18/13 10:52 AM, Phillip Hallam-Baker wrote:
>     > I am rather disappointed that there hasn't been any followup to the
>     > diversity discussion that took place at the plenary.
>
>     Speak for yourself. Some of us are taking concrete actions (e.g.,
>     recruiting people for document shepherd and WG chair roles) instead of
>     pontificating at the mic.
>
>     Peter
>
>     --
>     Peter Saint-Andre
>     https://stpeter.im/
>
>
>
>
>
> -- 
> Website: http://hallambaker.com/


--------------000906050807020607080502
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 18/06/13 21:08, Phillip Hallam-Baker
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com"
      type="cite">
      <div dir="ltr">When I make a statement at the microphone and then
        have multiple people come to thank me afterwards for making that
        point I don't consider it pontificating.
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    sorry, just point it out, sometimes you said it right, but that does
    not guarantee you are always right. to correct and make it clearer,
    "when ... made a statement, ... people came to thank"&nbsp; for past
    experience, no present tense please. <br>
    <br>
    no further comment, since I actually appreciate what you said and
    the intention, as you described below.<br>
    <br>
    -- Aaron<br>
    <br>
    <blockquote
cite="mid:CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div style="">I do however consider your own response to be an
          example of the type of exclusionary behavior that I was
          talking about. Dismissing those concerns as 'pontificating'
          does not help matters. And you have no idea what actions I
          have taken to attempt to recruit people to get involved.&nbsp;</div>
        <div style=""><br>
        </div>
        <div style="">The issue was raised in the IETF plenary I would
          have expected mention of a followup mailing list to be made
          here on the ietf discussion list.&nbsp;</div>
        <div style=""><br>
        </div>
        <div style=""><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Tue, Jun 18, 2013 at 1:09 PM, Peter
          Saint-Andre <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:stpeter@stpeter.im" target="_blank">stpeter@stpeter.im</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div class="im">On 6/18/13 10:52 AM, Phillip Hallam-Baker
              wrote:<br>
              &gt; I am rather disappointed that there hasn't been any
              followup to the<br>
              &gt; diversity discussion that took place at the plenary.<br>
              <br>
            </div>
            Speak for yourself. Some of us are taking concrete actions
            (e.g.,<br>
            recruiting people for document shepherd and WG chair roles)
            instead of<br>
            pontificating at the mic.<br>
            <span class="HOEnZb"><font color="#888888"><br>
                Peter<br>
                <br>
                --<br>
                Peter Saint-Andre<br>
                <a moz-do-not-send="true" href="https://stpeter.im/"
                  target="_blank">https://stpeter.im/</a><br>
                <br>
                <br>
              </font></span></blockquote>
        </div>
        <br>
        <br clear="all">
        <div><br>
        </div>
        -- <br>
        Website: <a moz-do-not-send="true"
          href="http://hallambaker.com/">http://hallambaker.com/</a><br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------000906050807020607080502--

From paf@frobbit.se  Tue Jun 18 23:25:12 2013
Return-Path: <paf@frobbit.se>
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 2960321F9EAF for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 23:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 d7Nr9zf4iu3o for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 23:25:11 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id A3E7321F9EAD for <ietf@ietf.org>; Tue, 18 Jun 2013 23:25:11 -0700 (PDT)
Received: from [IPv6:2a01:3f0:1::95cc:691e:3338:5ca2] (unknown [IPv6:2a01:3f0:1:0:95cc:691e:3338:5ca2]) by mail.frobbit.se (Postfix) with ESMTPSA id C6870219D6; Wed, 19 Jun 2013 08:25:10 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
Date: Wed, 19 Jun 2013 08:25:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1508)
Cc: John C Klensin <john-ietf@jck.com>, ietf <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, 19 Jun 2013 06:25:12 -0000

On 18 jun 2013, at 18:54, Jari Arkko <jari.arkko@piuha.net> wrote:

> As for the rest of the discussion - I'm sure there are things to be =
improved in ICANN. I'd suggest though that some of the feedback might be =
better placed in an ICANN discussion than on IETF list. And is not like =
there'd be nothing to improve on our side :-) Lets focus on IETF aspects =
here.

I think this is the correct strategy, BUT, I see as a very active =
participant in ICANN (chair of SSAC) that work in ICANN could be easier =
if some "more" technical standards where developed in IETF, and moved =
forward along standards track, that ICANN can reference. Same with some =
epp-related issues, and also DNS-related, which I must admit I think has =
stalled in the IETF. When that happens, ICANN start to "invent" or at =
least discuss IETF related issues -- which I think is non optimal. But =
on the other hand, if IETF do not move forward, then what should ICANN =
do?

I will btw be the first few days (until including Tuesday or so) at IETF =
in Berlin and am happy to discuss this issue with anyone interested.

   Patrik F=E4ltstr=F6m
   Chair SSAC, ICANN


From sm@resistor.net  Wed Jun 19 02:15:42 2013
Return-Path: <sm@resistor.net>
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 708C121F9FC0 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 02:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.365
X-Spam-Level: 
X-Spam-Status: No, score=-102.365 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 tTyo6PUo5bbV for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 02:15:41 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A036A21F9FA7 for <ietf@ietf.org>; Wed, 19 Jun 2013 02:15:41 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5J9FS8V016073; Wed, 19 Jun 2013 02:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1371633335; bh=c5h/+VT1QS/eKiH5xm3G41nBvRo7Jl+6ef/9jww1SAM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cNq6DENqzMT65SxTGMBu6u78zhCXJ8XSOWJwAzWPiwNr+sblMgQH8h/j2hqJ/lk1Z 1BKqYZ/9+AQ+4WaGfbydPgEPl1700w8LHcLYjuwU64jSvKylLE4Nor8H2ZpTO+upY9 wOkFvSVgv3XYnUiC3uTAyfPhft+RgZRShAOvmEn4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1371633335; i=@resistor.net; bh=c5h/+VT1QS/eKiH5xm3G41nBvRo7Jl+6ef/9jww1SAM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pHV+nL/4DzVGoSVSWgfWQz1xjbnPOC1UU9tK0Hfy1endPkVJSNmWMhIGtHJLS8j1+ AJoMSLtsnDhyF6kAVifGmzSKfKx7rIMUHBRA71B+nU+bBsqR1onmOCg6tw+7moTfBn JYZd7uFbmBbR6HOXtkkhjNBPz2ohkcnah7lR4aAA=
Message-Id: <6.2.5.6.2.20130619000239.0b0ebd38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 19 Jun 2013 01:59:28 -0700
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
From: SM <sm@resistor.net>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
In-Reply-To: <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: John C Klensin <john-ietf@jck.com>, ietf <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, 19 Jun 2013 09:15:42 -0000

Hi Patrik,
At 23:25 18-06-2013, Patrik F=E4ltstr=F6m wrote:
>I think this is the correct strategy, BUT, I see=20
>as a very active participant in ICANN (chair of=20
>SSAC) that work in ICANN could be easier if some=20
>"more" technical standards where developed in=20
>IETF, and moved forward along standards track,=20
>that ICANN can reference. Same with some=20
>epp-related issues, and also DNS-related, which=20
>I must admit I think has stalled in the IETF.=20
>When that happens, ICANN start to "invent" or at=20
>least discuss IETF related issues -- which I=20
>think is non optimal. But on the other hand, if=20
>IETF do not move forward, then what should ICANN do?

I'll highlight part of a comment from Steve Crocker:

    (I sometimes have to explain to my colleagues at ICANN who have not had=
 the
    benefit of the IETF experience that "let's=20
send it over to the IETF" doesn't
    work.  The IETF isn't a standing army ready=20
to do ours or anyone else's work.
    Rather, I say, it's a place where the=20
relevant people can get together to get
    their work done.

It is easy to see why there isn't significant=20
progress about DNS-related issues in the=20
IETF.  If nobody volunteers to do the work the=20
work does not get done.  Whether the problems are=20
acute enough to require surgery is not for me to decide.

The ITU does work as the IETF does not show=20
interest in doing that work when it had the=20
opportunity to do so.  I would not worry too much=20
about ICANN inventing as, to quote John Klensin:

   I don't know whether that is because they don't have time to write=
 shorter
   reports or because they don't think the subject matter can be covered in
   more concise reports, but the pattern is clear,   When those committees
   cannot agree or discover the issues are, in fact, contentious, they
   typically recommend the creation of more committees.

Sometimes people either do not see the problems=20
or pretend not to see them (I am not inferring=20
that you do that).  In the latter case I would be=20
asked to explain why I think the problem is a=20
problem when I mention it.  I am somewhat=20
suspicious when people who have much more experience than me do that. :-)

I don't know whether you have been following the=20
URNbis discussions.  That WG had leisurely=20
discussions about the drafts since over three=20
years.  It has not been able to publish a single=20
RFC.  DNSEXT has been in shutdown mode since over=20
a year.  The call for adoption of a draft in=20
DNSOP failed as there wasn't significant interest=20
within the working group to do that work.

I'll ask a question to the other persons=20
subscribed to this mailing list.  Are there other=20
active participants in ICANN interested in doing work in the IETF?

Regards,
-sm=20


From paf@frobbit.se  Wed Jun 19 02:27:58 2013
Return-Path: <paf@frobbit.se>
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 287B721F9D86 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 02:27:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 qu4NqVFOs3ri for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 02:27:52 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 226E221F9D50 for <ietf@ietf.org>; Wed, 19 Jun 2013 02:27:51 -0700 (PDT)
Received: from [IPv6:2a01:3f0:1::855f:3877:442b:8adf] (unknown [IPv6:2a01:3f0:1:0:855f:3877:442b:8adf]) by mail.frobbit.se (Postfix) with ESMTPSA id 6F2E722036; Wed, 19 Jun 2013 11:27:50 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <6.2.5.6.2.20130619000239.0b0ebd38@resistor.net>
Date: Wed, 19 Jun 2013 11:27:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DACC4421-03B2-4F64-856C-FF3080B587AE@frobbit.se>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <6.2.5.6.2.20130619000239.0b0ebd38@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1508)
Cc: John C Klensin <john-ietf@jck.com>, ietf <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, 19 Jun 2013 09:27:58 -0000

On 19 jun 2013, at 10:59, SM <sm@resistor.net> wrote:

> I'll highlight part of a comment from Steve Crocker:
>=20
>   (I sometimes have to explain to my colleagues at ICANN who have not =
had the
>   benefit of the IETF experience that "let's send it over to the IETF" =
doesn't
>   work.  The IETF isn't a standing army ready to do ours or anyone =
else's work.
>   Rather, I say, it's a place where the relevant people can get =
together to get
>   their work done.
>=20
> It is easy to see why there isn't significant progress about =
DNS-related issues in the IETF.  If nobody volunteers to do the work the =
work does not get done.  Whether the problems are acute enough to =
require surgery is not for me to decide.

Correct, and this is a/the weakness of both IETF and ICANN. And to some =
degree there might be parties that see the lack of progress as a good =
thing...

> The ITU does work as the IETF does not show interest in doing that =
work when it had the opportunity to do so.  I would not worry too much =
about ICANN inventing as, to quote John Klensin:
>=20
>  I don't know whether that is because they don't have time to write =
shorter
>  reports or because they don't think the subject matter can be covered =
in
>  more concise reports, but the pattern is clear,   When those =
committees
>  cannot agree or discover the issues are, in fact, contentious, they
>  typically recommend the creation of more committees.

This is one pattern, correct. And lack of RFCs is one of the reasons =
"more committees" is an attractive tool.

I am not saying this is the only issue, I see it is one of them.

Take (lack of) progress of draft-liman-tld-names for example.

The need for this draft is in the ICANN context, not the IETF context, =
so of course it is hard to see the need in the IETF. Lack of an RFC =
there is by definition creating discussions in ICANN that goes on and =
on.

And do not let me get started on EPP or Whois issues... ;-)

> Sometimes people either do not see the problems or pretend not to see =
them (I am not inferring that you do that).  In the latter case I would =
be asked to explain why I think the problem is a problem when I mention =
it.  I am somewhat suspicious when people who have much more experience =
than me do that. :-)

The need is in ICANN, not in the IETF.

That I see is the largest problem. Individuals then spending time in =
ICANN do not, although they see the need, participate in the IETF, or do =
not know how to participate, or fails to express the need/problem =
statement in IETF.

> I don't know whether you have been following the URNbis discussions.

Oh yes! As one of the editors of the first URN documents, I have sort of =
a "hobby" to follow that :-P

> That WG had leisurely discussions about the drafts since over three =
years. It has not been able to publish a single RFC.  DNSEXT has been in =
shutdown mode since over a year.  The call for adoption of a draft in =
DNSOP failed as there wasn't significant interest within the working =
group to do that work.

That is one of the problems for IETF. "Can not say yes" to something, =
while it seems (if I exaggerate) ITU and ICANN "Can not say no" to =
things.

> I'll ask a question to the other persons subscribed to this mailing =
list.  Are there other active participants in ICANN interested in doing =
work in the IETF?

  Patrik


From hallam@gmail.com  Wed Jun 19 04:45:00 2013
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 1BA5D21F9A7A for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 04:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  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 jZYOj74x-9xd for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 04:44:59 -0700 (PDT)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3AB21F9C06 for <ietf@ietf.org>; Wed, 19 Jun 2013 04:44:57 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id e11so4470152wgh.30 for <ietf@ietf.org>; Wed, 19 Jun 2013 04:44:56 -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=N/h+hqLBixh+1If6gsiPlSivR4bABA7SJejYJggfdfQ=; b=IRKhzF92/Pmo/EuDr9C87+gDlQRqEf2WV46wJhAIvo4oSVkpl1IEsE7GjrLuPpBxvu o9X5VcTkF531g3QCrjg7UmuFy6TeX+ou1CWp8dH6B9p421wFKhEzJXn76Dtl96fXah0r DBhOggZuRy1Z1ANpcT2UROusIrgPnjts4df4+o/HXTCbIJBI6tecrVcddEfETDsBWMWd nnlQp1fb5NWkrG2EYlARbddJREbVuLi/Cfk1LDU71JpFWffa8/yrSZMDxfs/lmeE3Dz6 VESlc/9K7ASGHteqjynaOOX6HLRYHVc34AToaOaVe4PK053iQLS155lQScQ32RtEnFn+ EoaQ==
MIME-Version: 1.0
X-Received: by 10.180.9.242 with SMTP id d18mr10632691wib.18.1371642296594; Wed, 19 Jun 2013 04:44:56 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Wed, 19 Jun 2013 04:44:56 -0700 (PDT)
In-Reply-To: <51C14C06.1060207@cs.helsinki.fi>
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi>
Date: Wed, 19 Jun 2013 07:44:56 -0400
Message-ID: <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com>
Subject: Re: IETF Diversity
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Aaron Yi DING <yding@cs.helsinki.fi>
Content-Type: multipart/alternative; boundary=001a11c2228cd8f92404df805baf
Cc: 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, 19 Jun 2013 11:45:00 -0000

--001a11c2228cd8f92404df805baf
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jun 19, 2013 at 2:13 AM, Aaron Yi DING <yding@cs.helsinki.fi> wrote:

>  On 18/06/13 21:08, Phillip Hallam-Baker wrote:
>
> When I make a statement at the microphone and then have multiple people
> come to thank me afterwards for making that point I don't consider it
> pontificating.
>
>
>
> sorry, just point it out, sometimes you said it right, but that does not
> guarantee you are always right. to correct and make it clearer, "when ...
> made a statement, ... people came to thank"  for past experience, no
> present tense please.
>
> no further comment, since I actually appreciate what you said and the
> intention, as you described below.
>


It is hard to encourage, much easier to discourage. I thought Peter's
attempt at a slap down was completely out of line and demonstrates the
problem I am talking about here. Agenda denial is a strategy where to avoid
discussing the topic that you know you have a weak case you suggest a
change of topic.

There is a real problem with accountability and transparency in the IETF
constitution which was designed by a bunch of old boys to maintain control
in their own hands. Peter is a member of the IETF establishment so of
course he sees no structural problem.

What I suggested is that the status quo is going to lead to applications
area work moving to forums outside the IETF. The Jabber folk have already
done this with the XMPP foundation.


I have the greatest of respect for Vint Cerf's technical capabilities but
he consistently failed to establish open and transparent governance
mechanisms.


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

--001a11c2228cd8f92404df805baf
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Jun 19, 2013 at 2:13 AM, Aaron Yi DING <span dir=
=3D"ltr">&lt;<a href=3D"mailto:yding@cs.helsinki.fi" target=3D"_blank">ydin=
g@cs.helsinki.fi</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF"><div class=3D"im">
    <div>On 18/06/13 21:08, Phillip Hallam-Baker
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">When I make a statement at the microphone and then
        have multiple people come to thank me afterwards for making that
        point I don&#39;t consider it pontificating.
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
    <br></div>
    sorry, just point it out, sometimes you said it right, but that does
    not guarantee you are always right. to correct and make it clearer,
    &quot;when ... made a statement, ... people came to thank&quot;=A0 for =
past
    experience, no present tense please. <br>
    <br>
    no further comment, since I actually appreciate what you said and
    the intention, as you described below.</div></blockquote><div><br></div=
><div><br></div><div style>It is hard to encourage, much easier to discoura=
ge. I thought Peter&#39;s attempt at a slap down was completely out of line=
 and demonstrates the problem I am talking about here. Agenda denial is a s=
trategy where to avoid discussing the topic that you know you have a weak c=
ase you suggest a change of topic.=A0</div>
<div style><br></div><div style>There is a real problem with accountability=
 and transparency in the IETF constitution which was designed by a bunch of=
 old boys to maintain control in their own hands. Peter is a member of the =
IETF establishment so of course he sees no structural problem.=A0</div>
<div style><br></div><div style>What I suggested is that the status quo is =
going to lead to applications area work moving to forums outside the IETF. =
The Jabber folk have already done this with the XMPP foundation.</div><div =
style>
<br></div><div style><br></div><div style>I have the greatest of respect fo=
r Vint Cerf&#39;s technical capabilities but he consistently failed to esta=
blish open and transparent governance mechanisms.</div><div><br></div><div =
style>
<br></div></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://=
hallambaker.com/</a><br>
</div></div>

--001a11c2228cd8f92404df805baf--

From tjc@ecs.soton.ac.uk  Wed Jun 19 05:34:16 2013
Return-Path: <tjc@ecs.soton.ac.uk>
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 4342D21F9C24 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 05:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.244
X-Spam-Level: 
X-Spam-Status: No, score=-2.244 tagged_above=-999 required=5 tests=[AWL=0.095,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_OBFU_Z=0.259]
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 zPsHGvyUdz0J for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 05:34:15 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 076BC21F9C1F for <ietf@ietf.org>; Wed, 19 Jun 2013 05:34:12 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r5JCYAVq004784 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:34:10 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r5JCYAVq004784
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1371645250; bh=0cF6bhiMoSSYzwWoE5ppEhIJSuk=; h=From:Subject:Date:To:Mime-Version:References; b=GfYwOdHpF7/p4RvJUfaPBdQGr/I6AltflWmg3j6IiiyGjP6RFH4xFYLAV2SPaIy12 5ai+Ebj/oQuUQlZA4BvePZJnUaw9aVx9TjF4Z3zGpidUH++fB5n4R1mWjDUkkko5vw wyyG4s327Ha8RgHxHVvCoMraEEuCuHEm8glHQmHo=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p5IDYA0430659631pV ret-id none; Wed, 19 Jun 2013 13:34:10 +0100
Received: from dhcp-205-24.wireless.soton.ac.uk (dhcp-205-24.wireless.soton.ac.uk [152.78.205.24]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r5JCY8gk018409 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Wed, 19 Jun 2013 13:34:08 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_112D8C89-E295-4976-89A2-58BAEBA129E1"
Subject: Berlin BoFzilla
Message-ID: <EMEW3|a01d4733cdda5279712aad148367e4dap5IDYA03tjc|ecs.soton.ac.uk|AC2C9C7B-352A-4FE6-8742-5F3B69EC9321@ecs.soton.ac.uk>
Date: Wed, 19 Jun 2013 13:34:14 +0100
To: "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p5IDYA043065963100; tid=p5IDYA0430659631pV; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <AC2C9C7B-352A-4FE6-8742-5F3B69EC9321@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r5JCYAVq004784
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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, 19 Jun 2013 12:34:16 -0000

--Apple-Mail=_112D8C89-E295-4976-89A2-58BAEBA129E1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

So I was looking at http://trac.tools.ietf.org/bof/trac/wiki/WikiStart =
to check the sdnssd BoF text, and was surprised to see a total of 15 =
proposed BoFs. That seems to be something of a record?

That people are coming to the IETF with proposals to do work is probably =
a healthy thing; it would be more worrying if there were no BoFs =
proposed. But if all the proposals are accepted, and they all lead to =
WGs being formed, that's a lot of new groups to be created, scheduled =
and supported.

In contrast, how many WGs have been closed in the past few months? I see =
there's http://trac.tools.ietf.org/wg/concluded from which I can see =
there are 10 WGs listed there which seem to have closed this year:
	iri 2013-01-19
	imapmove 2013-01-31
	csi 2013-02-12
	sipclf 2013-02-20
	bliss 2013-02-27
	simple 2013-02-27
	fecframe 2013-03-06
	krb-wg 2013-03-19
	eai 2013-03-19
	6tch 2013-04-19

I wonder how the volume and lifetimes of WGs has changed over the years, =
e.g. the number we have, how quickly they complete their work, etc. Has =
anyone been looking at this?

Tim=

--Apple-Mail=_112D8C89-E295-4976-89A2-58BAEBA129E1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">So I =
was looking at&nbsp;<a =
href=3D"http://trac.tools.ietf.org/bof/trac/wiki/WikiStart">http://trac.to=
ols.ietf.org/bof/trac/wiki/WikiStart</a>&nbsp;to check the sdnssd BoF =
text, and was surprised to see a total of 15 proposed BoFs. That seems =
to be something of a record?<div><br></div><div>That people are coming =
to the IETF with proposals to do work is probably a healthy thing; it =
would be more worrying if there were no BoFs proposed. But if all the =
proposals are accepted, and they all lead to WGs being formed, that's a =
lot of new groups to be created, scheduled and =
supported.</div><div><br></div><div>In contrast, how many WGs have been =
closed in the past few months? I see there's&nbsp;<a =
href=3D"http://trac.tools.ietf.org/wg/concluded">http://trac.tools.ietf.or=
g/wg/concluded</a>&nbsp;from which I can see there are 10 WGs listed =
there which seem to have closed this year:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>iri =
2013-01-19</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>imapmove =
2013-01-31</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>csi 2013-02-12</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>sipclf =
2013-02-20</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>bliss 2013-02-27</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>simple =
2013-02-27</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>fecframe =
2013-03-06</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>krb-wg 2013-03-19</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>eai =
2013-03-19</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>6tch =
2013-04-19</div><div><br></div><div>I wonder how the volume and =
lifetimes of WGs has changed over the years, e.g. the number we have, =
how quickly they complete their work, etc. Has anyone been looking at =
this?</div><div><br></div><div>Tim</div></body></html>=

--Apple-Mail=_112D8C89-E295-4976-89A2-58BAEBA129E1--

From dave@cridland.net  Wed Jun 19 05:35:32 2013
Return-Path: <dave@cridland.net>
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 95C6721F9C25 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 05:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.962
X-Spam-Level: 
X-Spam-Status: No, score=-1.962 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 y9iVvwprzmS8 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 05:35:30 -0700 (PDT)
Received: from mail-ee0-x22c.google.com (mail-ee0-x22c.google.com [IPv6:2a00:1450:4013:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 982F021F9C19 for <ietf@ietf.org>; Wed, 19 Jun 2013 05:35:29 -0700 (PDT)
Received: by mail-ee0-f44.google.com with SMTP id c13so3133321eek.17 for <ietf@ietf.org>; Wed, 19 Jun 2013 05:35:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=content-type:mime-version:in-reply-to:references:subject:x-mailer :date:message-id:from:to:cc; bh=nj6/SKjyPedrB5aL1mlU8sFC4g5UZ/is8PzKIPkzjM0=; b=AGc0eru6n7tQgDJt7CxMfyEjCDPAAc2nzVjpRA1DUeS+ghcLvMV9YaXPzAD3aTHYhp hoNm+WCQp/B2sdzsc52Z9bCyrmLZ4xFSaYM3Yd/aenjcOIb64B1xEX5WSInKgyBRzvCK dB8jjm74uGFRVXw9hFfruIH4SyAKyC4/GLGv4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:in-reply-to:references:subject:x-mailer :date:message-id:from:to:cc:x-gm-message-state; bh=nj6/SKjyPedrB5aL1mlU8sFC4g5UZ/is8PzKIPkzjM0=; b=U9jfO5y60IZuU5K7/3yQeTbXZQySFyNgRVrKs6p/mfC7Zk8KZwdjVBNh3qHVQS2PRZ q+22ViQGn5XfxfBUiGEC20MIh2BlJGLYasAMIKSvOngusJabBvN1AiXDvqCa0EoRUxv7 Spjs3GR6WStuHXA/jU4OEDrZw9dqazM5LjTpoSTJBXsFpsfM2OjuKDMgjQ9KNjjzHiuX a0ORu+sSob6ioaqB9j/+uRWr96xcFYQ0ykG03O1u0jAhqyNDpxZeYAbhtlgBmKGoVqtp gptxvHovMTLw5mlernb+wQrqxAukKoPtLKrzw5SBH9s0siZbtZ2ge/KiEyT3ZgaTC7ca 98HQ==
X-Received: by 10.15.55.199 with SMTP id v47mr2502851eew.41.1371645328615; Wed, 19 Jun 2013 05:35:28 -0700 (PDT)
Received: from [10.42.211.62] (peirce.dave.cridland.net. [217.155.137.61]) by mx.google.com with ESMTPSA id z52sm36703067eea.1.2013.06.19.05.35.26 for <multiple recipients> (version=TLSv1.1 cipher=RC4-SHA bits=128/128); Wed, 19 Jun 2013 05:35:27 -0700 (PDT)
Content-Type: multipart/alternative; boundary="===============0455933289=="
MIME-Version: 1.0
In-Reply-To: <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>
Subject: Re:  IETF Diversity
X-Mailer: Inky (TM) v1.0.51C0.13CF ("Epoch")
Date: Wed, 19 Jun 2013 12:35:25 -0000
Message-Id: <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: "Phillip Hallam-Baker" <hallam@gmail.com>
X-Gm-Message-State: ALoCoQljVV0A5ah7mT/D3WmCwPdzEvsBi/jL2C7aml+6feaZTgSJWPPKKe7Rvi+DUcxK+/ZF5oGO
Cc: 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, 19 Jun 2013 12:35:32 -0000

--===============0455933289==
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Phillip Hallam-Baker wrote:





There is a real problem with accountability and transparency in the
IETF constitution which was designed by a bunch of old boys to
maintain control in their own hands. Peter is a member of the IETF
establishment so of course he sees no structural problem.

PSA's been an AD, yes, but:







What I suggested is that the status quo is going to lead to
applications area work moving to forums outside the IETF. The Jabber
folk have already done this with the XMPP foundation.

He's also one of the Jabber folk, and indeed Executive Director of the
XSF.

So given these two statements are in conflict, there must be a problem
with them.

I think it's in the implication that the XMPP folk came and looked at
the IETF and decided there was some structural problem. I don't think
that's the case. You'd need to ask someone who was there when it
formed, like Peter, but I suspect it really mutated gradually from an
umbrella organization for open-source software projects, and by the
time anyone realised it was an SDO, then the IETF was already
committed to SIP/SIMPLE (to the point of giving them their own area),
and was in addition happy to cite XEPs and use the technology
operationally.

Dave.


Sent with [inky: <http://inky.com?kme=3Dsignature>]


--===============0455933289==
Content-Type: text/html; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<body><div class=3D"inlined-message" id=3D"message-coda" name=3D"message-co=
da">
	<span class=3D"message-attribution">Phillip Hallam-Baker wrote:</span>
	<div class=3D"quoted" style=3D"border-left: 1px solid black; margin: 0pt 0=
pt 0pt 0.25em; padding-left: 1em; padding-top: 1ex;">
		<div class=3D"sanitized-message">
			<div dir=3D"ltr">
				<div class=3D"gmail_extra">
					<div class=3D"gmail_quote">
						<div>
							There is a real problem with accountability and transparency in the =
IETF constitution which was designed by a bunch of old boys to maintain con=
trol in their own hands. Peter is a member of the IETF establishment so of =
course he sees no structural problem.=A0</div>
					</div>
				</div>
			</div>
		</div>
	</div>
</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inline-text">
	PSA's been an AD, yes, but:</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inlined-message" name=3D"message-coda">
	<div class=3D"quoted" style=3D"border-left: 1px solid black; margin: 0pt 0=
pt 0pt 0.25em; padding-left: 1em; padding-top: 1ex;">
		<div class=3D"sanitized-message">
			<div dir=3D"ltr">
				<div class=3D"gmail_extra">
					<div class=3D"gmail_quote">
						<div>
							What I suggested is that the status quo is going to lead to applicat=
ions area work moving to forums outside the IETF. The Jabber folk have alre=
ady done this with the XMPP foundation.</div>
					</div>
				</div>
			</div>
		</div>
	</div>
</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inline-text">
	He's also one of the Jabber folk, and indeed Executive Director of the XSF=
.</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inline-text">
	So given these two statements are in conflict, there must be a problem wit=
h them.</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inline-text">
	I think it's in the implication that the XMPP folk came and looked at the =
IETF and decided there was some structural problem. I don't think that's th=
e case. You'd need to ask someone who was there when it formed, like Peter,=
 but I suspect it really mutated gradually from an umbrella organization fo=
r open-source software projects, and by the time anyone realised it was an =
SDO, then the IETF was already committed to SIP/SIMPLE (to the point of giv=
ing them their own area), and was in addition happy to cite XEPs and use th=
e technology operationally.</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inline-text">
	Dave.</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"message-signature" id=3D"signature_1371644549159-1402752353" =
name=3D"signature_1371644549159-1402752353">
	<div>
		<span style=3D"font-family: Arial, Helvetica Neue, Helvetica, sans-serif;=
 color: rgb(153, 153, 153);">Sent with=A0<a href=3D"http://inky.com?kme=3Ds=
ignature"><span style=3D"color: rgb(51, 150, 192); text-decoration: underli=
ne;">inky</span></a></span></div>
</div>
<p style=3D"margin: 0px; padding: 0px; ">
	=A0</p>
</body>
--===============0455933289==--

From yding@cs.helsinki.fi  Wed Jun 19 05:45:15 2013
Return-Path: <yding@cs.helsinki.fi>
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 5A48021F9B63 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 05:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 vDoDjIz+PARJ for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 05:45:10 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E33221F9B64 for <ietf@ietf.org>; Wed, 19 Jun 2013 05:45:10 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Wed Jun 19 15:44:54 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= dkim20130528; bh=wlXGaGnqeYTrzd6MI616WJ3miJJVdSJjFxpHktOKaZU=; b= T3SQv67gTtGobJSJkPe6cI6DINGzkulHGp2TuoWz1Zy39Ym+IVOt5FM015LQQ6Nf 7n0swJwBqfjdHAb9TBRPtYC/RD+aILX2nrhJGH3+nd0pm49+py1a98U8S0v/+LDt PtjtoEflRorM3eGzpvpqi9COgF4K4lXyOsFC921L0Eg=
Received: from [128.214.9.154] (wel-33.cs.helsinki.fi [128.214.9.154]) (AUTH: PLAIN yding, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Wed, 19 Jun 2013 15:44:54 +0300 id 00068AB8.51C1A7C6.000077C7
Message-ID: <51C1A7C6.8080708@cs.helsinki.fi>
Date: Wed, 19 Jun 2013 15:44:54 +0300
From: Aaron Yi DING <yding@cs.helsinki.fi>
Organization: Helsinki University
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IETF Diversity
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com>
In-Reply-To: <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 12:45:15 -0000

On 19/06/13 14:44, Phillip Hallam-Baker wrote:
> On Wed, Jun 19, 2013 at 2:13 AM, Aaron Yi DING <yding@cs.helsinki.fi 
> <mailto:yding@cs.helsinki.fi>> wrote:
>
>     On 18/06/13 21:08, Phillip Hallam-Baker wrote:
>>     When I make a statement at the microphone and then have multiple
>>     people come to thank me afterwards for making that point I don't
>>     consider it pontificating.
>>
>     sorry, just point it out, sometimes you said it right, but that
>     does not guarantee you are always right. to correct and make it
>     clearer, "when ... made a statement, ... people came to thank" 
>     for past experience, no present tense please.
>
>     no further comment, since I actually appreciate what you said and
>     the intention, as you described below.
>
>
> It is hard to encourage, much easier to discourage. I thought Peter's 
> attempt at a slap down was completely out of line and demonstrates the 
> problem I am talking about here. Agenda denial is a strategy where to 
> avoid discussing the topic that you know you have a weak case you 
> suggest a change of topic.
>


Definitely not hinting to change the topic..

As I just exchange opinions with other IETFer on this. With no 
disrespect, I agree with the latter part of your previous mail, 
especially about the tendency of being an exclusive environment.

It's not about correcting the grammar or sth other trivial thing. What I 
want to convey through the message is that our past experience may 
affect our judgment of upcoming deed. Believe or not, smart people like 
most IETFers, perhaps tend to be bit cocky as there are so many positive 
experience accumulated in the past. However, experience may not stand 
always perfectly correct, and it is not a justification for every future 
action. This is not targeting at you or any specific person.

There is visible problem here and perhaps more. Constructive suggestions 
and actions will be most welcome. Comments with pure emotional 
reflections are comments, e.g. not happy about this; those are 
completely wrong; it is hopeless...

I repeat that I appreciate your suggestions.

It would be nice if we all appreciate the time of the readers on the list.

Thanks,
Aaron



> There is a real problem with accountability and transparency in the 
> IETF constitution which was designed by a bunch of old boys to 
> maintain control in their own hands. Peter is a member of the IETF 
> establishment so of course he sees no structural problem.
>
> What I suggested is that the status quo is going to lead to 
> applications area work moving to forums outside the IETF. The Jabber 
> folk have already done this with the XMPP foundation.
>
>
> I have the greatest of respect for Vint Cerf's technical capabilities 
> but he consistently failed to establish open and transparent 
> governance mechanisms.
>
>
> -- 
> Website: http://hallambaker.com/


From cabo@tzi.org  Wed Jun 19 05:49:53 2013
Return-Path: <cabo@tzi.org>
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 80C6321F9B88 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 05:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.073
X-Spam-Level: 
X-Spam-Status: No, score=-106.073 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Z=0.259, USER_IN_WHITELIST=-100]
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 WHgb0JrkW5dQ for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 05:49:47 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 5A18721F9A10 for <ietf@ietf.org>; Wed, 19 Jun 2013 05:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r5JCniss028072; Wed, 19 Jun 2013 14:49:44 +0200 (CEST)
Received: from [192.168.217.105] (p54893A31.dip0.t-ipconnect.de [84.137.58.49]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 18AE73A01; Wed, 19 Jun 2013 14:49:44 +0200 (CEST)
Subject: Re: Berlin BoFzilla
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <EMEW3|a01d4733cdda5279712aad148367e4dap5IDYA03tjc|ecs.soton.ac.uk|AC2C9C7B-352A-4FE6-8742-5F3B69EC9321@ecs.soton.ac.uk>
Date: Wed, 19 Jun 2013 14:49:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8A4D138-ACE2-45B8-81E1-C163BCB08FB9@tzi.org>
References: <AC2C9C7B-352A-4FE6-8742-5F3B69EC9321@ecs.soton.ac.uk> <EMEW3|a01d4733cdda5279712aad148367e4dap5IDYA03tjc|ecs.soton.ac.uk|AC2C9C7B-352A-4FE6-8742-5F3B69EC9321@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org 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, 19 Jun 2013 12:49:53 -0000

Well, one of the BOFs is for 6Lo, which is meant to replace a WG =
(6LoWPAN) that is closing.

So make that 14 potential new WGs, but it is still a large number =
indeed.

(Actually, not all BOF descriptions are entirely explicit about the =
desire to have a new WG as an outcome...)

Gr=FC=DFe, Carsten


From jari.arkko@piuha.net  Wed Jun 19 06:05:55 2013
Return-Path: <jari.arkko@piuha.net>
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 DE98721F99DE for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 06:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.414
X-Spam-Level: 
X-Spam-Status: No, score=-102.414 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, SARE_SUB_OBFU_Z=0.259, USER_IN_WHITELIST=-100]
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 hQMSHFyQtxX4 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 06:05:51 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB7421F99C3 for <ietf@ietf.org>; Wed, 19 Jun 2013 06:05:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id ADE772CC53; Wed, 19 Jun 2013 16:05:47 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RERDfLsHxrQe; Wed, 19 Jun 2013 16:05:47 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 19F3C2CC48; Wed, 19 Jun 2013 16:05:47 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Berlin BoFzilla
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <EMEW3|a01d4733cdda5279712aad148367e4dap5IDYA03tjc|ecs.soton.ac.uk|AC2C9C7B-352A-4FE6-8742-5F3B69EC9321@ecs.soton.ac.uk>
Date: Wed, 19 Jun 2013 16:05:47 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <8280E226-3F45-4EC1-ABE8-F31DBB8F7164@piuha.net>
References: <AC2C9C7B-352A-4FE6-8742-5F3B69EC9321@ecs.soton.ac.uk> <EMEW3|a01d4733cdda5279712aad148367e4dap5IDYA03tjc|ecs.soton.ac.uk|AC2C9C7B-352A-4FE6-8742-5F3B69EC9321@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1503)
Cc: "ietf@ietf.org 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, 19 Jun 2013 13:05:56 -0000

Tim,

> was surprised to see a total of 15 proposed BoFs

That is a relatively big number. There is a very high attrition rate, =
however.

>=20
> That people are coming to the IETF with proposals to do work is =
probably a healthy thing; it would be more worrying if there were no =
BoFs proposed.

Indeed! More is better.

> But if all the proposals are accepted, and they all lead to WGs being =
formed, that's a lot of new groups to be created, scheduled and =
supported.

The crux is getting good enough proposals that they actually deserve a =
BoF slot and eventually lead to a working group. As noted, many =
proposals do not even make the first cut.

>=20
> In contrast, how many WGs have been closed in the past few months? I =
see there's http://trac.tools.ietf.org/wg/concluded from which I can see =
there are 10 WGs listed there which seem to have closed this year:
> 	iri 2013-01-19
> 	imapmove 2013-01-31
> 	csi 2013-02-12
> 	sipclf 2013-02-20
> 	bliss 2013-02-27
> 	simple 2013-02-27
> 	fecframe 2013-03-06
> 	krb-wg 2013-03-19
> 	eai 2013-03-19
> 	6tch 2013-04-19
>=20
> I wonder how the volume and lifetimes of WGs has changed over the =
years, e.g. the number we have, how quickly they complete their work, =
etc. Has anyone been looking at this?


We don't have a very good picture of that. My perception is that many of =
our working groups generally live quite long. That's fine when they are =
chartered to, e.g., maintain an important spec. But for new feature =
work, a faster turnaround rate might be preferable. Come in, do the =
work, close the working group, create a new working group for the next =
thing, etc. But for a good picture of the WG lifetimes, one would also =
have to look at rechartering.

I also think that the number of working groups at the IETF has been =
relatively stable over the years. There are also obvious limiting =
factors, like the number of slots in our meetings, for working groups =
that meet.

Jari


From joelja@bogus.com  Wed Jun 19 06:29:36 2013
Return-Path: <joelja@bogus.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 F0BDF21F9BD0 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 06:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.165
X-Spam-Level: 
X-Spam-Status: No, score=-102.165 tagged_above=-999 required=5 tests=[AWL=0.435, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 zlnl1AO5SQTz for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 06:29:34 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 65E1F21F9A1E for <ietf@ietf.org>; Wed, 19 Jun 2013 06:29:34 -0700 (PDT)
Received: from joels-MacBook-Air.local ([199.108.68.6]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r5JDTVRZ060094 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 19 Jun 2013 13:29:33 GMT (envelope-from joelja@bogus.com)
Message-ID: <51C1B235.6020507@bogus.com>
Date: Wed, 19 Jun 2013 06:29:25 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>
In-Reply-To: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 19 Jun 2013 13:29:34 +0000 (UTC)
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, 19 Jun 2013 13:29:37 -0000

Given that this document was revved twice and had it's requested status 
change during IETF last call in response to discussion criticism and new 
contribution I am going to rerun the last call.

Thanks
joel

On 5/20/13 6:44 AM, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Resource Records for EUI-48 and EUI-64 Addresses in the DNS'
>    <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-17. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     48-bit Extended Unique Identifiers (EUI-48) and 64-bit Extended
>     Unique Identifiers (EUI-64) are address formats specified by the IEEE
>     for use in various layer-2 networks, e.g. ethernet.
>
>     This document defines two new DNS resource record types, EUI48 and
>     EUI64, for encoding ethernet addresses in the DNS.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-jabley-dnsext-eui48-eui64-rrtypes/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-jabley-dnsext-eui48-eui64-rrtypes/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>


From paul.hoffman@vpnc.org  Wed Jun 19 07:01:51 2013
Return-Path: <paul.hoffman@vpnc.org>
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 A782721F9C1E for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.547
X-Spam-Level: 
X-Spam-Status: No, score=-101.547 tagged_above=-999 required=5 tests=[AWL=-0.914, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_FWDLOOK=1.666, USER_IN_WHITELIST=-100]
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 YlrTPUnNZF4Y for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:01:51 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 191EF21F9C15 for <ietf@ietf.org>; Wed, 19 Jun 2013 07:01:51 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5JE1dou032901 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 19 Jun 2013 07:01:40 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <DACC4421-03B2-4F64-856C-FF3080B587AE@frobbit.se>
Date: Wed, 19 Jun 2013 07:01:39 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <002D3B5B-3B2C-495E-A500-A95C1856355D@vpnc.org>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <6.2.5.6.2.20130619000239.0b0ebd38@resistor.net> <DACC4421-03B2-4F64-856C-FF3080B587AE@frobbit.se>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-Mailer: Apple Mail (2.1508)
Cc: ietf <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, 19 Jun 2013 14:01:51 -0000

On Jun 19, 2013, at 2:27 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:

> And do not let me get started on EPP or Whois issues... ;-)

Actually, let's let you get started. :-)

Part of the problem you are seeing with the lack of RFCs desired by =
ICANN is that it is now harder to get an individual submission standards =
track RFC than it was ten years ago. ADs want more more done in WGs so =
they get more review before the document comes to IETF last call.

But there is no EPP WG. And WEIRDS is supposed to only be =
forward-looking, not dealing with practices with the current protocol.

The problem is that the IETF is saying two different things to ICANN: =
let us do the work, and we don't really care about the work you need =
done because it is about old protocols.

The Applications Area Directors have done a good job of spinning up =
short-lived WGs for narrow topics, and letting single-topic documents =
come to AppsAWG, but ICANN's needs are greater than that.

In the past, it was easy for a small group to put together a small =
protocol spec and get it on standards track if it was a follow-on to an =
existing protocol, but that is much more difficult now. ICANN needs it =
to be easier. The IETF should support them in that.

--Paul Hoffman=

From dhc@dcrocker.net  Wed Jun 19 07:30:38 2013
Return-Path: <dhc@dcrocker.net>
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 C091621F9C4B for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.548
X-Spam-Level: 
X-Spam-Status: No, score=-6.548 tagged_above=-999 required=5 tests=[AWL=0.051,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 zyVVOSf8J5PX for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:30:33 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C8CBE21F9C3B for <ietf@ietf.org>; Wed, 19 Jun 2013 07:30:33 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5JEUTcc017562 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 19 Jun 2013 07:30:32 -0700
Message-ID: <51C1C075.5070102@dcrocker.net>
Date: Wed, 19 Jun 2013 07:30:13 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Arturo Servin <aservin@lacnic.net>
Subject: Re: IETF Diversity
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <A5AD378E-0497-42C2-A6BA-BCBFCC9F9691@piuha.net> <51C0A4D2.9020106@dcrocker.net> <51C1162B.4040606@lacnic.net>
In-Reply-To: <51C1162B.4040606@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 19 Jun 2013 07:30:33 -0700 (PDT)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 19 Jun 2013 14:30:38 -0000

On 6/18/2013 7:23 PM, Arturo Servin wrote:
>      We created an IETF-TF in LACNOG;


Arturo,

Many thanks for the summary of efforts within the region; they sound 
quite promising.

Just to be clear, my question was specifically concerning the activity 
of the IAOC that Jari cited.

That effort has been started and pursued in isolation of any other 
efforts and it has been the subject of direct IETF discussion.  So I 
was/am asking about it's follow-up effort.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From dhc@dcrocker.net  Wed Jun 19 07:32:27 2013
Return-Path: <dhc@dcrocker.net>
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 68E7721F9C35 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.55
X-Spam-Level: 
X-Spam-Status: No, score=-6.55 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 k1O1xx7qgBZX for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:32:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7AF0B21F9BFE for <ietf@ietf.org>; Wed, 19 Jun 2013 07:32:22 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5JEWHtu017611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 19 Jun 2013 07:32:20 -0700
Message-ID: <51C1C0E1.8000900@dcrocker.net>
Date: Wed, 19 Jun 2013 07:32:01 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com>
In-Reply-To: <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 19 Jun 2013 07:32:20 -0700 (PDT)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 19 Jun 2013 14:32:27 -0000

On 6/19/2013 5:35 AM, Dave Cridland wrote:
> Phillip Hallam-Baker wrote:
> There is a real problem with accountability and transparency in the IETF
> constitution which was designed by a bunch of old boys to maintain
> control in their own hands. Peter is a member of the IETF establishment
> so of course he sees no structural problem.
> PSA's been an AD, yes, but:


Forgive me, but you just responded to a rather unpleasant ad hominem.

We should not sustain such threads.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From stpeter@stpeter.im  Wed Jun 19 08:08:58 2013
Return-Path: <stpeter@stpeter.im>
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 1395121F9C4B for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 pCCrBw5zK-bF for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:08:53 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E292A21F9BB5 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:08:52 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 20D8041278; Wed, 19 Jun 2013 09:08:50 -0600 (MDT)
Message-ID: <51C1C980.6000606@stpeter.im>
Date: Wed, 19 Jun 2013 09:08:48 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net>
In-Reply-To: <51C1C0E1.8000900@dcrocker.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 15:08:58 -0000

On 6/19/13 8:32 AM, Dave Crocker wrote:
> On 6/19/2013 5:35 AM, Dave Cridland wrote:
>> Phillip Hallam-Baker wrote:
>> There is a real problem with accountability and transparency in the IETF
>> constitution which was designed by a bunch of old boys to maintain
>> control in their own hands. Peter is a member of the IETF establishment
>> so of course he sees no structural problem.
>> PSA's been an AD, yes, but:
> 
> 
> Forgive me, but you just responded to a rather unpleasant ad hominem.
> 
> We should not sustain such threads.

My point, poorly expressed though it was, is that it's not productive
for us all to wait from word on high before taking positive action.
Members of the IESG, IAB, IOAC, or any other "official" body are just
folks who are temporarily serving the community in a defined role. If we
want to change the culture of our community with respect to diversity,
it's better for us to work to encourage, nurture, and mentor particular
individuals.

My apologies for the extremely egregious manner in which I stated the
point. It was not directed personally at Mr. Hallam-Baker, but at all of
us who talk and don't take action -- myself very much included.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From dhc@dcrocker.net  Wed Jun 19 08:15:54 2013
Return-Path: <dhc@dcrocker.net>
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 90DF221F8F87 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.554
X-Spam-Level: 
X-Spam-Status: No, score=-6.554 tagged_above=-999 required=5 tests=[AWL=0.045,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 vws0+uYCvgIQ for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:15:49 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id F322921F9C2F for <ietf@ietf.org>; Wed, 19 Jun 2013 08:15:48 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5JFFbu0018524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 19 Jun 2013 08:15:40 -0700
Message-ID: <51C1CB09.5020109@dcrocker.net>
Date: Wed, 19 Jun 2013 08:15:21 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im>
In-Reply-To: <51C1C980.6000606@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 19 Jun 2013 08:15:40 -0700 (PDT)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 19 Jun 2013 15:15:54 -0000

On 6/19/2013 8:08 AM, Peter Saint-Andre wrote:
> On 6/19/13 8:32 AM, Dave Crocker wrote:
>> On 6/19/2013 5:35 AM, Dave Cridland wrote:
>>> Phillip Hallam-Baker wrote:
>>> There is a real problem with accountability and transparency in the IETF
>>> constitution which was designed by a bunch of old boys to maintain
>>> control in their own hands. Peter is a member of the IETF establishment
>>> so of course he sees no structural problem.
>>> PSA's been an AD, yes, but:
>>
>>
>> Forgive me, but you just responded to a rather unpleasant ad hominem.
>>
>> We should not sustain such threads.
...
> My apologies for the extremely egregious manner in which I stated the
> point. It was not directed personally at Mr. Hallam-Baker, but at all of
> us who talk and don't take action -- myself very much included.


oh dear.  /my/ apologies for being unclear.  I didn't mean that /your/ 
posting was an ad hominem, but that you were responding to one.

Your own point is fine and constructive.  Worthy thought.  Worth 
pursuing.  Offered independently it would have been dandy.

My point is that we need to stop tolerating ad hominem content and that 
starts by not responding to it.  Posting a reply -- even one that 
ignores the offensive content -- constitutes tolerance for the behavior.

The view that we should be resilient against such behavior is long past 
its time.  We should, instead, demand professional demeanor, and that 
means shunning behavior that attacks people and their motives.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From stpeter@stpeter.im  Wed Jun 19 08:16:42 2013
Return-Path: <stpeter@stpeter.im>
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 AB18021F90FD for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 1JWIcFhA9n97 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:16:37 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E7FA421F8FB3 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:16:32 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C6B9D412C8; Wed, 19 Jun 2013 09:16:32 -0600 (MDT)
Message-ID: <51C1CB4D.4030006@stpeter.im>
Date: Wed, 19 Jun 2013 09:16:29 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com>
In-Reply-To: <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 15:16:42 -0000

On 6/19/13 6:35 AM, Dave Cridland wrote:
> Phillip Hallam-Baker wrote:
>> There is a real problem with accountability and transparency in the IETF
>> constitution which was designed by a bunch of old boys to maintain
>> control in their own hands. Peter is a member of the IETF establishment
>> so of course he sees no structural problem. 

Actually I see lots of structural problems -- I just happen to be of the
mindset that working from the bottom up is the only sustainable model
for change.

> PSA's been an AD, yes, but:
>  
>> What I suggested is that the status quo is going to lead to applications
>> area work moving to forums outside the IETF. The Jabber folk have
>> already done this with the XMPP foundation.
>  
> He's also one of the Jabber folk, and indeed Executive Director of the XSF.
>  
> So given these two statements are in conflict, there must be a problem
> with them.
>  
> I think it's in the implication that the XMPP folk came and looked at
> the IETF and decided there was some structural problem. I don't think
> that's the case. You'd need to ask someone who was there when it formed,
> like Peter, but I suspect it really mutated gradually from an umbrella
> organization for open-source software projects, and by the time anyone
> realised it was an SDO, then the IETF was already committed to
> SIP/SIMPLE (to the point of giving them their own area), and was in
> addition happy to cite XEPs and use the technology operationally.

Well, the Jabberites were working in their own open-source community in
1999 and were quite clueless about IETF activities until the XMPP WG was
formed in 2002 (and, one might argue, even after that). We continued to
work on XMPP extensions at the XSF in parallel with working on the core
of XMPP at the IETF because I don't think it would have been productive
to define hundreds of XMPP extensions in the XMPP WG at the IETF (that
might have been perceived as a DoS attack, if you will).

But this is really not a diversity issue, so if we're going to continue
this thread I suggest that at the least we change the subject line.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From abdussalambaryun@gmail.com  Wed Jun 19 08:16:47 2013
Return-Path: <abdussalambaryun@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 6646721F9C92 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.057
X-Spam-Level: 
X-Spam-Status: No, score=-2.057 tagged_above=-999 required=5 tests=[AWL=0.541,  BAYES_00=-2.599, HTML_MESSAGE=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 rjAmI5fNIyWP for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:16:42 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id B911021F9123 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:16:42 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r10so5171486pdi.27 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:16:42 -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=Elud3ze4DVwOWshp1uc+TvxPdqqRzsz8gxEVdzvULSw=; b=wDZ8ETKDDBRbL16DgWECWryqniZ94NC5QKpaCooBGZg10Dpu1z8baufWpUIpzkx1ku va/KImt5i/J5Ae9NFApmVxbIcqjVv/+UjctoRubB2BNp8W3k7waKG5Qn6QJ88fg1BSSV wRoHjdbAM8+71sDTAQHSKtkuLM787lWrSHJPF0SGs1Fw5bOXWhRN2E10CAZv5FygiL26 ZWnach0HSiEAbsN/4yrLWHT9q7FklcEKwquTUt4kpXeZ5p7CQIxBl6tjMShRZNBggpW7 HL31likxLpt1/BLcTrg1vhsEDeTrfQGKv4gn9qOs2TzdjijzJMALnD16KwGwHG6jI3Cu cSYQ==
MIME-Version: 1.0
X-Received: by 10.66.230.199 with SMTP id ta7mr7352618pac.153.1371655002514; Wed, 19 Jun 2013 08:16:42 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Wed, 19 Jun 2013 08:16:42 -0700 (PDT)
In-Reply-To: <51C1C980.6000606@stpeter.im>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im>
Date: Wed, 19 Jun 2013 16:16:42 +0100
Message-ID: <CADnDZ89JnMc=cJBJb9ioGafmZj_5jv6be-UFST=8AVxWv+KP5g@mail.gmail.com>
Subject: Re: IETF Diversity
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=047d7b15ab2d2de86404df83514b
Cc: Dave Crocker <dcrocker@bbiw.net>, 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, 19 Jun 2013 15:16:47 -0000

--047d7b15ab2d2de86404df83514b
Content-Type: text/plain; charset=ISO-8859-1

Commenting is already an action taken, so we thank who made effort to bring
the points forward. I always add my comments even though I had given no
title. However, thoes folks that have been given titles by the IETF I think
they should do actions more regarding this diversity issue as
Mr.Hallam-baker requesting. I never give excuses to managers, but
appreciate all their efforts and patients for the community :-)

AB


On Wed, Jun 19, 2013 at 4:08 PM, Peter Saint-Andre <stpeter@stpeter.im>wrote:

> On 6/19/13 8:32 AM, Dave Crocker wrote:
> > On 6/19/2013 5:35 AM, Dave Cridland wrote:
> >> Phillip Hallam-Baker wrote:
> >> There is a real problem with accountability and transparency in the IETF
> >> constitution which was designed by a bunch of old boys to maintain
> >> control in their own hands. Peter is a member of the IETF establishment
> >> so of course he sees no structural problem.
> >> PSA's been an AD, yes, but:
> >
> >
> > Forgive me, but you just responded to a rather unpleasant ad hominem.
> >
> > We should not sustain such threads.
>
> My point, poorly expressed though it was, is that it's not productive
> for us all to wait from word on high before taking positive action.
> Members of the IESG, IAB, IOAC, or any other "official" body are just
> folks who are temporarily serving the community in a defined role. If we
> want to change the culture of our community with respect to diversity,
> it's better for us to work to encourage, nurture, and mentor particular
> individuals.
>
> My apologies for the extremely egregious manner in which I stated the
> point. It was not directed personally at Mr. Hallam-Baker, but at all of
> us who talk and don't take action -- myself very much included.
>
> Peter
>
> --
> Peter Saint-Andre
> https://stpeter.im/
>
>
>

--047d7b15ab2d2de86404df83514b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Commenting is already an action taken, so we thank wh=
o made effort to bring the points forward. I always add my comments even th=
ough I had given no title. However, thoes folks that have been given titles=
 by the IETF I think they should do actions more regarding this diversity i=
ssue as Mr.Hallam-baker requesting. I never give excuses to managers, but a=
ppreciate all their efforts and patients for the community=A0:-)</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Wed, Jun 19, 2013 at 4:08 PM, Peter Saint-Andre <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:stpeter@stpeter.im" target=3D"_blank">s=
tpeter@stpeter.im</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 6/19/13 8:32 AM, Dave C=
rocker wrote:<br>
&gt; On 6/19/2013 5:35 AM, Dave Cridland wrote:<br>
&gt;&gt; Phillip Hallam-Baker wrote:<br>
&gt;&gt; There is a real problem with accountability and transparency in th=
e IETF<br>
&gt;&gt; constitution which was designed by a bunch of old boys to maintain=
<br>
&gt;&gt; control in their own hands. Peter is a member of the IETF establis=
hment<br>
&gt;&gt; so of course he sees no structural problem.<br>
&gt;&gt; PSA&#39;s been an AD, yes, but:<br>
&gt;<br>
&gt;<br>
&gt; Forgive me, but you just responded to a rather unpleasant ad hominem.<=
br>
&gt;<br>
&gt; We should not sustain such threads.<br>
<br>
</div>My point, poorly expressed though it was, is that it&#39;s not produc=
tive<br>
for us all to wait from word on high before taking positive action.<br>
Members of the IESG, IAB, IOAC, or any other &quot;official&quot; body are =
just<br>
folks who are temporarily serving the community in a defined role. If we<br=
>
want to change the culture of our community with respect to diversity,<br>
it&#39;s better for us to work to encourage, nurture, and mentor particular=
<br>
individuals.<br>
<br>
My apologies for the extremely egregious manner in which I stated the<br>
point. It was not directed personally at Mr. Hallam-Baker, but at all of<br=
>
us who talk and don&#39;t take action -- myself very much included.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Peter<br>
<br>
--<br>
Peter Saint-Andre<br>
<a href=3D"https://stpeter.im/" target=3D"_blank">https://stpeter.im/</a><b=
r>
<br>
<br>
</font></span></blockquote></div><br></div>

--047d7b15ab2d2de86404df83514b--

From stpeter@stpeter.im  Wed Jun 19 08:21:30 2013
Return-Path: <stpeter@stpeter.im>
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 5ACEC21F9346 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level: 
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 055u5x8BCQEB for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:21:24 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 417C421F92E3 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:21:24 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 467E4412C8; Wed, 19 Jun 2013 09:21:24 -0600 (MDT)
Message-ID: <51C1CC71.4060104@stpeter.im>
Date: Wed, 19 Jun 2013 09:21:21 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im> <51C1CB09.5020109@dcrocker.net>
In-Reply-To: <51C1CB09.5020109@dcrocker.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 15:21:30 -0000

On 6/19/13 9:15 AM, Dave Crocker wrote:
> On 6/19/2013 8:08 AM, Peter Saint-Andre wrote:
>> On 6/19/13 8:32 AM, Dave Crocker wrote:
>>> On 6/19/2013 5:35 AM, Dave Cridland wrote:
>>>> Phillip Hallam-Baker wrote:
>>>> There is a real problem with accountability and transparency in the
>>>> IETF
>>>> constitution which was designed by a bunch of old boys to maintain
>>>> control in their own hands. Peter is a member of the IETF establishment
>>>> so of course he sees no structural problem.
>>>> PSA's been an AD, yes, but:
>>>
>>>
>>> Forgive me, but you just responded to a rather unpleasant ad hominem.
>>>
>>> We should not sustain such threads.
> ...
>> My apologies for the extremely egregious manner in which I stated the
>> point. It was not directed personally at Mr. Hallam-Baker, but at all of
>> us who talk and don't take action -- myself very much included.
> 
> 
> oh dear.  /my/ apologies for being unclear.  I didn't mean that /your/
> posting was an ad hominem, but that you were responding to one.
> 
> Your own point is fine and constructive.  Worthy thought.  Worth
> pursuing.  Offered independently it would have been dandy.
> 
> My point is that we need to stop tolerating ad hominem content and that
> starts by not responding to it.  Posting a reply -- even one that
> ignores the offensive content -- constitutes tolerance for the behavior.
> 
> The view that we should be resilient against such behavior is long past
> its time.  We should, instead, demand professional demeanor, and that
> means shunning behavior that attacks people and their motives.

Dave, you are completely correct and I'm going to make a commitment to
personal improvement. :-)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From melinda.shore@gmail.com  Wed Jun 19 08:23:03 2013
Return-Path: <melinda.shore@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 EE8D121F9CD3 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 y+XOkQNH+Arr for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:22:57 -0700 (PDT)
Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) by ietfa.amsl.com (Postfix) with ESMTP id BFDA921F9C95 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:22:55 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id 10so5186811pdi.11 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:22:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=d0N9XDwj3HRENcHS+bykXRfqzhgKCa/aCUXfiJcIn/U=; b=H4mrzGcvzd9I8yvs84vvrJYkGhuchzFdkscTncmov7dwX9s1inpMWF8WCvDMjqNAva Mj2Ky42NvOOMr769RN+WwK4GtYfkWJdG8YO1qo1aT/e1KHVNJUjwMqlhL2p50r+f/FV4 dkcYFKIoG90UEsGZyff8pyTo96xONWIFL1CgdQD43EMPv+bdKW202sZtG1/87zTpQdnL 3jBONh0O4YnXBeY7MMFfgkzySaf4zyn6oyKhOpGPu6F5Z/7orMqnMnaBjUKPEwTbOejq 7efvnK8WlN9TwQsI7hSCSRH9Wky5YabW9u5GXEYmfULvvSDlErhFkCA6P2bQLn9BGQdb FxmQ==
X-Received: by 10.66.221.163 with SMTP id qf3mr7252234pac.38.1371655375009; Wed, 19 Jun 2013 08:22:55 -0700 (PDT)
Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id pm7sm23524516pbb.31.2013.06.19.08.22.53 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 08:22:53 -0700 (PDT)
Message-ID: <51C1CCCB.3060601@gmail.com>
Date: Wed, 19 Jun 2013 07:22:51 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im>
In-Reply-To: <51C1CB4D.4030006@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 15:23:03 -0000

On 6/19/13 7:16 AM, Peter Saint-Andre wrote:
> Actually I see lots of structural problems -- I just happen to be of the
> mindset that working from the bottom up is the only sustainable model
> for change.

Don't know about that one.  In the US, at least, legal mandates
have typically led social change, at least when it comes to civil
rights, etc.

Melinda



From brian@innovationslab.net  Wed Jun 19 08:26:24 2013
Return-Path: <brian@innovationslab.net>
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 08BC321F9ABC for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.614
X-Spam-Level: 
X-Spam-Status: No, score=-102.614 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 dvd0XuXhiPh3 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:26:17 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD7521F9121 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:26:16 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 3FD7A880FB for <ietf@ietf.org>; Wed, 19 Jun 2013 08:26:16 -0700 (PDT)
Received: from clemson.local (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 00B01130003 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:26:15 -0700 (PDT)
Message-ID: <51C1CD95.4060106@innovationslab.net>
Date: Wed, 19 Jun 2013 11:26:13 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im>
In-Reply-To: <51C1C980.6000606@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 15:26:24 -0000

On 6/19/13 11:08 AM, Peter Saint-Andre wrote:

>
> My point, poorly expressed though it was, is that it's not productive
> for us all to wait from word on high before taking positive action.
> Members of the IESG, IAB, IOAC, or any other "official" body are just
> folks who are temporarily serving the community in a defined role. If we
> want to change the culture of our community with respect to diversity,
> it's better for us to work to encourage, nurture, and mentor particular
> individuals.

To help facilitate the mentoring aspect, there will be a call soon for 
volunteers to act as mentors for newcomers (starting with IETF 87). 
Once the web page for the mentoring program with all the information is 
up, you should be seeing a call for mentors.

We hope that this type of program will aid in assisting newer members of 
the IETF community become more involved and productive in our activities.

Regards,
Brian


From stpeter@stpeter.im  Wed Jun 19 08:26:28 2013
Return-Path: <stpeter@stpeter.im>
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 F277121F9ABD for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:26:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 xIxgt6ry4U9V for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:26:21 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 5542F21F9AA2 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:26:21 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9CBAA412CC; Wed, 19 Jun 2013 09:26:21 -0600 (MDT)
Message-ID: <51C1CD9A.2020004@stpeter.im>
Date: Wed, 19 Jun 2013 09:26:18 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com>
In-Reply-To: <51C1CCCB.3060601@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 15:26:28 -0000

On 6/19/13 9:22 AM, Melinda Shore wrote:
> On 6/19/13 7:16 AM, Peter Saint-Andre wrote:
>> Actually I see lots of structural problems -- I just happen to be of the
>> mindset that working from the bottom up is the only sustainable model
>> for change.
> 
> Don't know about that one.  In the US, at least, legal mandates
> have typically led social change, at least when it comes to civil
> rights, etc.

That's a topic for the ietf-philosophy discussion list, methinks. :-)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From melinda.shore@gmail.com  Wed Jun 19 08:29:52 2013
Return-Path: <melinda.shore@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 A988C21F9D0C for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:29:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 NTyaMmtuLxfP for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:29:46 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id D9A8921F9D0A for <ietf@ietf.org>; Wed, 19 Jun 2013 08:29:46 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id p10so5208250pdj.36 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:29:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=1LyidWHJ2jPfqy/ZA/BP7Fyjp4RcOMKb9O9X/OUnTnM=; b=BhtzZ49YQLPN8nJOgOunZs5OzBlngIuF8b72EGloLAe2VfPbEo92xLQPyUl8S+Y0LY C5Y4LOT8pWrSl/2ppjJ1GWyIguYvDhKYBnFSH2S+1FGvOlWvPKRQYYRIlg7ciE3Md9cr ntqWj1Bq8wInnq/8A46Fl5/an28ENS1VoMilcdpZD5BH5vEXiKY8qtV4HE0sskCkmwUv ati73vrWvSg6HXKGUGPaWCVKCoQl1JVyhNmKB0f0f0/aP6SPY6kZYSJkta2vC4bVJpSL 74fbFapeszxLSsYOLX5OiYI9FFe/9v380gvjeeKjOeSPRJwIqI2J2AFsijndIH7Yy8Wk Q1xw==
X-Received: by 10.68.131.168 with SMTP id on8mr3299667pbb.97.1371655786688; Wed, 19 Jun 2013 08:29:46 -0700 (PDT)
Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id o10sm23533569pbq.39.2013.06.19.08.29.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 08:29:45 -0700 (PDT)
Message-ID: <51C1CE67.3020703@gmail.com>
Date: Wed, 19 Jun 2013 07:29:43 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <51C1CD9A.2020004@stpeter.im>
In-Reply-To: <51C1CD9A.2020004@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 15:29:52 -0000

On 6/19/13 7:26 AM, Peter Saint-Andre wrote:
> On 6/19/13 9:22 AM, Melinda Shore wrote:
>> Don't know about that one.  In the US, at least, legal mandates
>> have typically led social change, at least when it comes to civil
>> rights, etc.
> That's a topic for the ietf-philosophy discussion list, methinks. :-)

To the extent that unexamined assertions about how social/cultural
change works are being used to explain why the organization doesn't
need to be particularly proactive, I don't think so.

Melinda



From stpeter@stpeter.im  Wed Jun 19 08:31:42 2013
Return-Path: <stpeter@stpeter.im>
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 CBE7221F9BA7 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Zh6yEIk4vKmr for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:31:37 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B6E1521F9017 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:31:37 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0F1F0412CC; Wed, 19 Jun 2013 09:31:37 -0600 (MDT)
Message-ID: <51C1CED7.8090803@stpeter.im>
Date: Wed, 19 Jun 2013 09:31:35 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im> <51C1CD95.4060106@innovationslab.net>
In-Reply-To: <51C1CD95.4060106@innovationslab.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 15:31:42 -0000

On 6/19/13 9:26 AM, Brian Haberman wrote:
> On 6/19/13 11:08 AM, Peter Saint-Andre wrote:
> 
>>
>> My point, poorly expressed though it was, is that it's not productive
>> for us all to wait from word on high before taking positive action.
>> Members of the IESG, IAB, IOAC, or any other "official" body are just
>> folks who are temporarily serving the community in a defined role. If we
>> want to change the culture of our community with respect to diversity,
>> it's better for us to work to encourage, nurture, and mentor particular
>> individuals.
> 
> To help facilitate the mentoring aspect, there will be a call soon for
> volunteers to act as mentors for newcomers (starting with IETF 87). Once
> the web page for the mentoring program with all the information is up,
> you should be seeing a call for mentors.
> 
> We hope that this type of program will aid in assisting newer members of
> the IETF community become more involved and productive in our activities.

That's great!

However, why do we need to wait for a program? Can't we simply be human,
introduce ourselves to new participants, reach out to individual
contributors about becoming document shepherds, document editors, WG
secretaries, WG chairs, BoF chairs, etc.? That's what I've been doing,
and so far the results have been positive.

I'm not saying that's the only way to make progress, but I see it as
very much worth the effort.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From hallam@gmail.com  Wed Jun 19 08:34:05 2013
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 D3E7521F9D1D for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  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 EHNA-YtKPPqL for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:34:03 -0700 (PDT)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id B6B1B21F9BB2 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:33:59 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id q56so4653011wes.31 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:33:58 -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=3sPiMZiX+eHQJBGYtyRdR42G+WZSF29WOW7NWHnBMLc=; b=gRM9qfuwCjlyD0xyfwm4rn1j+ST6aIrBDA9Cv92cfyx6DqMqOicz5puFH/SbogNOLl gfkypLDUc+/lKlLPuTjoGDWo728qgVyrtnrKtqg6Xesa7m1cFg1WlK5YbGI0uxs5XXJY pFgJFWife8sLDxfvLfpgAcsIyuu+ISyQqcnYFj83qFbPXfxcCqdvTyfJf0NAtLGsZOKy k5wM058oZ/2mVzt8YvCJxTS3OVOYpYlbvcmoGc6/ZLCparauOEbGa3i0pJQf50ry+mA3 zDLb9jJpWLubKcHfK1gFpGO+XxTfq+ezi7w4srntw8dEMIcX5eEtGLWGj2lhm52Z/NJx c5Dg==
MIME-Version: 1.0
X-Received: by 10.180.9.242 with SMTP id d18mr11372790wib.18.1371656038829; Wed, 19 Jun 2013 08:33:58 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Wed, 19 Jun 2013 08:33:58 -0700 (PDT)
In-Reply-To: <51C1CCCB.3060601@gmail.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com>
Date: Wed, 19 Jun 2013 11:33:58 -0400
Message-ID: <CAMm+Lwh6_ZTqaR9B7kWL3re+08tqbXUDUJ5=sPMxo_Rr+GEpLg@mail.gmail.com>
Subject: Re: IETF Diversity
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2228cf2d79304df838ed1
Cc: 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, 19 Jun 2013 15:34:06 -0000

--001a11c2228cf2d79304df838ed1
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jun 19, 2013 at 11:22 AM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 6/19/13 7:16 AM, Peter Saint-Andre wrote:
> > Actually I see lots of structural problems -- I just happen to be of the
> > mindset that working from the bottom up is the only sustainable model
> > for change.
>
> Don't know about that one.  In the US, at least, legal mandates
> have typically led social change, at least when it comes to civil
> rights, etc.
>

When the IETF was being started Harvard had just abolished its quota on
hiring Jews and was attempting to correct their past discrimination by
awarding tenure to people like Larry Summers a year after they handed in
their dissertation.

That was not bottom up change. It was change that was forced from the top
down in response to bottom up pressure on the decision makers. It was not
Harvard that decided to reform, it was the government that told Harvard
that it would reform or see no more government grants. They still have the
'legacies' program in place that was originally adopted to keep Jews out of
a Protestant organization.


Academia is still one of the worst environments for discrimination. They
don't have formal barriers as in the past but the informal barriers are
steep.

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

--001a11c2228cf2d79304df838ed1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Jun 19, 2013 at 11:22 AM, Melinda Shore <span dir=
=3D"ltr">&lt;<a href=3D"mailto:melinda.shore@gmail.com" target=3D"_blank">m=
elinda.shore@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra">=
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 6/19/13 7:16 AM, Peter =
Saint-Andre wrote:<br>
&gt; Actually I see lots of structural problems -- I just happen to be of t=
he<br>
&gt; mindset that working from the bottom up is the only sustainable model<=
br>
&gt; for change.<br>
<br>
</div>Don&#39;t know about that one. =A0In the US, at least, legal mandates=
<br>
have typically led social change, at least when it comes to civil<br>
rights, etc.<br></blockquote><div><br></div><div style>When the IETF was be=
ing started Harvard had just abolished its quota on hiring Jews and was att=
empting to correct their past discrimination by awarding tenure to people l=
ike Larry Summers a year after they handed in their dissertation.</div>
<div style><br></div><div style>That was not bottom up change. It was chang=
e that was forced from the top down in response to bottom up pressure on th=
e decision makers. It was not Harvard that decided to reform, it was the go=
vernment that told Harvard that it would reform or see no more government g=
rants. They still have the &#39;legacies&#39; program in place that was ori=
ginally adopted to keep Jews out of a Protestant organization.</div>
</div><div><br></div><div><br></div><div style>Academia is still one of the=
 worst environments for discrimination. They don&#39;t have formal barriers=
 as in the past but the informal barriers are steep.</div><div style><br>
</div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambake=
r.com/</a><br>
</div></div>

--001a11c2228cf2d79304df838ed1--

From brian@innovationslab.net  Wed Jun 19 08:36:26 2013
Return-Path: <brian@innovationslab.net>
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 1F2D021F9C95 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.614
X-Spam-Level: 
X-Spam-Status: No, score=-102.614 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 h6Vtt8tJk1nc for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:36:19 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id A3EAB21F949F for <ietf@ietf.org>; Wed, 19 Jun 2013 08:36:12 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 62F46880FA; Wed, 19 Jun 2013 08:36:12 -0700 (PDT)
Received: from clemson.local (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 03341130003; Wed, 19 Jun 2013 08:36:11 -0700 (PDT)
Message-ID: <51C1CFEC.50206@innovationslab.net>
Date: Wed, 19 Jun 2013 11:36:12 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im> <51C1CD95.4060106@innovationslab.net> <51C1CED7.8090803@stpeter.im>
In-Reply-To: <51C1CED7.8090803@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 15:36:26 -0000

On 6/19/13 11:31 AM, Peter Saint-Andre wrote:
> On 6/19/13 9:26 AM, Brian Haberman wrote:
>> On 6/19/13 11:08 AM, Peter Saint-Andre wrote:
>>
>>>
>>> My point, poorly expressed though it was, is that it's not productive
>>> for us all to wait from word on high before taking positive action.
>>> Members of the IESG, IAB, IOAC, or any other "official" body are just
>>> folks who are temporarily serving the community in a defined role. If we
>>> want to change the culture of our community with respect to diversity,
>>> it's better for us to work to encourage, nurture, and mentor particular
>>> individuals.
>>
>> To help facilitate the mentoring aspect, there will be a call soon for
>> volunteers to act as mentors for newcomers (starting with IETF 87). Once
>> the web page for the mentoring program with all the information is up,
>> you should be seeing a call for mentors.
>>
>> We hope that this type of program will aid in assisting newer members of
>> the IETF community become more involved and productive in our activities.
>
> That's great!
>
> However, why do we need to wait for a program? Can't we simply be human,
> introduce ourselves to new participants, reach out to individual
> contributors about becoming document shepherds, document editors, WG
> secretaries, WG chairs, BoF chairs, etc.? That's what I've been doing,
> and so far the results have been positive.

I would highly encourage people taking that initiative and appreciate 
folks who do that of their own accord.

>
> I'm not saying that's the only way to make progress, but I see it as
> very much worth the effort.

Absolutely agree.  The goal of this experimental mentoring program is to 
provide people who may not be sure *how* to be mentors a framework to 
work within.

Regards,
Brian



From abdussalambaryun@gmail.com  Wed Jun 19 08:40:26 2013
Return-Path: <abdussalambaryun@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 AA87121F9D45 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.051,  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 CZvB5DzDUR6B for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:40:26 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 3F33221F9D48 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:40:16 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so5204234pbc.1 for <ietf@ietf.org>; Wed, 19 Jun 2013 08:40:16 -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=/4B7zlhVl3cBQLXCubYBe+1K65mw3b+5pAz/lshKI8M=; b=EXvW9zHzAWztEhKQATyEy1pxzPpm5rYv7bGezNUqze2yKSYtKrxn0V3vtmGbB1eP43 oxvaVs9GxiQwM4mk0bT/5tzRMUN08c3WWuJX+z45i9/onG8rK7BhfIwENlApgCLeQROO 6F+VtMdw/Dzsl9MU0ZVFKM8khhkOx5m/Zq+e87fuGStnpY+cOzuKSNzkyWXYK+fnLbMw 5jUAsigtxCKx76pECaeoCJjMO/vwBtFwq5mT8q3lJNZbXS6vM9RL7thdNJl3NSW9VE+2 Mcy7dwsGWvTfU6JIRRa3qRb+1OzPYugY2E57GSbtQ6V0RQzNXycbbSyYqM+xH80nKwKg BRLQ==
MIME-Version: 1.0
X-Received: by 10.68.203.103 with SMTP id kp7mr3255955pbc.165.1371656416006; Wed, 19 Jun 2013 08:40:16 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Wed, 19 Jun 2013 08:40:15 -0700 (PDT)
In-Reply-To: <51C1CFEC.50206@innovationslab.net>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im> <51C1CD95.4060106@innovationslab.net> <51C1CED7.8090803@stpeter.im> <51C1CFEC.50206@innovationslab.net>
Date: Wed, 19 Jun 2013 16:40:15 +0100
Message-ID: <CADnDZ88xNqSRVaN=5KKfHbsxTWVaF-EXftwcxRCTgWiz_AUH8w@mail.gmail.com>
Subject: Re: IETF Diversity
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b15af5d6e1b9304df83a5a8
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, 19 Jun 2013 15:40:26 -0000

--047d7b15af5d6e1b9304df83a5a8
Content-Type: text/plain; charset=ISO-8859-1

I think all need mentoring. It is a both way learning for top and down
levels. So maybe newcomer can be mentoring to management of what is a
newcomer like these days :-)

AB


--047d7b15af5d6e1b9304df83a5a8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I think all need mentoring. It is a both way learning=
 for top and down levels. So maybe newcomer can be mentoring to=A0managemen=
t of what is a newcomer like these days :-)</div><div>=A0</div><div>AB</div=
></div>

--047d7b15af5d6e1b9304df83a5a8--

From hsantos@isdg.net  Wed Jun 19 08:44:38 2013
Return-Path: <hsantos@isdg.net>
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 3F03321F9D56 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:44:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Sbp6c5e9gIc2 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:44:20 -0700 (PDT)
Received: from secure.winserver.com (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2DEAF21F9D4F for <ietf@ietf.org>; Wed, 19 Jun 2013 08:44:19 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2324; t=1371656648; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=FAn41wG dYcZLxtViqvplF7QBbDc=; b=BT/f7CpqfVXp+gX66FsVYujGH8oGMKgBykOv9D5 i1tBlVynnrjg6h8b5qGH1X4GZmEhTRunp5PTlEEEhr6eFLIO7hVLAdswK3Jwn387 qiRAvABtlsdf2mn7+aNH4t0RSBadhBic/Zcvpe2jLnUuVfqxqcZ4l9zC5BOXLdpo iKCc=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 19 Jun 2013 11:44:08 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2414194080.4394.1536; Wed, 19 Jun 2013 11:44:07 -0400
Message-ID: <51C1D131.2030500@isdg.net>
Date: Wed, 19 Jun 2013 11:41:37 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im> <51C1CB09.5020109@dcrocker.net>
In-Reply-To: <51C1CB09.5020109@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 15:44:38 -0000

It is one thing to follow this practice of, for lack of a better word, 
ignorance, for yourself but to advocate it as a whole for the rest of 
the community to follow is probably not the optimal path when addressing 
the "diversity" conflicts.  Everyone has a motive and interest in what 
they do, why they are here, etc. You will never be able to eliminate 
this nature element among people, especially among such a diverse group 
of disciplines, especially as the growth of electronic diversity 
continues.  I hate to see "Rough Consensus By Osmosis" being one of the 
recommendation outcomes from the Diversity Design Team.

Thank You

Sincerely,
Hector Santos, CTO
Santronics Software, Inc.

On 6/19/2013 11:15 AM, Dave Crocker wrote:
> On 6/19/2013 8:08 AM, Peter Saint-Andre wrote:
>> On 6/19/13 8:32 AM, Dave Crocker wrote:
>>> On 6/19/2013 5:35 AM, Dave Cridland wrote:
>>>> Phillip Hallam-Baker wrote:
>>>> There is a real problem with accountability and transparency in the
>>>> IETF
>>>> constitution which was designed by a bunch of old boys to maintain
>>>> control in their own hands. Peter is a member of the IETF establishment
>>>> so of course he sees no structural problem.
>>>> PSA's been an AD, yes, but:
>>>
>>>
>>> Forgive me, but you just responded to a rather unpleasant ad hominem.
>>>
>>> We should not sustain such threads.
> ...
>> My apologies for the extremely egregious manner in which I stated the
>> point. It was not directed personally at Mr. Hallam-Baker, but at all of
>> us who talk and don't take action -- myself very much included.
>
>
> oh dear.  /my/ apologies for being unclear.  I didn't mean that /your/
> posting was an ad hominem, but that you were responding to one.
>
> Your own point is fine and constructive.  Worthy thought.  Worth
> pursuing.  Offered independently it would have been dandy.
>
> My point is that we need to stop tolerating ad hominem content and that
> starts by not responding to it.  Posting a reply -- even one that
> ignores the offensive content -- constitutes tolerance for the behavior.
>
> The view that we should be resilient against such behavior is long past
> its time.  We should, instead, demand professional demeanor, and that
> means shunning behavior that attacks people and their motives.
>
> d/
>


From stpeter@stpeter.im  Wed Jun 19 08:56:38 2013
Return-Path: <stpeter@stpeter.im>
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 2208421F9D9A for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4hW0SZBmh-a8 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:56:33 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 18CAB21F9D7E for <ietf@ietf.org>; Wed, 19 Jun 2013 08:56:27 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C59D141278; Wed, 19 Jun 2013 09:56:23 -0600 (MDT)
Message-ID: <51C1D4A5.5070205@stpeter.im>
Date: Wed, 19 Jun 2013 09:56:21 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <51C1CD9A.2020004@stpeter.im> <51C1CE67.3020703@gmail.com>
In-Reply-To: <51C1CE67.3020703@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 15:56:38 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/19/13 9:29 AM, Melinda Shore wrote:
> On 6/19/13 7:26 AM, Peter Saint-Andre wrote:
>> On 6/19/13 9:22 AM, Melinda Shore wrote:
>>> Don't know about that one.  In the US, at least, legal
>>> mandates have typically led social change, at least when it
>>> comes to civil rights, etc.
>> That's a topic for the ietf-philosophy discussion list, methinks.
>> :-)
> 
> To the extent that unexamined assertions about how social/cultural 
> change works are being used to explain why the organization
> doesn't need to be particularly proactive, I don't think so.

Why do you believe that my opinions are unexamined? I have been
thinking and reading about social, cultural, and personal change for a
very long time.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRwdSkAAoJEOoGpJErxa2poHoQAJq66EMUMW0GST2GjbpT5r+D
qRUd7T1m4yI+ZY2YNSBC+HjE9Sh7F+zBinFxttV6/uzGPwUnl39Ag22YepbDPY0o
UUut8w70FxUilepdL1AGSiu1tJZjla+RTEul13I0mV/YNDAMHME+wIE0u8Bxt4BU
hh0U9MLGclmzKr/yTnly1kRBY2acS0VexN4z7gNNTgmsmE7/jKUIOstpjaqKEvFs
OLX6X4HSu+5tQfVN6BjLemXTFHNjZJGAxQFISaELb0sJHISh0BFO9fNe2Lmi0fhM
bYDKSrGUpOm1zjx0qlYetZndLlcDMltkzJ3/JvcgGsTafIjwRV+V+ZximmuB2NLw
m8xsFi70lnErudpk2hKP9ep3bpkZUnXaniuEQFZHEGeijy5Lxpfe9KsarsppKRPu
mQGLUYmtLDO5C/Z6GWqI/IEXkPcBXGZ7hIu3AsfXVtIn/bV/RmG1PhXL8vxQ1rTf
DEBD5l9II/cZvvVEoBhvL4BvfF2rB6SH0mJC6cp/2ffr9pNZ7/XHb8DFh58sP17b
9UacSl060g+2Os1It7CIEDMBahZaM1CSztK/JwcVueDooYUGbjizHJd6zYQMfL0h
gYjBDcptnF/R11zHgYnHYtIoRKkSZrF3SEE8c6TLkpSt1CpAnEehj6iSBax5qs3q
eO8eYLKl7/L+vPnNlFG/
=9qss
-----END PGP SIGNATURE-----

From stpeter@stpeter.im  Wed Jun 19 08:59:13 2013
Return-Path: <stpeter@stpeter.im>
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 79CB621F9D98 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 MtK3S-q6NvtD for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 08:59:08 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id CF6C621F997F for <ietf@ietf.org>; Wed, 19 Jun 2013 08:59:08 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 3211A41278; Wed, 19 Jun 2013 09:59:09 -0600 (MDT)
Message-ID: <51C1D54A.2060600@stpeter.im>
Date: Wed, 19 Jun 2013 09:59:06 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im> <51C1CD95.4060106@innovationslab.net> <51C1CED7.8090803@stpeter.im> <51C1CFEC.50206@innovationslab.net>
In-Reply-To: <51C1CFEC.50206@innovationslab.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 15:59:13 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/19/13 9:36 AM, Brian Haberman wrote:
> On 6/19/13 11:31 AM, Peter Saint-Andre wrote:
>> On 6/19/13 9:26 AM, Brian Haberman wrote:
>>> On 6/19/13 11:08 AM, Peter Saint-Andre wrote:
>>> 
>>>> 
>>>> My point, poorly expressed though it was, is that it's not
>>>> productive for us all to wait from word on high before taking
>>>> positive action. Members of the IESG, IAB, IOAC, or any other
>>>> "official" body are just folks who are temporarily serving
>>>> the community in a defined role. If we want to change the
>>>> culture of our community with respect to diversity, it's
>>>> better for us to work to encourage, nurture, and mentor
>>>> particular individuals.
>>> 
>>> To help facilitate the mentoring aspect, there will be a call
>>> soon for volunteers to act as mentors for newcomers (starting
>>> with IETF 87). Once the web page for the mentoring program with
>>> all the information is up, you should be seeing a call for
>>> mentors.
>>> 
>>> We hope that this type of program will aid in assisting newer
>>> members of the IETF community become more involved and
>>> productive in our activities.
>> 
>> That's great!
>> 
>> However, why do we need to wait for a program? Can't we simply be
>> human, introduce ourselves to new participants, reach out to
>> individual contributors about becoming document shepherds,
>> document editors, WG secretaries, WG chairs, BoF chairs, etc.?
>> That's what I've been doing, and so far the results have been
>> positive.
> 
> I would highly encourage people taking that initiative and
> appreciate folks who do that of their own accord.
> 
>> 
>> I'm not saying that's the only way to make progress, but I see it
>> as very much worth the effort.
> 
> Absolutely agree.  The goal of this experimental mentoring program
> is to provide people who may not be sure *how* to be mentors a
> framework to work within.

That sounds quite helpful! I'm not completely sure how to be a mentor,
either, I'm just doing the best I can given what I know so far...

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRwdVKAAoJEOoGpJErxa2pHYsP/32PjmK7t+mUphABDzRMV7Nt
WJAwkax0mKf+L84k3L3RJF4WdLRNYJJa+IH8IXsw/3BI3zZy4Ez78/gx8Z26vPdv
Vk5Z/qy+mTG8MCOSblbZKxOodFFdnV3JOFPUqQlp/RnE86uXQg5N5d0ZECRRxtb9
62wZm+uHIxVkouCkIXTYo+IZgm3ag428UnWtTU032GIRorbzSkYtQgNv/HGJ9STt
2w1iIfkFU4ZgO42ik2nJpAzLVh7ExzhtHgK30faPoDdRAzse4OYSGeilv1lrOx0x
HcNoU3cQCIawBCY3FvK5QFNAiJTrvLtWIgn/4wJG/oa4vZJE6xHbKkp1AfowjDDs
6ExKdpH8DwudzBgtY9D9lNyqpeLXjmHCpHWBe6Ngzor89JUtnrdlJFn8XNb+bwJt
Ba5xuOPn+bjD7dmMyHjda0kjFN489bqQ6d+VfNLGsaXfd2Be8c1MIv6KiWZjgTrp
rR+4b3i4qHff33yI158zV+FnjHlgzHUVoCskQ+EMboG6GMHqe0RRd08cyKNU5gvY
CJEvtyvg7mmQG2FI0YJlyT1uxNWBTK6P+ziSrcdySevnVNAliVQtohaHaFa6oZZA
nx1mCbZUE9TGKl1iIBfK4pz88Q16Ygk5Z7JB4zFKgKEk3J41pxAT5C3ekK5cap7V
mPnBDKexXTU9/+Um+kwL
=uq52
-----END PGP SIGNATURE-----

From melinda.shore@gmail.com  Wed Jun 19 09:01:15 2013
Return-Path: <melinda.shore@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 4756B21F9A62 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Q27b9HIXXFyJ for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:01:03 -0700 (PDT)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id 0A15F21F9DE8 for <ietf@ietf.org>; Wed, 19 Jun 2013 09:00:36 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id 14so5175872pdj.40 for <ietf@ietf.org>; Wed, 19 Jun 2013 09:00:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=JJ1ew++p0RuOXdF1ESbSOvMHGDqpTUoz8UCbwEj2NEg=; b=B81teuXHfh62oqadNEeK+WhLxXKh6me8A3yS/OnLb5p5Gz8hiP8DbyLqJOv6Ort+BE sh5g6QIEfHfrmXMZMYVqgU3JXPgDcODiXW8ttj4z7aSmvXMJTQTRiGeVLvZBa/c8KCyV SDSaJAQsrWoc0OZVkYRuBr7eL8l00M18NrLG+RloXUt1bPqq2nV9TBwJidl/aZNTSA2R QydtHCzHAqzJ/yvXCb5ZVcwSKfsK4YI5CRXKWkJJ+De5uyD1fAtLFfCId6RE3x+keypo 9sLZTGRUSuNsiDj8OQlEIQAPQAuGfYY44pZ2pGk5jaHpZr3hdfdgV/T4LhD2sD9Ke5rd Atsg==
X-Received: by 10.68.213.42 with SMTP id np10mr3499235pbc.37.1371657634779; Wed, 19 Jun 2013 09:00:34 -0700 (PDT)
Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id z5sm23688659pbk.0.2013.06.19.09.00.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 09:00:33 -0700 (PDT)
Message-ID: <51C1D59F.6010608@gmail.com>
Date: Wed, 19 Jun 2013 08:00:31 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <51C1CD9A.2020004@stpeter.im> <51C1CE67.3020703@gmail.com> <51C1D4A5.5070205@stpeter.im>
In-Reply-To: <51C1D4A5.5070205@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 16:01:16 -0000

On 6/19/13 7:56 AM, Peter Saint-Andre wrote:
> Why do you believe that my opinions are unexamined? I have been
> thinking and reading about social, cultural, and personal change for a
> very long time.

You made an assertion that's at least a little ahistorical, you
used it to support an argument against organizational change, and
when I disagreed you went to the "Let's not talk about it" place.

Melinda


From ed.lewis@neustar.biz  Wed Jun 19 09:01:57 2013
Return-Path: <ed.lewis@neustar.biz>
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 1E06621F9DE9 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:01:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.369
X-Spam-Level: 
X-Spam-Status: No, score=-100.369 tagged_above=-999 required=5 tests=[AWL=-0.833, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, SARE_FWDLOOK=1.666, USER_IN_WHITELIST=-100]
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 TL1i7FqfsiKR for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:01:47 -0700 (PDT)
Received: from smtp118.ord1c.emailsrvr.com (smtp118.ord1c.emailsrvr.com [108.166.43.118]) by ietfa.amsl.com (Postfix) with ESMTP id 66B9721F9A29 for <ietf@ietf.org>; Wed, 19 Jun 2013 09:01:30 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id D4E091B81B6; Wed, 19 Jun 2013 12:01:20 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: edlewis-AT-ogud.com) with ESMTPSA id 865141B81E0;  Wed, 19 Jun 2013 12:01:20 -0400 (EDT)
Subject: Lessons from PROVREG WG was Re: IETF, ICANN and Whois...
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B024C7A4-58C6-42A1-9CCD-7919874BBDC6"
From: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <002D3B5B-3B2C-495E-A500-A95C1856355D@vpnc.org>
Date: Wed, 19 Jun 2013 12:01:18 -0400
Message-Id: <9A9C6AA8-08FD-4022-AEAE-D4C725456E3F@neustar.biz>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <6.2.5.6.2.20130619000239.0b0ebd38@resistor.net> <DACC4421-03B2-4F64-856C-FF3080B587AE@frobbit.se> <002D3B5B-3B2C-495E-A500-A95C1856355D@vpnc.org>
To: ietf <ietf@ietf.org>
X-Mailer: Apple Mail (2.1283)
Cc: Edward Lewis <ed.lewis@neustar.biz>
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, 19 Jun 2013 16:01:57 -0000

--Apple-Mail=_B024C7A4-58C6-42A1-9CCD-7919874BBDC6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Jun 19, 2013, at 10:01, Paul Hoffman wrote:

> But there is no EPP WG. And WEIRDS is supposed to only be =
forward-looking, not dealing with practices with the current protocol.


Brief history and then maybe a point.  (Written as one of the co-chairs =
of the PROVREG WG.)

In December 2000 a BoF was held to start the work on EPP at the San =
Diego meeting.  A few months passed by before the PROVREG WG was =
formalized. I was told by a then-IESG member that the decision to form =
the group was contentious because EPP was to be a limited scope (B2B if =
you will) protocol and not something for general use.

The WG progressed by 2003 to have a nearly complete specification when =
it ran into IESG pushback.  I was told that the group was nearly =
shutdown despite the WG having come to consensus.  In March 2003 the =
group met for the last time, nailing down an acceptable (to the IESG) =
set of documents.

The group formally closed in 2004 once the drafts passed the RFC Editor =
queue.  At the time, the queue was quite lengthy (in duration) and in =
fairness there was a dependency on a trailing document.

In 2009 (5 years hence) at a ccTLD registry meeting the chorus of "EPP =
stinks" got quite loud.  What made this irritating was the EPP had =
progressed to Full Standard (Proposed, Draft and then Full) in full =
accordance with IETF procedures and policies.  So I took on a little =
exercise to figure out why, on the one hand, operators dissed EPP but =
the protocol engineers elevated it.

First, once the PROVREG WG was shutdown the mail list was kept open.  At =
the same time (2004-2009) the industry EPP that supports blossomed.  The =
new majority (operators coming on line then) were not aware of the mail =
list as the list had no cover, no publicity, no "home" if you will.  =
This pretty much was the root cause, as it spawned a side effect.

The material deficiency surrounding the chorus of "EPP stinks" was due =
to the new majority not having access to the originators of the =
documents and the lack of publicity for the "5th" document.  There was =
conventional wisdom built of how to extend the protocol that was not =
in-line with the intent of the design and this was causing, well, =
chaffing.  Was there a document describing what should have been done?  =
Yes, the "5th" document.  The first four EPP documents were the ones =
elevated through the standards process while the 5th was just =
informational.  As the first 4 were elevated, the 5th was forgotten, =
again, because the link to it was lost.  (RFP's would cite the 4 latest =
ones, the Full Standard, and not the original 5th.)

Once the new majority was "rejoined" with the mail list communications =
were re-opened between the new majority and the originators.  The =
technical issues were quickly solved (at one of the "formal" Bar BoFs in =
spring 2003/Anaheim).  With the publicity surrounding some open-source =
EPP software the plethora of extensions became less of a concern to the =
operators.  (Software trumps spec!)

To underscore the point, despite sporadic traffic in the 2004-2009 =
timeframe, today the list is moderately active.  There are new phases of =
operations that EPP supports, so there is constant growth in =
engineering.

At the next round of the ccTLD meeting that started my task, all of this =
was explained.  The alternative was, continue on with this re-patched =
relationship or try to invent EPP 2.0 - meaning a whole new development, =
deployment, and adoption effort.  The consensus was, forget EPP 2.0, the =
situation was now "good to go."  There's been no more choruses of "EPP =
stinks."

Looking back in hindsight, what would help is to have some means for the =
IETF to provide a maintenance vehicle for it's products.  Or realize =
that the "waterfall model" that seems to be in place is no longer =
appropriate.  (As if you've never heard that before!)  The world changes =
(the new majority) but the IETF acts as if "once it's an RFC it is =
done."

This is an example of an ICANN initiated piece of work that barely got =
into the IETF, the IETF completed it in a way that has benefit beyond =
ICANN (meaning many ccTLDs have adopted it on their own accord), but the =
IETF didn't make it easy and didn't help the deployment.  I hope the =
latter phase isn't repeated with the WEIRDS WG and RDAP.

PS. With WEIRDS there's a much more substantial industry and majority =
than "back in the day".  Just something to keep in mind.

=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Edward Lewis            =20
NeuStar                    You can leave a voice message at =
+1-571-434-5468

There are no answers - just tradeoffs, decisions, and responses.


--Apple-Mail=_B024C7A4-58C6-42A1-9CCD-7919874BBDC6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 19, 2013, at 10:01, Paul Hoffman =
wrote:</div><div><br></div><blockquote type=3D"cite"><div>But there is =
no EPP WG. And WEIRDS is supposed to only be forward-looking, not =
dealing with practices with the current =
protocol.</div></blockquote></div><div><br></div><div>Brief history and =
then maybe a point. &nbsp;(Written as one of the co-chairs of the =
PROVREG WG.)</div><div><br></div><div>In December 2000 a BoF was held to =
start the work on EPP at the San Diego meeting. &nbsp;A few months =
passed by before the PROVREG WG was formalized. I was told by a =
then-IESG member that the decision to form the group was contentious =
because EPP was to be a limited scope (B2B if you will) protocol and not =
something for general use.</div><div><br></div><div>The WG progressed by =
2003 to have a nearly complete specification when it ran into IESG =
pushback. &nbsp;I was told that the group was nearly shutdown despite =
the WG having come to consensus. &nbsp;In March 2003 the group met for =
the last time, nailing down an acceptable (to the IESG) set of =
documents.</div><div><br></div><div>The group formally closed in 2004 =
once the drafts passed the RFC Editor queue. &nbsp;At the time, the =
queue was quite lengthy (in duration) and in fairness there was a =
dependency on a trailing document.</div><div><br></div><div>In 2009 (5 =
years hence) at a ccTLD registry meeting the chorus of "EPP stinks" got =
quite loud. &nbsp;What made this irritating was the EPP had progressed =
to Full Standard (Proposed, Draft and then Full) in full accordance with =
IETF procedures and policies. &nbsp;So I took on a little exercise to =
figure out why, on the one hand, operators dissed EPP but the protocol =
engineers elevated it.</div><div><br></div><div>First, once the PROVREG =
WG was shutdown the mail list was kept open. &nbsp;At the same time =
(2004-2009) the industry EPP that supports blossomed. &nbsp;The new =
majority (operators coming on line then) were not aware of the mail list =
as the list had no cover, no publicity, no "home" if you will. =
&nbsp;This pretty much was the root cause, as it spawned a side =
effect.</div><div><br></div><div>The material deficiency surrounding the =
chorus of "EPP stinks" was due to the new majority not having access to =
the originators of the documents and the lack of publicity for the "5th" =
document. &nbsp;There was conventional wisdom built of how to extend the =
protocol that was not in-line with the intent of the design and this was =
causing, well, chaffing. &nbsp;Was there a document describing what =
should have been done? &nbsp;Yes, the "5th" document. &nbsp;The first =
four EPP documents were the ones elevated through the standards process =
while the 5th was just informational. &nbsp;As the first 4 were =
elevated, the 5th was forgotten, again, because the link to it was lost. =
&nbsp;(RFP's would cite the 4 latest ones, the Full Standard, and not =
the original 5th.)</div><div><br></div><div>Once the new majority was =
"rejoined" with the mail list communications were re-opened between the =
new majority and the originators. &nbsp;The technical issues were =
quickly solved (at one of the "formal" Bar BoFs in spring 2003/Anaheim). =
&nbsp;With the publicity surrounding some open-source EPP software the =
plethora of extensions became less of a concern to the operators. =
&nbsp;(Software trumps spec!)</div><div><br></div><div>To underscore the =
point,&nbsp;despite sporadic traffic in the 2004-2009 timeframe, today =
the list is moderately active. &nbsp;There are new phases of operations =
that EPP supports, so there is constant growth in =
engineering.</div><div><br></div><div>At the next round of the ccTLD =
meeting that started my task, all of this was explained. &nbsp;The =
alternative was, continue on with this re-patched relationship or try to =
invent EPP 2.0 - meaning a whole new development, deployment, and =
adoption effort. &nbsp;The consensus was, forget EPP 2.0, the situation =
was now "good to go." &nbsp;There's been no more choruses of "EPP =
stinks."</div><div><br></div><div>Looking back in hindsight, what would =
help is to have some means for the IETF to provide a maintenance vehicle =
for it's products. &nbsp;Or realize that the "waterfall model" that =
seems to be in place is no longer appropriate. &nbsp;(As if you've never =
heard that before!) &nbsp;The world changes (the new majority) but the =
IETF acts as if "once it's an RFC it is =
done."</div><div><br></div><div>This is an example of an ICANN initiated =
piece of work that barely got into the IETF, the IETF completed it in a =
way that has benefit beyond ICANN (meaning many ccTLDs have adopted it =
on their own accord), but the IETF didn't make it easy and didn't help =
the deployment. &nbsp;I hope the latter phase isn't repeated with the =
WEIRDS WG and RDAP.</div><div><br></div><div>PS. With WEIRDS there's a =
much more substantial industry and majority than "back in the day". =
&nbsp;Just something to keep in mind.</div><div><br></div><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D<span></sp=
an>-=3D-=3D-=3D-<span class=3D"Apple-style-span" style=3D"border-collapse:=
 separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>Edward =
Lewis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span></s=
pan>&nbsp;&nbsp;&nbsp;<br>NeuStar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<span></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; You can leave a voice message at =
+1-571-434-5468<br><br>There are no answers - just tradeoffs, decisions, =
and responses.</div></div></div></span></span>
</div>
<br></body></html>=

--Apple-Mail=_B024C7A4-58C6-42A1-9CCD-7919874BBDC6--

From kathleen.moriarty@emc.com  Wed Jun 19 09:11:31 2013
Return-Path: <kathleen.moriarty@emc.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 EDB9F21F99D6 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 viZ1qVxhhMYJ for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:11:26 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 094D321F9C1E for <ietf@ietf.org>; Wed, 19 Jun 2013 09:11:25 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5JGBEmt004118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Jun 2013 12:11:22 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Wed, 19 Jun 2013 12:11:02 -0400
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.222.70.203]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5JGB0U6004891; Wed, 19 Jun 2013 12:11:00 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub06.corp.emc.com ([128.222.70.203]) with mapi; Wed, 19 Jun 2013 12:11:00 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Melinda Shore <melinda.shore@gmail.com>, Peter Saint-Andre <stpeter@stpeter.im>
Date: Wed, 19 Jun 2013 12:11:00 -0400
Subject: RE: IETF Diversity
Thread-Topic: IETF Diversity
Thread-Index: Ac5tBlkwzu0AzOfkQBicP0DKkHKrawAAG2Nh
Message-ID: <F5063677821E3B4F81ACFB7905573F24DF0530E7@MX15A.corp.emc.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <51C1CD9A.2020004@stpeter.im> <51C1CE67.3020703@gmail.com> <51C1D4A5.5070205@stpeter.im>,<51C1D59F.6010608@gmail.com>
In-Reply-To: <51C1D59F.6010608@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <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, 19 Jun 2013 16:11:32 -0000

A little earlier in the thread, ways to improve things came up.  I presente=
d at an international conference in Bangkok this week on the subject area c=
overed by MILE.  While the focus was intended to be more on how we can look=
 at the problem space to make faster/more effective progress, standards wil=
l enable some of those activities.  The second half of the talk provided ba=
ckground on MILE, what we are trying to do and gave the audience a general =
challenge as well as had specific requests for help.  My last slide was on =
how to engage in the IETF.  Outreach and helping people understand how they=
 can be effective within the IETF may be useful for other WGs as well and c=
ould help improve diversity.  I had 2 requests following the talk to give t=
he same presentation at other conferences and will likely do them to assist=
 in this area as well as to make faster progress (and hopefully drive peopl=
e to think about how to share information more effectively.  There are many=
 opportunities for people to help in this space. =20

Best regards,
Kathleen
________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Melinda Sh=
ore [melinda.shore@gmail.com]
Sent: Wednesday, June 19, 2013 12:00 PM
To: Peter Saint-Andre
Cc: ietf@ietf.org
Subject: Re: IETF Diversity

On 6/19/13 7:56 AM, Peter Saint-Andre wrote:
> Why do you believe that my opinions are unexamined? I have been
> thinking and reading about social, cultural, and personal change for a
> very long time.

You made an assertion that's at least a little ahistorical, you
used it to support an argument against organizational change, and
when I disagreed you went to the "Let's not talk about it" place.

Melinda


From stpeter@stpeter.im  Wed Jun 19 09:12:42 2013
Return-Path: <stpeter@stpeter.im>
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 C643521F9D68 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:12:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 WTTHZhevr1hY for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:12:38 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 54E5821F9D64 for <ietf@ietf.org>; Wed, 19 Jun 2013 09:12:37 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0A81641278; Wed, 19 Jun 2013 10:12:37 -0600 (MDT)
Message-ID: <51C1D873.9090303@stpeter.im>
Date: Wed, 19 Jun 2013 10:12:35 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <51C1CD9A.2020004@stpeter.im> <51C1CE67.3020703@gmail.com> <51C1D4A5.5070205@stpeter.im> <51C1D59F.6010608@gmail.com>
In-Reply-To: <51C1D59F.6010608@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 16:12:42 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/19/13 10:00 AM, Melinda Shore wrote:
> On 6/19/13 7:56 AM, Peter Saint-Andre wrote:
>> Why do you believe that my opinions are unexamined? I have been 
>> thinking and reading about social, cultural, and personal change
>> for a very long time.
> 
> You made an assertion that's at least a little ahistorical,

That depends on which historians you've been reading.

> you used it to support an argument against organizational change,

No, I didn't. Please re-read what I wrote.

> and when I disagreed you went to the "Let's not talk about it"
> place.

I simply don't think it's productive to have a long discussion on the
ietf@ietf.org list about the philosophy of history.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRwdhzAAoJEOoGpJErxa2p950P/RzHdo8O+EJqF5IUpDzPysCM
Zr6jmf64rfo8HMTBg23+HT1zHrPyyU3djEE6YnjVH46mWjC3CGKjlmK9PMlSBVfm
sSye8fW/G+HVVO6n6xit7msWCN15ZwAMzC57OjDz7l2s5UvSzfRO2nkwl93dpPAA
h2+gz3DitjXBaL9L8Hb2llqXkpjt6Z69EgCv76kiXcoVYr6GrFgbN6dmD2+9PIuG
ju6PMAdqpuvOT9zpAwx2hoAHU9mayut6HkD18NuaOpTlRVcRHA2+civtR6NqrmoA
fRoz8zL+vTEVNquYsuRXA4cRMI3SEni0FH7AybhUQCqWPLq850acAzYtY9MA+vb7
Vgezd5zV6F4nuUgCnyoiM61SaLeMjOgQeP9X5Qb3Ellkn/FyYNfuPp1HbCrqKkaP
tpXq4SEXzVJldI9XCPlltjmsuUFSNiaRW5trlbaNlqZzaEtRORjm30uB4wGphocq
F+9UotNx2d/KERHzortewpRVBKPGo/M5++3aRE5C6GGy/NjIvYD8k/Drj8sHxipr
/6P8jadKiow05wHG9Al9hlrFguYiuV6vyjWJo6gXSvqp9QeWfPeYSGgYpePga97B
EH27dgX6+OmYog0NwWp/1TLx6g/cBVsBo3y/rQWifeNeuBO6zaJL3kiy9QzgQnrJ
clPXdOR90n1jv0bTeBKf
=LGTI
-----END PGP SIGNATURE-----

From joelja@bogus.com  Wed Jun 19 09:22:28 2013
Return-Path: <joelja@bogus.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 A544421F9C6B for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.712
X-Spam-Level: 
X-Spam-Status: No, score=-102.712 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ASEMV6m7MLCq for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:22:28 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 17D2B21F9C61 for <ietf@ietf.org>; Wed, 19 Jun 2013 09:22:27 -0700 (PDT)
Received: from joels-MacBook-Air.local ([199.108.68.6]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r5JGMJhQ062407 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 19 Jun 2013 16:22:24 GMT (envelope-from joelja@bogus.com)
Message-ID: <51C1DAB5.1060802@bogus.com>
Date: Wed, 19 Jun 2013 09:22:13 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: Edward Lewis <ed.lewis@neustar.biz>, ietf <ietf@ietf.org>
Subject: Re: Lessons from PROVREG WG was Re: IETF, ICANN and Whois...
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com>	<CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com>	<4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>	<D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>	<6.2.5.6.2.20130619000239.0b0ebd38@resistor.net>	<DACC4421-03B2-4F64-856C-FF3080B587AE@frobbit.se>	<002D3B5B-3B2C-495E-A500-A95C1856355D@vpnc.org> <9A9C6AA8-08FD-4022-AEAE-D4C725456E3F@neustar.biz>
In-Reply-To: <9A9C6AA8-08FD-4022-AEAE-D4C725456E3F@neustar.biz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 19 Jun 2013 16:22:27 +0000 (UTC)
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, 19 Jun 2013 16:22:28 -0000

On 6/19/13 9:01 AM, Edward Lewis wrote:
>
> Looking back in hindsight, what would help is to have some means for 
> the IETF to provide a maintenance vehicle for it's products.  Or 
> realize that the "waterfall model" that seems to be in place is no 
> longer appropriate.  (As if you've never heard that before!)  The 
> world changes (the new majority) but the IETF acts as if "once it's an 
> RFC it is done."
>
Are we perhaps not using area meetings with the effectiveness that we 
should be? Now that I'm cutting my teeth on the AD sponsoring thing I'm 
begining to understand why AD's are reluctant to use the tool liberally 
and the next best place assuming the existance of a critical mass of 
existing participants would be for example appsawg.
> This is an example of an ICANN initiated piece of work that barely got 
> into the IETF, the IETF completed it in a way that has benefit beyond 
> ICANN (meaning many ccTLDs have adopted it on their own accord), but 
> the IETF didn't make it easy and didn't help the deployment.  I hope 
> the latter phase isn't repeated with the WEIRDS WG and RDAP.
>
> PS. With WEIRDS there's a much more substantial industry and majority 
> than "back in the day".  Just something to keep in mind.
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Edward Lewis
> NeuStar           You can leave a voice message at +1-571-434-5468
>
> There are no answers - just tradeoffs, decisions, and responses.
>


From melinda.shore@gmail.com  Wed Jun 19 09:25:28 2013
Return-Path: <melinda.shore@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 7711F21F9D7A for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 l7udH2Od93By for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:25:27 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id D3A6521F9D7B for <ietf@ietf.org>; Wed, 19 Jun 2013 09:25:27 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa11so5342544pad.19 for <ietf@ietf.org>; Wed, 19 Jun 2013 09:25:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=VdkfStwwKMLwP8u7RcvlSmy0kOP8nuJFuTCWbRX3Hb8=; b=jdp+8OgB2FLu7K29ffV9bxER1cU3hkygNwyVuB/sb5QJm4XTZHyvgi3qvrMvXwHWVS QWNGc0eKtNSVOy0WCOv50/w3LbsiigpTV4n0/0SOE82cVlOm7wqqyceogEg6VX8hOVzp k7Ixx4Ej7NXZXFmRqUPZDoRPOze4XmI6v1r6Bwq/2LBfeilo9I88jYmsG68NxNKcqiiu ZY/h++gZ5cG0+cRbj4EWq6hSGbljMq43KPvesadM4lsxFvoewrX9BU7SiUnYe8UMkTjo QGYt06ajhkud/Sl1DgqPEejAkFJ9e0R4YTd6ZZbTUwHhTujwJUPuFZ1fk3N72uozZ9Ou PuoA==
X-Received: by 10.66.149.5 with SMTP id tw5mr7554549pab.87.1371659127569; Wed, 19 Jun 2013 09:25:27 -0700 (PDT)
Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id ix3sm23712921pbc.37.2013.06.19.09.25.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 09:25:26 -0700 (PDT)
Message-ID: <51C1DB74.9020409@gmail.com>
Date: Wed, 19 Jun 2013 08:25:24 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <51C1CD9A.2020004@stpeter.im> <51C1CE67.3020703@gmail.com> <51C1D4A5.5070205@stpeter.im> <51C1D59F.6010608@gmail.com> <51C1D873.9090303@stpeter.im>
In-Reply-To: <51C1D873.9090303@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 16:25:28 -0000

On 6/19/13 8:12 AM, Peter Saint-Andre wrote:
> On 6/19/13 10:00 AM, Melinda Shore wrote:
>> On 6/19/13 7:56 AM, Peter Saint-Andre wrote:
>>> Why do you believe that my opinions are unexamined? I have been 
>>> thinking and reading about social, cultural, and personal change
>>> for a very long time.
>>
>> You made an assertion that's at least a little ahistorical,
> 
> That depends on which historians you've been reading.

Peter, it's a fact in the US and Canada that court cases preceded
civil rights protections which preceded social change.  This has been
true for racial minorities, women, glbt folk, etc.  I expect that
there are historians who'd argue otherwise but allow me to suggest
that if so they are very, very far out of the mainstream.

It seems to me that without some sort of institutional change it's
likely that for a few cycles nomcoms will try to be "sensitive" to
the question of the underrepresentation of women and then it will
be back to business as usual, because that's the way these things
go.  It's unusual for people to voluntarily surrender their
privilege.

Melinda


From stpeter@stpeter.im  Wed Jun 19 09:34:41 2013
Return-Path: <stpeter@stpeter.im>
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 1240D21F9D09 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4c0icnNMfccs for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:34:36 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A619621F9D1E for <ietf@ietf.org>; Wed, 19 Jun 2013 09:34:36 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id ACAAC41278; Wed, 19 Jun 2013 10:34:36 -0600 (MDT)
Message-ID: <51C1DD99.2070208@stpeter.im>
Date: Wed, 19 Jun 2013 10:34:33 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <51C1CD9A.2020004@stpeter.im> <51C1CE67.3020703@gmail.com> <51C1D4A5.5070205@stpeter.im> <51C1D59F.6010608@gmail.com> <51C1D873.9090303@stpeter.im> <51C1DB74.9020409@gmail.com>
In-Reply-To: <51C1DB74.9020409@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 16:34:41 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/19/13 10:25 AM, Melinda Shore wrote:
> On 6/19/13 8:12 AM, Peter Saint-Andre wrote:
>> On 6/19/13 10:00 AM, Melinda Shore wrote:
>>> On 6/19/13 7:56 AM, Peter Saint-Andre wrote:
>>>> Why do you believe that my opinions are unexamined? I have
>>>> been thinking and reading about social, cultural, and
>>>> personal change for a very long time.
>>> 
>>> You made an assertion that's at least a little ahistorical,
>> 
>> That depends on which historians you've been reading.
> 
> Peter, it's a fact in the US and Canada that court cases preceded 
> civil rights protections which preceded social change.  This has
> been true for racial minorities, women, glbt folk, etc.  I expect
> that there are historians who'd argue otherwise but allow me to
> suggest that if so they are very, very far out of the mainstream.

I'm not a great believer in intellectual mainstreams.

> It seems to me that without some sort of institutional change it's 
> likely that for a few cycles nomcoms will try to be "sensitive" to 
> the question of the underrepresentation of women and then it will 
> be back to business as usual, because that's the way these things 
> go.  It's unusual for people to voluntarily surrender their 
> privilege.

Thanks for giving me something to think about.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRwd2ZAAoJEOoGpJErxa2pq2wP/3Nigg7SweNe9PClvp57mprg
yKouJl0+5LuAzAw0jncVFN6KEuWebsF5cgLeYE1ttbJRCkwlrKDoxphq59MZHW8S
wbCtU+ziDfSVWBIwr1IqKggH2bpXGmfR8LNkDpRuOWjSvsXGNnb0BFlW5IF7Z95c
7+5yRHn+u8pKmLaSqxYS3bte6/EESGUL1GEgRbwXiFFszkHe4jNPEPB2yMgYFbJV
4COIfbTAt34lcC0SYrbQ2egL2wcVpiMlGUSFyDWtTszFS5skZHEbj/GgiAzTteIb
lEXa4inCHLJ/AJSKY6JgKKn0Oq5qemocJGL2590rYbI8kjoDDxmXwJD5cAUvf9WY
SLE8QNgQHO4pt0QoJ0AlWeHj/ZnnUz9tKOG1Va4ZAg05PIDZ65f5nILgwLc6fvHQ
wKpj/Fal8zrTBcEarT9lw/ctpTtYLnCbv+MmE6WXO0z0O2cCylTEEfCJICkbfq2Q
uID2n88bZdTFWeej1iA6oBlsTeXElOXiRwrp+6KTuZ/ua1N/uOIqbrzuLQXbXQ6J
CjqlIMLDbMfyuRQVh9bcr1u1hFPc6QH/ba0Z4m9DlBYC8f0HC7goteLgTQladUTz
/wLt4T4scuwWDd34LSRS2lwAB8CIZZTTnlfB0sMODwZCczesJKSTHJmp1+AdVCS0
Lc8jAuOmBQwcomy56keV
=oy8+
-----END PGP SIGNATURE-----

From Ted.Lemon@nominum.com  Wed Jun 19 09:45:53 2013
Return-Path: <Ted.Lemon@nominum.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 4B33821F9962 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.602
X-Spam-Level: 
X-Spam-Status: No, score=-106.602 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 s3DWluOet5Rc for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 09:45:46 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 2288221F9D22 for <ietf@ietf.org>; Wed, 19 Jun 2013 09:45:46 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUcHgOYfQyNvCXMqFFHQdGCJGykWtAq5/@postini.com; Wed, 19 Jun 2013 09:45:46 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 893721B8112 for <ietf@ietf.org>; Wed, 19 Jun 2013 09:45:45 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 7F50419005D; Wed, 19 Jun 2013 09:45:45 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 19 Jun 2013 09:45:45 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Diversity
Thread-Topic: IETF Diversity
Thread-Index: AQHObQAXJUyUZ5i2N0ispxbwenRGMpk9nRGAgAAXKQA=
Date: Wed, 19 Jun 2013 16:45:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com>
In-Reply-To: <51C1CCCB.3060601@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <0BF78DD4ECB5F34F9868815471D6DBA9@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <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, 19 Jun 2013 16:45:53 -0000

On Jun 19, 2013, at 11:22 AM, Melinda Shore <melinda.shore@gmail.com> wrote=
:
> Don't know about that one.  In the US, at least, legal mandates
> have typically led social change, at least when it comes to civil
> rights, etc.

Yup.   First the Civil Rights act, then Selma...  ;)


From narten@us.ibm.com  Wed Jun 19 10:06:34 2013
Return-Path: <narten@us.ibm.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 895AA21F9D9B for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 10:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 a3hQ4SBny3Gp for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 10:06:21 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id 541A121F9A57 for <ietf@ietf.org>; Wed, 19 Jun 2013 10:06:21 -0700 (PDT)
Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Wed, 19 Jun 2013 13:06:20 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 19 Jun 2013 13:06:18 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id BBD6738C8059 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:06:16 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r5JH4s0l296268 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:04:55 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r5JH4sWe026422 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:04:54 -0400
Received: from cichlid.raleigh.ibm.com ([9.57.84.204]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r5JH4qsI026221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Jun 2013 13:04:53 -0400
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r5JH4po3019185; Wed, 19 Jun 2013 13:04:51 -0400
Message-Id: <201306191704.r5JH4po3019185@cichlid.raleigh.ibm.com>
To: Edward Lewis <ed.lewis@neustar.biz>
Subject: Re: Lessons from PROVREG WG was Re: IETF, ICANN and Whois...
In-reply-to: <9A9C6AA8-08FD-4022-AEAE-D4C725456E3F@neustar.biz>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <6.2.5.6.2.20130619000239.0b0ebd38@resistor.net> <DACC4421-03B2-4F64-856C-FF3080B587AE@frobbit.se> <002D3B5B-3B2C-495E-A500-A95C1856355D@vpnc.org> <9A9C6AA8-08FD-4022-AEAE-D4C725456E3F@neustar.biz>
Comments: In-reply-to Edward Lewis <ed.lewis@neustar.biz> message dated "Wed, 19 Jun 2013 12:01:18 -0400."
Date: Wed, 19 Jun 2013 13:04:51 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13061917-5806-0000-0000-000021C91AF4
Cc: ietf <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, 19 Jun 2013 17:06:34 -0000

> Looking back in hindsight, what would help is to have some means for the 
> IETF to provide a maintenance vehicle for it's products.

I think there is some truth to this.

The reality has at times been that some WGs get a bit out of control
after they've been around a while, and getting them to deliver final
product is a challenge. Rather then finish a MIB or do the boring OAM
stuff that a real protocol needs, folk are much more interested in
develeping all sorts of extensions and other features. As such, ADs
often want to shut down the WG and make everyone go away.

The challenge of creating maintenance WGs is that unless handled well,
they become magnets for all the leftover and unfinshed (and often
uneeded) work and random individual drafts from the original WG. And
all the same players with all the same agendas are tempted to show up
at the new WG.

Maintenance WGs are definitely needed. And they need to be timed
correctly. Wait too long, and you miss the window of opportunity
during which folk are starting to implement/deploy, and you can still
fix the spec.

Successful maintenance WGs also need strong chairs and carefuly
crafted charters that keep them from becoming nuisance magnets. The
challenge in doing that I think keeps ADs from chartering such WGs in
some cases when a WG really is needed.

Even today, there are maintenance WGs that have issues. They can be
identified by the ratio of mail/drafts/discussion to the actual
importance of the problem purported to being solved.

Thomas


From jnc@mercury.lcs.mit.edu  Wed Jun 19 10:07:10 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
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 A191F21F9DF7 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 10:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 dzQ+457EKl4x for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 10:07:05 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 0910221F9DD8 for <ietf@ietf.org>; Wed, 19 Jun 2013 10:06:57 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 3297C18C0E6; Wed, 19 Jun 2013 13:06:54 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IETF Diversity
Message-Id: <20130619170654.3297C18C0E6@mercury.lcs.mit.edu>
Date: Wed, 19 Jun 2013 13:06:54 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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, 19 Jun 2013 17:07:10 -0000

    > From: Melinda Shore <melinda.shore@gmail.com>

    > it's likely that for a few cycles nomcoms will try to be "sensitive" to
    > the question of the underrepresentation of women and then it will be
    > back to business as usual ...
    > It's unusual for people to voluntarily surrender their privilege.

Yes, the men of the IETF are just irretrievably opposed to handing over any
power to women. It's going to have to be pried from their cold, dead hands...

	Noel

From paf@frobbit.se  Wed Jun 19 10:09:35 2013
Return-Path: <paf@frobbit.se>
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 CBC6221F9E06 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 10:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
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 d9MezUASzE2V for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 10:09:33 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id A2AAD21F9E05 for <ietf@ietf.org>; Wed, 19 Jun 2013 10:09:32 -0700 (PDT)
Received: from [10.123.4.95] (unknown [192.36.80.8]) by mail.frobbit.se (Postfix) with ESMTPSA id 376FE2025C; Wed, 19 Jun 2013 19:09:31 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_E8639840-2066-42FC-A805-7784EA0B3416"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Lessons from PROVREG WG was Re: IETF, ICANN and Whois...
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <9A9C6AA8-08FD-4022-AEAE-D4C725456E3F@neustar.biz>
Date: Wed, 19 Jun 2013 19:09:14 +0200
Message-Id: <F716B1CA-5C9B-41A5-9B7A-0FD626E66945@frobbit.se>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <6.2.5.6.2.20130619000239.0b0ebd38@resistor.net> <DACC4421-03B2-4F64-856C-FF3080B587AE@frobbit.se> <002D3B5B-3B2C-495E-A500-A95C1856355D@vpnc.org> <9A9C6AA8-08FD-4022-AEAE-D4C725456E3F@neustar.biz>
To: Edward Lewis <ed.lewis@neustar.biz>
X-Mailer: Apple Mail (2.1508)
Cc: ietf <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, 19 Jun 2013 17:09:35 -0000

--Apple-Mail=_E8639840-2066-42FC-A805-7784EA0B3416
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 19 jun 2013, at 18:01, Edward Lewis <ed.lewis@neustar.biz> wrote:

> Looking back in hindsight, what would help is to have some means for =
the IETF to provide a maintenance vehicle for it's products.  Or realize =
that the "waterfall model" that seems to be in place is no longer =
appropriate.  (As if you've never heard that before!)  The world changes =
(the new majority) but the IETF acts as if "once it's an RFC it is =
done."
>=20
> This is an example of an ICANN initiated piece of work that barely got =
into the IETF, the IETF completed it in a way that has benefit beyond =
ICANN (meaning many ccTLDs have adopted it on their own accord), but the =
IETF didn't make it easy and didn't help the deployment.  I hope the =
latter phase isn't repeated with the WEIRDS WG and RDAP.


To complete the story for newcomers...I did bring up EPP just because =
when EPP was discussed in IETF, I was the responsible Area Director. So =
I am (a) definitely aware of the problem, and (b) still annoyed over the =
result.

If I could travel back in time and try again...

Anyway....

So, the example was very explicitly chosen so that my story was not to =
blame any individuals, but the situation which I am both part of an =
frustrated of.

      Patrik


--Apple-Mail=_E8639840-2066-42FC-A805-7784EA0B3416
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On 19 jun 2013, at 18:01, Edward Lewis &lt;<a =
href=3D"mailto:ed.lewis@neustar.biz">ed.lewis@neustar.biz</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"font-family: 'Lucida Sans Typewriter'; =
font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
">Looking back in hindsight, what would help is to have some means for =
the IETF to provide a maintenance vehicle for it's products. &nbsp;Or =
realize that the "waterfall model" that seems to be in place is no =
longer appropriate. &nbsp;(As if you've never heard that before!) =
&nbsp;The world changes (the new majority) but the IETF acts as if "once =
it's an RFC it is done."</div><div style=3D"font-family: 'Lucida Sans =
Typewriter'; font-size: medium; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><br></div><div style=3D"font-family: 'Lucida Sans Typewriter'; =
font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">This =
is an example of an ICANN initiated piece of work that barely got into =
the IETF, the IETF completed it in a way that has benefit beyond ICANN =
(meaning many ccTLDs have adopted it on their own accord), but the IETF =
didn't make it easy and didn't help the deployment. &nbsp;I hope the =
latter phase isn't repeated with the WEIRDS WG and =
RDAP.</div></blockquote></div><div><br></div><div>To complete the story =
for newcomers...I did bring up EPP just because when EPP was discussed =
in IETF, I was the responsible Area Director. So I am (a) definitely =
aware of the problem, and (b) still annoyed over the =
result.</div><div><br></div><div>If I could travel back in time and try =
again...</div><div><br></div><div>Anyway....</div><div><br></div><div>So, =
the example was very explicitly chosen so that my story was not to blame =
any individuals, but the situation which I am both part of an frustrated =
of.</div><div><br></div><div>&nbsp; &nbsp; &nbsp; =
Patrik</div><div><br></div></body></html>=

--Apple-Mail=_E8639840-2066-42FC-A805-7784EA0B3416--

From shollenbeck@verisign.com  Wed Jun 19 10:44:37 2013
Return-Path: <shollenbeck@verisign.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 7927521F9D70 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 10:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 tPLoAkyvNWXW for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 10:44:31 -0700 (PDT)
Received: from exprod6og107.obsmtp.com (exprod6og107.obsmtp.com [64.18.1.208]) by ietfa.amsl.com (Postfix) with ESMTP id 07C1121F9D87 for <ietf@ietf.org>; Wed, 19 Jun 2013 10:44:23 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob107.postini.com ([64.18.5.12]) with SMTP ID DSNKUcHt9saOsh78I452u+nCF5Jqm+zHEyA8@postini.com; Wed, 19 Jun 2013 10:44:23 PDT
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id r5JHiMZp018136 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Jun 2013 13:44:22 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Wed, 19 Jun 2013 13:44:21 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Edward Lewis <ed.lewis@neustar.biz>, ietf <ietf@ietf.org>
Subject: RE: Lessons from PROVREG WG was Re: IETF, ICANN and Whois...
Thread-Topic: Lessons from PROVREG WG was Re: IETF, ICANN and Whois...
Thread-Index: AQHObQZ0zNgYemTUHUW2LUo6zNbvM5k9TqMg
Date: Wed, 19 Jun 2013 17:44:21 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F243AF107@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <6.2.5.6.2.20130619000239.0b0ebd38@resistor.net> <DACC4421-03B2-4F64-856C-FF3080B587AE@frobbit.se> <002D3B5B-3B2C-495E-A500-A95C1856355D@vpnc.org> <9A9C6AA8-08FD-4022-AEAE-D4C725456E3F@neustar.biz>
In-Reply-To: <9A9C6AA8-08FD-4022-AEAE-D4C725456E3F@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: multipart/alternative; boundary="_000_831693C2CDA2E849A7D7A712B24E257F243AF107BRN1WNEXMBX01vc_"
MIME-Version: 1.0
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, 19 Jun 2013 17:44:37 -0000

--_000_831693C2CDA2E849A7D7A712B24E257F243AF107BRN1WNEXMBX01vc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Edw=
ard Lewis
Sent: Wednesday, June 19, 2013 12:01 PM
To: ietf
Cc: Edward Lewis
Subject: Lessons from PROVREG WG was Re: IETF, ICANN and Whois...

[snip]

> This is an example of an ICANN initiated piece of work that barely got in=
to the IETF, the IETF completed it in a way that has benefit beyond ICANN (=
meaning many ccTLDs have adopted it on their own accord), but the IETF didn=
't make it easy and didn't help the deployment.

Actually, I first wrote the protocol in Internet-Draft form and then social=
ized it among members of the ICANN community. It wasn't really initiated by=
 ICANN.

Scott

--_000_831693C2CDA2E849A7D7A712B24E257F243AF107BRN1WNEXMBX01vc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ietf-bou=
nces@ietf.org [mailto:ietf-bounces@ietf.org]
<b>On Behalf Of </b>Edward Lewis<br>
<b>Sent:</b> Wednesday, June 19, 2013 12:01 PM<br>
<b>To:</b> ietf<br>
<b>Cc:</b> Edward Lewis<br>
<b>Subject:</b> Lessons from PROVREG WG was Re: IETF, ICANN and Whois...<o:=
p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1F497D">[snip]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt; </span>This is an=
 example of an ICANN initiated piece of work that barely got into the IETF,=
 the IETF completed it in a way that has benefit beyond ICANN (meaning many=
 ccTLDs have adopted it on their own accord),
 but the IETF didn't make it easy and didn't help the deployment. <o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1F497D">Actually, I first wrote the protocol in In=
ternet-Draft form and then socialized it among members of the ICANN communi=
ty. It wasn&#8217;t really initiated by ICANN.<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1F497D">Scott<o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_831693C2CDA2E849A7D7A712B24E257F243AF107BRN1WNEXMBX01vc_--

From ed.lewis@neustar.biz  Wed Jun 19 10:52:32 2013
Return-Path: <ed.lewis@neustar.biz>
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 4A66A21F9CAF for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 10:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.785
X-Spam-Level: 
X-Spam-Status: No, score=-100.785 tagged_above=-999 required=5 tests=[AWL=0.416, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
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 HfJPLETyPWjw for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 10:52:19 -0700 (PDT)
Received: from smtp102.ord1c.emailsrvr.com (smtp102.ord1c.emailsrvr.com [108.166.43.102]) by ietfa.amsl.com (Postfix) with ESMTP id 8F49421F9C3B for <ietf@ietf.org>; Wed, 19 Jun 2013 10:52:19 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 1E4311B017A; Wed, 19 Jun 2013 13:52:17 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: edlewis-AT-ogud.com) with ESMTPSA id 044B51B0143;  Wed, 19 Jun 2013 13:52:16 -0400 (EDT)
Subject: Re: Lessons from PROVREG WG was Re: IETF, ICANN and Whois...
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_1C1273E2-E771-45BE-92AC-5A75EFF64A65"
From: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F243AF107@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Date: Wed, 19 Jun 2013 13:52:14 -0400
Message-Id: <E44A1D11-0DE5-449C-B5F5-339988D504F4@neustar.biz>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <6.2.5.6.2.20130619000239.0b0ebd38@resistor.net> <DACC4421-03B2-4F64-856C-FF3080B587AE@frobbit.se> <002D3B5B-3B2C-495E-A500-A95C1856355D@vpnc.org> <9A9C6AA8-08FD-4022-AEAE-D4C725456E3F@neustar.biz> <831693C2CDA2E849A7D7A712B24E257F243AF107@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
To: Scott Hollenbeck <shollenbeck@verisign.com>
X-Mailer: Apple Mail (2.1283)
Cc: Edward Lewis <ed.lewis@neustar.biz>, ietf <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, 19 Jun 2013 17:52:32 -0000

--Apple-Mail=_1C1273E2-E771-45BE-92AC-5A75EFF64A65
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

I stand corrected.

My recollection about the initial pushback should be clarified...by the =
time the reason got to me, EPP was something ICANN had asked of the =
IETF.  Consider that to be subject to the "telephone game =
(http://en.wikipedia.org/wiki/Telephone_game)" syndrome. ;)

On Jun 19, 2013, at 13:44, Hollenbeck, Scott wrote:

> Actually, I first wrote the protocol in Internet-Draft form and then =
socialized it among members of the ICANN community. It wasn=92t really =
initiated by ICANN.

=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Edward Lewis            =20
NeuStar                    You can leave a voice message at =
+1-571-434-5468

There are no answers - just tradeoffs, decisions, and responses.


--Apple-Mail=_1C1273E2-E771-45BE-92AC-5A75EFF64A65
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>I stand corrected.</div><div><br></div><div>My recollection about =
the initial pushback should be clarified...by the time the reason got to =
me, EPP was something ICANN had asked of the IETF. &nbsp;Consider that =
to be subject to the "telephone game (<a =
href=3D"http://en.wikipedia.org/wiki/Telephone_game">http://en.wikipedia.o=
rg/wiki/Telephone_game</a>)" syndrome. ;)</div><div><br></div><div>On =
Jun 19, 2013, at 13:44, Hollenbeck, Scott =
wrote:</div><div><br></div><div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"color: rgb(31, 73, 125); =
font-family: Calibri, sans-serif; font-size: 16px; ">Actually, I first =
wrote the protocol in Internet-Draft form and then socialized it among =
members of the ICANN community. It wasn=92t really initiated by =
ICANN.</span></blockquote></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D<span></sp=
an>-=3D-=3D-=3D-<span class=3D"Apple-style-span" style=3D"border-collapse:=
 separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>Edward =
Lewis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span></s=
pan>&nbsp;&nbsp;&nbsp;<br>NeuStar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<span></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; You can leave a voice message at =
+1-571-434-5468<br><br>There are no answers - just tradeoffs, decisions, =
and responses.</div></div></div></span></span>
</div>
<br></body></html>=

--Apple-Mail=_1C1273E2-E771-45BE-92AC-5A75EFF64A65--

From dougb@dougbarton.us  Wed Jun 19 11:03:46 2013
Return-Path: <dougb@dougbarton.us>
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 59D4E21F9DEE for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:03:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 OHfNQDgkuffB for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:03:36 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id D8C4821F9AE7 for <ietf@ietf.org>; Wed, 19 Jun 2013 11:03:35 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id AB21322B28 for <ietf@ietf.org>; Wed, 19 Jun 2013 18:03:35 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1371665015; bh=owSiV6tN5OZQqpYG7vgLXqbIYBz8IHqh2paGlzzUMic=; h=Date:From:To:Subject:References:In-Reply-To; b=Kixrx0aR178cZj0cvNOUC3XpKDZnFgt47ZRVNjryOLA7wmPrzU3dHW++1v7a/D6Ah ZzVp/JgPPqOdMEtLB54X0oY7FCdrXxN5t66HQQOn/xjR7Aa5mDutnMyZbuSr8p6g4A Q4Cy6S1u73ImlIjKheU722xQgJ1nKxEnQkiDy6Uo=
Message-ID: <51C1F277.8050902@dougbarton.us>
Date: Wed, 19 Jun 2013 11:03:35 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 18:03:47 -0000

On 06/19/2013 09:45 AM, Ted Lemon wrote:
> On Jun 19, 2013, at 11:22 AM, Melinda Shore <melinda.shore@gmail.com> wrote:
>> Don't know about that one.  In the US, at least, legal mandates
>> have typically led social change, at least when it comes to civil
>> rights, etc.
>
> Yup.   First the Civil Rights act, then Selma...  ;)

Yes, this rather succinctly makes the point that I was starting to think 
about how to write out much more verbosely. Without the grassroots 
movements pushing for attitudes to change the legislation never would 
have been passed. Melinda is correct that the legislation does affect 
attitudes after it comes into being, but it's a cycle, not a strict 
cause/effect chain.

Short version, if everyone does what they can to encourage diverse 
participation, we won't need "legislation" to fix the problem.

Doug (whatever that is)


From melinda.shore@gmail.com  Wed Jun 19 11:11:48 2013
Return-Path: <melinda.shore@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 9C4E721F9BCE for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 UcaVTeCihS-Y for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:11:48 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id B2A8021F9C03 for <ietf@ietf.org>; Wed, 19 Jun 2013 11:11:46 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx10so5421695pab.27 for <ietf@ietf.org>; Wed, 19 Jun 2013 11:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Ewo98PVOwiGXiF+S6CxCIyDOMewtI61k7YnGQv1E1/Y=; b=kb0uL6o90Twr/yqZ8eMofedYvdpVPgDUTOX+aDQ8vN3GmOYZ+YncR1FM2/BvrtkNyX JMXqylKF0z3992OwI8AjQc6pANZGtB4XedWN32ufnH1Fb8R1EAdSR0Tu3IqMA8XOw5gk TXZeIeIggJmlIYFNEUMQpPpyUpTzzM0SAqjemqUUkCOr4QNiZ2HyTPV0UrR+OJQGZm0L saDFguAWP76mlvHnY/JKfmx/C8uiyAMXdIruqdSHpMU9/L3cF2KQi0HuQhoMWClgbP7D IkfHHpuBI6SHVzcPZmkxqZbA7zCTJNWBNy9YaR9RPWHtHSSH701/p8AqvDiUP3l7YJhY L5qQ==
X-Received: by 10.68.58.231 with SMTP id u7mr3891594pbq.144.1371665506341; Wed, 19 Jun 2013 11:11:46 -0700 (PDT)
Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id iq2sm24070937pbb.19.2013.06.19.11.11.44 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 11:11:45 -0700 (PDT)
Message-ID: <51C1F45E.2030805@gmail.com>
Date: Wed, 19 Jun 2013 10:11:42 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us>
In-Reply-To: <51C1F277.8050902@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 18:11:48 -0000

On 6/19/13 10:03 AM, Doug Barton wrote:
> Short version, if everyone does what they can to encourage diverse
> participation, we won't need "legislation" to fix the problem.

I'd like it if that were true but I don't think it is.  For example,
the majority of academic librarians are women (one demographic
survey I saw said 80%) but the majority of academic library directors
are men (again, ~80%).  I'd like to think that good intentions and
happy thoughts will provide a durable solution to the problem but
I'm not convinced.  I am convinced, however, that because of our
decision-making processes we would not be able to do "legislation,"
in any event.

Melinda



From dougb@dougbarton.us  Wed Jun 19 11:16:54 2013
Return-Path: <dougb@dougbarton.us>
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 CB90E21F9E25 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, 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 t1ixmvimK+sc for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:16:54 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2192321F9B12 for <ietf@ietf.org>; Wed, 19 Jun 2013 11:16:54 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 3FB8822B28 for <ietf@ietf.org>; Wed, 19 Jun 2013 18:16:51 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1371665811; bh=YdPsG22SmRB4JUN9EA8J36f7mnavMQwwCEO0jbTRq+E=; h=Date:From:To:Subject:References:In-Reply-To; b=odjiuuxCx3EVW4Zl+g28hAabYMfJuN+CCcv3sHvQ+SY4C8kQm6PVGmFCs2/dGhHQJ zFCqsL4Zpw97+XMlhKjRfVW5NBU6AdVRJ1zfJI8qcWqQiSO8vNL/LwGy+mIfY31bHC jvjaH/NAQ5i4UJECyU410gqp0tx1ERlyMT2SgQGU=
Message-ID: <51C1F592.1060708@dougbarton.us>
Date: Wed, 19 Jun 2013 11:16:50 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com>
In-Reply-To: <51C1F45E.2030805@gmail.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 18:16:54 -0000

On 06/19/2013 11:11 AM, Melinda Shore wrote:
> On 6/19/13 10:03 AM, Doug Barton wrote:
>> Short version, if everyone does what they can to encourage diverse
>> participation, we won't need "legislation" to fix the problem.
>
> I'd like it if that were true but I don't think it is.  For example,
> the majority of academic librarians are women (one demographic
> survey I saw said 80%) but the majority of academic library directors
> are men (again, ~80%).

It's not clear to me how this example relates to the IETF.

> I'd like to think that good intentions and
> happy thoughts will provide a durable solution to the problem but
> I'm not convinced.

That's not at all what I was suggesting, and others in this thread (and 
elsewhere) have already outlined their actions in regards to reaching 
out to new participants, mentoring, etc. Personally I agree that those 
are the kinds of ACTIONS needed to address the diversity issue ... hence 
my suggestion that people DO what they can.

... and while we're on that topic, what are you doing to help?



From melinda.shore@gmail.com  Wed Jun 19 11:31:31 2013
Return-Path: <melinda.shore@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 AB9BE21F9DA9 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 8C73TXkUdttU for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:31:31 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 41A0D21F9D36 for <ietf@ietf.org>; Wed, 19 Jun 2013 11:31:31 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj3so5450114pad.0 for <ietf@ietf.org>; Wed, 19 Jun 2013 11:31:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Tr1zwBj7ip68Sw+aGqy5lZgBaINw/lKueiFhENv/YnA=; b=Im2FDQ4pK59CjV8QxUJbkZooaCZRVbUI7xj7ecxDL8xv3I+VhvYhfCabkmtUje1NsZ 9/rw7jOjFkkiXVEGbpSTn4Lkr1Jzg8m9u3MwhIdW44D2WvOFPmdJ8BoKJANA5vSupNw9 ePTeY6TFHeWEo9uZ577WdXXD+7JquD7u0GRCL7FQNKaDCq6xUnqJboxnz3CB/knRplMs YZCBx4qsdiWYic/tIJ0I5Q8pQS0TElakfgbB17Swb1jhUg6uG4FgllxU6ZGZHxalfFdD ywKHMNIZ4jXvIZey3DaUz5PI1TF51D22npPu1x8l3JHDeJXoHxrp4qDwwBHG4EOd2TKa 0K5Q==
X-Received: by 10.66.155.138 with SMTP id vw10mr7896020pab.91.1371666691023; Wed, 19 Jun 2013 11:31:31 -0700 (PDT)
Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id dc3sm24141832pbc.9.2013.06.19.11.31.29 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 11:31:29 -0700 (PDT)
Message-ID: <51C1F8FF.90100@gmail.com>
Date: Wed, 19 Jun 2013 10:31:27 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us>
In-Reply-To: <51C1F592.1060708@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 18:31:31 -0000

On 6/19/13 10:16 AM, Doug Barton wrote:
> It's not clear to me how this example relates to the IETF.

Even in fields in which the overwhelming majority of
practitioners, the majority of people in leadership or
management positions are men.  Everybody's got good
intentions - I'd be very surprised if anybody is sitting
around consciously thinking that women are less capable
of doing a good job in management than men.  But you
end up with some disturbing trends in aggregate.  Meaning
well really is not enough, and as I said my expectation
is that we'll get a few cycles of trying to be more
balanced but we won't get institutional change that would
inhibit backsliding.

> ... and while we're on that topic, what are you doing to help?

That is truly an unfortunate line of argument, and I hope
you don't use it very often.

Melinda



From dhc@dcrocker.net  Wed Jun 19 11:35:32 2013
Return-Path: <dhc@dcrocker.net>
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 8685B21F9EA2 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.559
X-Spam-Level: 
X-Spam-Status: No, score=-6.559 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 jWH5G2tuu2Hz for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:35:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 93CF521F9E91 for <ietf@ietf.org>; Wed, 19 Jun 2013 11:35:27 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5JIZORY023375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 19 Jun 2013 11:35:27 -0700
Message-ID: <51C1F9DC.8010803@dcrocker.net>
Date: Wed, 19 Jun 2013 11:35:08 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1F8FF.90100@gmail.com>
In-Reply-To: <51C1F8FF.90100@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 19 Jun 2013 11:35:27 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 19 Jun 2013 18:35:32 -0000

On 6/19/2013 11:31 AM, Melinda Shore wrote:
> Even in fields in which the overwhelming majority of
> practitioners, the majority of people in leadership or
> management positions are men.  Everybody's got good
> intentions


indeed, almost everyone claims that they are a better than average driver.

individual self-assessment tends to be a very unreliable mechanism upon 
which to base efforts at social change.


d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From yding@cs.helsinki.fi  Wed Jun 19 11:41:09 2013
Return-Path: <yding@cs.helsinki.fi>
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 7362821F934D for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_51=0.6, RCVD_IN_DNSWL_MED=-4]
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 adWdDfNgqq6x for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 11:41:04 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5861A21F9285 for <ietf@ietf.org>; Wed, 19 Jun 2013 11:41:03 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Wed Jun 19 21:40:48 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= dkim20130528; bh=6mntF8+jgRclzz69w1Q2LsI+QpFjPPeeCdx9J9e442M=; b= TA18MSWT0U//T0qa0X0+FiGMs+0APM2B76Vb68L1ND3qDhUR9iywlm4JNNIt2kki d31VOqkFH8q6w7HPW+E2g59COVsBh/D2keepI89Ug3la3Ap4JmQdDwm2IQBeZDSV rsDCInymfsYHTFGGLBS2Y0DkjFK0vdZ2/p4VIo4XXBM=
Received: from [192.168.93.100] (host-94-101-2-100.igua.fi [94.101.2.100]) (AUTH: PLAIN yding, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Wed, 19 Jun 2013 21:40:48 +0300 id 0006807F.51C1FB30.000047CD
Message-ID: <51C1FB2B.7080205@cs.helsinki.fi>
Date: Wed, 19 Jun 2013 21:40:43 +0300
From: Aaron Yi DING <yding@cs.helsinki.fi>
Organization: Helsinki University
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us>
In-Reply-To: <51C1F592.1060708@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 18:41:09 -0000

On 19/06/13 21:16, Doug Barton wrote:
> On 06/19/2013 11:11 AM, Melinda Shore wrote:
>> On 6/19/13 10:03 AM, Doug Barton wrote:
>>> Short version, if everyone does what they can to encourage diverse
>>> participation, we won't need "legislation" to fix the problem.
>>
>> I'd like it if that were true but I don't think it is.  For example,
>> the majority of academic librarians are women (one demographic
>> survey I saw said 80%) but the majority of academic library directors
>> are men (again, ~80%).

> It's not clear to me how this example relates to the IETF.
>

On 19/06/13 18:33, Phillip Hallam-Baker wrote:
>
> Academia is still one of the worst environments for discrimination. 
> They don't have formal barriers as in the past but the informal 
> barriers are steep.
>


Relating to the statement above(I assume Phillip is addressing the US 
Academia), not quite sure are we still discussing the same topic?  
sorry, I am bit confused ..  since IETF is an international organization.

If yes, good to know more about it.

Aaron



>> I'd like to think that good intentions and
>> happy thoughts will provide a durable solution to the problem but
>> I'm not convinced.
>
> That's not at all what I was suggesting, and others in this thread 
> (and elsewhere) have already outlined their actions in regards to 
> reaching out to new participants, mentoring, etc. Personally I agree 
> that those are the kinds of ACTIONS needed to address the diversity 
> issue ... hence my suggestion that people DO what they can.
>
> ... and while we're on that topic, what are you doing to help?
>
>


From sm@resistor.net  Wed Jun 19 12:08:11 2013
Return-Path: <sm@resistor.net>
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 F166F21F9F48 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.22
X-Spam-Level: 
X-Spam-Status: No, score=-102.22 tagged_above=-999 required=5 tests=[AWL=-0.221, BAYES_00=-2.599, J_CHICKENPOX_51=0.6, USER_IN_WHITELIST=-100]
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 xARNLkTMM7UW for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:08:10 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 57B1F21F9F69 for <ietf@ietf.org>; Wed, 19 Jun 2013 12:08:08 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5JJ7wbs019082; Wed, 19 Jun 2013 12:08:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1371668883; bh=hv5XEFD8tcXfgkwN+ImgEADERoAo/+sK6eGtTL2QqCI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=V9gITGVCufHcHKHMffVSEE1jNzSCp0naChzh2pN3aAahYzzd+6mbh5Ar9ot/ls4Xq UMQf9l9z5WbF6VOlop7uXyI32jNB9exU2hru6fIvQsvMHtUbfxGT5pFPWenBWBBmxE PIZe4xSXBV1hOQKCnneCNpk7B0iYy+vnDDBj9Jrc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1371668883; i=@resistor.net; bh=hv5XEFD8tcXfgkwN+ImgEADERoAo/+sK6eGtTL2QqCI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2h4xa0w4KaXo81TBZ/O747dRgY5nYRAeWs25iPEZflna7tYmz1rLSTDafmynjIhut yFrJPsrfnViYwf2O1e63BSIfOocZIV1oXZTb9gCJBBWnA3fGW4F+D8+aEMIGT9iZij 1mwWjaJHRoT370SmrzOkNuHRYTZIXzTtP+tr4hLU=
Message-Id: <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 19 Jun 2013 12:07:39 -0700
To: Aaron Yi DING <yding@cs.helsinki.fi>
From: SM <sm@resistor.net>
Subject: Is the IETF is an international organization? (was: IETF Diversity)
In-Reply-To: <51C1FB2B.7080205@cs.helsinki.fi>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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, 19 Jun 2013 19:08:11 -0000

Hi Aaron,
At 11:40 19-06-2013, Aaron Yi DING wrote:
>Relating to the statement above(I assume Phillip is addressing the 
>US Academia), not quite sure are we still discussing the same topic?
>sorry, I am bit confused ..  since IETF is an international organization.

I changed the subject line as I am as confused as to whether the IETF 
is an international organization.

There was a mention of "First the Civil Rights act, then 
Selma...  ;)".  I assume that the act is an Act for the United States 
of America.  Harvard was also mentioned.  I did a quick search and I 
found out that "Harvard University is an American private Ivy League 
research university".

Regards,
-sm 


From dougb@dougbarton.us  Wed Jun 19 12:12:52 2013
Return-Path: <dougb@dougbarton.us>
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 6818821F9EED for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_51=0.6]
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 rMYEWCaorBMt for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:12:48 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 2062321F9EDC for <ietf@ietf.org>; Wed, 19 Jun 2013 12:12:48 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id C46B122B6A for <ietf@ietf.org>; Wed, 19 Jun 2013 19:12:47 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1371669167; bh=lIiJcMomYJcO8SiRCfPF5zooBB3pxsT6Wyz3kvermUU=; h=Date:From:To:Subject:References:In-Reply-To; b=wT9+MXO68QQh9AO2I3IZ961+yNXDxl/7GUbeHwrHZVtcH3iOIjDYORs6kPrH2rSai LsF7pCKLVhuQGPCUWenU7mxROoYHBtatPzOZn13RJVOGce35vRgMwlZhrTY/tW7irl 3ylgX1vI2G4bxvWOMMaGbbsuHIp/xsa3VBNqxW6Y=
Message-ID: <51C202AD.10600@dougbarton.us>
Date: Wed, 19 Jun 2013 12:12:45 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi>
In-Reply-To: <51C1FB2B.7080205@cs.helsinki.fi>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 19:12:52 -0000

On 06/19/2013 11:40 AM, Aaron Yi DING wrote:
> On 19/06/13 21:16, Doug Barton wrote:
>> On 06/19/2013 11:11 AM, Melinda Shore wrote:
>>> On 6/19/13 10:03 AM, Doug Barton wrote:
>>>> Short version, if everyone does what they can to encourage diverse
>>>> participation, we won't need "legislation" to fix the problem.
>>>
>>> I'd like it if that were true but I don't think it is.  For example,
>>> the majority of academic librarians are women (one demographic
>>> survey I saw said 80%) but the majority of academic library directors
>>> are men (again, ~80%).
>
>> It's not clear to me how this example relates to the IETF.
>>
>
> On 19/06/13 18:33, Phillip Hallam-Baker wrote:
>>
>> Academia is still one of the worst environments for discrimination.
>> They don't have formal barriers as in the past but the informal
>> barriers are steep.
>>
>
>
> Relating to the statement above(I assume Phillip is addressing the US
> Academia), not quite sure are we still discussing the same topic? sorry,
> I am bit confused ..  since IETF is an international organization.

We can point to all kinds of examples that are outside the IETF of where 
various biases exist. It's not at all clear that the existence of those 
problems elsewhere corresponds to any actual problem within our 
organization.

That is NOT to say that we don't have a problem, only that making 
conclusions based on unrelated data is bad science.

Doug


From stpeter@stpeter.im  Wed Jun 19 12:14:28 2013
Return-Path: <stpeter@stpeter.im>
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 E07BF21F9FF9 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.24
X-Spam-Level: 
X-Spam-Status: No, score=-102.24 tagged_above=-999 required=5 tests=[AWL=-0.241, BAYES_00=-2.599, J_CHICKENPOX_51=0.6, USER_IN_WHITELIST=-100]
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 GvRTTdRVK9iE for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:14:23 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id CFBFA21F9FF2 for <ietf@ietf.org>; Wed, 19 Jun 2013 12:14:23 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 22F3241278; Wed, 19 Jun 2013 13:14:23 -0600 (MDT)
Message-ID: <51C2030C.5000606@stpeter.im>
Date: Wed, 19 Jun 2013 13:14:20 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <51C202AD.10600@dougbarton.us>
In-Reply-To: <51C202AD.10600@dougbarton.us>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 19:14:29 -0000

On 6/19/13 1:12 PM, Doug Barton wrote:
> On 06/19/2013 11:40 AM, Aaron Yi DING wrote:
>> On 19/06/13 21:16, Doug Barton wrote:
>>> On 06/19/2013 11:11 AM, Melinda Shore wrote:
>>>> On 6/19/13 10:03 AM, Doug Barton wrote:
>>>>> Short version, if everyone does what they can to encourage diverse
>>>>> participation, we won't need "legislation" to fix the problem.
>>>>
>>>> I'd like it if that were true but I don't think it is.  For example,
>>>> the majority of academic librarians are women (one demographic
>>>> survey I saw said 80%) but the majority of academic library directors
>>>> are men (again, ~80%).
>>
>>> It's not clear to me how this example relates to the IETF.
>>>
>>
>> On 19/06/13 18:33, Phillip Hallam-Baker wrote:
>>>
>>> Academia is still one of the worst environments for discrimination.
>>> They don't have formal barriers as in the past but the informal
>>> barriers are steep.
>>>
>>
>>
>> Relating to the statement above(I assume Phillip is addressing the US
>> Academia), not quite sure are we still discussing the same topic? sorry,
>> I am bit confused ..  since IETF is an international organization.
> 
> We can point to all kinds of examples that are outside the IETF of where
> various biases exist. It's not at all clear that the existence of those
> problems elsewhere corresponds to any actual problem within our
> organization.
> 
> That is NOT to say that we don't have a problem, only that making
> conclusions based on unrelated data is bad science.

On the other hand, every organization thinks it is special, and most
aren't. :-)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From ynir@checkpoint.com  Wed Jun 19 12:18:59 2013
Return-Path: <ynir@checkpoint.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 6894721F9FDE for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.386
X-Spam-Level: 
X-Spam-Status: No, score=-10.386 tagged_above=-999 required=5 tests=[AWL=-0.387, BAYES_00=-2.599, J_CHICKENPOX_51=0.6, RCVD_IN_DNSWL_HI=-8]
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 wpxYHzVwkJNk for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:18:53 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 2F29F21F9FC3 for <ietf@ietf.org>; Wed, 19 Jun 2013 12:18:52 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r5JJIaCD024730; Wed, 19 Jun 2013 22:18:40 +0300
X-CheckPoint: {51C2040C-14-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.180]) with mapi id 14.02.0342.003; Wed, 19 Jun 2013 22:18:35 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: SM <sm@resistor.net>
Subject: Re: Is the IETF is an international organization? (was: IETF Diversity)
Thread-Topic: Is the IETF is an international organization? (was: IETF Diversity)
Thread-Index: AQHObSBiW+j9ED7vQkS7cpthW8uL8Zk9NwkA
Date: Wed, 19 Jun 2013 19:18:35 +0000
Message-ID: <0D1D10FE-39B0-4C51-9283-715823CD4969@checkpoint.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.146]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 11e75a623b80d7b91e0b2f119ad94a05c98245c1e4
Content-Type: text/plain; charset="us-ascii"
Content-ID: <74883DB06322E44A98D99420D744AE42@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <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, 19 Jun 2013 19:18:59 -0000

On Jun 19, 2013, at 10:07 PM, SM <sm@resistor.net>
 wrote:

> Hi Aaron,
> At 11:40 19-06-2013, Aaron Yi DING wrote:
>> Relating to the statement above(I assume Phillip is addressing the US Ac=
ademia), not quite sure are we still discussing the same topic?
>> sorry, I am bit confused ..  since IETF is an international organization=
.
>=20
> I changed the subject line as I am as confused as to whether the IETF is =
an international organization.
>=20
> There was a mention of "First the Civil Rights act, then Selma...  ;)".  =
I assume that the act is an Act for the United States of America.  Harvard =
was also mentioned.  I did a quick search and I found out that "Harvard Uni=
versity is an American private Ivy League research university".

Yeah, and "act" is what Americans call statutes, and Selma is a city in Ala=
bama where there was some controversy about voting rights. You sure need to=
 know a lot of Americana to participate meaningfully in some of these discu=
ssions.


From dromasca@avaya.com  Wed Jun 19 12:20:14 2013
Return-Path: <dromasca@avaya.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 3778821E808A for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:20:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.163
X-Spam-Level: 
X-Spam-Status: No, score=-103.163 tagged_above=-999 required=5 tests=[AWL=-0.164, BAYES_00=-2.599, J_CHICKENPOX_51=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 POGqoQ2gQuwE for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:20:07 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id EAFFF21E8091 for <ietf@ietf.org>; Wed, 19 Jun 2013 12:19:57 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkEFAAH/ZlHGmAcF/2dsb2JhbABQgmUhviqDVIEHFnSCHwEBAQEDEig/DAQCAQgNBAQBAQEKFAkHMhQJCAIEAQ0FCA0Nh3IBoEedI45lJgsHBoJaYQOdKYpogwuCKA
X-IronPort-AV: E=Sophos;i="4.87,456,1363147200"; d="scan'208";a="16266540"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 19 Jun 2013 15:19:57 -0400
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 19 Jun 2013 15:17:56 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Wed, 19 Jun 2013 15:19:55 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: SM <sm@resistor.net>, Aaron Yi DING <yding@cs.helsinki.fi>
Subject: RE: Is the IETF is an international organization? (was: IETF Diversity)
Thread-Topic: Is the IETF is an international organization? (was: IETF Diversity)
Thread-Index: AQHObSBe4CYx1T3x6EiS1Z++oGgqQJk9aFbg
Date: Wed, 19 Jun 2013 19:19:55 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA1A767E@AZ-FFEXMB04.global.avaya.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <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, 19 Jun 2013 19:20:14 -0000

Well, this is a cultural thing :-) Some of our American colleagues cannot a=
void using examples related to the American constitution, history or academ=
y, forgetting that out-of-the-US interlocutors may not that familiar with t=
hem. Luckily, they did not mention any baseball rule in this discussions (y=
et) :-)=20

Regards,

Dan



> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> SM
> Sent: Wednesday, June 19, 2013 10:08 PM
> To: Aaron Yi DING
> Cc: ietf@ietf.org
> Subject: Is the IETF is an international organization? (was: IETF
> Diversity)
>=20
> Hi Aaron,
> At 11:40 19-06-2013, Aaron Yi DING wrote:
> >Relating to the statement above(I assume Phillip is addressing the US
> >Academia), not quite sure are we still discussing the same topic?
> >sorry, I am bit confused ..  since IETF is an international
> organization.
>=20
> I changed the subject line as I am as confused as to whether the IETF is
> an international organization.
>=20
> There was a mention of "First the Civil Rights act, then Selma...  ;)".
> I assume that the act is an Act for the United States of America.
> Harvard was also mentioned.  I did a quick search and I found out that
> "Harvard University is an American private Ivy League research
> university".
>=20
> Regards,
> -sm


From ynir@checkpoint.com  Wed Jun 19 12:21:43 2013
Return-Path: <ynir@checkpoint.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 EE5FC21E80BE for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.343
X-Spam-Level: 
X-Spam-Status: No, score=-10.343 tagged_above=-999 required=5 tests=[AWL=-0.344, BAYES_00=-2.599, J_CHICKENPOX_51=0.6, RCVD_IN_DNSWL_HI=-8]
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 LUG19KjDSt7t for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:21:35 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id E087D21F9BFE for <ietf@ietf.org>; Wed, 19 Jun 2013 12:21:31 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r5JJLQi0026543; Wed, 19 Jun 2013 22:21:26 +0300
X-CheckPoint: {51C204B5-15-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.180]) with mapi id 14.02.0342.003; Wed, 19 Jun 2013 22:21:25 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: IETF Diversity
Thread-Topic: IETF Diversity
Thread-Index: AQHObQAZqmgSTahI2USTxY3ox5JPBJk89W6AgAAXKACAABXBgIAAAkQAgAABbwCAAAatgIAACPOAgAACagA=
Date: Wed, 19 Jun 2013 19:21:25 +0000
Message-ID: <50A1FFCD-E5F0-4D93-A7D2-CC3CB4CAE6E7@checkpoint.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <51C202AD.10600@dougbarton.us>
In-Reply-To: <51C202AD.10600@dougbarton.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.146]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 111965c2f9c31030eb278befc9adfbf1d9b6ac4fe9
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <ED2891152D39A144AC6B34B80FD7999A@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <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, 19 Jun 2013 19:21:43 -0000

On Jun 19, 2013, at 10:12 PM, Doug Barton <dougb@dougbarton.us>
 wrote:
>>=20
>> On 19/06/13 18:33, Phillip Hallam-Baker wrote:
>>>=20
>>> Academia is still one of the worst environments for discrimination.
>>> They don't have formal barriers as in the past but the informal
>>> barriers are steep.
>>>=20
>>=20
>>=20
>> Relating to the statement above(I assume Phillip is addressing the US
>> Academia), not quite sure are we still discussing the same topic? sorry,
>> I am bit confused ..  since IETF is an international organization.
>=20
> We can point to all kinds of examples that are outside the IETF of where =
various biases exist. It's not at all clear that the existence of those pro=
blems elsewhere corresponds to any actual problem within our organization.

Looking at how similar problems were solved in other places could help us f=
igure out how to solve such problems in the IETF.

And Academia is much more similar to the IETF than is the state of Alabama.

Yoav


From dougb@dougbarton.us  Wed Jun 19 12:27:51 2013
Return-Path: <dougb@dougbarton.us>
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 68CF421F9FEB for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, 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 7mV97zOYynaU for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:27:50 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id D1E4621F9FE7 for <ietf@ietf.org>; Wed, 19 Jun 2013 12:27:50 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id A503822B28 for <ietf@ietf.org>; Wed, 19 Jun 2013 19:27:50 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1371670070; bh=K3ZPJcckd4atZlMlBXatbdeI+8maO92KfyK0X9T73bY=; h=Date:From:To:Subject:References:In-Reply-To; b=TaXQw2PNsaioHHgxDlFUjYx4WGYDXuaOjiq3ZFeqUsVHXa4wwr1vv8SkyLUW0+3jl bpfvryltOC44giUxmHJaHuiPSYQJvXaNHO9u3IWDI7P3CQoPg/Un9U5v5Xy+x0xgNA zQcwNclEt+aU05ovxhuYceSKQGpFdsJfcff3Mv9g=
Message-ID: <51C20636.20807@dougbarton.us>
Date: Wed, 19 Jun 2013 12:27:50 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <51C202AD.10600@dougbarton.us> <51C2030C.5000606@stpeter.im>
In-Reply-To: <51C2030C.5000606@stpeter.im>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 19:27:51 -0000

On 06/19/2013 12:14 PM, Peter Saint-Andre wrote:
> On 6/19/13 1:12 PM, Doug Barton wrote:
>>
>> We can point to all kinds of examples that are outside the IETF of where
>> various biases exist. It's not at all clear that the existence of those
>> problems elsewhere corresponds to any actual problem within our
>> organization.
>>
>> That is NOT to say that we don't have a problem, only that making
>> conclusions based on unrelated data is bad science.
>
> On the other hand, every organization thinks it is special, and most
> aren't. :-)

I thought I made it clear that I'm not saying, "there is no problem." I 
am only saying that pointing to other, unrelated situations and saying 
"They seem to have a problem, so we must have a problem" is a waste of 
everyone's time.

The more interesting questions are whether or not the current makeup of 
the IETF leadership is reflective of the population (nee "membership") 
of the IETF as a whole; and whether or not the IETF population reflects 
the larger population of the tech community it draws from. Those are 
problems that outreach, mentorship, etc. can make concrete impacts on.

But until we understand what WE are dealing with (as opposed to what 
other organizations are dealing with) we're not going to make any actual 
progress.

Doug


From johnl@iecc.com  Wed Jun 19 12:44:08 2013
Return-Path: <johnl@iecc.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 BBAE821F9E87 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.747
X-Spam-Level: 
X-Spam-Status: No, score=-110.747 tagged_above=-999 required=5 tests=[AWL=0.452, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 WaISBOAMXrvd for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:44:04 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 1051021F9E85 for <ietf@ietf.org>; Wed, 19 Jun 2013 12:44:03 -0700 (PDT)
Received: (qmail 64663 invoked from network); 19 Jun 2013 19:44:01 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Jun 2013 19:44:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51c20a00.xn--btvx9d.k1306; i=johnl@user.iecc.com; bh=2Ixh0xYHy1vjae0fEZIziDz+MTlks8115mWXyc8zw7Y=; b=p+OdwZADe9aQ+8oG/meEcYC7drWTl87J7u0J6Xp3ql0x9kiuf5vujfXh4J28pU+rPf6UhvvpDaSpt0fTYnYIM1+AJZfBCC36elZ8hLyNJ3owMXayoXuow+d9+o1p9Fbod938sMD3cHsHJGqCj7RIVk7bg1Y9KNFrNq5+M+/1qLrvjbK6XkM6nvoSg3KvmC6zy1vegGfMVsOZJWmSEHtjUEkNBS3NTUgWYMRAQZKwGYVpeHfOoaanjt6Cc4NqTh4n
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51c20a00.xn--btvx9d.k1306; olt=johnl@user.iecc.com; bh=2Ixh0xYHy1vjae0fEZIziDz+MTlks8115mWXyc8zw7Y=; b=DehiHX930sGcG4b8M8A8ZEoNqX5MJW31so8RLyQjJyO0e5PD4IJiEBYFsv9VabuMCuuz1at1P/zQA20y82I7yiZIF94EHf0t50TZ1xOSxTbgcEdDRHAAga2KM98wssCJy2VL1wQrjB+KR39SwcJl6v55Wy2QKo4zjdyFALyP+Z/ToMhkiXuZ/Yo/3fyaDJdKE83JRyakscFxeXVeuhGn+ILOsUdM11PE6MQE0nBdGUqfULW0zX1s2BfakSh73l+Z
Date: 19 Jun 2013 19:43:38 -0000
Message-ID: <20130619194338.49286.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF, ICANN and non-standards
In-Reply-To: <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: paf@frobbit.se
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, 19 Jun 2013 19:44:08 -0000

>I think this is the correct strategy, BUT, I see as a very active participant in ICANN
>(chair of SSAC) that work in ICANN could be easier if some "more" technical standards where
>developed in IETF, and moved forward along standards track, that ICANN can reference.

As a concrete example, the EPP systems used in production by TLD
registries use extensions that are documented only in I-Ds, often
expired I-Ds, or in dusty I-D like web documents.  If you look at the
applications for new TLDs on the ICANN web site at
https://gtldresult.icann.org/application-result/applicationstatus you
will find that nearly all of them plan to use EPP extensions not
described in an RFC.  Most of these extensions should be utterly
uncontroversial, e.g., one to synchronize renewal dates among multiple
domains, or another to tell a client that its credit balance has
dropped below a threshold.

Assuming we care about stability and interoperability, wouldn't it
make sense for the IETF to spin up a WG, collect these drafts, clean
up the language, make sure they agree with the widely implemented
reality, and publish them?

R's,
John


From dougb@dougbarton.us  Wed Jun 19 12:47:33 2013
Return-Path: <dougb@dougbarton.us>
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 2D72721F9EDE for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level: 
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, 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 g8vm2Jdal-bm for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:47:32 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 93E6D21F9EF1 for <ietf@ietf.org>; Wed, 19 Jun 2013 12:47:32 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 5916C22B28 for <ietf@ietf.org>; Wed, 19 Jun 2013 19:47:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1371671252; bh=EOmzlisP4KbfQCYbWktRz6BIv2TeKRnQRzkV8i4/quQ=; h=Date:From:To:Subject:References:In-Reply-To; b=WcZpzfJ6I2zlx3tKBC6CYmyrT6oRs6uPsPb/BNPCEcMPgkVjiGmw6kilQZ9Ch8kkO SPzKreR9g7wxQQCF3TJn9IrEF46iASahBhKyRZp2mTexOMR1ShhDBEenJ+mVkkNsz+ RfO+h1DwMuucOglC8wjxHPY1EzoQdNER+dx057BA=
Message-ID: <51C20AD4.5060807@dougbarton.us>
Date: Wed, 19 Jun 2013 12:47:32 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1F8FF.90100@gmail.com>
In-Reply-To: <51C1F8FF.90100@gmail.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 19:47:33 -0000

On 06/19/2013 11:31 AM, Melinda Shore wrote:
> On 6/19/13 10:16 AM, Doug Barton wrote:
>> It's not clear to me how this example relates to the IETF.
>
> Even in fields in which the overwhelming majority of
> practitioners, the majority of people in leadership or
> management positions are men.

So again, it's not at all clear how that relates to the IETF (given that 
we don't fall into the category of "the overwhelming majority of 
practitioners [are women]."

To be clear, I'm not trying to be critical of your point, I'm simply 
asking you to compare apples to apples.

> Everybody's got good
> intentions - I'd be very surprised if anybody is sitting
> around consciously thinking that women are less capable
> of doing a good job in management than men.  But you
> end up with some disturbing trends in aggregate.  Meaning
> well really is not enough, and as I said my expectation
> is that we'll get a few cycles of trying to be more
> balanced but we won't get institutional change that would
> inhibit backsliding.

Yes, you've made the point rather amply that you think there is an 
institutional problem with lack of women in leadership roles _in the 
IETF_. My experience has been considerably different however, and as a 
result I find it hard to accept your premise unconditionally. At this 
moment in time I think it's correct to say that women are 
underrepresented, but I don't think it's proven yet that this represents 
any kind of institutional bias.

I look at women like Leslie Daigle, Allison Mankin, Margaret Wasserman, 
Lynn St. Amour, Joyce Reynolds ... those are just off the top of my 
head; certainly not my intention to slight anyone ... all of whom have 
now, or have had significant leadership roles, and made lasting impacts 
on the IETF both in its work product and culture.

Can we (and should we) do better? Absolutely. I would love to see more 
participation by different groups, nationalities, genders, etc. And I 
have a vested interest here. I have a daughter who is smart as a whip, 
and when it comes time for her to find a job I want to be sure that 
every door is open to her.

But I also think it's possible for us to agree that we have room to 
improve without constantly banging the drum that we have a deep-seated 
institutional bias, especially when that point is far from proven.

>> ... and while we're on that topic, what are you doing to help?
>
> That is truly an unfortunate line of argument, and I hope
> you don't use it very often.

It's not a "line of argument," it's a legitimate question. Others have 
described their actions to help improve the situation, which hopefully 
still others can latch onto and emulate. You bring a unique perspective 
to the table, so I'm hoping that you can describe what you're doing to 
help solve the problem so that others can emulate your example.

Doug


From stpeter@stpeter.im  Wed Jun 19 12:48:06 2013
Return-Path: <stpeter@stpeter.im>
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 7B0DB21F9F31 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 LNv+l9mgHrka for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:48:01 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 57A0821F9EE0 for <ietf@ietf.org>; Wed, 19 Jun 2013 12:48:01 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4978E41278; Wed, 19 Jun 2013 13:47:55 -0600 (MDT)
Message-ID: <51C20AE8.2010100@stpeter.im>
Date: Wed, 19 Jun 2013 13:47:52 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <51C202AD.10600@dougbarton.us> <51C2030C.5000606@stpeter.im> <51C20636.20807@dougbarton.us>
In-Reply-To: <51C20636.20807@dougbarton.us>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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, 19 Jun 2013 19:48:06 -0000

On 6/19/13 1:27 PM, Doug Barton wrote:
> On 06/19/2013 12:14 PM, Peter Saint-Andre wrote:
>> On 6/19/13 1:12 PM, Doug Barton wrote:
>>>
>>> We can point to all kinds of examples that are outside the IETF of where
>>> various biases exist. It's not at all clear that the existence of those
>>> problems elsewhere corresponds to any actual problem within our
>>> organization.
>>>
>>> That is NOT to say that we don't have a problem, only that making
>>> conclusions based on unrelated data is bad science.
>>
>> On the other hand, every organization thinks it is special, and most
>> aren't. :-)
> 
> I thought I made it clear that I'm not saying, "there is no problem." I
> am only saying that pointing to other, unrelated situations and saying
> "They seem to have a problem, so we must have a problem" is a waste of
> everyone's time.
> 
> The more interesting questions are whether or not the current makeup of
> the IETF leadership is reflective of the population (nee "membership")
> of the IETF as a whole; and whether or not the IETF population reflects
> the larger population of the tech community it draws from. Those are
> problems that outreach, mentorship, etc. can make concrete impacts on.
> 
> But until we understand what WE are dealing with (as opposed to what
> other organizations are dealing with) we're not going to make any actual
> progress.

Very well said.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From ynir@checkpoint.com  Wed Jun 19 12:56:44 2013
Return-Path: <ynir@checkpoint.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 D018F21F9BB1 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.609
X-Spam-Level: 
X-Spam-Status: No, score=-10.609 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 MJUFm-iVma39 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 12:56:34 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 60F4F21F83EF for <ietf@ietf.org>; Wed, 19 Jun 2013 12:56:34 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r5JJuW8b015560; Wed, 19 Jun 2013 22:56:33 +0300
X-CheckPoint: {51C20CF0-D-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.180]) with mapi id 14.02.0342.003; Wed, 19 Jun 2013 22:56:32 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Brian Haberman <brian@innovationslab.net>
Subject: Re: IETF Diversity
Thread-Topic: IETF Diversity
Thread-Index: AQHObPnf/HFkfSvE50K2nUoRI/ZL0Jk88Y4AgAAE3YCAAEuEAA==
Date: Wed, 19 Jun 2013 19:56:32 +0000
Message-ID: <EBC640C6-E812-479F-9166-D0AEC941117C@checkpoint.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im> <51C1CD95.4060106@innovationslab.net>
In-Reply-To: <51C1CD95.4060106@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.146]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 11606b90feae8ecf680db9a21145b39c884a6a8980
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <481D4023F02E4B4CAAA1099522BB751B@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <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, 19 Jun 2013 19:56:45 -0000

On Jun 19, 2013, at 6:26 PM, Brian Haberman <brian@innovationslab.net> wrot=
e:

> To help facilitate the mentoring aspect, there will be a call soon for vo=
lunteers to act as mentors for newcomers (starting with IETF 87). Once the =
web page for the mentoring program with all the information is up, you shou=
ld be seeing a call for mentors.
>=20
> We hope that this type of program will aid in assisting newer members of =
the IETF community become more involved and productive in our activities.

This may be helpful in getting first-time attendees to stay on with the IET=
F. That is a laudable goal in itself, but I'm not sure if it will help dive=
rsity. Just bringing in new white male employees of US router companies wil=
l not increase diversity. It might work if the pool of newcomers is conside=
rably more diverse than the pool of veterans, but having been in the last t=
wo meet-and-greets, I see a lot of the same, except that the newcomer group=
 has more people from China. I see few women, hardly any Africans (from Afr=
ica or the US), and not a lot of company names I recognize as operators.

So unless we find a way to get a more diverse group to the meetings, such a=
 mentoring program will only help us get some new blood - same as the old b=
lood, but new.=

From dougb@dougbarton.us  Wed Jun 19 13:08:24 2013
Return-Path: <dougb@dougbarton.us>
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 311B321F9FBC for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
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 12TdefVHu94b for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:08:20 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF5D21F9FFD for <ietf@ietf.org>; Wed, 19 Jun 2013 13:08:14 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 5F40222B28 for <ietf@ietf.org>; Wed, 19 Jun 2013 20:08:13 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1371672493; bh=m6hjEDOXNBFCuwpHjf24FEtQE5Gqnyp98Mp5vVj/x5A=; h=Date:From:To:Subject:References:In-Reply-To; b=GuBIyyJgE24z1rmsbS8Jyb0KhgtCXTd5JQE/30hzVoZGJmLHglbftVvhKEAKMjpUN k+Ut6upk1WXp42nGV9J9LaQcWyMLeayLDBu8gQKYoLFrJcKvvLSAM7j85BDUeGjJJq NbyUlMBl612fJ2QmCsMuhfTNFa9lMIRaq1b6TXHw=
Message-ID: <51C20FAC.4020309@dougbarton.us>
Date: Wed, 19 Jun 2013 13:08:12 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <51C202AD.10600@dougbarton.us> <50A1FFCD-E5F0-4D93-A7D2-CC3CB4CAE6E7@checkpoint.com>
In-Reply-To: <50A1FFCD-E5F0-4D93-A7D2-CC3CB4CAE6E7@checkpoint.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 20:08:24 -0000

On 06/19/2013 12:21 PM, Yoav Nir wrote:
>
> On Jun 19, 2013, at 10:12 PM, Doug Barton <dougb@dougbarton.us>
>   wrote:
>
>> We can point to all kinds of examples that are outside the IETF of where various biases exist. It's not at all clear that the existence of those problems elsewhere corresponds to any actual problem within our organization.
>
> Looking at how similar problems were solved in other places could help us figure out how to solve such problems in the IETF.

Of course, but we have to be sure that the problems really are similar 
first.

> And Academia is much more similar to the IETF than is the state of Alabama.

Yeah, but so what? That's like saying that avocados and oranges are more 
similar than avocados and rocks. But if I want to make guacamole I 
better be able to differentiate the different kinds of fruit.

I'm not trying to be pedantic for its own sake here. It is genuinely 
important to understand the population you are working with if you're 
going to address social issues. Concepts (and more importantly 
solutions) that are relevant for one group may very well not be 
applicable to another group because the populations differ in subtle but 
important ways.

Doug


From yding@cs.helsinki.fi  Wed Jun 19 13:25:16 2013
Return-Path: <yding@cs.helsinki.fi>
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 AD6E721F9EED for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.561
X-Spam-Level: 
X-Spam-Status: No, score=-6.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 xWppVPiv-bCr for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:25:11 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F75821F9FEA for <ietf@ietf.org>; Wed, 19 Jun 2013 13:25:10 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Wed Jun 19 23:24:42 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= dkim20130528; bh=Cm1D0ScjZCU0BQbuR/krL+SSd+3SkSLw3ppOPlbNLa8=; b= ekbkRdD9NShflwsXlg+g+hz//u0zKCPeMEgrilbsNNc8Knq7ockIBAFIJEnLO/j/ tSf9qMfGGJoDEI0OzLtu5b+wPij2u7EChFxbBFc3laQt+z2cfgKN6LnSRsLMUlWC wi/EeWx8jgbS2cSvIyxwMyuYb5KUHTINDw4X+rSk/gM=
Received: from [192.168.93.100] (host-94-101-2-100.igua.fi [94.101.2.100]) (AUTH: PLAIN yding, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Wed, 19 Jun 2013 23:24:42 +0300 id 00068086.51C2138A.00001C0C
Message-ID: <51C21389.8020209@cs.helsinki.fi>
Date: Wed, 19 Jun 2013 23:24:41 +0300
From: Aaron Yi DING <yding@cs.helsinki.fi>
Organization: Helsinki University
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>, Brian Haberman <brian@innovationslab.net>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im> <51C1CD95.4060106@innovationslab.net> <EBC640C6-E812-479F-9166-D0AEC941117C@checkpoint.com>
In-Reply-To: <EBC640C6-E812-479F-9166-D0AEC941117C@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "<ietf@ietf.org>" <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, 19 Jun 2013 20:25:16 -0000

On 19/06/13 22:56, Yoav Nir wrote:
> On Jun 19, 2013, at 6:26 PM, Brian Haberman <brian@innovationslab.net> wrote:
>
>> To help facilitate the mentoring aspect, there will be a call soon for volunteers to act as mentors for newcomers (starting with IETF 87). Once the web page for the mentoring program with all the information is up, you should be seeing a call for mentors.
>>
>> We hope that this type of program will aid in assisting newer members of the IETF community become more involved and productive in our activities.
> This may be helpful in getting first-time attendees to stay on with the IETF. That is a laudable goal in itself, but I'm not sure if it will help diversity. Just bringing in new white male employees of US router companies will not increase diversity. It might work if the pool of newcomers is considerably more diverse than the pool of veterans, but having been in the last two meet-and-greets, I see a lot of the same, except that the newcomer group has more people from China. I see few women, hardly any Africans (from Africa or the US), and not a lot of company names I recognize as operators.
>
> So unless we find a way to get a more diverse group to the meetings, such a mentoring program will only help us get some new blood - same as the old blood, but new.


That sounds similar to "new bottles but still filled with the old type 
wine" - long lasting old Chinese saying :)

Personally speaking, mentoring is a viable one to start with, although 
some colleagues told me it has been here for quite a while.. Anyway, as 
we still got several unsolved questions, such as what Doug mentioned,  
"until we understand what WE are dealing with (as opposed to what other 
organizations are dealing with) we're not going to make any actual 
progress.", unless our community come up with better ones soon 
addressing those, diversity won't make to IETF in a couple months.

Thanks for Brian and folks taking their time to setup the whole thing.

From brian.e.carpenter@gmail.com  Wed Jun 19 13:29:15 2013
Return-Path: <brian.e.carpenter@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 F37FE21E80CA for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 EFnGKLi32Zhf for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:29:09 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id 37AD821E80C7 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:29:09 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id p10so5409151pdj.22 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:29:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BrKqEfUQ0zyDItBkCrZ8Yedt1QlAsmar7OA+HbwHBmk=; b=B/dFQTSnr4MkhX32I+C1LAnXjldsLBsl7LQhpoQ9yMtVbkCKUmsGWwCtfaur8XH1K8 lIfPg+5bVVbVjMc/rcwn3tG/slR//GVqPhztzm9p1T4qV9F42120ltSjd3dzmV9splDb 45gSLJcDZe0hafNBa8aqceUHlbzHyZreF1OSFyjfAVxfjYzd7cgZBNMciWd7Qk1L+ZgS J3URRl+y7GyVVbb0F/uoYYjIY391DJiaOdEgKD5TqF1fGYwTMDOjeAlhFVmtNnkU745t S9JFvr1dcZjORdzHeoK6/EHV7F2SjylWVw/meLJqMmZ72gDYcuHA6vVSN3xNf3DxDAbb lp5w==
X-Received: by 10.68.239.194 with SMTP id vu2mr1096294pbc.152.1371673748720; Wed, 19 Jun 2013 13:29:08 -0700 (PDT)
Received: from [192.168.178.20] (36.200.69.111.dynamic.snap.net.nz. [111.69.200.36]) by mx.google.com with ESMTPSA id ty8sm26205583pac.8.2013.06.19.13.29.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 13:29:08 -0700 (PDT)
Message-ID: <51C21498.3020008@gmail.com>
Date: Thu, 20 Jun 2013 08:29:12 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com>	<CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com>	<4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>
In-Reply-To: <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: John C Klensin <john-ietf@jck.com>, ietf <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, 19 Jun 2013 20:29:15 -0000

On 19/06/2013 18:25, Patrik F=C3=A4ltstr=C3=B6m wrote:
> On 18 jun 2013, at 18:54, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
>> As for the rest of the discussion - I'm sure there are things to be im=
proved in ICANN. I'd suggest though that some of the feedback might be be=
tter placed in an ICANN discussion than on IETF list. And is not like the=
re'd be nothing to improve on our side :-) Lets focus on IETF aspects her=
e.
>=20
> I think this is the correct strategy, BUT, I see as a very active parti=
cipant in ICANN (chair of SSAC) that work in ICANN could be easier if som=
e "more" technical standards where developed in IETF,=20

A pre-condition for that is that technical and operational problem statem=
ents
are formulated, which could be sent to appropriate WGs or used to justify=

a BOF. If ICANN could focus on that instead of solutionism or committeeis=
m,
progress should be possible.

    Brian

> and moved forward along standards track, that ICANN can reference. Same=
 with some epp-related issues, and also DNS-related, which I must admit I=
 think has stalled in the IETF. When that happens, ICANN start to "invent=
" or at least discuss IETF related issues -- which I think is non optimal=
=2E But on the other hand, if IETF do not move forward, then what should =
ICANN do?
>=20
> I will btw be the first few days (until including Tuesday or so) at IET=
F in Berlin and am happy to discuss this issue with anyone interested.
>=20
>    Patrik F=C3=A4ltstr=C3=B6m
>    Chair SSAC, ICANN
>=20
> .
>=20


From Ted.Lemon@nominum.com  Wed Jun 19 13:40:55 2013
Return-Path: <Ted.Lemon@nominum.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 4DCCA21F9B23 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.602
X-Spam-Level: 
X-Spam-Status: No, score=-106.602 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 ls08qDx7xo1c for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:40:48 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 8F0A921F9ADC for <ietf@ietf.org>; Wed, 19 Jun 2013 13:40:48 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKUcIXUIiKB5aqy6yCZbg7QCRwGmZd4S0C@postini.com; Wed, 19 Jun 2013 13:40:48 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 036041B81B0 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:40:48 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id ED15519005D; Wed, 19 Jun 2013 13:40:47 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 19 Jun 2013 13:40:48 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Is the IETF is an international organization? (was: IETF Diversity)
Thread-Topic: Is the IETF is an international organization? (was: IETF Diversity)
Thread-Index: AQHObSHgelgfZ3LCwEWEpc5SvNT4pZk99aKA
Date: Wed, 19 Jun 2013 20:40:47 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751E132F@mbx-01.win.nominum.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net> <0D1D10FE-39B0-4C51-9283-715823CD4969@checkpoint.com>
In-Reply-To: <0D1D10FE-39B0-4C51-9283-715823CD4969@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A8C1B4A9591F124BA9A99A4C94FA8786@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: SM <sm@resistor.net>, "<ietf@ietf.org>" <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, 19 Jun 2013 20:40:55 -0000

On Jun 19, 2013, at 3:18 PM, Yoav Nir <ynir@checkpoint.com> wrote:
> Yeah, and "act" is what Americans call statutes, and Selma is a city in A=
labama where there was some controversy about voting rights. You sure need =
to know a lot of Americana to participate meaningfully in some of these dis=
cussions.

Sorry.   That was directed largely at Melinda who is, to the best of my und=
erstanding, an American.   The point was that in fact the civil rights move=
ment started with individuals, not the government.


From Ted.Lemon@nominum.com  Wed Jun 19 13:42:58 2013
Return-Path: <Ted.Lemon@nominum.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 1063021E8064 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.602
X-Spam-Level: 
X-Spam-Status: No, score=-106.602 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 6elS4gThLFaI for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:42:51 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 531D621F9FF1 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:42:51 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUcIXy/UgnR5nutB54yx4fpYc8kyyr4Nh@postini.com; Wed, 19 Jun 2013 13:42:51 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id F1BAD1B816F for <ietf@ietf.org>; Wed, 19 Jun 2013 13:42:50 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id EB81119005D; Wed, 19 Jun 2013 13:42:50 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 19 Jun 2013 13:42:44 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John Levine <johnl@taugh.com>
Subject: Re: IETF, ICANN and non-standards
Thread-Topic: IETF, ICANN and non-standards
Thread-Index: AQHObSVkPOfQiKyI4Eeu6ZUqJ2j5V5k99iWA
Date: Wed, 19 Jun 2013 20:42:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751E1362@mbx-01.win.nominum.com>
References: <20130619194338.49286.qmail@joyce.lan>
In-Reply-To: <20130619194338.49286.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <855A5E84E2D8AE4288AA328614417BF9@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, "<paf@frobbit.se>" <paf@frobbit.se>
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, 19 Jun 2013 20:42:58 -0000

On Jun 19, 2013, at 3:43 PM, John Levine <johnl@taugh.com> wrote:
> Assuming we care about stability and interoperability, wouldn't it
> make sense for the IETF to spin up a WG, collect these drafts, clean
> up the language, make sure they agree with the widely implemented
> reality, and publish them?

The only way that something like this can happen is for some current or fut=
ure IETF participants to do it.   "The IETF" doesn't spin up working groups=
.   IETF participants do.


From randy@psg.com  Wed Jun 19 13:45:36 2013
Return-Path: <randy@psg.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 28DE321E80B2 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
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 tPd4kpr8PtB8 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:45:35 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id B6ACA21E8064 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:45:35 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UpPG2-000ESn-Nv; Wed, 19 Jun 2013 20:45:35 +0000
Date: Thu, 20 Jun 2013 05:45:33 +0900
Message-ID: <m2mwqlyglu.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource	Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
In-Reply-To: <51C1B235.6020507@bogus.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: 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, 19 Jun 2013 20:45:36 -0000

> Given that this document was revved twice and had it's requested status 
> change during IETF last call in response to discussion criticism and new 
> contribution I am going to rerun the last call.

the recent changes resolved my issue.  thanks joe and joel.

randy

From melinda.shore@gmail.com  Wed Jun 19 13:52:14 2013
Return-Path: <melinda.shore@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 802F321F9CF3 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:52:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 35dRgppmdNcr for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 13:52:14 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 245D621F9C69 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:52:14 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro2so5437053pbb.41 for <ietf@ietf.org>; Wed, 19 Jun 2013 13:52:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=l/AS4xg7jFwO/I4YGV4SmXSZnyEmSnvz+0Dgl1LohAM=; b=PDjN4HUT8MMYBJEAN8T3PRp4d682dx6EtOF37uZLQuxmKAJ24cjFa1RBOXKqraHcKw EklDAwWRa9S4McfjpIjOfdWAGf2/JEq63o7i8VmWThJh6U1u1+J85Kw29p7TALsCBpBQ M7JVNvGZI25yPKCalJUGQNgGUVmhhBE0tc8qXA1urzFi93EsTIse/KYUwSQh3WKEzwXj dOGsZAkIAN+W6/EKIlPND93Hkx7rjZOercx9ehqznQX9EJVT9A/GcLR3eGE42Gt64gn+ r5LSvsd7vROThOJBJqj7DpDpHcL+m5V0tWAPLFalV8y02elnkke5xEE3uXFgo0DPvOXU bPQQ==
X-Received: by 10.66.145.201 with SMTP id sw9mr8414621pab.63.1371675133931; Wed, 19 Jun 2013 13:52:13 -0700 (PDT)
Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id dc3sm24539235pbc.9.2013.06.19.13.52.12 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 13:52:12 -0700 (PDT)
Message-ID: <51C219FA.9030605@gmail.com>
Date: Wed, 19 Jun 2013 12:52:10 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is the IETF is an international organization?
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net> <0D1D10FE-39B0-4C51-9283-715823CD4969@checkpoint.com> <8D23D4052ABE7A4490E77B1A012B6307751E132F@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751E132F@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 20:52:14 -0000

On 6/19/13 12:40 PM, Ted Lemon wrote:
> Sorry.   That was directed largely at Melinda who is, to the best of
> my understanding, an American.  

Binational.  Thanks for asking.

Melinda


From warren@kumari.net  Wed Jun 19 14:04:17 2013
Return-Path: <warren@kumari.net>
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 16ACB21F9FF1 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kPwkogD8iFTw for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:04:00 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39CF821F9FEA for <ietf@ietf.org>; Wed, 19 Jun 2013 14:03:57 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 08FB31B40227; Wed, 19 Jun 2013 17:03:56 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] Re: IETF, ICANN and non-standards
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <20130619194338.49286.qmail@joyce.lan>
Date: Wed, 19 Jun 2013 17:03:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9408A04D-CBF9-49F2-85F3-2409805B80CB@kumari.net>
References: <20130619194338.49286.qmail@joyce.lan>
To: "John Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org, paf@frobbit.se
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, 19 Jun 2013 21:04:18 -0000

On Jun 19, 2013, at 3:43 PM, "John Levine" <johnl@taugh.com> wrote:

>> I think this is the correct strategy, BUT, I see as a very active =
participant in ICANN
>> (chair of SSAC) that work in ICANN could be easier if some "more" =
technical standards where
>> developed in IETF, and moved forward along standards track, that =
ICANN can reference.
>=20
> As a concrete example, the EPP systems used in production by TLD
> registries use extensions that are documented only in I-Ds, often
> expired I-Ds, or in dusty I-D like web documents.  If you look at the
> applications for new TLDs on the ICANN web site at
> https://gtldresult.icann.org/application-result/applicationstatus you
> will find that nearly all of them plan to use EPP extensions not
> described in an RFC.  Most of these extensions should be utterly
> uncontroversial, e.g., one to synchronize renewal dates among multiple
> domains, or another to tell a client that its credit balance has
> dropped below a threshold.
>=20
> Assuming we care about stability and interoperability, wouldn't it
> make sense for the IETF to spin up a WG, collect these drafts, clean
> up the language, make sure they agree with the widely implemented
> reality, and publish them?

I realize you were asking a larger question, but..

If we do, I volunteer to help collect, review, clean up, check and push =
them along.

W

>=20
> R's,
> John
>=20

--
"Working the ICANN process is like being nibbled to death by ducks,
it takes forever, it doesn't make sense, and in the end we're still dead =
in the water."=20
    -- Tom Galvin, VeriSign's vice president for government relations.




From jabley@hopcount.ca  Wed Jun 19 14:14:26 2013
Return-Path: <jabley@hopcount.ca>
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 0D1CC21E80CC for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 atxmH1SU6pj6 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:14:21 -0700 (PDT)
Received: from mail-pd0-f174.google.com (mail-pd0-f174.google.com [209.85.192.174]) by ietfa.amsl.com (Postfix) with ESMTP id AB3E421E80D1 for <ietf@ietf.org>; Wed, 19 Jun 2013 14:14:17 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id 10so5473774pdc.33 for <ietf@ietf.org>; Wed, 19 Jun 2013 14:14:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=oEIlLsPVZPZ56ZROXz4XV8Qdy/WgCOgvWEQuZsNXVjk=; b=fOsMOzOl6LFzJ6eDnY65kcUhf6RfpRLLAZ5vE1Ul0aRfckRMFsoTMV8Vxtd69x9qHX 88Y5eX13QzKoi7+BL1Sdmsdrr+Qvc3WodPdTd/JXOPzAoA3AaCnnph+3OBANA6xA90LM 8lEltU1cJJR1INza9QM284YCH6Vz4Mp/GFwmg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=oEIlLsPVZPZ56ZROXz4XV8Qdy/WgCOgvWEQuZsNXVjk=; b=cgxZys+FYtu7/1ier0FDSH3sjgxuvyKXjU4Dw60DJjEaQl90b3+6Ic48CuNvGks9gB LsHz9GZxF+Q6vc+NmKCkLFGRqo7JlFPy9wdweVK76ZcRmaGVbOTZFUPWYLdAcNrEeNJJ QhKw9cGx4NKxAyaAq9m4cNwEOSsplq0Wc+xBoaqq+MQp9DNtCPx+FdTh571TZpeWdTEc yjqe0Jz6FsTYPYJEUDxtY1IkivN85/fR1DYgUH3mkj8wB58TDSYo7eXoyGqBSP77EsFw LFv4kWelAeXZiBLHxlQbEj3fqH5M3WqUlpqwTI2eux7bgM/uFdVxlu+iWw1xdrsTifUh irjw==
X-Received: by 10.68.248.100 with SMTP id yl4mr4510035pbc.125.1371676457088; Wed, 19 Jun 2013 14:14:17 -0700 (PDT)
Received: from dh30.r1.hopcount.ca (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id jb2sm24601281pbc.8.2013.06.19.14.14.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 14:14:16 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] Re: IETF, ICANN and non-standards
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <9408A04D-CBF9-49F2-85F3-2409805B80CB@kumari.net>
Date: Wed, 19 Jun 2013 17:14:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <82B9CDA7-6871-4718-BC3E-AFFFE98CFCF7@hopcount.ca>
References: <20130619194338.49286.qmail@joyce.lan> <9408A04D-CBF9-49F2-85F3-2409805B80CB@kumari.net>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQlb8dBEoVJOLui7cl/yFgUdOWDJQSa/VCM6PxfBKNT8f3h4L6TszQD1Yk5WqdWpQdNhy4rp
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org, paf@frobbit.se
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, 19 Jun 2013 21:14:26 -0000

On 2013-06-19, at 17:03, Warren Kumari <warren@kumari.net> wrote:

> On Jun 19, 2013, at 3:43 PM, "John Levine" <johnl@taugh.com> wrote:
>=20
>> Assuming we care about stability and interoperability, wouldn't it
>> make sense for the IETF to spin up a WG, collect these drafts, clean
>> up the language, make sure they agree with the widely implemented
>> reality, and publish them?
>=20
> I realize you were asking a larger question, but..
>=20
> If we do, I volunteer to help collect, review, clean up, check and =
push them along.

This is also something we could dedicate ICANN staff time to.


Joe


From warren@kumari.net  Wed Jun 19 14:14:44 2013
Return-Path: <warren@kumari.net>
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 9904A21E80ED for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.433
X-Spam-Level: 
X-Spam-Status: No, score=-102.433 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 yZZF4bqbnmEx for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:14:33 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6342321E80CA for <ietf@ietf.org>; Wed, 19 Jun 2013 14:14:33 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 46EE01B40BB1; Wed, 19 Jun 2013 17:14:32 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <51C21498.3020008@gmail.com>
Date: Wed, 19 Jun 2013 17:14:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8EEFB02-5637-4247-98F6-3B414E045E0E@kumari.net>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com>	<CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com>	<4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <51C21498.3020008@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: John C Klensin <john-ietf@jck.com>, ietf <ietf@ietf.org>, =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
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, 19 Jun 2013 21:14:44 -0000

On Jun 19, 2013, at 4:29 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 19/06/2013 18:25, Patrik F=E4ltstr=F6m wrote:
>> On 18 jun 2013, at 18:54, Jari Arkko <jari.arkko@piuha.net> wrote:
>>=20
>>> As for the rest of the discussion - I'm sure there are things to be =
improved in ICANN. I'd suggest though that some of the feedback might be =
better placed in an ICANN discussion than on IETF list. And is not like =
there'd be nothing to improve on our side :-) Lets focus on IETF aspects =
here.
>>=20
>> I think this is the correct strategy, BUT, I see as a very active =
participant in ICANN (chair of SSAC) that work in ICANN could be easier =
if some "more" technical standards where developed in IETF,=20
>=20

+ lots.

If these are not developed in the IETF, we run the risk of ICANN doing =
technical stuff.

As someone whose time is now[0] split between ICANN and IETF, I can tell =
you something -- you[1] *really* don't want ICANN developing technical =
standard.

> A pre-condition for that is that technical and operational problem =
statements
> are formulated, which could be sent to appropriate WGs or used to =
justify
> a BOF. If ICANN could focus on that instead of solutionism or =
committeeism,
> progress should be possible.

Yup. This message needs to be properly communicated though -- Suzanne =
Woolf has been attempting (and being fairly effective) to do so.

W
[0]: I, along with some other IETF folk, serve on the SSAC under Patrik.=20=

[1]: You in the general sense, not you as in Brian or Patrik -- although =
I'm guessing you don't either. Are you confused yet with which you you =
are?

>=20
>    Brian
>=20
>> and moved forward along standards track, that ICANN can reference. =
Same with some epp-related issues, and also DNS-related, which I must =
admit I think has stalled in the IETF. When that happens, ICANN start to =
"invent" or at least discuss IETF related issues -- which I think is non =
optimal. But on the other hand, if IETF do not move forward, then what =
should ICANN do?
>>=20
>> I will btw be the first few days (until including Tuesday or so) at =
IETF in Berlin and am happy to discuss this issue with anyone =
interested.
>>=20
>>   Patrik F=E4ltstr=F6m
>>   Chair SSAC, ICANN
>>=20
>> .
>>=20
>=20

--
She'd even given herself a middle initial - X - which stood for "someone =
who has a cool and exciting middle name".

    -- (Terry Pratchett, Maskerade)



From johnl@iecc.com  Wed Jun 19 14:14:50 2013
Return-Path: <johnl@iecc.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 A49D821E80CA for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.448
X-Spam-Level: 
X-Spam-Status: No, score=-102.448 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 0r7osxkKgeFv for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:14:50 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9EF0B21E80EE for <ietf@ietf.org>; Wed, 19 Jun 2013 14:14:45 -0700 (PDT)
Received: (qmail 85061 invoked from network); 19 Jun 2013 21:14:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=14c44.51c21f43.k1306; bh=/KsPs+C8r4fSfChHlJCwf9kOu5u/nhtjY4g49YODmQQ=; b=G2HWFWmYbzxt7vYLWg5xEb6AMScpdOkpCghYnU9XU9HHq4IFkzMb/tRUAmpCXDOT8Ve4FQOhLj/qeoz1v0Ntc2qP4qYtF0TCGvrpcSS54ZJpm0pTOidu1uUNV0pAXzlhuFELeiwT5LOkaDqZ5vLt8X2McpzsxXGR2Wl0YvBZUWt1D7CXBl1G3oKBQAx8OviICY6yAMqm3V+vaVpokSyUtnHYphf2iE/iGUWE3Ku8mSHXlBcgVLGblYs3AXOExkf9
Received: (ofmipd 127.0.0.1); 19 Jun 2013 21:14:21 -0000
Date: 19 Jun 2013 17:14:42 -0400
Message-ID: <alpine.BSF.2.00.1306191714190.49435@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>
Subject: Re: IETF, ICANN and non-standards
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751E1362@mbx-01.win.nominum.com>
References: <20130619194338.49286.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B6307751E1362@mbx-01.win.nominum.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>, "<paf@frobbit.se>" <paf@frobbit.se>
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, 19 Jun 2013 21:14:50 -0000

> On Jun 19, 2013, at 3:43 PM, John Levine <johnl@taugh.com> wrote:
>> Assuming we care about stability and interoperability, wouldn't it
>> make sense for the IETF to spin up a WG, collect these drafts, clean
>> up the language, make sure they agree with the widely implemented
>> reality, and publish them?
>
> The only way that something like this can happen is for some current or 
> future IETF participants to do it.  "The IETF" doesn't spin up working 
> groups.  IETF participants do.

I'd do it if there were other interest.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From doug.mtview@gmail.com  Wed Jun 19 14:18:40 2013
Return-Path: <doug.mtview@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 5FBCF21E8090 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_00=-2.599, J_CHICKENPOX_51=0.6]
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 D9oGeOMGSYTN for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:18:34 -0700 (PDT)
Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by ietfa.amsl.com (Postfix) with ESMTP id 8FDA921F9A4E for <ietf@ietf.org>; Wed, 19 Jun 2013 14:18:34 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id 4so5494479pdd.20 for <ietf@ietf.org>; Wed, 19 Jun 2013 14:18:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=xVfZpGa2VHBLs0xFMN79h8QJ1hU+9ynARwZWcDLt82w=; b=sbDrKkkN2knSLpwpSmAVXJtgCfTcv79vUDLcDncR0MfPGlsnctM+hmGr/UcD7r0cU/ I0RCdHL96R6VrAw59uT8r+ZTGig5RbARNwWXsckcT/eiyYPSFlU0100zYZrGkMOhvU+9 4fMydwn5tpVsxCsL2xVkWRH+Z73PjBRngUbnfP8p4e1TaIL5nd9zEs08iHk010YpwY6l eauYe0AAl/tj0FjNGzxmqITcmk3s5mRsGgajE4kxx3MraySX+Zv0M0eUW/9jS4Zc4vio qiWc+jlLSRE6O+pVjzWYducUxfaI8M6cqIA0EgKK4ltZWDRFrnjEQLrB0n7i/C1AZRLg LA6w==
X-Received: by 10.66.7.164 with SMTP id k4mr8584085paa.142.1371676710728; Wed, 19 Jun 2013 14:18:30 -0700 (PDT)
Received: from dhcp194.priv.bungi.com (c-24-4-157-244.hsd1.ca.comcast.net. [24.4.157.244]) by mx.google.com with ESMTPSA id kq2sm11987351pab.19.2013.06.19.14.18.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 14:18:29 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Is the IETF is an international organization? (was: IETF Diversity)
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net>
Date: Wed, 19 Jun 2013 14:18:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D75AF692-E571-4A50-8A75-CE62D7390491@gmail.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1508)
Cc: 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, 19 Jun 2013 21:18:40 -0000

On Jun 19, 2013, at 12:07 PM, SM <sm@resistor.net> wrote:

> Hi Aaron,
> At 11:40 19-06-2013, Aaron Yi DING wrote:
>> Relating to the statement above(I assume Phillip is addressing the US =
Academia), not quite sure are we still discussing the same topic?
>> sorry, I am bit confused ..  since IETF is an international =
organization.
>=20
> I changed the subject line as I am as confused as to whether the IETF =
is an international organization.
>=20
> There was a mention of "First the Civil Rights act, then Selma...  =
;)".  I assume that the act is an Act for the United States of America.  =
Harvard was also mentioned.  I did a quick search and I found out that =
"Harvard University is an American private Ivy League research =
university".

Dear SM,

Are new ideas embraced without any prior geographic endorsement? While =
this seems to be the case, organizations with greater resources, often =
from various regions, will steer development. =20

There be dragons empathizing about motivations to understand declared =
rules, stated justifications, or even what censuses really means.  Even =
with the best of intentions, it is very difficult to have meaningful =
discussions about motivations .=20

In respect to privacy, organizations both sell and purchase profile =
information containing individual preferences and contact information.  =
There are also organizations that attempt offer selective relationships, =
often via a social network.  In deciding what is important to protect, =
the identity of those initiating transactions, or those receiving them =
are at odds.=20

Even a statement females are more sensitive about security than men in =
respect to technology in the home can be viewed as either a real insight =
or a sexist view.  By having gender diversity, questioning the =
underlying motivations can be avoided.  It seems the same can be said of =
those trading profiles or and those offering protection from profilers.  =
Motivation plays a critical role in steering development.  It is just =
not something easily discussed within an international organization.

Regards,
Douglas Otis=20

  =20=

From warren@kumari.net  Wed Jun 19 14:19:36 2013
Return-Path: <warren@kumari.net>
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 D151821F9A4E for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level: 
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 0j8hkqWwJapP for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 14:19:31 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5A0F21E80EB for <ietf@ietf.org>; Wed, 19 Jun 2013 14:19:31 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 3217B1B4029B; Wed, 19 Jun 2013 17:19:31 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] Re: IETF Diversity
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <51C1F9DC.8010803@dcrocker.net>
Date: Wed, 19 Jun 2013 17:19:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <176ED95D-1B67-4853-BE94-81102775EC3C@kumari.net>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1F8FF.90100@gmail.com> <51C1F9DC.8010803@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1508)
Cc: 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, 19 Jun 2013 21:19:36 -0000

On Jun 19, 2013, at 2:35 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 6/19/2013 11:31 AM, Melinda Shore wrote:
>> Even in fields in which the overwhelming majority of
>> practitioners, the majority of people in leadership or
>> management positions are men.  Everybody's got good
>> intentions
>=20
>=20
> indeed, almost everyone claims that they are a better than average =
driver.

Nah, I'm better than everyone else, because I don't suffer from the =
Dunning=96Kruger effect.

>=20
> individual self-assessment tends to be a very unreliable mechanism =
upon which to base efforts at social change.

Indeed.

W
>=20
>=20
> d/
>=20
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>=20

--=20
Never criticize a man till you've walked a mile in his shoes.  Then if =
he didn't like what you've said, he's a mile away and barefoot.=20




From marka@isc.org  Wed Jun 19 15:45:56 2013
Return-Path: <marka@isc.org>
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 B563321F9DAC for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 15:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.213
X-Spam-Level: 
X-Spam-Status: No, score=-2.213 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
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 oxsoEFTObNXX for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 15:45:51 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id EC45F21F9C75 for <ietf@ietf.org>; Wed, 19 Jun 2013 15:45:51 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 73261C9425; Wed, 19 Jun 2013 22:45:43 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1371681951; bh=sgEiINZlZD6G5CIUy4baS0iDqzmoF3995On+L2kccmw=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=bdR9ButfYQ6eqGAHuoYUozKBrcHWNebk2DHem7M/naDPIbKUbnG53qvV2nXipS8BI SZvfU4vYXqCBvA4gmPY4o/Qlyq1sG3L3xHxofxALowBmzvO8BnAjwUvCvyeYsMsnhv lu5YEaNIttmRQqZvdnNd16cq1z7Tpet2A4KsIHdE=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 19 Jun 2013 22:45:43 +0000 (UTC) (envelope-from marka@isc.org)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id A680116006D; Wed, 19 Jun 2013 22:46:26 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id ckHSpDURpY9Q; Wed, 19 Jun 2013 22:46:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 4080A160076; Wed, 19 Jun 2013 22:46:26 +0000 (UTC)
X-Virus-Scanned: amavisd-new at zmx1.isc.org
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Lt7BAYdlXaPX; Wed, 19 Jun 2013 22:46:26 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) by zmx1.isc.org (Postfix) with ESMTPSA id D331416006D; Wed, 19 Jun 2013 22:46:25 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id ED56F3612FD0; Thu, 20 Jun 2013 08:44:43 +1000 (EST)
To: Randy Bush <randy@psg.com>
From: Mark Andrews <marka@isc.org>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <m2mwqlyglu.wl%randy@psg.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
In-reply-to: Your message of "Thu, 20 Jun 2013 05:45:33 +0900." <m2mwqlyglu.wl%randy@psg.com>
Date: Thu, 20 Jun 2013 08:44:43 +1000
Message-Id: <20130619224443.ED56F3612FD0@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: 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, 19 Jun 2013 22:45:56 -0000

In message <m2mwqlyglu.wl%randy@psg.com>, Randy Bush writes:
> > Given that this document was revved twice and had it's requested status 
> > change during IETF last call in response to discussion criticism and new 
> > contribution I am going to rerun the last call.
> 
> the recent changes resolved my issue.  thanks joe and joel.
> 
> randy

I have read -05 and in my opinion it is good to go.o

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From yding@cs.helsinki.fi  Wed Jun 19 15:58:12 2013
Return-Path: <yding@cs.helsinki.fi>
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 6A38D21F9DF2; Wed, 19 Jun 2013 15:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 45I9tiGRpeY0; Wed, 19 Jun 2013 15:58:07 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id F27E621F9733; Wed, 19 Jun 2013 15:58:06 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Thu Jun 20 01:57:50 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s= dkim20130528; bh=FdadBp+76uYLOaIYe5/YXa+XJtU0qITjUyqfPODrXGg=; b= c2Wg0lDTN6ejPQ5wM7bcUoroFfiRHlu7IZUjAbprGjw9YKOGBOcvJofAXG8GlA6j 9LH2btufEjkeh7BzMiBtntfK6ofjlTdtYseVpiVe8i/DMA2S5Cnls0e0QD5gYuVY eKGRPuLPZTAK8egd4Cc3xKrg79/EH71Yat2oUnBAsvA=
Received: from [192.168.93.100] (host-94-101-2-100.igua.fi [94.101.2.100]) (AUTH: PLAIN yding, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Thu, 20 Jun 2013 01:57:50 +0300 id 00068086.51C2376E.00006CC5
Message-ID: <51C2376E.80400@cs.helsinki.fi>
Date: Thu, 20 Jun 2013 01:57:50 +0300
From: Aaron Yi DING <yding@cs.helsinki.fi>
Organization: Helsinki University
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "<ietf@ietf.org>" <ietf@ietf.org>, "<diversity@ietf.org>" <diversity@ietf.org>
Subject: IETF Diversity vs. White Male ??
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im> <51C1CD95.4060106@innovationslab.net> <EBC640C6-E812-479F-9166-D0AEC941117C@checkpoint.com>
In-Reply-To: <EBC640C6-E812-479F-9166-D0AEC941117C@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 19 Jun 2013 22:58:12 -0000

On 19/06/13 22:56, Yoav Nir wrote:
> On Jun 19, 2013, at 6:26 PM, Brian Haberman <brian@innovationslab.net> wrote:
>
>> To help facilitate the mentoring aspect, there will be a call soon for volunteers to act as mentors for newcomers (starting with IETF 87). Once the web page for the mentoring program with all the information is up, you should be seeing a call for mentors.
>>
>> We hope that this type of program will aid in assisting newer members of the IETF community become more involved and productive in our activities.
> This may be helpful in getting first-time attendees to stay on with the IETF. That is a laudable goal in itself, but I'm not sure if it will help diversity. Just bringing in new white male employees of US router companies will not increase diversity. It might work if the pool of newcomers is considerably more diverse than the pool of veterans, but having been in the last two meet-and-greets, I see a lot of the same, except that the newcomer group has more people from China. I see few women, hardly any Africans (from Africa or the US), and not a lot of company names I recognize as operators.
>



There is one observation puzzled me, and it will be good to hear from 
the community, sort of like 'request for comments'.  Part of it is based 
on the previous IETF panel discussions plus all sorts of mails from ietf 
related lists.

By following our diversity discussions so far, the term "white male" 
seems to be cited rather frequently and most of time with some kind of 
emotions attached to it, e.g. dominant, power, monopoly etc.  To be 
honest, I do have a mixed feeling when encountering such KEY WORD in a 
public speech or along the lines of mail. That feeling resembles very 
much when I heard Chinese being associated with minority, passive, 
reserved or even, communist ...

I understand the term "black" is not friendly to mention in US, but 
seriously, is the other term WHITE now being so freely used as such, 
especially in IETF, not even a slight concern? Just because the 
tolerance level among the white male group is already so high that no 
one really cares about it anymore? or just because currently IETF 
engineers tagged with white male background are found in most 
management/leadership slots so that it is easier to draw some kind of 
hatred feeling or recognition from the under-present group who have 
being pressed for so long? Sometimes it is quite hard to distinguish the 
intention of such, being considerate and thoughtful for the healthy 
development of our community, or just to fit in certain group's craving 
for the taste of the throne (here I don't target at any specific person, 
seriously)

One visible flaw is that to wire the "white male" up against diversity 
in IETF is largely irrelevant to the topic itself. This is in large a 
stereotype. Like currently there are so many Chinese living 
permanently/grow up in America, Europe and Asia. The "white male" are 
similarly not just from or living/working in the US, there are so many I 
know actually are living outside, oh well, definitely covering EU, and 
in many Asian areas, Japan, Korea, Singapore, and in major Chinese 
cities like Shanghai and Hong Kong. They definitely can understand and 
appreciate the culture differences in terms of working and 
communications, which are most relevant to the IETF functionality.

The more relevant thing here is that what do we actually want? Would it 
be that we need more diverse participation from the globe which in the 
end maximize the output and impact of IETF? Right now our white male 
engineers are put on the front line to be 'scrutinized' under the 
'diversity' microscope, what if a couple years later, the trend shifts 
to Asians? or Latin America or Australians or Africans. Sorry, I really 
try to avoid the skin color or gender here, because I personally believe 
it is essentially off the topic of the whole IETF diversity thing we 
shall focus on.

As the title hinted, really hope the goal of this diversity movement 
does not end up into against or wiping out "white male" from IETF, just 
because people 'firmly' believe they are the ones controlling the whole 
scene and resources, and won't let it go unless a revolution is called 
upon (btw, does it sound similar to many others demanding a radical 
revolution to the existing Chinese dominant 'group'? :)

Well, if the dominant ones later being replaced by other groups, do we 
need to revamp again? What will be the end?


Thanks, particularly for tolerating such long mail,
Aaron

From jsalowey@cisco.com  Wed Jun 19 16:23:11 2013
Return-Path: <jsalowey@cisco.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 10E3F21F9D69; Wed, 19 Jun 2013 16:23:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 bS54rLKLBgZi; Wed, 19 Jun 2013 16:23:05 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 33D5421F9D5B; Wed, 19 Jun 2013 16:23:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14139; q=dns/txt; s=iport; t=1371684185; x=1372893785; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=UMC3pumKxAdqjVQNgYLKqxTstKU6qCVlVRhqL7fKB1c=; b=i7jhDQctPk04RQa/EoOYrd3s1HH0KfMP18GWAC+yWegrcz8xNKy0LEvq XF/kTlaaO1fItEBefrZcCNRmht503U6giqETf24B3WDXzkf+tHKdXXVIt 7UDQ4QkqBUyKJ9TkiTdN12sxymkJG5CHa8a0NUD1iKHYnlaOmYWocs8O5 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEFALY8wlGtJXHA/2dsb2JhbABQCoMJMUm2YYg6gQAWdIIjAQEBBHkMBAIBCBEEAQELHQcyFAkIAgQOBQiIBrwGjgaBCzEHBgOCd2EDmGqKeYUigw+CKA
X-IronPort-AV: E=Sophos;i="4.87,900,1363132800";  d="scan'208,217";a="225035286"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-6.cisco.com with ESMTP; 19 Jun 2013 23:23:04 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r5JNN4gd009359 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Jun 2013 23:23:04 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.004; Wed, 19 Jun 2013 18:23:04 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Black, David" <david.black@emc.com>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQAAClxl4P//t2GAgAA80uCAAbNjgA==
Date: Wed, 19 Jun 2013 23:23:03 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628D03C96@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71298265300@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71298265300@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.248.222]
Content-Type: multipart/alternative; boundary="_000_A95B4818FD85874D8F16607F1AC7C628D03C96xmbrcdx09ciscocom_"
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <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, 19 Jun 2013 23:23:11 -0000

--_000_A95B4818FD85874D8F16607F1AC7C628D03C96xmbrcdx09ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for the text,  some revision to address
On Jun 18, 2013, at 12:34 PM, "Black, David" <david.black@emc.com<mailto:da=
vid.black@emc.com>> wrote:

[Joe] Good points, the text can be more specific:

"In environments where EAP is used for purposes other than network access
authentication all EAP servers MUST enforce channel bindings.  For applicat=
ion
authentication, the EAP server MUST require that the correct EAP lower-laye=
r
attribute be present in the channel binding data.   For network access
authentication, the EAP server MUST require that if channel bindings are
present they MUST contain the correct EAP lower-layer attribute.   All netw=
ork
access EAP peer implementations SHOULD use channel bindings including the E=
AP
lower-layer attribute to explicitly identify the reason for authentication.
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r
attribute to prevent confusion with network access usage. "

This is looking good, modulo Sam's comment on EAP lower-layer vs. something
else that I'll leave to you and he to sort out.  I have a suggested rewrite=
,
mostly to clarify MUST vs. SHOULD requirements for support vs. usage, and
to reformat into a structured bullet list of requirements (this is not
intended to change any requirements from what you wrote):

"In environments where EAP is used for purposes other than network access
authentication:

o All EAP servers and all application access EAP peers MUST
support channel bindings.  All network access EAP peers
SHOULD support channel bindings.

o Channel binding MUST be used for all application authentication.
The EAP server MUST require that the correct EAP lower-layer
attribute be present in the channel binding data for
application authentication.

o Channel binding MUST be used for all application authentication.
The EAP server MUST either require that the correct EAP lower-layer
attribute or another attribute indicating the purpose of the authentication
be present in the channel binding data for application authentication.


o Channel binding SHOULD be used for all network access authentication,
and when channel binding data is present, the EAP server MUST
require that it contain the correct EAP lower-layer attribute
to explicitly identify the reason for authentication.

o Any new usage of EAP MUST use channel bindings including the
EAP lower-layer attribute to prevent confusion with network
access usage.

Thanks,
--David


-----Original Message-----
From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com<http://cisco.com=
>]
Sent: Tuesday, June 18, 2013 1:47 PM
To: Black, David
Cc: stefan.winter@restena.lu<mailto:stefan.winter@restena.lu>; General Area=
 Review Team; abfab@ietf.org<mailto:abfab@ietf.org>;
ietf@ietf.org<mailto:ietf@ietf.org>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03


I think we could state this a bit better as something like:

"In environments where EAP is used for applications authentication and netw=
ork
access authentication all EAP servers MUST understand channel bindings and
require that application bindings MUST be present in application
authentication and that application bindings MUST be absent in network
authentication.   All network access EAP peer implementations SHOULD suppor=
t
channel binding to explicitly identify the reason for authentication.  Any =
new
usage of EAP MUST support channel bindings to prevent confusion with networ=
k
access usage. "

That text is an improvement, and it's headed in the same direction as Sam's
comment - "application bindings MUST be present in application authenticati=
on"
is a "MUST use" requirement, not just a "MUST implement" requirement.

OTOH, I'm not clear on what "application bindings" means, as that term's no=
t
in the current draft.  Specifically, I'm a bit unclear on "application bind=
ings
MUST be absent in network authentication" - does that mean that channel
binding must be absent, or that channel binding is optional, but if channel
binding is present, it MUST NOT be an "application binding", whatever that
is?


[Joe] Good points, the text can be more specific:

"In environments where EAP is used for purposes other than network access
authentication all EAP servers MUST enforce channel bindings.  For applicat=
ion
authentication, the EAP server MUST require that the correct EAP lower-laye=
r
attribute be present in the channel binding data.   For network access
authentication, the EAP server MUST require that if channel bindings are
present they MUST contain the correct EAP lower-layer attribute.   All netw=
ork
access EAP peer implementations SHOULD use channel bindings including the E=
AP
lower-layer attribute to explicitly identify the reason for authentication.
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r
attribute to prevent confusion with network access usage. "

Does this help?

Thanks,

Joe




--_000_A95B4818FD85874D8F16607F1AC7C628D03C96xmbrcdx09ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <AA2F65A4081D814C84E2017D57A884DA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Thanks for the text, &nbsp;some revision to address&nbsp;<br>
<div>
<div>On Jun 18, 2013, at 12:34 PM, &quot;Black, David&quot; &lt;<a href=3D"=
mailto:david.black@emc.com">david.black@emc.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<blockquote type=3D"cite">[Joe] Good points, the text can be more specific:=
<br>
<br>
&quot;In environments where EAP is used for purposes other than network acc=
ess<br>
authentication all EAP servers MUST enforce channel bindings. &nbsp;For app=
lication<br>
authentication, the EAP server MUST require that the correct EAP lower-laye=
r<br>
attribute be present in the channel binding data. &nbsp;&nbsp;For network a=
ccess<br>
authentication, the EAP server MUST require that if channel bindings are<br=
>
present they MUST contain the correct EAP lower-layer attribute. &nbsp;&nbs=
p;All network<br>
access EAP peer implementations SHOULD use channel bindings including the E=
AP<br>
lower-layer attribute to explicitly identify the reason for authentication.=
<br>
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r<br>
attribute to prevent confusion with network access usage. &quot;<br>
</blockquote>
<br>
This is looking good, modulo Sam's comment on EAP lower-layer vs. something=
<br>
else that I'll leave to you and he to sort out. &nbsp;I have a suggested re=
write,<br>
mostly to clarify MUST vs. SHOULD requirements for support vs. usage, and<b=
r>
to reformat into a structured bullet list of requirements (this is not<br>
intended to change any requirements from what you wrote):<br>
<br>
&quot;In environments where EAP is used for purposes other than network acc=
ess<br>
authentication:<br>
<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>o All EAP s=
ervers and all application access EAP peers MUST<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>support channel bindin=
gs. &nbsp;All network access EAP peers<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>SHOULD support channel=
 bindings.<br>
<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>o Channel b=
inding MUST be used for all application authentication.<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>The EAP server MUST re=
quire that the correct EAP lower-layer<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>attribute be present i=
n the channel binding data for<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>application authentica=
tion.</blockquote>
<div>
<blockquote type=3D"cite"></blockquote>
<font color=3D"#0f61c8"><br>
</font>
<blockquote type=3D"cite"></blockquote>
<span class=3D"Apple-tab-span" style=3D"white-space: pre; "></span>o Channe=
l binding MUST be used for all application authentication.<br>
<blockquote type=3D"cite"></blockquote>
<span class=3D"Apple-tab-span" style=3D"white-space: pre; "></span><span cl=
ass=3D"Apple-tab-span" style=3D"white-space: pre; "></span>The EAP server M=
UST either require that the correct EAP lower-layer<br>
<blockquote type=3D"cite"></blockquote>
<span class=3D"Apple-tab-span" style=3D"white-space: pre; "></span><span cl=
ass=3D"Apple-tab-span" style=3D"white-space: pre; "></span>attribute or ano=
ther attribute indicating the purpose of the authentication</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>be pre=
sent in the channel binding data for&nbsp;application authentication.</div>
<br>
<blockquote type=3D"cite"><br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>o Channel b=
inding SHOULD be used for all network access authentication,<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>and when channel bindi=
ng data is present, the EAP server MUST<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>require that it contai=
n the correct EAP lower-layer attribute<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>to explicitly identify=
 the reason for authentication.<br>
<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>o Any new u=
sage of EAP MUST use channel bindings including the<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>EAP lower-layer attrib=
ute to prevent confusion with network<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>access usage.<br>
<br>
Thanks,<br>
--David<br>
<br>
<br>
<blockquote type=3D"cite">-----Original Message-----<br>
From: Joseph Salowey (jsalowey) [mailto:jsalowey@<a href=3D"http://cisco.co=
m">cisco.com</a>]<br>
Sent: Tuesday, June 18, 2013 1:47 PM<br>
To: Black, David<br>
Cc: <a href=3D"mailto:stefan.winter@restena.lu">stefan.winter@restena.lu</a=
>; General Area Review Team;
<a href=3D"mailto:abfab@ietf.org">abfab@ietf.org</a>;<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03=
<br>
<br>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><br>
I think we could state this a bit better as something like:<br>
<br>
&quot;In environments where EAP is used for applications authentication and=
 network<br>
access authentication all EAP servers MUST understand channel bindings and<=
br>
require that application bindings MUST be present in application<br>
authentication and that application bindings MUST be absent in network<br>
authentication. &nbsp;&nbsp;All network access EAP peer implementations SHO=
ULD support<br>
channel binding to explicitly identify the reason for authentication. &nbsp=
;Any new<br>
usage of EAP MUST support channel bindings to prevent confusion with networ=
k<br>
access usage. &quot;<br>
</blockquote>
<br>
That text is an improvement, and it's headed in the same direction as Sam's=
<br>
comment - &quot;application bindings MUST be present in application authent=
ication&quot;<br>
is a &quot;MUST use&quot; requirement, not just a &quot;MUST implement&quot=
; requirement.<br>
<br>
OTOH, I'm not clear on what &quot;application bindings&quot; means, as that=
 term's not<br>
in the current draft. &nbsp;Specifically, I'm a bit unclear on &quot;applic=
ation bindings<br>
MUST be absent in network authentication&quot; - does that mean that channe=
l<br>
binding must be absent, or that channel binding is optional, but if channel=
<br>
binding is present, it MUST NOT be an &quot;application binding&quot;, what=
ever that<br>
</blockquote>
is?<br>
<blockquote type=3D"cite"><br>
</blockquote>
<br>
[Joe] Good points, the text can be more specific:<br>
<br>
&quot;In environments where EAP is used for purposes other than network acc=
ess<br>
authentication all EAP servers MUST enforce channel bindings. &nbsp;For app=
lication<br>
authentication, the EAP server MUST require that the correct EAP lower-laye=
r<br>
attribute be present in the channel binding data. &nbsp;&nbsp;For network a=
ccess<br>
authentication, the EAP server MUST require that if channel bindings are<br=
>
present they MUST contain the correct EAP lower-layer attribute. &nbsp;&nbs=
p;All network<br>
access EAP peer implementations SHOULD use channel bindings including the E=
AP<br>
lower-layer attribute to explicitly identify the reason for authentication.=
<br>
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r<br>
attribute to prevent confusion with network access usage. &quot;<br>
<br>
Does this help?<br>
<br>
Thanks,<br>
<br>
Joe<br>
<br>
</blockquote>
<br>
</blockquote>
</div>
<br>
</body>
</html>

--_000_A95B4818FD85874D8F16607F1AC7C628D03C96xmbrcdx09ciscocom_--

From john-ietf@jck.com  Wed Jun 19 16:43:15 2013
Return-Path: <john-ietf@jck.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 B925121F9EA8 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 16:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level: 
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 MxCa8L+vor3R for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 16:43:10 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D8B5321F9D3F for <ietf@ietf.org>; Wed, 19 Jun 2013 16:43:09 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UpS1s-0002QE-EX; Wed, 19 Jun 2013 19:43:08 -0400
Date: Wed, 19 Jun 2013 19:43:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: IETF, ICANN and non-standards
Message-ID: <ECA5C9D199DED153278C63C2@JcK-HP8200.jck.com>
In-Reply-To: <20130619194338.49286.qmail@joyce.lan>
References: <20130619194338.49286.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: paf@frobbit.se
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, 19 Jun 2013 23:43:15 -0000

--On Wednesday, June 19, 2013 19:43 +0000 John Levine
<johnl@taugh.com> wrote:

>...
> As a concrete example, the EPP systems used in production by
> TLD registries use extensions that are documented only in
> I-Ds, often expired I-Ds, or in dusty I-D like web documents.
> If you look at the applications for new TLDs on the ICANN web
>..
> Assuming we care about stability and interoperability,
> wouldn't it make sense for the IETF to spin up a WG, collect
> these drafts, clean up the language, make sure they agree with
> the widely implemented reality, and publish them?

I hate to put a damper on this sudden enthusiasm, but we
presumably also care about issues of change control and
adoption.    It seems to me that we could reasonably do two
things:

(1) Try to do what you suggest but with the understanding that
those who haven't come to us and said "standardize this" may
still not come... and may not consider that they have any
interest or obligation to conform, long-term, to whatever we
come up with.  I think that gets us Informational documents that
are basically a cleaned-up version of the I-Ds.

(2) At least partially follow the lead of  Joe Abley's comment.
Go to ICANN, suggest that having these commitments in the new
gTLD process depend on I-Ds that are not supposed to be
referenced normatively and might change at any time is not in
the best interest of anyone, especially the best interest of
Internet stabiiity, usability, and interoperability.  See if we
can persuade them to initiate a policy development process that
would require adherence to whatever consensus standards are
developed in this area.  Then, per Joe's comment, let their
staff poll the various actors to find out what they are doing,
be sure that the various implementations are at least intended
to be consistent and get that documented.  Then we work with
them to get the I-Ds updated and to work a process that includes
reviews from those who are actually using and depending on the
specs.  

Seems to me that would both minimize IETF workload and get us a
higher quality and better-vetted set of specs for which there
was actually a committed audience.

   john




From presnick@qti.qualcomm.com  Wed Jun 19 17:10:01 2013
Return-Path: <presnick@qti.qualcomm.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 8B87C21F9EF8 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 17:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 D+H0SK7kCSHh for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 17:09:57 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 65CDC21F9EF6 for <ietf@ietf.org>; Wed, 19 Jun 2013 17:09:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1371686996; x=1403222996; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=HwcliUoaA54B8tSGt/viU3E74O4TBQomFih+Ovw3/hc=; b=O3ln0RXyg+jElkVva1ljDnpdzbZs1wfjno0h5H762KsdOOvmWeU5lDXy wQn20WAvvcBHPpad0xEzuWaBtMw/qgQbV0Cr1I7QbvwHXI5i5ZtLueMmY MmJu+fVErA+poZmdZvezoTdZV5Dooa1NSfoOmKOJMxhBAedKwBdb/4VgT I=;
X-IronPort-AV: E=Sophos;i="4.87,900,1363158000"; d="scan'208";a="57789793"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 19 Jun 2013 17:09:56 -0700
X-IronPort-AV: E=Sophos;i="4.87,900,1363158000"; d="scan'208";a="502676669"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 19 Jun 2013 17:09:56 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 19 Jun 2013 17:09:55 -0700
Message-ID: <51C24851.8040208@qti.qualcomm.com>
Date: Wed, 19 Jun 2013 19:09:53 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im>	<CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com>	<CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com>	<51C14C06.1060207@cs.helsinki.fi>	<CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>	<2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com>	<51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com>	<51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com>	<51C1F592.1060708@dougbarton.us> <51C1F8FF.90100@gmail.com> <51C20AD4.5060807@dougbarton.us>
In-Reply-To: <51C20AD4.5060807@dougbarton.us>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: 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: Thu, 20 Jun 2013 00:10:02 -0000

On 6/19/13 2:47 PM, Doug Barton wrote:
> On 06/19/2013 11:31 AM, Melinda Shore wrote:
>> Even in fields in which the overwhelming majority of
>> practitioners, the majority of people in leadership or
>> management positions are men.
>
> So again, it's not at all clear how that relates to the IETF (given 
> that we don't fall into the category of "the overwhelming majority of 
> practitioners [are women]."

I think the point was that if organizations that have a majority of 
women in the ranks have trouble getting women into leadership roles 
(where one would think, ceterus paribus, women would have an easier time 
moving up as against other organizations), then an organization that has 
a majority male population won't fare much better unless there's some 
reason to believe it is interestingly different.

Institutional biases in organizations are not uncommon. We almost 
certainly have *some* brand of it here, whether it's Americo-centrism 
(cf. SM's comments about Selma and Dan's comments about baseball), or 
one of gender. I'd be (happily) shocked if there were some reason to 
believe that we're different than other organizations when it comes to 
gender, but I haven't seen much to convince me we're all that different. 
Certainly we should look for evidence of the existence and nature of any 
biases that exist in our institutional practices, but given how 
prevalent such biases are elsewhere, I'm not uncomfortable presuming 
prima facia that we do have some and doing some things that might 
(again, surprisingly to me) turn out unnecessary.

> I look at women like Leslie Daigle, Allison Mankin, Margaret 
> Wasserman, Lynn St. Amour, Joyce Reynolds ... those are just off the 
> top of my head; certainly not my intention to slight anyone ... all of 
> whom have now, or have had significant leadership roles, and made 
> lasting impacts on the IETF both in its work product and culture.

As the saying goes, the plural of "anecdote" is not "data", but it might 
be interesting to discuss with each of the people you noted their 
experiences getting into leadership and their experiences in it. 
(However, see the last paragraph of this message below.)

> Can we (and should we) do better? Absolutely. I would love to see more 
> participation by different groups, nationalities, genders, etc. And I 
> have a vested interest here. I have a daughter who is smart as a whip, 
> and when it comes time for her to find a job I want to be sure that 
> every door is open to her.

Agree wholeheartedly.

> But I also think it's possible for us to agree that we have room to 
> improve without constantly banging the drum that we have a deep-seated 
> institutional bias, especially when that point is far from proven.

Even if such a bias does not exist, it can come across a bit 
self-serving to complain about the banging drum. So someone has said 
there is an institutional bias against the (minority and not in 
leadership) group they are in and for the (majority and in leadership) 
group you are in... No use in getting insulted or complaining about the 
words used to express that perception. Looking to make sure that there 
is no bias and addressing any biases you find is a good use of time and 
energy.

>>> ... and while we're on that topic, what are you doing to help?
>>
>> That is truly an unfortunate line of argument, and I hope
>> you don't use it very often.
>
> It's not a "line of argument," it's a legitimate question.

It did sound a bit confrontational in the original message. The MIME 
Intonation Protocol being what it is, this can sometimes be an 
unintended problem. I will take full blame for the lack of deployment of 
that protocol.

> Others have described their actions to help improve the situation, 
> which hopefully still others can latch onto and emulate. You bring a 
> unique perspective to the table, so I'm hoping that you can describe 
> what you're doing to help solve the problem so that others can emulate 
> your example.

That's a reasonable request. People should in general describe 
experiences and volunteer whatever advice they can for the community. 
However, do keep in mind that some things folks might do (especially 
folks in the minority population) are not things that they necessarily 
want to talk about it public. For example, if some folks were helping 
women off-list to deal with incidents of harassment or sexist behavior, 
or simply poor treatment that seemed different than how males were 
treated, they might not feel comfortable talking about that publicly 
because it would bring up some thorny issues that are difficult to 
discuss in private, let alone in public. And there are certainly other 
things of less serious import that are still dicey to lay open in 
public. So it's probably at least a bit pushy to individualize a message 
saying "what are you doing to help?".

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From fred@cisco.com  Wed Jun 19 17:14:28 2013
Return-Path: <fred@cisco.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 194AB21F9F14; Wed, 19 Jun 2013 17:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 vPi6LdH2sgT2; Wed, 19 Jun 2013 17:14:23 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id E232721F9F11; Wed, 19 Jun 2013 17:14:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1785; q=dns/txt; s=iport; t=1371687263; x=1372896863; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=8Doh482jpI+92HSrpPi8aNOtniLkZ+VtABaXG5y4DU8=; b=DVAagMznvVXzKA1vfOqNxw7jPaXpSCB0RFwWBhIlibNGnwC+8Sp0/svR 9Taecgbb0USbIzMZfzAInw0ht6qot3v/9WclQu+28qgkqUI5M3YDXh8o2 ZyUiPwpWRsWDZ4o3QpfZfyMnCOvKodPpq2jg0AjZpsjzqDqJV7Etk3Eke Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnMFAG1IwlGtJV2d/2dsb2JhbABagwkxSb8bgQAWdIIjAQEBAwF5BQsCAQgiJDIlAgQOBQgNBYduBgy7c41/gRACMQeDAGEDiGigHYMPgig
X-IronPort-AV: E=Sophos;i="4.87,900,1363132800"; d="scan'208";a="224838728"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 20 Jun 2013 00:14:22 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r5K0EMYi020330 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 20 Jun 2013 00:14:22 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.004; Wed, 19 Jun 2013 19:14:21 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Aaron Yi DING <yding@cs.helsinki.fi>
Subject: Re: IETF Diversity vs. White Male ??
Thread-Topic: IETF Diversity vs. White Male ??
Thread-Index: AQHObUCKaWBM5IGjeUWnCm2sXIq1X5k+D4YA
Date: Thu, 20 Jun 2013 00:14:21 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B91F405@xmb-rcd-x09.cisco.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1C0E1.8000900@dcrocker.net> <51C1C980.6000606@stpeter.im> <51C1CD95.4060106@innovationslab.net> <EBC640C6-E812-479F-9166-D0AEC941117C@checkpoint.com> <51C2376E.80400@cs.helsinki.fi>
In-Reply-To: <51C2376E.80400@cs.helsinki.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.125]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <BADEA596FC393341829E442022543CF4@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<diversity@ietf.org>" <diversity@ietf.org>, "<ietf@ietf.org>" <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: Thu, 20 Jun 2013 00:14:28 -0000

On Jun 19, 2013, at 3:57 PM, Aaron Yi DING <yding@cs.helsinki.fi> wrote:

> Well, if the dominant ones later being replaced by other groups, do we ne=
ed to revamp again? What will be the end?

I'm told that white babies are now a minority of the population in the US. =
http://www.dailymail.co.uk/news/article-2341066/Whites-soon-minority-Americ=
an-children-age-5.html

It's all about political correctness. It is not politically correct to comm=
ent on women unless you are one and hate men. It is not politically correct=
 to comment on whatever-they're-called-this-week, black, negro, afro-americ=
ans, or whatever. It is not politically correct to comment on hispanics, or=
 to note that they are not a race; they might be a culture, but for the mos=
t part they are people who grew up outside spain but speak - or whose paren=
ts speak - some derivative of spanish as a native language. Or Asians, for =
that matter. But it is absolutely politically correct to make racist and se=
xist remarks - the same remarks that would draw outrage and umbrage if made=
 about any of a list of other groups - about people who happen to be caucas=
ian and male.

A conversation from the 1993 movie Gettysburg comes to mind.=20

Colonel Joshua Lawrence Chamberlain: Tell me something, Buster... What do y=
ou think of Negroes?=20
Sergeant 'Buster' Kilrain: Well, if you mean the race, I don't really know.=
 This is not a thing to be ashamed of. The thing is, you cannot judge a rac=
e. Any man who judges by the group is a pea-wit. You take men one at a time=
.

I would replace "man" or "men" with "person" or "people" in the observation=
, and would agree with it. There are a lot of pea-wits in the world. Some o=
f them are white males. Many are not.=

From john-ietf@jck.com  Wed Jun 19 17:43:14 2013
Return-Path: <john-ietf@jck.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 BC24621F9D19 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 17:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.468
X-Spam-Level: 
X-Spam-Status: No, score=-102.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 QZcWUdo7-jIG for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 17:43:08 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BD7D921F9D14 for <ietf@ietf.org>; Wed, 19 Jun 2013 17:43:08 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UpSxu-0002Xt-Mt; Wed, 19 Jun 2013 20:43:06 -0400
Date: Wed, 19 Jun 2013 20:43:01 -0400
From: John C Klensin <john-ietf@jck.com>
To: Warren Kumari <warren@kumari.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [IETF] Re: IETF,	ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt>	(The Internet Numbers Registry System) to Informational RFC)
Message-ID: <BB52D64B1827B309BF7D9629@JcK-HP8200.jck.com>
In-Reply-To: <C8EEFB02-5637-4247-98F6-3B414E045E0E@kumari.net>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <51C21498.3020008@gmail.com> <C8EEFB02-5637-4247-98F6-3B414E045E0E@kumari.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf <ietf@ietf.org>, =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
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: Thu, 20 Jun 2013 00:43:14 -0000

--On Wednesday, June 19, 2013 17:14 -0400 Warren Kumari
<warren@kumari.net> wrote:

>>> I think this is the correct strategy, BUT, I see as a very
>>> active participant in ICANN (chair of SSAC) that work in
>>> ICANN could be easier if some "more" technical standards
>>> where developed in IETF, 
> 
> + lots.
> 
> If these are not developed in the IETF, we run the risk of
> ICANN doing technical stuff.

Risk of ICANN doing technical stuff?  You mean like the
technical details of the escrow policy and how zones are
supposed to be restored?  Or how about Label Generation Rules
for IDNs?  Or how about the existing policies about registration
data availability and what information is required?

The point, Warren (and others) is that all of these are "ICANN
doing technical stuff" and even "technical standards" in a broad
sense of that term.   Some of it is stuff that the IETF really
should not want to do (I'm tempted to say "avoid like the
plague").  Some of it probably should be here.  As an outsider
to both, there is a certain amount of stuff that has ended up in
SSAC and even RSAC that might have been better located in SAAG
or some IETF or NOG DNS operations group.  I certainly won't
argue that we've got the balance right.  And I think it is
unfortunate that the very early redesign of the original PSO had
the side effect of making it hard or impossible to work out
optimal boundaries and cross-review mechanisms with ICANN and
that we are instead having a discussion more than a dozen years
later about keeping ICANN from doing technical work or making
standards.

Let's not complicate things further by making the assumption
that anything that reasonably looks like "technical stuff"
belongs in the IETF and not in ICANN.  It is likely to just make
having the right conversations even harder.
 
> As someone whose time is now[0] split between ICANN and IETF,
> I can tell you something -- you[1] *really* don't want ICANN
> developing technical standard.

Sorry.  Too late.  The horse left the barn well over a decade
ago, arguably after we opened the door, led it out, and gave it
a good swat.

More broadly, there are lots of organizations I'd rather not
have developing technical standards.  In a few areas, the IETF
might even be on the list.  But stopping them would take not the
usual Protocol Police force, but the IETF Army and I don't know
where to find or how to deploy them.  Perhaps you do.  But, if
not, the best we can do is to try to figure out and describe
realistic boundaries and then try to negotiate, starting with
having good arguments about what should be done where and why.
And we should be really, really, careful about what we wish for
because a lot of the space in which ICANN operates mixes really
protocol issues with Layer 8 and 9 considerations and really
heavy-duty politics.

>> A pre-condition for that is that technical and operational
>> problem statements are formulated, which could be sent to
>> appropriate WGs or used to justify a BOF. If ICANN could
>> focus on that instead of solutionism or committeeism,
>> progress should be possible.

Sure.  Especially if ICANN could actually commit. where
appropriate, to mandate whatever comes out of that process and
then to enforce its mandates.  Of course, I would also like a
pony... or perhaps a stable-full.

> Yup. This message needs to be properly communicated though --

You mean like the requirements for variant aliases communicated
to DNSEXT and other groups?   Or did you have in mind the
registration data requirements that went to CRISP?  Or the more
recent ones that have been handed off to WEIRDS after going
through enough of an ICANN Policy Development Process that we
can be reasonably confident that the requirements are real?

Sorry, but, if we are going to have this conversation, I think
it is very important that we be both real and specific, rather
than engaging in fantasies about how things might work in the
Best of All Possible Worlds or some other alternate reality.

best,
   john


From arturo.servin@gmail.com  Wed Jun 19 19:18:16 2013
Return-Path: <arturo.servin@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 1D45921F9F1D for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 19:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
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 Pa1jCUoFaQ9O for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 19:18:14 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB7121F9EBB for <ietf@ietf.org>; Wed, 19 Jun 2013 19:18:14 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa11so5788939pad.19 for <ietf@ietf.org>; Wed, 19 Jun 2013 19:18:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-forwarded-message-id:content-type; bh=PT/2Sm+uYJBcj/WgTUW/pOi7UrZoQz11jhGkC/BjtoY=; b=LwpU7yX4r852NCbDqOK341Q20HZzcdn3UVwqC2Bc8t2kHPIJMky+LTVhstUkqihABE 6Gq4z8zPefCFeurcerCfIUogZFvQCTABfz+kiarx7J+9rR//DJfkEcEodZ21x4FFrIhI x1oH2bPR5y0ljNRuzsdGDEJvqKRA7882qlYtSLXhhBuloma54Jbpillti24UwH0ROGr0 Rd11Z/xGaboyIf/0sJE5zmzxRo0V4+O3WU4qhKFUl3+SaJ5BaMw/QoXxvjhenrkqOzzX Z8fp5oAoET9tQ6dvY+nh7LybUpmrJmGY/U6RJvzf+TxOwUdZN2ehftU5kwiSFWebx/+o ZGsw==
X-Received: by 10.66.27.44 with SMTP id q12mr9292174pag.138.1371694694373; Wed, 19 Jun 2013 19:18:14 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (110-170-171-184.static.asianet.co.th. [110.170.171.184]) by mx.google.com with ESMTPSA id sq5sm27310799pab.11.2013.06.19.19.18.12 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Jun 2013 19:18:13 -0700 (PDT)
Message-ID: <51C26662.2060904@gmail.com>
Date: Thu, 20 Jun 2013 09:18:10 +0700
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Fwd: [ISOC] Applications open for ISOC Fellowship to IETF 88 (Vancouver)
References: <CDDB7EEA.15A89%conte@isoc.org>
In-Reply-To: <CDDB7EEA.15A89%conte@isoc.org>
X-Forwarded-Message-Id: <CDDB7EEA.15A89%conte@isoc.org>
Content-Type: multipart/mixed; boundary="------------010001040205090603010607"
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: Thu, 20 Jun 2013 02:18:16 -0000

This is a multi-part message in MIME format.
--------------010001040205090603010607
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


	Para los interesados.

Slds
as

-------- Original Message --------
Subject: 	[ISOC] Applications open for ISOC Fellowship to IETF 88
(Vancouver)
Date: 	Mon, 10 Jun 2013 20:02:37 +0000
From: 	Steve Conte <conte@isoc.org>
To: 	isoc-members-announce@elists.isoc.org
<isoc-members-announce@elists.isoc.org>



Dear Colleagues,

The Internet Society has announced that it is inviting applications for
its latest Internet Society Fellowships to the IETF.  The Fellowship
programme allows engineers from emerging and developing economies to
attend an Internet Engineering Task Force (IETF) meeting.

As you know, the IETF is the Internet's premier standards-making body,
responsible for the development of protocols used in IP-based networks.
IETF participants represent an international community of network
designers, operators, vendors, and researchers involved in the technical
operation of the Internet and the continuing evolution of Internet
architecture.

Fellowships will be awarded through a competitive application process.
The Internet Society is currently accepting fellowship applications for
the IETF 88 in Vancouver, Canada:

* IETF 88, November 03-08, 2013, Vancouver, British Columbia, Canada

Information and links to apply can be found at:
http://www.internetsociety.org/fellows-ietf

Fellowship applications are due by 05 July 2013.

I encourage you apply or pass this information about this program to
individuals involved in your network that have a keen interest in the
Internet protocol development activities of the IETF.

The Internet Society Fellowships to the IETF are sponsored by Afilias,
SIDN, Google, Microsoft, and Verisign.

If you have questions, please do not hesitate to contact Steve Conte
<conte@isoc.org>.

Kind Regards,

Steve Conte

-----
Steve Conte
Internet Leadership Programme
The Internet Society
conte@isoc.org




--------------010001040205090603010607
Content-Type: text/plain; charset=UTF-8;
 name="Attached Message Part"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Attached Message Part"

_______________________________________________
To manage your ISOC subscriptions or unsubscribe,
please log into the ISOC Member Portal:
https://portal.isoc.org/
Then choose Interests & Subscriptions from the My Account menu.

--------------010001040205090603010607--

From aservin@lacnic.net  Wed Jun 19 19:54:30 2013
Return-Path: <aservin@lacnic.net>
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 58DDF21F9FE8 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 19:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.426
X-Spam-Level: 
X-Spam-Status: No, score=0.426 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HOST_EQ_STATIC=1.172]
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 gcDWG-DwE4pK for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 19:54:21 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 988E521F9FE4 for <ietf@ietf.org>; Wed, 19 Jun 2013 19:54:21 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (110-170-171-184.static.asianet.co.th [110.170.171.184]) by mail.lacnic.net.uy (Postfix) with ESMTP id 5AB2330847E for <ietf@ietf.org>; Wed, 19 Jun 2013 23:53:57 -0300 (UYT)
Message-ID: <51C26ED1.8080803@lacnic.net>
Date: Thu, 20 Jun 2013 09:54:09 +0700
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Fwd: [ISOC] Applications open for ISOC Fellowship to IETF 88 (Vancouver)
References: <CDDB7EEA.15A89%conte@isoc.org> <51C26662.2060904@gmail.com>
In-Reply-To: <51C26662.2060904@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
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: Thu, 20 Jun 2013 02:54:30 -0000

    Ignore!

    Wrong list. Jetlag.

my apologies,
as




From dougb@dougbarton.us  Wed Jun 19 20:56:29 2013
Return-Path: <dougb@dougbarton.us>
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 BF9A221E8054 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 20:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
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 ZCCH+DJAYdpx for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 20:56:25 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 49AD821E804C for <ietf@ietf.org>; Wed, 19 Jun 2013 20:56:25 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 917C822B13 for <ietf@ietf.org>; Thu, 20 Jun 2013 03:56:23 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1371700583; bh=1KahoL8+jveI+iQxCQTm1PFAqNhBK9IJx9UCMp9Zh0g=; h=Date:From:To:Subject:References:In-Reply-To; b=Jaz3N19hsjO5X/RrQJlfp/q5Xd6YoK02uICMTLLNsbqONgGp5KkIiIWzjNfuLlj4f dk+Uz3ykG/7DBGuGCAdavLt+PzxU7s6d7fQd5ISnr3Dea7sSUE7QZSNY/XHM32c0zL 14ahav4F5p2vWMRgfZE3I54qRk3KILTKLY2plNj4=
Message-ID: <51C27D66.6000509@dougbarton.us>
Date: Wed, 19 Jun 2013 20:56:22 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <51C09437.5040006@stpeter.im>	<CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com>	<CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com>	<51C14C06.1060207@cs.helsinki.fi>	<CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>	<2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com>	<51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com>	<51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com>	<51C1F592.1060708@dougbarton.us> <51C1F8FF.90100@gmail.com> <51C20AD4.5060807@dougbarton.us> <51C24851.8040208@qti.qualcomm.com>
In-Reply-To: <51C24851.8040208@qti.qualcomm.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 20 Jun 2013 03:56:29 -0000

On 06/19/2013 05:09 PM, Pete Resnick wrote:
> On 6/19/13 2:47 PM, Doug Barton wrote:
>> On 06/19/2013 11:31 AM, Melinda Shore wrote:
>>> Even in fields in which the overwhelming majority of
>>> practitioners, the majority of people in leadership or
>>> management positions are men.
>>
>> So again, it's not at all clear how that relates to the IETF (given
>> that we don't fall into the category of "the overwhelming majority of
>> practitioners [are women]."
>
> I think the point was that if organizations that have a majority of
> women in the ranks have trouble getting women into leadership roles
> (where one would think, ceterus paribus, women would have an easier time
> moving up as against other organizations), then an organization that has
> a majority male population won't fare much better unless there's some
> reason to believe it is interestingly different.

Yes, Pete, I understand what the point was supposed to be. The point *I* 
am making is that unless you have a solid understanding of the 2 
populations the comparison is not only at best meaningless, it is almost 
certainly actively harmful because it leads to a short-circuit of the 
very path to understanding that is required to actually address the 
problem. I could count all of the unfounded assumptions you're making 
just in the paragraph above for you, but you're a smart guy, I'm sure 
you can take that on as a side project if you're interested.

> Institutional biases in organizations are not uncommon. We almost
> certainly have *some* brand of it here, whether it's Americo-centrism
> (cf. SM's comments about Selma and Dan's comments about baseball),

So again, there is absolutely zero evidence that those kinds of comments 
are a form of institutional bias. The fact that people use cultural 
references that they are familiar with IS evidence that they are human, 
but you cannot extrapolate from Ted's comment (directed at Melinda who 
Ted had a reasonable belief would be familiar with it) that Ted is de 
facto biased against non-Americans. In fact, one of the things I enjoy 
about working in the I* realm is being exposed to other cultures, and 
learning a bit about their culture, idioms, humor, etc. And $DEITY 
forbid we actually achieve some of that diversity stuff, how are you 
going to react to even MORE people bringing their own cultural 
experience to bear in the IETF?!? The nerve of them!

> or
> one of gender. I'd be (happily) shocked if there were some reason to
> believe that we're different than other organizations when it comes to
> gender,

For the Nth time now, let me be clear that I do not think we have zero 
problems in this area. But "we can improve" is different from "we have a 
widespread and deep-seated problem with institutional bias." More about 
the importance of the distinction below.

> but I haven't seen much to convince me we're all that different.

... remember what you said to me about anecdotes vs. data? :)

> Certainly we should look for evidence of the existence and nature of any
> biases that exist in our institutional practices, but given how
> prevalent such biases are elsewhere, I'm not uncomfortable presuming
> prima facia that we do have some and doing some things that might
> (again, surprisingly to me) turn out unnecessary.

I find this perspective highly disturbing, and potentially very dangerous.

>> I look at women like Leslie Daigle, Allison Mankin, Margaret
>> Wasserman, Lynn St. Amour, Joyce Reynolds ... those are just off the
>> top of my head; certainly not my intention to slight anyone ... all of
>> whom have now, or have had significant leadership roles, and made
>> lasting impacts on the IETF both in its work product and culture.
>
> As the saying goes, the plural of "anecdote" is not "data", but it might
> be interesting to discuss with each of the people you noted their
> experiences getting into leadership and their experiences in it.

Assuming they (and other similar folks) are willing, I agree. Just to be 
clear, I was not volunteering anyone for anything. :)

>> Can we (and should we) do better? Absolutely. I would love to see more
>> participation by different groups, nationalities, genders, etc. And I
>> have a vested interest here. I have a daughter who is smart as a whip,
>> and when it comes time for her to find a job I want to be sure that
>> every door is open to her.
>
> Agree wholeheartedly.
>
>> But I also think it's possible for us to agree that we have room to
>> improve without constantly banging the drum that we have a deep-seated
>> institutional bias, especially when that point is far from proven.
>
> Even if such a bias does not exist, it can come across a bit
> self-serving to complain about the banging drum.

Agreed, which is why I have waited so long to speak up.

> So someone has said
> there is an institutional bias against the (minority and not in
> leadership) group they are in and for the (majority and in leadership)
> group you are in... No use in getting insulted or complaining about the
> words used to express that perception.

Well I'm sorry to say, I actually DO find it insulting. There has been a 
near-constant undercurrent from one person particularly, with ripples 
vibrating through a few other ponds, that the IETF is biased generally; 
and against women particularly. As someone who is part of the 
organization, and worse yet one of those privileged (by the standards of 
many) white (gasp!) males (oh my!) I fall into the category of those 
against whom this accusation is being made, and I don't appreciate it. 
And while I try very hard not to get offended on behalf of other people, 
I personally think the (baseless, to date) accusation is insulting to 
the many people I know in the IETF of all genders, nationalities, etc. 
in whom I have not only never seen a trace of bias, but in fact have 
often seen quite the opposite. Furthermore I think that blanket 
statements of the sort "women cannot get ahead in the I* without 
institutional help" is more than a little insulting to those women who 
have, in fact, been very successful leaders already, in every sense of 
the word.

But I do agree with you about one thing, my hurt feelings (however noble 
they may, or may not be) are essentially meaningless. What I AM 
concerned about though is what the larger negative effect of the 
drum-beating is likely to be. If you want to assume that there is bias, 
go right ahead. I don't really care what your motivation is for 
encouraging outreach and equal opportunity, as long as we're working on 
the same goals.

> Looking to make sure that there
> is no bias and addressing any biases you find is a good use of time and
> energy.

I agree with the latter, I do not agree with the former. If there are 
real examples of bias that are known, they definitely should be 
addressed. If the organization believes that we have a problem, and 
wants to spend precious resources on a proper study to answer that 
question, well, Ok then. However we've already demonstrated that people 
are very bad at extrapolating useful conclusions from anecdotes, I don't 
think encouraging people to do more of that is a useful exercise.

... and it's not for nothing that a couple of people much smarter than 
me have posted some preliminary data analysis that seems to demonstrate 
that the believed bias problem does not exist. I find it interesting 
that their work has been ignored and/or shouted down since it doesn't 
fit the narrative.

>>>> ... and while we're on that topic, what are you doing to help?
>>>
>>> That is truly an unfortunate line of argument, and I hope
>>> you don't use it very often.
>>
>> It's not a "line of argument," it's a legitimate question.
>
> It did sound a bit confrontational in the original message. The MIME
> Intonation Protocol being what it is, this can sometimes be an
> unintended problem. I will take full blame for the lack of deployment of
> that protocol.

... and I will take full blame for not making my purpose more complete. 
I thought it was obvious from context, but I can see how it could have 
been interpreted differently.

>> Others have described their actions to help improve the situation,
>> which hopefully still others can latch onto and emulate. You bring a
>> unique perspective to the table, so I'm hoping that you can describe
>> what you're doing to help solve the problem so that others can emulate
>> your example.
>
> That's a reasonable request. People should in general describe
> experiences and volunteer whatever advice they can for the community.
> However, do keep in mind that some things folks might do (especially
> folks in the minority population) are not things that they necessarily
> want to talk about it public.

Of course.

> For example, if some folks were helping
> women off-list to deal with incidents of harassment or sexist behavior,
> or simply poor treatment that seemed different than how males were
> treated, they might not feel comfortable talking about that publicly
> because it would bring up some thorny issues that are difficult to
> discuss in private, let alone in public. And there are certainly other
> things of less serious import that are still dicey to lay open in
> public. So it's probably at least a bit pushy to individualize a message
> saying "what are you doing to help?".

I see your point, however I really think it should go without saying 
that what you describe above isn't what I was referring to (assuming 
what you're describing is actually occurring at all).

To be totally clear, I'm interested in what the women actively involved 
in the IETF now are doing, have in mind to do, or think should be done 
to encourage more active participation by women; both those who are 
"involved" but not "active" currently, and those who have no current 
association with the IETF at all. As a PWM I would not want to presume 
to tell women how to best get other women involved, I think it's much 
better to hear it from them.

Doug


From medel@globetel.com.ph  Wed Jun 19 21:42:06 2013
Return-Path: <medel@globetel.com.ph>
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 0A5C421E8056 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 21:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.605
X-Spam-Level: 
X-Spam-Status: No, score=-1.605 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RELAY_IS_203=0.994]
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 x6jf0XV5yme6 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 21:42:01 -0700 (PDT)
Received: from smtp02.globetel.com.ph (smtp02.globetel.com.ph [203.177.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id A032E11E80F6 for <ietf@ietf.org>; Wed, 19 Jun 2013 21:41:59 -0700 (PDT)
Received: from exgtbh02.globetel.com ([10.225.208.154]) by smtp02.globetel.com.ph (8.14.4/8.14.4) with ESMTP id r5K4fpDo029445;  Thu, 20 Jun 2013 12:41:53 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.146]) by exgtbh02.globetel.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 20 Jun 2013 12:50:55 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: IETF Diversity
Date: Thu, 20 Jun 2013 12:50:53 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE21E147A4@EXVSGT02.globetel.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24DF0530E7@MX15A.corp.emc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IETF Diversity
Thread-Index: Ac5tBlkwzu0AzOfkQBicP0DKkHKrawAAG2NhABqnvSA=
References: <51C09437.5040006@stpeter.im><CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com><CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com><51C14C06.1060207@cs.helsinki.fi><CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com><2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com><51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com><51C1CD9A.2020004@stpeter.im> <51C1CE67.3020703@gmail.com><51C1D4A5.5070205@stpeter.im>, <51C1D59F.6010608@gmail.com> <F5063677821E3B4F81ACFB7905573F24DF0530E7@MX15A.corp.emc.com>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
X-OriginalArrivalTime: 20 Jun 2013 04:50:55.0481 (UTC) FILETIME=[BFAC8690:01CE6D71]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-06-20_02:2013-06-19, 2013-06-20, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1305240000 definitions=main-1306190325
Cc: 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: Thu, 20 Jun 2013 04:42:06 -0000

Kathleen,
Thanks, well understood  indeed... I hear you.

Medel Ramirez
Globe Telecom, Inc.
Manila , Philippines.
+++++++++++++++++++++++++++


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Moriarty, Kathleen
Sent: Thursday, June 20, 2013 12:11 AM
To: Melinda Shore; Peter Saint-Andre
Cc: ietf@ietf.org
Subject: RE: IETF Diversity

A little earlier in the thread, ways to improve things came up.  I
presented at an international conference in Bangkok this week on the
subject area covered by MILE.  While the focus was intended to be more
on how we can look at the problem space to make faster/more effective
progress, standards will enable some of those activities.  The second
half of the talk provided background on MILE, what we are trying to do
and gave the audience a general challenge as well as had specific
requests for help.  My last slide was on how to engage in the IETF.
Outreach and helping people understand how they can be effective within
the IETF may be useful for other WGs as well and could help improve
diversity.  I had 2 requests following the talk to give the same
presentation at other conferences and will likely do them to assist in
this area as well as to make faster progress (and hopefully drive people
to think about how to share information more effectively.  There are
many opportunities for people to help in this space.=20=20

Best regards,
Kathleen
________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Melinda
Shore [melinda.shore@gmail.com]
Sent: Wednesday, June 19, 2013 12:00 PM
To: Peter Saint-Andre
Cc: ietf@ietf.org
Subject: Re: IETF Diversity

On 6/19/13 7:56 AM, Peter Saint-Andre wrote:
> Why do you believe that my opinions are unexamined? I have been=20
> thinking and reading about social, cultural, and personal change for a

> very long time.

You made an assertion that's at least a little ahistorical, you used it
to support an argument against organizational change, and when I
disagreed you went to the "Let's not talk about it" place.

Melinda

This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.

From kathleen.moriarty@emc.com  Wed Jun 19 22:07:43 2013
Return-Path: <kathleen.moriarty@emc.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 BAC5521E80A5 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 22:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.742
X-Spam-Level: 
X-Spam-Status: No, score=-2.742 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599]
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 v5QJ3shvGRrI for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 22:07:38 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 83D9121E80AA for <ietf@ietf.org>; Wed, 19 Jun 2013 22:07:38 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5K57LE9028983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Jun 2013 01:07:21 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 20 Jun 2013 01:07:06 -0400
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5K575tp010096; Thu, 20 Jun 2013 01:07:06 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub26.corp.emc.com ([10.254.110.182]) with mapi; Thu, 20 Jun 2013 01:07:05 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
Date: Thu, 20 Jun 2013 01:07:01 -0400
Subject: Re: IETF Diversity
Thread-Topic: IETF Diversity
Thread-Index: Ac5tdAFs2Hk+D10zSpSMzogdVHHmcg==
Message-ID: <E01E599A-E78E-41CD-87F8-8502845A2AC7@emc.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <51C1CD9A.2020004@stpeter.im> <51C1CE67.3020703@gmail.com> <51C1D4A5.5070205@stpeter.im> <51C1D59F.6010608@gmail.com> <F5063677821E3B4F81ACFB7905573F24DF0530E7@MX15A.corp.emc.com> <A5AD67DA1ACB9648831FD753485B2BFE21E147A4@EXVSGT02.globetel.com>
In-Reply-To: <A5AD67DA1ACB9648831FD753485B2BFE21E147A4@EXVSGT02.globetel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <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: Thu, 20 Jun 2013 05:07:43 -0000

Thanks, Medel.

I just wanted to clarify that my closing 'in this space' was intended for d=
iversity improvements.  Getting more users, operators, and vendors involved=
 will help.  Having diverse input will help us have better solutions come o=
ut of the WG.

Thanks,
Kathleen=20


Sent from my iPhone

On Jun 20, 2013, at 11:42 AM, "GT RAMIREZ, Medel G." <medel@globetel.com.ph=
> wrote:

> Kathleen,
> Thanks, well understood  indeed... I hear you.
>=20
> Medel Ramirez
> Globe Telecom, Inc.
> Manila , Philippines.
> +++++++++++++++++++++++++++
>=20
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Moriarty, Kathleen
> Sent: Thursday, June 20, 2013 12:11 AM
> To: Melinda Shore; Peter Saint-Andre
> Cc: ietf@ietf.org
> Subject: RE: IETF Diversity
>=20
> A little earlier in the thread, ways to improve things came up.  I
> presented at an international conference in Bangkok this week on the
> subject area covered by MILE.  While the focus was intended to be more
> on how we can look at the problem space to make faster/more effective
> progress, standards will enable some of those activities.  The second
> half of the talk provided background on MILE, what we are trying to do
> and gave the audience a general challenge as well as had specific
> requests for help.  My last slide was on how to engage in the IETF.
> Outreach and helping people understand how they can be effective within
> the IETF may be useful for other WGs as well and could help improve
> diversity.  I had 2 requests following the talk to give the same
> presentation at other conferences and will likely do them to assist in
> this area as well as to make faster progress (and hopefully drive people
> to think about how to share information more effectively.  There are
> many opportunities for people to help in this space. =20
>=20
> Best regards,
> Kathleen
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Melinda
> Shore [melinda.shore@gmail.com]
> Sent: Wednesday, June 19, 2013 12:00 PM
> To: Peter Saint-Andre
> Cc: ietf@ietf.org
> Subject: Re: IETF Diversity
>=20
> On 6/19/13 7:56 AM, Peter Saint-Andre wrote:
>> Why do you believe that my opinions are unexamined? I have been=20
>> thinking and reading about social, cultural, and personal change for a
>=20
>> very long time.
>=20
> You made an assertion that's at least a little ahistorical, you used it
> to support an argument against organizational change, and when I
> disagreed you went to the "Let's not talk about it" place.
>=20
> Melinda
>=20
> This e-mail message (including attachments, if any) is intended for the u=
se of the individual or the entity to whom it is addressed and may contain =
information that is privileged, proprietary, confidential and exempt from d=
isclosure. If you are not the intended recipient, you are notified that any=
 dissemination, distribution or copying of this communication is strictly p=
rohibited. If you have received this communication in error, please notify =
the sender and delete this E-mail message immediately.
>=20

From randy_presuhn@mindspring.com  Wed Jun 19 22:14:05 2013
Return-Path: <randy_presuhn@mindspring.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 D388A21E80A3 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 22:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.979
X-Spam-Level: 
X-Spam-Status: No, score=-100.979 tagged_above=-999 required=5 tests=[AWL=-0.980, BAYES_50=0.001, USER_IN_WHITELIST=-100]
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 5AKiJD5W17u1 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 22:13:59 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 0985921E80A5 for <ietf@ietf.org>; Wed, 19 Jun 2013 22:13:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=FCUDmQc2Mq/ljesaYv62rNARO/JMau3J0X0e68Ec6oRQbg1u+iH5UBg8kPZb+BHY; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.37] (helo=elwamui-karabash.atl.sa.earthlink.net) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1UpXBn-0006QQ-Rk for ietf@ietf.org; Thu, 20 Jun 2013 01:13:43 -0400
Received: from 99.23.162.83 by webmail.earthlink.net with HTTP; Thu, 20 Jun 2013 01:13:43 -0400
Message-ID: <30137519.1371705223642.JavaMail.root@elwamui-karabash.atl.sa.earthlink.net>
Date: Wed, 19 Jun 2013 22:13:43 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: ietf@ietf.org
Subject: Re: IETF Diversity
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888ba196d48fc2e3f0837605637ba0dad9b4f81eb19e434683a350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.37
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.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: Thu, 20 Jun 2013 05:14:05 -0000

Hi -

It seems as though participants in this thread are operating
with different understandings of what constitutes "institutional
bias."  A critical difference is whether *intent* is necessary
for bias to exist.  As I understand it, institutional bias
can exist in the absence of ill intent, and can even be an
unintended consequence of efforts to *reduce* bias.

If something about the way we do business makes it more difficult
for otherwise qualified individuals from some group to participate
at a given level, then we have to admit the possibility that
we have a case of institutional bias.  The available remedies
might be worse than the problem, but we shouldn't fool ourselves
into thinking that we're any better at this stuff than any other
well-meaning bunch of people, and we shouldn't pretend that
privilege doesn't exist, no matter how much that conflicts
with our self-image fantasy of being a meritocracy.  Embracing
an ideal does not mean ignoring reality.

For a hopefully non-controversial example, consider how excessively
idiomatic English, over-reliance on sports metaphors, and obscure
cultural references all serve as barriers to participation.
It doesn't matter whether I intend to exclude anyone through,
for example, my use of long sentences.  But if my long sentences
make it too much harder for others to participate, then I *am*
part of the problem, and need to think about how that effect might
be mitigated.

Randy

From dougb@dougbarton.us  Wed Jun 19 22:32:39 2013
Return-Path: <dougb@dougbarton.us>
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 97A6921E80C3 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 22:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599]
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 HKWS4mqGv2JX for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2013 22:32:33 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id DA3F121E80BD for <ietf@ietf.org>; Wed, 19 Jun 2013 22:32:33 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 993E122B13 for <ietf@ietf.org>; Thu, 20 Jun 2013 05:32:33 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1371706353; bh=7KIWBkzbb6zWQwN+WwT9mvuIMr8fDU/tXDENWVkD06A=; h=Date:From:To:Subject:References:In-Reply-To; b=eB4Ld4mx3VtlA2ktWfTPUV1X7VCOhad1gYcSgWKzPqS/+kAkVJ6H+MdlLLTliFO3t ELMlmOgelLKvLXzEDo2jt0R/PCKCffYgTNAWezkdg38SzcsSSbjEb1eo8JEofttMUF lHZ7wyVXJ1HyyW6IoUiru/k2c8gKQ3qHEQs7YLLk=
Message-ID: <51C293F1.70101@dougbarton.us>
Date: Wed, 19 Jun 2013 22:32:33 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity
References: <30137519.1371705223642.JavaMail.root@elwamui-karabash.atl.sa.earthlink.net>
In-Reply-To: <30137519.1371705223642.JavaMail.root@elwamui-karabash.atl.sa.earthlink.net>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 20 Jun 2013 05:32:39 -0000

On 06/19/2013 10:13 PM, Randy Presuhn wrote:
> Hi -
>
> It seems as though participants in this thread are operating
> with different understandings of what constitutes "institutional
> bias."  A critical difference is whether *intent* is necessary
> for bias to exist.  As I understand it, institutional bias
> can exist in the absence of ill intent, and can even be an
> unintended consequence of efforts to *reduce* bias.

I would disagree with your definition, but that's a minor issue. I don't 
care if you want to call it a "barrier to entry," as you did later in 
your post, bias, or whatever other term is trendy atm. Personally, I 
have been explicitly addressing the issue of intent, which has rather 
strongly been hinted at, if not an accusation directly leveled.

Meanwhile, I personally have said explicitly that we can do better at 
removing the barriers to entry that unquestionably do exist, so one 
wonders what your point may be.

Most importantly however, the reason I think we need to focus more on 
positive actions around outreach and equal opportunity is that by 
focusing on "bias" we run the very real risk of making self-flagellation 
its own goal.

Doug (and its own reward)


From jnc@mercury.lcs.mit.edu  Thu Jun 20 00:12:59 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
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 CAAE021E80D2 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 00:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 nT8kgfHzo059 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 00:12:54 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 4C69C21E80B0 for <ietf@ietf.org>; Thu, 20 Jun 2013 00:12:44 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 8765D18C119; Thu, 20 Jun 2013 03:12:43 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IETF Diversity
Message-Id: <20130620071243.8765D18C119@mercury.lcs.mit.edu>
Date: Thu, 20 Jun 2013 03:12:43 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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: Thu, 20 Jun 2013 07:12:59 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > their work has been ignored and/or shouted down since it doesn't fit
    > the narrative.

The usual fate of those who care more about the data than the herd-meme of the
moment. For a good example of this in action, those who are unfamiliar with
the work of Barbara McClintock should try looking her up. (She actually
stopped publishing because the reception given to her work was so negative.)

(In honour of the thread, I have carefully picked a female example. Is that
being sensitive, or patronizing? Left as an exercise for the reader...)

	Noel

From hartmans@painless-security.com  Thu Jun 20 02:56:35 2013
Return-Path: <hartmans@painless-security.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 288CA11E8116; Thu, 20 Jun 2013 02:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 IlneuKxmBuI6; Thu, 20 Jun 2013 02:56:29 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 4802221F9FFD; Thu, 20 Jun 2013 02:56:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 70C6C20127; Thu, 20 Jun 2013 05:52:31 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPqBf-X0ASKW; Thu, 20 Jun 2013 05:52:31 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 20 Jun 2013 05:52:31 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 75C24807E8; Thu, 20 Jun 2013 05:56:12 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: "Joseph Salowey \(jsalowey\)" <jsalowey@cisco.com>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71298265300@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628D03C96@xmb-rcd-x09.cisco.com>
Date: Thu, 20 Jun 2013 05:56:12 -0400
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628D03C96@xmb-rcd-x09.cisco.com> (Joseph Salowey's message of "Wed, 19 Jun 2013 23:23:03 +0000")
Message-ID: <tsla9mlt8ar.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "abfab@ietf.org" <abfab@ietf.org>, "Black, David" <david.black@emc.com>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <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: Thu, 20 Jun 2013 09:56:35 -0000

I'm fine with this text.
Either with eap-lower-layer as a MUST or the more complex version.

From mirja.kuehlewind@ikr.uni-stuttgart.de  Thu Jun 20 05:30:16 2013
Return-Path: <mirja.kuehlewind@ikr.uni-stuttgart.de>
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 69BBF21F9C10 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 05:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.292
X-Spam-Level: 
X-Spam-Status: No, score=-2.292 tagged_above=-999 required=5 tests=[AWL=0.117,  BAYES_00=-2.599, GB_I_INVITATION=-2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, SARE_RMML_Stock4=1.54]
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 hmhzCJHgFHAJ for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 05:30:11 -0700 (PDT)
Received: from mailsrv.ikr.uni-stuttgart.de (mailsrv.ikr.uni-stuttgart.de [129.69.170.2]) by ietfa.amsl.com (Postfix) with ESMTP id 1207721F9BA9 for <ietf@ietf.org>; Thu, 20 Jun 2013 05:30:10 -0700 (PDT)
Received: from netsrv1.ikr.uni-stuttgart.de (netsrv1-c [10.11.12.12]) by mailsrv.ikr.uni-stuttgart.de (Postfix) with ESMTP id 5F3746010B for <ietf@ietf.org>; Thu, 20 Jun 2013 14:30:09 +0200 (CEST)
Received: from vpn-2-cl195 (vpn-2-cl195 [10.41.21.195]) by netsrv1.ikr.uni-stuttgart.de (Postfix) with ESMTP id 57C14600FB for <ietf@ietf.org>; Thu, 20 Jun 2013 14:30:09 +0200 (CEST)
From: Mirja =?windows-1252?q?K=FChlewind?= <mirja.kuehlewind@ikr.uni-stuttgart.de>
To: ietf@ietf.org
Subject: Re: Reducing Internet Latency Workshop
Date: Thu, 20 Jun 2013 14:30:09 +0200
User-Agent: KMail/1.9.10 (enterprise35 0.20101217.1207316)
References: <29C57024-B48B-4797-9AEE-D654719253C4@isoc.org>
In-Reply-To: <29C57024-B48B-4797-9AEE-D654719253C4@isoc.org>
X-KMail-QuotePrefix: > 
MIME-Version: 1.0
Content-Type: Text/Plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <201306201430.09179.mkuehle@ikr.uni-stuttgart.de>
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: Thu, 20 Jun 2013 12:30:16 -0000

Hi Matt,

I currently writing a position paper but I'm travel tomorrow and over the=20
weekend and am not sure if I will be able to finish the paper today. Is it=
=20
maybe possible to submit the paper a couple days later?

Mirja


On Friday 14 June 2013 10:42:43 Matthew Ford wrote:
> Possibly of interest. (Short) Position paper deadline is 23rd June.
>
> Regards,
> Mat
>
> Workshop on Reducing Internet Latency
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 25 - 26 September 2013
> London, England
>
> Latency tends to have been sacrificed in favour of headline bandwidth in
> the way the Internet has been built. This two-day invitation-only workshop
> aims to galvanise action to fix that. All layers of the stack are in scop=
e.
> Latency is an increasingly important topic for networking researchers and
> Internet practitioners alike. Data from Google, Microsoft, Amazon and
> others indicate that latency increases for interactive Web applications
> result in less usage and less revenue from sales or advertising income.
> Whether trying to provide platforms for Web applications, high-frequency
> stock trading, multi-player online gaming or 'cloud' services of any kind,
> latency is a critical factor in determining end-user satisfaction and the
> success of products in the marketplace. Consequently, latency and variati=
on
> in latency are key performance metrics for services these days.
>
> But latency reduction is not just about increasing revenues for big
> business. Matt Mullenweg of WordPress motivates work on latency reduction
> well when he says, "My theory here is when an interface is faster, you fe=
el
> good. And ultimately what that comes down to is you feel in control. The
> [application] isn=92t controlling me, I=92m controlling it. Ultimately th=
at
> feeling of control translates to happiness in everyone. In order to
> increase the happiness in the world, we all have to keep working on this."
>
> Invitations to attend the workshop will depend on receipt of a position
> paper. In a spirit of co- ordination across the industry, submissions are
> encouraged from developers and network operators as well as the research
> and standards communities.
>
> A wide range of latency related topics are in scope including, but not
> limited to: - surveys of latency across all layers
> - analyses of sources of latency and severity/variability
> - the cost of latency problems to society and the economy, or the value of
> fixing it - principles for latency reduction across the stack
> - solutions to reduce latency, including cross-layer
> - deployment considerations for latency reducing technology
> - benchmarking, accreditation, measurement and market comparison practices
>
> Submissions
> -----------
> This is an invitation-only workshop. Prospective participants must submit
> short (up to 2 pages) position papers outlining their views on a specific
> aspect of the overall scope. The emphasis here is on relevance and brevity
> - you do not need to write a lot of text, just demonstrate that you have
> thought about the problem space and have something interesting to say on
> the topic.
>
> Please send position papers in PDF format to: latency@isoc.org
>
> Participant numbers will be limited to focus on discussion and identifying
> actions rather than slideware. Accepted position papers will be made
> public. A report on the workshop will be published after participants have
> agreed the content. Therefore, it will be possible to state views during
> the workshop without them being publicly attributed.
>
> Important Dates
> ---------------
> Position paper submission deadline: 23 June 2013
> Paper acceptance notification: 28 June 2013
> Workshop dates: 9am, Wednesday 25th =96 5pm, Thursday 26th September 2013
>
> Program committee
> -----------------
> Mat Ford, Internet Society, co-chair
> Bob Briscoe, BT, co-chair
> Gorry Fairhurst, University of Aberdeen
> Arvind Jain, Google
> Jason Livingood, Comcast
> Andrew McGregor, Google
>
> Workshop venue and other details
> --------------------------------
> Venue: Hilton London Paddington Hotel, 146 Praed Street, LONDON W2 1EE, UK
> Registration fee: There is no registration fee for the workshop.
> Recommended accommodation: Hilton London Paddington, registration link wi=
ll
> be supplied to accepted participants.
>
> The workshop is sponsored by the Internet Society, the RITE project, Simu=
la
> Research Labs and the TimeIn project. The Internet Society will host a
> workshop dinner on the Wednesday evening.



From scott.brim@gmail.com  Thu Jun 20 06:34:53 2013
Return-Path: <scott.brim@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 4710221F9BD5 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 06:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 P9DbMatA5Snu for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 06:34:52 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id B538421F9BCD for <ietf@ietf.org>; Thu, 20 Jun 2013 06:34:52 -0700 (PDT)
Received: by mail-ob0-f171.google.com with SMTP id dn14so7217044obc.16 for <ietf@ietf.org>; Thu, 20 Jun 2013 06:34:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=68xDAOzd0IKSNCuQAH/MSsT/fA2jdn+ntDnp5gNTIFs=; b=ToZWN18SiG5bgTxgalK+C09EqMtUck7nXGhKG69mGyyh3TXvhDXsXbwQmlbWiXh6VZ avfgxEdHg1QYjxnoVMKbidv9sj0cL4FTevfFXURFuWTPVbk+UgQuPq6G1VQ24AfFMaSt EX3LoCI06wEKxAsMnkb2XLXa75/zTlKuZEDGraJl76sRWrHzjpQD547Ita2J3o71+Ehi LbzCp7maGFWcoFK1g43eEvetQJTbe/KtnkVPr7giO3WBS+dOjPTYGjPh4wQXdLg3wqAi Oy5rXq+1gyEgZd6tunq6J4sW9bylkNIppNXprfXu7eI+jHfu7+5WOh01C7y1295+Soyt FdHQ==
X-Received: by 10.60.93.196 with SMTP id cw4mr4261471oeb.135.1371735292007; Thu, 20 Jun 2013 06:34:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.97.37 with HTTP; Thu, 20 Jun 2013 06:34:31 -0700 (PDT)
In-Reply-To: <20130620071243.8765D18C119@mercury.lcs.mit.edu>
References: <20130620071243.8765D18C119@mercury.lcs.mit.edu>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 20 Jun 2013 09:34:31 -0400
Message-ID: <CAPv4CP_8vBGHHCWM8bTsMUL0oFZt5tg9JpcA24J1-KZTXj+TTQ@mail.gmail.com>
Subject: Re: IETF Diversity
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary=047d7b33d6cace5a2104df9602bf
Cc: 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: Thu, 20 Jun 2013 13:34:53 -0000

--047d7b33d6cace5a2104df9602bf
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 20, 2013 at 3:12 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu>wrote:

>     > From: Doug Barton <dougb@dougbarton.us>
>
>     > their work has been ignored and/or shouted down since it doesn't fit
>     > the narrative.
>
> The usual fate of those who care more about the data than the herd-meme of
> the
> moment. For a good example of this in action, those who are unfamiliar with
> the work of Barbara McClintock should try looking her up. (She actually
> stopped publishing because the reception given to her work was so
> negative.)
>

But she won huge praise in the end, which says something ultimately good
about the process of science, that it can overcome the shortcomings of its
practitioners.


> (In honour of the thread, I have carefully picked a female example. Is that
> being sensitive, or patronizing?


Yes.

--047d7b33d6cace5a2104df9602bf
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 20, 2013 at 3:12 AM, Noel Chiappa <span dir=3D"ltr">&lt;<a href=
=3D"mailto:jnc@mercury.lcs.mit.edu" target=3D"_blank">jnc@mercury.lcs.mit.e=
du</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">

=A0 =A0 &gt; From: Doug Barton &lt;<a href=3D"mailto:dougb@dougbarton.us">d=
ougb@dougbarton.us</a>&gt;<br>
<br>
=A0 =A0 &gt; their work has been ignored and/or shouted down since it doesn=
&#39;t fit<br>
=A0 =A0 &gt; the narrative.<br>
<br>
The usual fate of those who care more about the data than the herd-meme of =
the<br>
moment. For a good example of this in action, those who are unfamiliar with=
<br>
the work of Barbara McClintock should try looking her up. (She actually<br>
stopped publishing because the reception given to her work was so negative.=
)<br></blockquote><div><br></div><div>But she won huge praise in the end, w=
hich says something ultimately good about the process of science, that it c=
an overcome the shortcomings of its practitioners.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
(In honour of the thread, I have carefully picked a female example. Is that=
<br>
being sensitive, or patronizing?</blockquote><div><br></div><div>Yes.=A0</d=
iv></div>

--047d7b33d6cace5a2104df9602bf--

From ogud@ogud.com  Thu Jun 20 06:39:22 2013
Return-Path: <ogud@ogud.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 1CDC521F9C9A for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 06:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.468
X-Spam-Level: 
X-Spam-Status: No, score=-102.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 SwsZFQx88mGr for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 06:39:17 -0700 (PDT)
Received: from smtp78.ord1c.emailsrvr.com (smtp78.ord1c.emailsrvr.com [108.166.43.78]) by ietfa.amsl.com (Postfix) with ESMTP id 0928E21F9C97 for <ietf@ietf.org>; Thu, 20 Jun 2013 06:39:16 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 93CF31E80F8; Thu, 20 Jun 2013 09:39:16 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp2.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 5E55F1E80FC;  Thu, 20 Jun 2013 09:39:15 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <51C1B235.6020507@bogus.com>
Date: Thu, 20 Jun 2013 09:39:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1508)
Cc: 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: Thu, 20 Jun 2013 13:39:22 -0000

On Jun 19, 2013, at 9:29 AM, joel jaeggli <joelja@bogus.com> wrote:

> Given that this document was revved twice and had it's requested =
status change during IETF last call in response to discussion criticism =
and new contribution I am going to rerun the last call.


I reviewed this version and I think this is a fine document that I =
support.=20
In particular the document goes out of its way to address the issues =
raised in prior=20
IETF last call to the extent possible.=20
The document is going to be the specification of two DNS RRtypes that =
have been allocated via expert review, we (DNS community) want to encore
that any such allocations be published as RFC's for future references.=20=


This document is not a product of any working group.

	Olafur (DNSEXT co-chair)=20


From turners@ieca.com  Thu Jun 20 06:46:15 2013
Return-Path: <turners@ieca.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 C67DE21F9005 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 06:46:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.676
X-Spam-Level: 
X-Spam-Status: No, score=-101.676 tagged_above=-999 required=5 tests=[AWL=-0.566, BAYES_05=-1.11, USER_IN_WHITELIST=-100]
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 IXoUNJZPK+pl for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 06:46:10 -0700 (PDT)
Received: from gateway03.websitewelcome.com (gateway03.websitewelcome.com [74.52.223.144]) by ietfa.amsl.com (Postfix) with ESMTP id ABEA221F9016 for <ietf@ietf.org>; Thu, 20 Jun 2013 06:46:10 -0700 (PDT)
Received: by gateway03.websitewelcome.com (Postfix, from userid 5007) id 29ACB2D915FBA; Thu, 20 Jun 2013 08:46:10 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway03.websitewelcome.com (Postfix) with ESMTP id 17D272D915F5B for <ietf@ietf.org>; Thu, 20 Jun 2013 08:46:10 -0500 (CDT)
Received: from [147.28.0.178] (port=57955 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1UpfBh-0000ct-Py; Thu, 20 Jun 2013 08:46:09 -0500
Message-ID: <51C307A0.70704@ieca.com>
Date: Thu, 20 Jun 2013 22:46:08 +0900
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: jose@ietf.org
Subject: JOSE Virtual Interim 6/17 mixup
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (thunderfish.local) [147.28.0.178]:57955
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 5
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: 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: Thu, 20 Jun 2013 13:46:15 -0000

There was an intent to have a virtual meeting of the JOSE WG on 
2013-06-17.  The announcement never made it to the IETF announce list. 
Because of this that virtual meeting is considered a design team meeting 
and not an official virtual interim meeting.  As such, all output is 
subject to approval, rejection or modification by the WG as a whole. 
The minutes of that design team have been posted here:

http://www.ietf.org/proceedings/interim/2013/06/17/jose/minutes/minutes-interim-2013-jose-2

Note that the next virtual interim was properly announced:
http://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=934&k2=12075&tid=1371735805

spt

From mnot@mnot.net  Thu Jun 20 08:03:39 2013
Return-Path: <mnot@mnot.net>
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 3AB6121F9984 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 08:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_51=0.6, USER_IN_WHITELIST=-100]
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 YfPF8RnZ1Clu for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 08:03:34 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 62CA421F9D65 for <ietf@ietf.org>; Thu, 20 Jun 2013 08:02:21 -0700 (PDT)
Received: from [10.71.2.195] (unknown [63.239.94.10]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 3FA47509B6; Thu, 20 Jun 2013 11:02:18 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Is the IETF is an international organization? (was: IETF Diversity)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net>
Date: Thu, 20 Jun 2013 08:02:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3425E471-1381-4512-9B98-39D6AB023C73@mnot.net>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1508)
Cc: 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: Thu, 20 Jun 2013 15:03:39 -0000

Keep in mind that you're talking to an organisation that believes that =
Vancouver qualifies as "Asia."


On 19/06/2013, at 12:07 PM, SM <sm@resistor.net> wrote:

> Hi Aaron,
> At 11:40 19-06-2013, Aaron Yi DING wrote:
>> Relating to the statement above(I assume Phillip is addressing the US =
Academia), not quite sure are we still discussing the same topic?
>> sorry, I am bit confused ..  since IETF is an international =
organization.
>=20
> I changed the subject line as I am as confused as to whether the IETF =
is an international organization.
>=20
> There was a mention of "First the Civil Rights act, then Selma...  =
;)".  I assume that the act is an Act for the United States of America.  =
Harvard was also mentioned.  I did a quick search and I found out that =
"Harvard University is an American private Ivy League research =
university".
>=20
> Regards,
> -sm=20

--
Mark Nottingham   http://www.mnot.net/




From john-ietf@jck.com  Thu Jun 20 08:17:51 2013
Return-Path: <john-ietf@jck.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 EC69C21F9A7A for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 08:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.478
X-Spam-Level: 
X-Spam-Status: No, score=-102.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hz3spQGJkcAr for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 08:17:33 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DF51A21F8F6D for <ietf@ietf.org>; Thu, 20 Jun 2013 08:17:27 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Upgbx-0004Xk-5Z; Thu, 20 Jun 2013 11:17:21 -0400
Date: Thu, 20 Jun 2013 11:17:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Olafur Gudmundsson <ogud@ogud.com>, joel jaeggli <joelja@bogus.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
Message-ID: <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com>
In-Reply-To: <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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: Thu, 20 Jun 2013 15:17:51 -0000

Olafur,

Based on reviewing the current draft and the handling of my
objections and other of others to the prior ones, I agree that
the document is ready for publication.  

However, I feel a need to comment on one of your observations
below because it seems to lie at the core of why this particular
document took up so much IETF list time and correspondence.
Most of that could have been avoided, IMO, and I think there is
something to be learned from it to which I hope you, the DNSEXT
WG, and Ted (as responsible AD) will pay attention.


--On Thursday, June 20, 2013 09:39 -0400 Olafur Gudmundsson
<ogud@ogud.com> wrote:

> The document is going to be the specification of two DNS
> RRtypes that have been allocated via expert review, we (DNS
> community) want to encore that any such allocations be
> published as RFC's for future references. 

The IETF has historically had strong opinions about change
control, consensus, and the nature of recommendations.
Personally, I hope those opinions will continue and, if
anything, get stronger.

It seems to me that it is reasonable to say "we want a
lightweight registration procedure that imposes few if any
requirements on allocating an RR TYPE" or you can say "want to
ensure RFC publication" but that you don't get to say both at
once, especially when Standards Track or the IETF Stream are
involved.  If you (and DNSECT) want the very lightweight
registration procedure, then you should reasonably expect to
make sure that any documents are clearly informational (in
content and category) and to take your chances about
publication: Informational in either the IETF Stream or the
Independent Submission Stream could result in a "no" answer or,
more likely, requirements to justify the design decisions behind
the RRTYPEs as a condition of publication.  You can't "ensure"
anything because the relevant groups really do get to evaluate
both document quality and appropriateness for use.

By contrast, if the WG really does "want to ensure..." then it
would be appropriate to change the registration procedure so
that the I-Ds are posted and RFC publication is agreed to before
the RRTYPEs are registered so everyone can be sure that the two
match.    That could be coupled with some sort of provisional
arrangement while document review is in progress, if the WG
thought that was necessary.   Howver the bottom line, IMO, is
that, if you want RFCs and want those RFCs to accurately
describe an RRTYPE and there is going to be open review during
the RFC development process, you can't have lightweight
registration and then insist that an RFC be published to
match... at least IMO and, if the discussions of the recent Last
Calls are indicative, a significant part of the the community
may share that view.

So some review of the DNSEXT-specified procedures and
expectations may be in order.

regards,
   john


From david.black@emc.com  Thu Jun 20 05:32:39 2013
Return-Path: <david.black@emc.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 6EC1E21F9C02; Thu, 20 Jun 2013 05:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 ZZZcakcQMArg; Thu, 20 Jun 2013 05:32:34 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9929F21F9BFF; Thu, 20 Jun 2013 05:32:34 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5KCWW9l005691 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Jun 2013 08:32:33 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 20 Jun 2013 08:32:13 -0400
Received: from mxhub33.corp.emc.com (mxhub33.corp.emc.com [10.254.93.81]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5KCW1eU006337; Thu, 20 Jun 2013 08:32:12 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub33.corp.emc.com ([::1]) with mapi; Thu, 20 Jun 2013 08:32:02 -0400
From: "Black, David" <david.black@emc.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
Date: Thu, 20 Jun 2013 08:32:00 -0400
Subject: RE: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQAAClxl4P//t2GAgAA80uCAAbNjgP//eC/w
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71298265674@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71298265300@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628D03C96@xmb-rcd-x09.cisco.com>
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628D03C96@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8D3D17ACE214DC429325B2B98F3AE71298265674MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 20 Jun 2013 09:11:35 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <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: Thu, 20 Jun 2013 12:32:40 -0000

--_000_8D3D17ACE214DC429325B2B98F3AE71298265674MX15Acorpemccom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I think this is ok, but my email client isn't distinguishing the new vs. ol=
d text.

If it's just changes to produce this new bullet, I have a small edit:

o Channel binding MUST be used for all application authentication.
The EAP server MUST either require that the correct EAP lower-layer
attribute or another attribute indicating the purpose of the authentication
be present in the channel binding data for application authentication.

"MUST either require that" --> "MUST require that either"

Thanks,
--David

From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]
Sent: Wednesday, June 19, 2013 7:23 PM
To: Black, David
Cc: stefan.winter@restena.lu; General Area Review Team; abfab@ietf.org; iet=
f@ietf.org
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03

Thanks for the text,  some revision to address
On Jun 18, 2013, at 12:34 PM, "Black, David" <david.black@emc.com<mailto:da=
vid.black@emc.com>> wrote:


[Joe] Good points, the text can be more specific:

"In environments where EAP is used for purposes other than network access
authentication all EAP servers MUST enforce channel bindings.  For applicat=
ion
authentication, the EAP server MUST require that the correct EAP lower-laye=
r
attribute be present in the channel binding data.   For network access
authentication, the EAP server MUST require that if channel bindings are
present they MUST contain the correct EAP lower-layer attribute.   All netw=
ork
access EAP peer implementations SHOULD use channel bindings including the E=
AP
lower-layer attribute to explicitly identify the reason for authentication.
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r
attribute to prevent confusion with network access usage. "

This is looking good, modulo Sam's comment on EAP lower-layer vs. something
else that I'll leave to you and he to sort out.  I have a suggested rewrite=
,
mostly to clarify MUST vs. SHOULD requirements for support vs. usage, and
to reformat into a structured bullet list of requirements (this is not
intended to change any requirements from what you wrote):

"In environments where EAP is used for purposes other than network access
authentication:

o All EAP servers and all application access EAP peers MUST
support channel bindings.  All network access EAP peers
SHOULD support channel bindings.

o Channel binding MUST be used for all application authentication.
The EAP server MUST require that the correct EAP lower-layer
attribute be present in the channel binding data for
application authentication.


o Channel binding MUST be used for all application authentication.

The EAP server MUST either require that the correct EAP lower-layer

attribute or another attribute indicating the purpose of the authentication
be present in the channel binding data for application authentication.



o Channel binding SHOULD be used for all network access authentication,
and when channel binding data is present, the EAP server MUST
require that it contain the correct EAP lower-layer attribute
to explicitly identify the reason for authentication.

o Any new usage of EAP MUST use channel bindings including the
EAP lower-layer attribute to prevent confusion with network
access usage.

Thanks,
--David



-----Original Message-----
From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com<http://cisco.com=
>]
Sent: Tuesday, June 18, 2013 1:47 PM
To: Black, David
Cc: stefan.winter@restena.lu<mailto:stefan.winter@restena.lu>; General Area=
 Review Team; abfab@ietf.org<mailto:abfab@ietf.org>;
ietf@ietf.org<mailto:ietf@ietf.org>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03



I think we could state this a bit better as something like:

"In environments where EAP is used for applications authentication and netw=
ork
access authentication all EAP servers MUST understand channel bindings and
require that application bindings MUST be present in application
authentication and that application bindings MUST be absent in network
authentication.   All network access EAP peer implementations SHOULD suppor=
t
channel binding to explicitly identify the reason for authentication.  Any =
new
usage of EAP MUST support channel bindings to prevent confusion with networ=
k
access usage. "

That text is an improvement, and it's headed in the same direction as Sam's
comment - "application bindings MUST be present in application authenticati=
on"
is a "MUST use" requirement, not just a "MUST implement" requirement.

OTOH, I'm not clear on what "application bindings" means, as that term's no=
t
in the current draft.  Specifically, I'm a bit unclear on "application bind=
ings
MUST be absent in network authentication" - does that mean that channel
binding must be absent, or that channel binding is optional, but if channel
binding is present, it MUST NOT be an "application binding", whatever that
is?



[Joe] Good points, the text can be more specific:

"In environments where EAP is used for purposes other than network access
authentication all EAP servers MUST enforce channel bindings.  For applicat=
ion
authentication, the EAP server MUST require that the correct EAP lower-laye=
r
attribute be present in the channel binding data.   For network access
authentication, the EAP server MUST require that if channel bindings are
present they MUST contain the correct EAP lower-layer attribute.   All netw=
ork
access EAP peer implementations SHOULD use channel bindings including the E=
AP
lower-layer attribute to explicitly identify the reason for authentication.
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r
attribute to prevent confusion with network access usage. "

Does this help?

Thanks,

Joe



--_000_8D3D17ACE214DC429325B2B98F3AE71298265674MX15Acorpemccom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: space;-webkit=
-line-break: after-white-space'><div class=3DWordSection1><p class=3DMsoNor=
mal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>=
I think this is ok, but my email client isn&#8217;t distinguishing the new =
vs. old text.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cour=
ier New";color:black'>If it&#8217;s just changes to produce this new bullet=
, I have a small edit:<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fam=
ily:"Courier New";color:black'>o Channel binding MUST be used for all appli=
cation authentication.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'm=
argin-left:.5in'><span style=3D'font-size:10.0pt;font-family:"Courier New";=
color:black'>The EAP server MUST either require that the correct EAP lower-=
layer<br>attribute or another attribute indicating the purpose of the authe=
ntication<o:p></o:p></span></p><p class=3DMsoNormal style=3D'text-indent:.5=
in'><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>=
be present in the channel binding data for&nbsp;application authentication.=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;=
font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'>&#8220;MUST either require that&#8221; --&gt; &#8220;MUST require =
that either&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p><=
/span></p><div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New";color:black'>Thanks,<br>--David</span><span style=
=3D'font-size:11.0pt;font-family:"Courier New";color:black'><o:p></o:p></sp=
an></p></div></div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><div style=
=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><di=
v><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0i=
n 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;=
font-family:"Tahoma","sans-serif"'> Joseph Salowey (jsalowey) [mailto:jsalo=
wey@cisco.com] <br><b>Sent:</b> Wednesday, June 19, 2013 7:23 PM<br><b>To:<=
/b> Black, David<br><b>Cc:</b> stefan.winter@restena.lu; General Area Revie=
w Team; abfab@ietf.org; ietf@ietf.org<br><b>Subject:</b> Re: [abfab] Gen-AR=
T review of draft-ietf-abfab-eapapplicability-03<o:p></o:p></span></p></div=
></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thank=
s for the text, &nbsp;some revision to address&nbsp;<o:p></o:p></p><div><di=
v><p class=3DMsoNormal>On Jun 18, 2013, at 12:34 PM, &quot;Black, David&quo=
t; &lt;<a href=3D"mailto:david.black@emc.com">david.black@emc.com</a>&gt; w=
rote:<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><bloc=
kquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p class=3DMsoNormal>=
[Joe] Good points, the text can be more specific:<br><br>&quot;In environme=
nts where EAP is used for purposes other than network access<br>authenticat=
ion all EAP servers MUST enforce channel bindings. &nbsp;For application<br=
>authentication, the EAP server MUST require that the correct EAP lower-lay=
er<br>attribute be present in the channel binding data. &nbsp;&nbsp;For net=
work access<br>authentication, the EAP server MUST require that if channel =
bindings are<br>present they MUST contain the correct EAP lower-layer attri=
bute. &nbsp;&nbsp;All network<br>access EAP peer implementations SHOULD use=
 channel bindings including the EAP<br>lower-layer attribute to explicitly =
identify the reason for authentication.<br>Any new usage of EAP MUST use ch=
annel bindings including the EAP lower-layer<br>attribute to prevent confus=
ion with network access usage. &quot;<o:p></o:p></p></blockquote><p class=
=3DMsoNormal><br>This is looking good, modulo Sam's comment on EAP lower-la=
yer vs. something<br>else that I'll leave to you and he to sort out. &nbsp;=
I have a suggested rewrite,<br>mostly to clarify MUST vs. SHOULD requiremen=
ts for support vs. usage, and<br>to reformat into a structured bullet list =
of requirements (this is not<br>intended to change any requirements from wh=
at you wrote):<br><br>&quot;In environments where EAP is used for purposes =
other than network access<br>authentication:<br><br>o All EAP servers and a=
ll application access EAP peers MUST<br>support channel bindings. &nbsp;All=
 network access EAP peers<br>SHOULD support channel bindings.<br><br>o Chan=
nel binding MUST be used for all application authentication.<br>The EAP ser=
ver MUST require that the correct EAP lower-layer<br>attribute be present i=
n the channel binding data for<br>application authentication.<o:p></o:p></p=
><div><p class=3DMsoNormal><span style=3D'color:#0F61C8'><br><br></span><o:=
p></o:p></p><p class=3DMsoNormal>o Channel binding MUST be used for all app=
lication authentication.<br><br><o:p></o:p></p><p class=3DMsoNormal>The EAP=
 server MUST either require that the correct EAP lower-layer<br><br><o:p></=
o:p></p><p class=3DMsoNormal>attribute or another attribute indicating the =
purpose of the authentication<o:p></o:p></p></div><div><p class=3DMsoNormal=
>be present in the channel binding data for&nbsp;application authentication=
.<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><p class=
=3DMsoNormal><br>o Channel binding SHOULD be used for all network access au=
thentication,<br>and when channel binding data is present, the EAP server M=
UST<br>require that it contain the correct EAP lower-layer attribute<br>to =
explicitly identify the reason for authentication.<br><br>o Any new usage o=
f EAP MUST use channel bindings including the<br>EAP lower-layer attribute =
to prevent confusion with network<br>access usage.<br><br>Thanks,<br>--Davi=
d<br><br><br><br><o:p></o:p></p><p class=3DMsoNormal>-----Original Message-=
----<br>From: Joseph Salowey (jsalowey) [mailto:jsalowey@<a href=3D"http://=
cisco.com">cisco.com</a>]<br>Sent: Tuesday, June 18, 2013 1:47 PM<br>To: Bl=
ack, David<br>Cc: <a href=3D"mailto:stefan.winter@restena.lu">stefan.winter=
@restena.lu</a>; General Area Review Team; <a href=3D"mailto:abfab@ietf.org=
">abfab@ietf.org</a>;<br><a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>=
<br>Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicabilit=
y-03<br><br><br><o:p></o:p></p><blockquote style=3D'margin-top:5.0pt;margin=
-bottom:5.0pt'><p class=3DMsoNormal><br>I think we could state this a bit b=
etter as something like:<br><br>&quot;In environments where EAP is used for=
 applications authentication and network<br>access authentication all EAP s=
ervers MUST understand channel bindings and<br>require that application bin=
dings MUST be present in application<br>authentication and that application=
 bindings MUST be absent in network<br>authentication. &nbsp;&nbsp;All netw=
ork access EAP peer implementations SHOULD support<br>channel binding to ex=
plicitly identify the reason for authentication. &nbsp;Any new<br>usage of =
EAP MUST support channel bindings to prevent confusion with network<br>acce=
ss usage. &quot;<o:p></o:p></p></blockquote><p class=3DMsoNormal><br>That t=
ext is an improvement, and it's headed in the same direction as Sam's<br>co=
mment - &quot;application bindings MUST be present in application authentic=
ation&quot;<br>is a &quot;MUST use&quot; requirement, not just a &quot;MUST=
 implement&quot; requirement.<br><br>OTOH, I'm not clear on what &quot;appl=
ication bindings&quot; means, as that term's not<br>in the current draft. &=
nbsp;Specifically, I'm a bit unclear on &quot;application bindings<br>MUST =
be absent in network authentication&quot; - does that mean that channel<br>=
binding must be absent, or that channel binding is optional, but if channel=
<br>binding is present, it MUST NOT be an &quot;application binding&quot;, =
whatever that<o:p></o:p></p><p class=3DMsoNormal>is?<br><br><o:p></o:p></p>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal style=3D'mar=
gin-bottom:12.0pt'><br>[Joe] Good points, the text can be more specific:<br=
><br>&quot;In environments where EAP is used for purposes other than networ=
k access<br>authentication all EAP servers MUST enforce channel bindings. &=
nbsp;For application<br>authentication, the EAP server MUST require that th=
e correct EAP lower-layer<br>attribute be present in the channel binding da=
ta. &nbsp;&nbsp;For network access<br>authentication, the EAP server MUST r=
equire that if channel bindings are<br>present they MUST contain the correc=
t EAP lower-layer attribute. &nbsp;&nbsp;All network<br>access EAP peer imp=
lementations SHOULD use channel bindings including the EAP<br>lower-layer a=
ttribute to explicitly identify the reason for authentication.<br>Any new u=
sage of EAP MUST use channel bindings including the EAP lower-layer<br>attr=
ibute to prevent confusion with network access usage. &quot;<br><br>Does th=
is help?<br><br>Thanks,<br><br>Joe<o:p></o:p></p><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div=
></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE71298265674MX15Acorpemccom_--

From nomcom-chair-2013@ietf.org  Wed Jun 19 15:14:23 2013
Return-Path: <nomcom-chair-2013@ietf.org>
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 1798921F9E9C; Wed, 19 Jun 2013 15:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[BAYES_50=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 4+p5FHZxmGoV; Wed, 19 Jun 2013 15:14:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7030821F9E8D; Wed, 19 Jun 2013 15:14:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: NomCom Chair 2013 <nomcom-chair-2013@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: NOMCOM 2013 - UPDATE of validated volunteers list so far
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130619221422.22392.12062.idtracker@ietfa.amsl.com>
Date: Wed, 19 Jun 2013 15:14:22 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: nomcom-chair-2013@ietf.org
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: Thu, 20 Jun 2013 16:26:12 -0000

Below is the current validated list of volunteers for Nomcom
2013.  If your name has a *, I'm waiting for a message back
from you.

Big thanks to everyone who has volunteered!

Now what are the rest of you waiting for?

We still need quite a few to get up to 200 volunteers.
Please reply and volunteer - include in the email: your
First Name, Last Name, email addresses you've used in the
last few years in registering for IETF meetings, preferred
email address, primary affiliation, and a contact phone
number for use if you're selected.

Thanks, =


Allison Mankin
Nomcom 2013 Chair


1 John Scudder
2 Stephen Hanna
3 Wassim Haddad
4 Russ White
5 Stephan Wenger
6 ZHAO Yi
7 Eric Gray
8 Steve Kent
9 Toerless Eckert
10 Alia Atlas
11 Victor Kuarsingh
12 Yizhou LI
13 Gonzalo Salgueiro
14 Gang CHEN
15 Ning KONG
16 Marcelo Bagnulo
17 SHEN Shuo =E6=B2=88=E7=83=81 (Sean)
18 Fernando Gont
19 Glen Zorn
20 Reinaldo Penno
21 Klaas Wierenga
22 Pascal Thubert
23 Mehmet Ersue
24 Ole Troan
25 Jouni Korhonen
26 Giles Heron
27 Gunter Van de Velde
28 Arturo Servin
29 Eric Vyncke
30 Cullen Jennings
31 Tina Tsou
32 Dhruv Dhody
33 Hongyu LI (Julio)
34 Scott Mansfield
35 John Drake
36 Andrew McLachlan
37 Derek Atkins
38 Suhas Nandakumar
39 Eric Rescorla
40 Karen Seo
41 Stig Venaas
42 Stan Ratliff
43 Ignas Bagdonas
44 Peter Yee
45 Donald Eastlake
46 ZHOU Qian (Cathy)
47 Sam Hartman
48 Lixia Zhang
49 Teemu Savolainen
50 Alvaro Retana
51 Terry Manderson
52 Bill VerSteeg
53 Melinda Shore
54 IJsbrand Wijnands
55 Karen O'Donoghue
56 Benson Schliesser
57 Ari Ker=C3=A4nen
58 Fangwei HU
59 Mach CHEN
60 Hui Deng
61 LIU Dapeng
62 Jaap Akkerhuis
63 Magnus Westerlund
64 Zehn CAO
65 Zaheduzzaman Sarker
66 Bhumip Khasnabish
67 Andrew Chi
68 Thomas Nadeau
69 Steven C (Craig) Whilte
70 Orit Levin
71 Sam Aldrin
72 Paul Ebersman
73 Christopher Liljenstolpe
74 Uma Chunduri
75 Suresh Krishnan
76 Varun Singh
77 Ron Bonica
78 Bill (William) Manning
79 Radia Perlman
80 Daniele Ceccarelli
81 Deborah Brungard
82 Kostas Pentikousis
83 Gregory Mirsky
84 Dave Sinicrope
85 Thomas Walsh
86 Zhaohui (Jeffrey) ZHANG
87 Xian ZHANG
88 Mark Townsley
89 Hannes Gredler
90 Brian Trammell
91 Carlos Martinez
92 Peter Koch
93 Daniel Migault
94 Yi (Aaron) Ding
95 Michael Richardson
96 Sohel Khan
97 John Bradley
98 Huaimo Chen
99 Matthew Campagna
100 Keith Drage
101 Chris Bowers
102 Jakob Heitz
103 Tomofumi Okubo
104 Emil Ivov
105 Timothy B. Terriberry
106 JIANG Yuanlong
107 Luigi Iannone
108 Damien Saucez
109 Lou Berger
110 Yana Stamcheva
111 Ond=C5=99ej Sur=C3=BD
112 Marcin Pilarski
113 Michael StJohns
114 Wes George
115 Christian O'Flaherty
116 Uwe Rauschenbach
117 Olafur Gudmundsson
118 Shwetha Subray Bhandari*
119 Tobias Gondrom
120 Christer Holmberg
121 Susan Hares
122 Kiran Kumar Chittimaneni
123 Donald Fedyk
124 Stephen Botzko*
125 Li Xue*
126 John Sauer*

From ajs@anvilwalrusden.com  Thu Jun 20 09:36:27 2013
Return-Path: <ajs@anvilwalrusden.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 A1BB721F9B5C for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 09:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 qCKWUeKyfYic for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 09:36:14 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 378B121F9920 for <ietf@ietf.org>; Thu, 20 Jun 2013 09:36:14 -0700 (PDT)
Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 72DDC8A031 for <ietf@ietf.org>; Thu, 20 Jun 2013 16:36:13 +0000 (UTC)
Date: Thu, 20 Jun 2013 12:36:12 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
Message-ID: <20130620163611.GB41900@mx1.yitter.info>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com> <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
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: Thu, 20 Jun 2013 16:36:27 -0000

On Thu, Jun 20, 2013 at 11:17:16AM -0400, John C Klensin wrote:
 
> So some review of the DNSEXT-specified procedures and
> expectations may be in order.

I encourage you, then, to organize the BOF session that will spin up
the WG to achieve this.  DNSEXT is only still alive because our last
document hasn't been published.

But more generally, as a practical matter it is better that people
register their stuff with us than that they don't.  We have, in the
wild, a used EDNS0 option code that is all over the Internet.  It is
undocumented, and the code point isn't actually registered.  That
state of affairs is surely worse than that the IETF didn't get to
provide good advice to authors.  DNSEXT already tried to be the DNS
cops, and has failed miserably, partly because of the usual
get-off-my-lawn crowd and partly because people unfamiliar with the
IETF find its procedures a little arcane.

My view is that we need to be more pragmatic.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From dougb@dougbarton.us  Thu Jun 20 10:05:02 2013
Return-Path: <dougb@dougbarton.us>
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 C8E8D21F9ECB for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
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 jSBiSsxpefWd for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:04:57 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 8879821F9EC9 for <ietf@ietf.org>; Thu, 20 Jun 2013 10:04:57 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 4B6E522B6A for <ietf@ietf.org>; Thu, 20 Jun 2013 17:04:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1371747895; bh=VcaU3+KIU571PMtychC89fjBrpuHTuA5pe1TM1qrdKk=; h=Date:From:To:Subject:References:In-Reply-To; b=Y6kvF0Dp91sXXnSu4H8YUllCOnr0VUYlcUXzclbRtDI802tLPAaDI35C0Pdy1vJCt GjpvMf8gYGspiaYN6PW4Btqij+rE34orcqAe+PQwA+pLjPjdK0CNmnvO/V2LrUNA1M v2ozo5IPbrldHfBtOwFwkLZj8ptCA1u2TGP6vrfY=
Message-ID: <51C33636.2040104@dougbarton.us>
Date: Thu, 20 Jun 2013 10:04:54 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com> <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com> <20130620163611.GB41900@mx1.yitter.info>
In-Reply-To: <20130620163611.GB41900@mx1.yitter.info>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 20 Jun 2013 17:05:02 -0000

On 06/20/2013 09:36 AM, Andrew Sullivan wrote:
> On Thu, Jun 20, 2013 at 11:17:16AM -0400, John C Klensin wrote:
>
>> So some review of the DNSEXT-specified procedures and
>> expectations may be in order.
>
> I encourage you, then, to organize the BOF session that will spin up
> the WG to achieve this.  DNSEXT is only still alive because our last
> document hasn't been published.
>
> But more generally, as a practical matter it is better that people
> register their stuff with us than that they don't.  We have, in the
> wild, a used EDNS0 option code that is all over the Internet.  It is
> undocumented, and the code point isn't actually registered.  That
> state of affairs is surely worse than that the IETF didn't get to
> provide good advice to authors.  DNSEXT already tried to be the DNS
> cops, and has failed miserably, partly because of the usual
> get-off-my-lawn crowd and partly because people unfamiliar with the
> IETF find its procedures a little arcane.
>
> My view is that we need to be more pragmatic.

I agree with at least a little of what each of Olafur, John, and Andrew 
have said; but I think there's a middle ground between "throw the doors 
wide open" and "everything we have tried before didn't work." At least I 
hope there is.

Perhaps we could have a non-WG mailing list so that people could submit 
proposals for review prior to the expert review process. Even some of 
the "get off my lawn" crowd offered good suggestions for this EUI case 
(make 1 record with a size field rather than 2 records) that could have 
made this whole process a lot smoother.

Doug


From Ted.Lemon@nominum.com  Thu Jun 20 10:10:30 2013
Return-Path: <Ted.Lemon@nominum.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 2DC5221F9E3E for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.601
X-Spam-Level: 
X-Spam-Status: No, score=-106.601 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 48fT+9k0hXTc for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:10:21 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id BD71B21F9D30 for <ietf@ietf.org>; Thu, 20 Jun 2013 10:10:21 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKUcM3fdxTRGbR86YkvP04H8m+Oh27SMP2@postini.com; Thu, 20 Jun 2013 10:10:21 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 584371B80D8 for <ietf@ietf.org>; Thu, 20 Jun 2013 10:10:21 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4D68A19005D; Thu, 20 Jun 2013 10:10:21 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Thu, 20 Jun 2013 10:10:21 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource	Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
Thread-Topic: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource	Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
Thread-Index: AQHObdhdqMBwr1nU6UKUzsJ1CVzyUJk/S70A
Date: Thu, 20 Jun 2013 17:10:20 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751E3376@mbx-01.win.nominum.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com> <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com> <20130620163611.GB41900@mx1.yitter.info> <51C33636.2040104@dougbarton.us>
In-Reply-To: <51C33636.2040104@dougbarton.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5B390800AC0F2B468D26548AB72981A7@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <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: Thu, 20 Jun 2013 17:10:31 -0000

On Jun 20, 2013, at 1:04 PM, Doug Barton <dougb@dougbarton.us> wrote:
> Perhaps we could have a non-WG mailing list so that people could submit p=
roposals for review prior to the expert review process. Even some of the "g=
et off my lawn" crowd offered good suggestions for this EUI case (make 1 re=
cord with a size field rather than 2 records) that could have made this who=
le process a lot smoother.

You mean like "namedroppers"?


From joelja@bogus.com  Thu Jun 20 10:14:17 2013
Return-Path: <joelja@bogus.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 02E1021F9E24 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hKCkFrQMC-TC for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:14:16 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7A25C21F9E06 for <ietf@ietf.org>; Thu, 20 Jun 2013 10:14:16 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r5KHEEEO080999 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 20 Jun 2013 17:14:14 GMT (envelope-from joelja@bogus.com)
Message-ID: <51C33862.6000105@bogus.com>
Date: Thu, 20 Jun 2013 10:14:10 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<51C1B235.6020507@bogus.com>	<E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com>	<FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com>	<20130620163611.GB41900@mx1.yitter.info> <51C33636.2040104@dougbarton.us>
In-Reply-To: <51C33636.2040104@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 20 Jun 2013 17:14:14 +0000 (UTC)
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: Thu, 20 Jun 2013 17:14:17 -0000

On 6/20/13 10:04 AM, Doug Barton wrote:
>
> I agree with at least a little of what each of Olafur, John, and 
> Andrew have said; but I think there's a middle ground between "throw 
> the doors wide open" and "everything we have tried before didn't 
> work." At least I hope there is.
>
Well recall that we still have DNSOP, which along with the dnsext 
mailing list once the wg is closed is probably a reasonable place to 
get/look for feedback.
> Perhaps we could have a non-WG mailing list so that people could 
> submit proposals for review prior to the expert review process. Even 
> some of the "get off my lawn" crowd offered good suggestions for this 
> EUI case (make 1 record with a size field rather than 2 records) that 
> could have made this whole process a lot smoother.
My impression of the outcome of the procedure change for the registry is 
the wg didn't feel that there should be any particular obstacle  beyond 
expert review for registration. It is possible that reasonable people 
should disagree on the application of given rr-types and that they 
should be registered anyway.

In 30 years we've allocated ~120 rrtypes most of which we don't use   
anymore.
>
> Doug
>


From ajs@anvilwalrusden.com  Thu Jun 20 10:27:34 2013
Return-Path: <ajs@anvilwalrusden.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 D54FF21F9D12 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 6N2bN5xThCmv for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:27:29 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 873BE21F9D1C for <ietf@ietf.org>; Thu, 20 Jun 2013 10:27:07 -0700 (PDT)
Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id A4D638A031 for <ietf@ietf.org>; Thu, 20 Jun 2013 17:27:06 +0000 (UTC)
Date: Thu, 20 Jun 2013 13:27:05 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
Message-ID: <20130620172705.GE41900@mx1.yitter.info>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com> <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com> <20130620163611.GB41900@mx1.yitter.info> <51C33636.2040104@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51C33636.2040104@dougbarton.us>
User-Agent: Mutt/1.5.21 (2010-09-15)
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: Thu, 20 Jun 2013 17:27:35 -0000

On Thu, Jun 20, 2013 at 10:04:54AM -0700, Doug Barton wrote:

> Perhaps we could have a non-WG mailing list so that people could
> submit proposals for review prior to the expert review process.

The WG list isn't going away with the WG.  The list is explicitly
called out as a good place to try out proposals, so people can in fact
do that today.

Best,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From ajs@anvilwalrusden.com  Thu Jun 20 10:28:32 2013
Return-Path: <ajs@anvilwalrusden.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 313F921F9ECB for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 SuUn6q+GLO8i for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:28:26 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 8D74821F9E4C for <ietf@ietf.org>; Thu, 20 Jun 2013 10:28:18 -0700 (PDT)
Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 3770F8A031 for <ietf@ietf.org>; Thu, 20 Jun 2013 17:28:18 +0000 (UTC)
Date: Thu, 20 Jun 2013 13:28:16 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: namedroppers (wasRe: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource	Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard)
Message-ID: <20130620172816.GF41900@mx1.yitter.info>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com> <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com> <20130620163611.GB41900@mx1.yitter.info> <51C33636.2040104@dougbarton.us> <8D23D4052ABE7A4490E77B1A012B6307751E3376@mbx-01.win.nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751E3376@mbx-01.win.nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
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: Thu, 20 Jun 2013 17:28:32 -0000

On Thu, Jun 20, 2013 at 05:10:20PM +0000, Ted Lemon wrote:
> You mean like "namedroppers"?

If only we still had that list.  Alas, it was the victim of politics.
Perhaps Randy Bush will bring it back to life.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From dougb@dougbarton.us  Thu Jun 20 10:44:31 2013
Return-Path: <dougb@dougbarton.us>
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 278C921F9F8A for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
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 xJEq0Bej6bj0 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 10:44:27 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id EE88921F9F4E for <ietf@ietf.org>; Thu, 20 Jun 2013 10:44:26 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id EFC2B22B6A for <ietf@ietf.org>; Thu, 20 Jun 2013 17:44:23 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1371750264; bh=TirxROl0nhNlfFUgT0P0IXWC9uZ6Nv5RJLh2TpdO0/g=; h=Date:From:To:Subject:References:In-Reply-To; b=k6v3cv/fxUwTar8rhCetO6IGpLhp/IUHehmLoOV8PmOEizoe8VkSns3OjH9tOr6JN JpUs1b4zDlW79KvaiKL1QdwAAdLvWPDyLEXrx+qczNbRuFD8XJjvXH0UIBrMLH0tDm Op55r+LJnLqOhJ29G4JEi35usei78zjArKIlfbu4=
Message-ID: <51C33F77.8020500@dougbarton.us>
Date: Thu, 20 Jun 2013 10:44:23 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com> <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com> <20130620163611.GB41900@mx1.yitter.info> <51C33636.2040104@dougbarton.us> <20130620172705.GE41900@mx1.yitter.info>
In-Reply-To: <20130620172705.GE41900@mx1.yitter.info>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 20 Jun 2013 17:44:31 -0000

On 06/20/2013 10:27 AM, Andrew Sullivan wrote:
> On Thu, Jun 20, 2013 at 10:04:54AM -0700, Doug Barton wrote:
>
>> Perhaps we could have a non-WG mailing list so that people could
>> submit proposals for review prior to the expert review process.
>
> The WG list isn't going away with the WG.  The list is explicitly
> called out as a good place to try out proposals, so people can in fact
> do that today.

I would argue that a fresh start here might be appropriate, although I 
wouldn't argue it strongly, and wouldn't object to using dnsext@ if that 
was the consensus.


From arturo.servin@gmail.com  Thu Jun 20 11:13:23 2013
Return-Path: <arturo.servin@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 1F70021F9D6B for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 11:13:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 Th-KMhFrvNLJ for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 11:13:18 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 6254121F9D33 for <ietf@ietf.org>; Thu, 20 Jun 2013 11:13:18 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r10so6511505pdi.13 for <ietf@ietf.org>; Thu, 20 Jun 2013 11:13:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=q37AJ7Y3yldTZCDp76mZdd1by9dt8sQ9SWuHG4Tc6wQ=; b=MGXm2Rkd6DywbSiamieBecohCzfduUwhtRfAmnoMApl0/Z32uAL/uwCDyVqGJisyCe xXURAaLN6SPFqQWu0gg0MgEWE4WuDsihZxlRTZKARW91onWSqOekUfnTumWJKMS3JRly +Az/8pEcKYsSGddGHGfDFb9XtR3jY3RdxPsw6rIhBF7EWM0qPSRlXJKhqlw1/TqEBtOz BjNSicwtLN/Obd+AKZpYJk7+qs3lNZ2hS3AFZL8pVEg8gg5eu4pINhiWe/jDSRoZwkO9 TvyWneBcEPqBUFJAPFRvgQsKRLLPVNkYBZf1rh/ei8r9KYWNrzNxlQvRfMUROaYsYGN3 vuRw==
X-Received: by 10.66.227.71 with SMTP id ry7mr12576798pac.54.1371751993662; Thu, 20 Jun 2013 11:13:13 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([202.183.168.2]) by mx.google.com with ESMTPSA id ka16sm1747383pad.14.2013.06.20.11.13.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Jun 2013 11:13:12 -0700 (PDT)
Message-ID: <51C3462D.5020704@gmail.com>
Date: Fri, 21 Jun 2013 01:13:01 +0700
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Conclusions on South American IETF Meeting
References: <20130620180046.12461.96111.idtracker@ietfa.amsl.com>
In-Reply-To: <20130620180046.12461.96111.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: The IAOC <bob.hinden@gmail.com>
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: Thu, 20 Jun 2013 18:13:23 -0000

    Thank you Bob and the IAOC for taking the time to analize the
possiblities of a meeting outside North America, Europe and Asia.

    Independently of the result, I think it had been a good opportunity
for many of us to take advantage of the momentum and to initiate some
actions to promote the IETF.

Regards,
as


On 6/21/13 1:00 AM, The IAOC wrote:
> The IAOC would like to thank all the people who commented on the IETF
> list and responded to the survey. It was very helpful to the IAOC in
> identifying issues and interest.
>
> As of 17 June 2013, the survey had 656 responses. This was more 
> responses than for any other survey we have done, and is more than 
> half of the number of people who usually attend an IETF meeting.
>
> Of the unfiltered data, 72.3% said they would very likely or likely 
> attend a meeting in Buenos Aires. 13.3% said unlikely or very 
> unlikely. Of these 17.1% have not attended an IETF meeting and 38.7% 
> are not on a committee, WG chair, I-D author, or full time student. In 
> this group 169 people (25.7%) were from South America, Latin America, 
> or the Caribbean. The unfiltered survey results can be found at:
>
> http://iaoc.ietf.org/documents/SurveySummary_Unfiltered_06172013.pdf
>
> Applying a filter of only looking at the most active participants 
> (that is, IESG, IAB, IAOC, NomCom members, WG chairs, and I-D authors) 
> the Likely and Very Likely is 71.8% indicated they will attend, and 
> 13.8% said they were unlikely or very unlikely. In this group 26 
> people (7.0%) were from South America, Latin America, or the 
> Caribbean. Also, this group of the most active participants was Likely 
> or Very Likely to attend London at 85.9% (higher than South America) 
> and Yokohama at 68.4% (lower than South America). The filtered survey 
> results can be found at:
>
> http://iaoc.ietf.org/documents/SurveySummary_Active_06172013-1.pdf
>
> Based on these survey results, we conclude there would be good 
> attendance at a meeting in Buenos Aires overall, good attendance from 
> people in the region, and that most active participants will attend. 
> Active participants would attend at similar rates to their attendance 
> at other IETF meetings. From this viewpoint, holding a meeting in 
> Buenos Aires appears to be similar holding it in other locations 
> around the world.
>
> The results from the survey by itself do not mean we should have an 
> IETF meeting in Buenos Aires, but it does eliminate several reasons 
> why we should not have a meeting there.
>
> The harder questions as discussed on the IETF list relate to if we 
> should have a meeting in Buenos Aires.
>
> The first part of this relates to whether having a single meeting in 
> South America will increase IETF participation from that region and 
> increase the diversity in the IETF. This was discussed a lot on the 
> IETF list. We agree that a single meeting isn't sufficient. We have 
> been talking with the Internet Society (ISOC) about programs and 
> events that could be held in the region leading up to and following an 
> IETF meeting in the region. They said that ISOC is planning to hold a 
> series of events and programs in South America. This would include:
>
>   - Increasing the IETF Fellows and policy makers from the region
>   - Local meetings about IETF technologies
>   - Local meetings about Internet deployment approaches
>   - Local meetings with general information on how the IETF works and 
>      how to participate
>
> The more detailed plan we received from ISOC can be found at:
>
>  http://iaoc.ietf.org/documents/ISOC%20Activities%20supporting%20IETF%20in%20LAC.pdf
>
> The IAOC thinks that scheduling an IETF meeting in Beunos Aires and 
> announcing a series of events will increase the participation from 
> this region and may improve the IETF's cultural diversity.
>
> The other general questions raised on the list are why should we do 
> this and will having a meeting in South America really help with the 
> issues we see relating to advancing the IETF in political and 
> international circles. Some people expressed skepticism that this 
> would really help. We don't think we can prove this factually, it is a 
> judgment call to a large extent, but we think the combination of the 
> IETF meeting and the ISOC events in the region will help.
>
> The IAOC will proceed with planning a single meeting in Buenos Aires 
> based on what we have heard from the community, the survey, and our 
> discussions with ISOC regarding organizing events in South America. We 
> will also continue to track attendance from participants in all 
> regions.
>
> We thank you for providing feedback on the IETF list and for 
> responding to the survey.
>
> Bob Hinden
> IAOC Chair


From carlosm3011@gmail.com  Thu Jun 20 11:21:47 2013
Return-Path: <carlosm3011@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 9CF4921F9B5C for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 11:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.038
X-Spam-Level: 
X-Spam-Status: No, score=-3.038 tagged_above=-999 required=5 tests=[AWL=0.561,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 FnNdWgG7zGVg for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 11:21:42 -0700 (PDT)
Received: from mail-qe0-f49.google.com (mail-qe0-f49.google.com [209.85.128.49]) by ietfa.amsl.com (Postfix) with ESMTP id 70C2421F99D1 for <ietf@ietf.org>; Thu, 20 Jun 2013 11:21:41 -0700 (PDT)
Received: by mail-qe0-f49.google.com with SMTP id cz11so4122914qeb.8 for <ietf@ietf.org>; Thu, 20 Jun 2013 11:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=6jbWqcJ+MRfiVP7F/0y9eiAilEPzyXKm2nH4riEFpvA=; b=Guk2/KE6arpBMuzGUIcqEh72ginqKAX9yhTGG9+p11BnigL/eaeXvTz5oljx2Yi+3v DxmInF0r+19I1cSKPRZDjLfnFmz5gXWjrLyaoEgFA+T90SCYU5fPxb+C/+KlQWrdiQL9 frpN7kLBIELpyLjRPLteKW8u8DpZzVObsOMNRRtBNuyXUFEmfhYbB27SeSrb+oYujMk5 IuLJZLQu4kwivx/cMxwQ12tKVvhwnBCdX+UOv46u1r02GLMJ4nesL68N064AB7GASxrt 79SzPh4AJmlBw6Q4YXB0EOUIK8V1SQRpsFTJe0KibYPQnYLr+rwHzCsH+zkarcZCPmFc YQ8w==
X-Received: by 10.224.177.201 with SMTP id bj9mr10358931qab.14.1371752500829;  Thu, 20 Jun 2013 11:21:40 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([200.7.87.57]) by mx.google.com with ESMTPSA id j5sm2230089qan.7.2013.06.20.11.21.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Jun 2013 11:21:39 -0700 (PDT)
Message-ID: <51C34833.30808@gmail.com>
Date: Thu, 20 Jun 2013 15:21:39 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Conclusions on South American IETF Meeting
References: <20130620180046.12461.96111.idtracker@ietfa.amsl.com> <51C3462D.5020704@gmail.com>
In-Reply-To: <51C3462D.5020704@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: The IAOC <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
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: Thu, 20 Jun 2013 18:21:47 -0000

+1!

On 6/20/13 3:13 PM, Arturo Servin wrote:
> 
>     Thank you Bob and the IAOC for taking the time to analize the
> possiblities of a meeting outside North America, Europe and Asia.
> 
>     Independently of the result, I think it had been a good opportunity
> for many of us to take advantage of the momentum and to initiate some
> actions to promote the IETF.
> 
> Regards,
> as
> 
> 
> On 6/21/13 1:00 AM, The IAOC wrote:
>> The IAOC would like to thank all the people who commented on the IETF
>> list and responded to the survey. It was very helpful to the IAOC in
>> identifying issues and interest.
>>
>> As of 17 June 2013, the survey had 656 responses. This was more 
>> responses than for any other survey we have done, and is more than 
>> half of the number of people who usually attend an IETF meeting.
>>
>> Of the unfiltered data, 72.3% said they would very likely or likely 
>> attend a meeting in Buenos Aires. 13.3% said unlikely or very 
>> unlikely. Of these 17.1% have not attended an IETF meeting and 38.7% 
>> are not on a committee, WG chair, I-D author, or full time student. In 
>> this group 169 people (25.7%) were from South America, Latin America, 
>> or the Caribbean. The unfiltered survey results can be found at:
>>
>> http://iaoc.ietf.org/documents/SurveySummary_Unfiltered_06172013.pdf
>>
>> Applying a filter of only looking at the most active participants 
>> (that is, IESG, IAB, IAOC, NomCom members, WG chairs, and I-D authors) 
>> the Likely and Very Likely is 71.8% indicated they will attend, and 
>> 13.8% said they were unlikely or very unlikely. In this group 26 
>> people (7.0%) were from South America, Latin America, or the 
>> Caribbean. Also, this group of the most active participants was Likely 
>> or Very Likely to attend London at 85.9% (higher than South America) 
>> and Yokohama at 68.4% (lower than South America). The filtered survey 
>> results can be found at:
>>
>> http://iaoc.ietf.org/documents/SurveySummary_Active_06172013-1.pdf
>>
>> Based on these survey results, we conclude there would be good 
>> attendance at a meeting in Buenos Aires overall, good attendance from 
>> people in the region, and that most active participants will attend. 
>> Active participants would attend at similar rates to their attendance 
>> at other IETF meetings. From this viewpoint, holding a meeting in 
>> Buenos Aires appears to be similar holding it in other locations 
>> around the world.
>>
>> The results from the survey by itself do not mean we should have an 
>> IETF meeting in Buenos Aires, but it does eliminate several reasons 
>> why we should not have a meeting there.
>>
>> The harder questions as discussed on the IETF list relate to if we 
>> should have a meeting in Buenos Aires.
>>
>> The first part of this relates to whether having a single meeting in 
>> South America will increase IETF participation from that region and 
>> increase the diversity in the IETF. This was discussed a lot on the 
>> IETF list. We agree that a single meeting isn't sufficient. We have 
>> been talking with the Internet Society (ISOC) about programs and 
>> events that could be held in the region leading up to and following an 
>> IETF meeting in the region. They said that ISOC is planning to hold a 
>> series of events and programs in South America. This would include:
>>
>>   - Increasing the IETF Fellows and policy makers from the region
>>   - Local meetings about IETF technologies
>>   - Local meetings about Internet deployment approaches
>>   - Local meetings with general information on how the IETF works and 
>>      how to participate
>>
>> The more detailed plan we received from ISOC can be found at:
>>
>>  http://iaoc.ietf.org/documents/ISOC%20Activities%20supporting%20IETF%20in%20LAC.pdf
>>
>> The IAOC thinks that scheduling an IETF meeting in Beunos Aires and 
>> announcing a series of events will increase the participation from 
>> this region and may improve the IETF's cultural diversity.
>>
>> The other general questions raised on the list are why should we do 
>> this and will having a meeting in South America really help with the 
>> issues we see relating to advancing the IETF in political and 
>> international circles. Some people expressed skepticism that this 
>> would really help. We don't think we can prove this factually, it is a 
>> judgment call to a large extent, but we think the combination of the 
>> IETF meeting and the ISOC events in the region will help.
>>
>> The IAOC will proceed with planning a single meeting in Buenos Aires 
>> based on what we have heard from the community, the survey, and our 
>> discussions with ISOC regarding organizing events in South America. We 
>> will also continue to track attendance from participants in all 
>> regions.
>>
>> We thank you for providing feedback on the IETF list and for 
>> responding to the survey.
>>
>> Bob Hinden
>> IAOC Chair
> 

From sm@resistor.net  Thu Jun 20 11:27:48 2013
Return-Path: <sm@resistor.net>
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 7328621F9019 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 11:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.522
X-Spam-Level: 
X-Spam-Status: No, score=-102.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 GSnN8IdvaUab for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 11:27:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D3D1421F9D56 for <ietf@ietf.org>; Thu, 20 Jun 2013 11:27:46 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5KIReOT010116; Thu, 20 Jun 2013 11:27:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1371752865; bh=zvG+l73EihKRcsSEBZb1IGazGxoLYo4+RbSiB1nPImU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VUjE+zWArT8Y9nPMUrifVnaZU2PGGCeIdibI/ccod+stugzcSUq2FFo5975j7rIxC UbTUr1ObBaF5zC4We5YddY6rY8DnwOwthTyO2JKmh0/ZBnXFt4MoIN83D1ZQxFqERy kYnnOQ4bmqfSi8lBJXtTfFVqyBCmpGcoSam4XXbM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1371752865; i=@resistor.net; bh=zvG+l73EihKRcsSEBZb1IGazGxoLYo4+RbSiB1nPImU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=J3Wf5rbsXCaMxhgdmfLCEM7DycBJXjWHtgpImYYb0dJE9QwjzOqqivWcOBK/7C3bb ZveteHGVG42rM1IswzRl3ceLNQj4wYbjFlb2zdMfO3SyEw1ILi6p3v8YWDZqLMtnAj vqqIjXu+aycBCDK6jS7Fg4kKBEY0zWM98YVEbnbg=
Message-Id: <6.2.5.6.2.20130620103343.06c01fb0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 20 Jun 2013 11:26:52 -0700
To: Mark Nottingham <mnot@mnot.net>, John C Klensin <john@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Is the IETF is an international organization? (was: IETF Diversity)
In-Reply-To: <3425E471-1381-4512-9B98-39D6AB023C73@mnot.net>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net> <3425E471-1381-4512-9B98-39D6AB023C73@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Thu, 20 Jun 2013 18:27:48 -0000

At 08:02 20-06-2013, Mark Nottingham wrote:
>Keep in mind that you're talking to an organisation that believes 
>that Vancouver qualifies as "Asia."

That should be added to the Tao. :-)

At 08:24 20-06-2013, John C Klensin wrote:
>Political convenience and expedience trumps geographical reality
>every time :-)

The question I would ask is how many continents are there.

Regards,
-sm 


From iad@ietf.org  Thu Jun 20 11:59:15 2013
Return-Path: <iad@ietf.org>
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 4605E11E80FB; Thu, 20 Jun 2013 11:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 vMd4vSCNz599; Thu, 20 Jun 2013 11:59:14 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CC9AD11E80D3; Thu, 20 Jun 2013 11:59:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IAOC Website Updated
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130620185914.19663.88097.idtracker@ietfa.amsl.com>
Date: Thu, 20 Jun 2013 11:59:14 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: Thu, 20 Jun 2013 18:59:15 -0000

One of the IAOC goals for 2013 was to update the IAOC website to improve
consistency, organization, linkage, and ease of use.

I am pleased to announce that the IAOC site has been updated and is availab=
le =

now for your use at <http://iaoc.ietf.org/>.

On the home page see a video of an Overview of the IAOC given by Chair Bob
Hinden in Orlando that includes a discussion of venue selection and IETF =

finances.  Also on the home page are recent announcements, as well as repor=
ts
from IANA, the RFC Editor, the IETF Chair, the NomCom Chair, and more.

The navigation bar makes it easy to find financial statements, minutes,
meeting sponsorship opportunities, and much more.

We hope you find this helpful, the IAOC as more transparent, and of course =
we
welcome your feedback.

Ray
IETF Administrative Director

PS:  Going to IETF 87 in Berlin?  The IAOC will be doing another overview
session there, Sunday July 28 at 3:00 PM.  Hope to see you there!

From sm@resistor.net  Thu Jun 20 12:39:01 2013
Return-Path: <sm@resistor.net>
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 8C03711E80FB; Thu, 20 Jun 2013 12:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 zyR+xmm2W+BD; Thu, 20 Jun 2013 12:39:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B78E921E805F; Thu, 20 Jun 2013 12:38:57 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5KJcqG4014255; Thu, 20 Jun 2013 12:38:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1371757137; bh=hMhyNd8w6AsnpVWLQivsU2HgEqBl1A/5mGlfGvSHKck=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qaqn9LgPVtNnMdZFmoAPfUYVMW+Ipuo+pnDz7Ed9E0aCsgo9KUAPF0aL7T4AJA2ZO PRgdUXbFPIMSvmA/EFEcIja64v9P5S4MufvbDzRLxbm7/MseMDn1MY7Ln/3YsyjkrS KVpMpBQ1i8D9kIIAfVPatCg/YBW7eHkGyICJ3+VY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1371757137; i=@resistor.net; bh=hMhyNd8w6AsnpVWLQivsU2HgEqBl1A/5mGlfGvSHKck=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=EDSvBmc3LrBxBq4NEgzvZhgPzY10fEYM+MpCyWR5+WhDz76TpSedsecud5IR3ywK5 m51G9L+pGixAm+0ekDX8QxpCkZl5RcUDxUDSAi+4lit4VCQYENNuUy5jZJKY0z0uU5 hx8FNRNQ8mjDO6ahRezDGwkGkrBKQOYa4wRyQpXU=
Message-Id: <6.2.5.6.2.20130620113213.0ce9b408@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 20 Jun 2013 12:38:30 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Policy makers (was: Conclusions on South American IETF Meeting)
In-Reply-To: <20130620180046.12461.96111.idtracker@ietfa.amsl.com>
References: <20130620180046.12461.96111.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: iab@iab.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: Thu, 20 Jun 2013 19:39:01 -0000

At 11:00 20-06-2013, The IAOC wrote:
>series of events and programs in South America. This would include:
>
>   - Increasing the IETF Fellows and policy makers from the region

I don't see any policy makers reviewing=20
Internet-Drafts.  I don't see any policy makers=20
writing IETF RFCs.  Policy makers do not usually=20
participate in IETF discussions.

During the diversity discussions it has been=20
pointed out that it would be useful if there were=20
more network operators and people who can write=20
code participating in the IETF.  What the IAB=20
seems to be have recommended instead is to=20
increase the number of policy makers attending IETF meetings.

I am reminded of a sentence from Patrik=20
F=E4ltstr=F6m: "And to some degree there might be=20
parties that see the lack of progress as a good=20
thing...".  I hope that the IAB is not one of=20
these parties as it might be seen as using the=20
IETF for its political convenience.

Regards,
-sm=20


From randy@psg.com  Thu Jun 20 12:54:19 2013
Return-Path: <randy@psg.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 2425C21E80B9 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 12:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,  BAYES_00=-2.599]
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 mC3yhrIneTeU for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 12:54:18 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id C07C221F9DED for <ietf@ietf.org>; Thu, 20 Jun 2013 12:54:18 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Upkvw-000MTB-83; Thu, 20 Jun 2013 19:54:16 +0000
Date: Fri, 21 Jun 2013 04:54:15 +0900
Message-ID: <m21u7wwobc.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: namedroppers (wasRe: Last Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource	Records for	EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard)
In-Reply-To: <20130620172816.GF41900@mx1.yitter.info>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com> <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com> <20130620163611.GB41900@mx1.yitter.info> <51C33636.2040104@dougbarton.us> <8D23D4052ABE7A4490E77B1A012B6307751E3376@mbx-01.win.nominum.com> <20130620172816.GF41900@mx1.yitter.info>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: 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: Thu, 20 Jun 2013 19:54:19 -0000

>> You mean like "namedroppers"?
> If only we still had that list.

any reports of its death are from questionable sources

> it was the victim of politics.

like much of life

randy

From fred@cisco.com  Thu Jun 20 14:05:43 2013
Return-Path: <fred@cisco.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 D8D4621E80A8 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 14:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 cVNfdAsR7pUJ for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 14:05:38 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4632E21E8093 for <ietf@ietf.org>; Thu, 20 Jun 2013 14:05:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=603; q=dns/txt; s=iport; t=1371762338; x=1372971938; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=BK+/DPoLlzOrZzaadMqN1CzhSpTLQTHBAh/I60YnYlI=; b=XDGdCguKJToL1s3JLQuNq5hS5jiiiZAK6war6fhzMd3O6wxwzOKYkSFN wIeJBrZv6M/YrZI7SLQJS9z5T/S4k3L1qhaTUCPVdcQKLmF9BBxmQu9sH nIwY7RUxdTWyvw3r1aJ85Tmn54wsXIi1ZXqjHHL/Kck53D1WacRoqvwi/ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmAFAJZtw1GtJV2Y/2dsb2JhbABbgwl6gjy8en8WdIIjAQEBAwE6PwULAgEIGAoUEDIlAgQOBQiIAAa8Qo8WAjEHgwBhA6kHgw+CKA
X-IronPort-AV: E=Sophos;i="4.87,907,1363132800"; d="scan'208";a="222533566"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-9.cisco.com with ESMTP; 20 Jun 2013 21:05:37 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r5KL5bqM002471 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 20 Jun 2013 21:05:37 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Thu, 20 Jun 2013 16:05:37 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: SM <sm@resistor.net>
Subject: Re: Is the IETF is an international organization? (was: IETF Diversity)
Thread-Topic: Is the IETF is an international organization? (was: IETF Diversity)
Thread-Index: AQHObcdz3s830Jy+T0usu3oKi0idA5k/P7oAgAAsWgA=
Date: Thu, 20 Jun 2013 21:05:36 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B920B4E@xmb-rcd-x09.cisco.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net> <3425E471-1381-4512-9B98-39D6AB023C73@mnot.net> <6.2.5.6.2.20130620103343.06c01fb0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130620103343.06c01fb0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.125]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A25543B7F2FD7C4FA3B4BC05259355F3@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Mark Nottingham <mnot@mnot.net>, John C Klensin <john@jck.com>, "<ietf@ietf.org>" <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: Thu, 20 Jun 2013 21:05:44 -0000

On Jun 20, 2013, at 11:26 AM, SM <sm@resistor.net> wrote:

> At 08:02 20-06-2013, Mark Nottingham wrote:
>> Keep in mind that you're talking to an organisation that believes that V=
ancouver qualifies as "Asia."
>=20
> That should be added to the Tao. :-)
>=20
> At 08:24 20-06-2013, John C Klensin wrote:
>> Political convenience and expedience trumps geographical reality
>> every time :-)
>=20
> The question I would ask is how many continents are there.

One. The rest are islands. Asia, by the way, is a peninsula sticking out fr=
om Europe.

Now that we've cleared that up...=

From ben@nostrum.com  Thu Jun 20 16:06:34 2013
Return-Path: <ben@nostrum.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 232FE21F9C55; Thu, 20 Jun 2013 16:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 1cdAQEpDNkeR; Thu, 20 Jun 2013 16:06:33 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id EBA9421F9B00; Thu, 20 Jun 2013 16:06:32 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5KN6VBg023628 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Jun 2013 18:06:31 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Date: Thu, 20 Jun 2013 18:06:31 -0500
Message-Id: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>
To: draft-thornburgh-adobe-rtmfp.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion 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: Thu, 20 Jun 2013 23:06:34 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:  draft-thornburgh-adobe-rtmfp-07
Reviewer: Ben Campbell
Review Date:  2013-06-20
IETF LC End Date: 2013-06-25

Summary: This draft is almost ready for publication as an informational =
RFC. However, I have some concerns about the purpose and intended status =
of the document that I think should be considered prior to publication.


Note: This is an informational draft that describes what I understand to =
be an existing protocol as implemented by commercial products. =
Therefore, this review does not attempt to evaluate the protocol itself. =
I assume the protocol is what it is, and it is not up to the IETF to =
agree or disagree with it.

*** Major issues:

-- Why does this need to be published as an IETF stream RFC?  If I =
understand correctly, this documents an existing protocol as implemented =
by commercial products. I agree with Martin's comment that there is =
value in publishing this sort of thing, but I applaud the Adobe and the =
author for publishing it so other implementations can interoperate with =
their products. But that could have done that in an independent stream =
document, or even in an Adobe published document. (Perhaps even in a =
prettier format ;-)  )  If we publish this as an IETF stream document, =
then I think it needs stronger clarification that it is not an IETF =
consensus doc than just its informational status.

Along those lines:

	-- Is this document the authoritative specification? (I suspect =
not.) Who owns change control? I assume that to be Adobe and/or the =
authors. What expectation do readers of this draft have that it =
represents the current version of RTMFP at any point in time?

	-- Under what circumstances would one desire to implement this? =
I can infer that from the introduction, but it would be nice to see some =
sort of applicability statement making it explicitly clear that this is =
not an IETF protocol, and that one would implement it in order to =
interoperate with certain Adobe products. I know that some of this may =
be implied by the fact that this is informational rather than standards =
track. But I don't expect readers who are not IETF insiders to =
understand that subtlety without some explicit words to that effect. In =
particular, it would be good to clarify the difference between this and =
the many "not quite accepted as standards track by some working group" =
nature of a number of our informational RFCs that describe protocols.

That all being said, this is overall a well written document. The rest =
of my comments are mostly pedantic nits.

*** Minor issues:

-- section 1.2:=20

I find the use of "MUST ONLY" confusing. I gather it means "you are =
_allowed_ to do X only under certain conditions" rather than "you are =
_required_ to do X under certain conditions." If correct, I think the =
words "MAY ONLY" would be more clear. If not, then I think the construct =
would be better handled using existing 2119 language.

-- section 3.2:

Do I understand correctly that all endpoints are expected to be able to =
present certificates? Do you find that common in the field? I realize =
the nature of the certs will depend on the security profiles.

-- sections 3.2 and 5

Do I assume correctly that endpoints need a common crypto profile to =
communicate? Is there a repository where one might find crypto profile =
documentation? Is there a commonly implemented one to which this draft =
could refer?

-- section 3.2: "Multiple endpoints SHOULD NOT have the same identity."

Why not MUST? Will things not break if two endpoints do have the same =
identity?

-- "Authenticity MAY comprise verifying an issuer signature chain in a =
public key infrastructure"

Is that really normative, or just an observation of fact?

-- " Canonical Endpoint Discriminators for distinct identities SHOULD be =
distinct."

What if they are not? Do things break? It might be worth making this a =
MUST, or adding some additional guidance about what might happen if the =
SHOULD is violated.

-- "A comparison function MAY comprise performing a lexicographic =
ordering..."

Is that really normative, or just an example of something one might do?

-- "A test SHOULD comprise testing whether the certificates are =
identical."

What if it doesn't? Also, what constitutes "identical"? All fields match =
values? Bitwise match?  Is it simply including the same identity or =
identities? Maybe an identity function provided by the crypto profile?

-- 3.5, last paragraph:

Can you offer guidance on reasonable buffer size and number ranges?

-- 3.5.1.1.1, 3rd paragraph:

What are the consequences of having a tag with less than 8 bytes of =
length? Is the SHOULD reasonable here?

-- 3.5.1.1.1 throughout, and following sections:

Does the upper case AND have special meaning?

-- 3.5.1.4, Deployment Note:

How would a redirector know which endpoints might do this? Or should it =
never initiate a session?

-- 3.5.2:

Do I infer correctly that two endpoints need not share the same =
congestion control algorithm to communicate?

-- 3.6.2.3.2, 2nd paragraph: "...an implementation SHOULD encode a Next =
User Data chunk instead of a User Data chunk"

I'm not sure why this needs to be normative, as I assume its just normal =
behavior. But if it does need to be normative, why not a MUST?  Can the =
far endpoint reasonably handle things if the SHOULD is violated?


*** Nits/editorial comments:

-- General: There's quite a bit of inconsistent use of third-person vs =
second-person language.

-- 3.1: It would be nice to see the overview earlier in the draft. I =
found it difficult to read through all the data format stuff prior to =
section 3 putting them into context.

-- 3.5.1.4, Deployment Note:

s/which/that

-- 3.5.1.6, last paragraph:

Which diagram? (An explicit cross-ref would help.)

-- 3.5.2:

What is meant by "aggressive" in this context? Aggressive in avoiding =
congestion, or aggressive in sending data?

-- 3.6.2.3.1 and subsequent sections:

Does the all-caps "FIRST" have special meaning?









From john-ietf@jck.com  Thu Jun 20 18:48:44 2013
Return-Path: <john-ietf@jck.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 B61F311E8146 for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 18:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.487
X-Spam-Level: 
X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Fxr3Ec7lrKMW for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 18:48:38 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D759321E80DF for <ietf@ietf.org>; Thu, 20 Jun 2013 18:48:38 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UpqSq-0005gT-QQ; Thu, 20 Jun 2013 21:48:36 -0400
Date: Thu, 20 Jun 2013 21:48:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to	Proposed Standard
Message-ID: <5D74490A7A2EBB54CBD1DD24@JcK-HP8200.jck.com>
In-Reply-To: <20130620163611.GB41900@mx1.yitter.info>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com> <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com> <20130620163611.GB41900@mx1.yitter.info>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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: Fri, 21 Jun 2013 01:48:44 -0000

--On Thursday, June 20, 2013 12:36 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

> On Thu, Jun 20, 2013 at 11:17:16AM -0400, John C Klensin wrote:
>  
>> So some review of the DNSEXT-specified procedures and
>> expectations may be in order.
>...
> But more generally, as a practical matter it is better that
> people register their stuff with us than that they don't.  We
> have, in the wild, a used EDNS0 option code that is all over
> the Internet.  It is undocumented, and the code point isn't
> actually registered.  That state of affairs is surely worse
> than that the IETF didn't get to provide good advice to
> authors.  DNSEXT already tried to be the DNS cops, and has
> failed miserably, partly because of the usual get-off-my-lawn
> crowd and partly because people unfamiliar with the IETF find
> its procedures a little arcane.
> 
> My view is that we need to be more pragmatic.

Andrew,

Just to be clear, I completely agree.  I thought that should
have been clear from the context of my note (context that you
omitted above).  I think that what I have referred to as the
lightweight registration procedure is just fine.  What I have
objected to since the first time a Last Call on the present
document was initiated is any assertion that, because something
is registered, it is entitled to be documented in the RFC
Series.   I object even more strongly to any implication that
such a registered RRTYPE should be accepted as a Standards Track
document without any further review because it is registered
already.

I thought that issue had been settled for this document by
reclassifying its intended status to Informational and
clarifying the relationship of the RRTYPEs to other
consideration, particularly privacy ones.  IMO, that
clarification along makes it worth publishing as an RFC, but the
notion of entitlement was, I thought, put to rest.

Consequently, I was mildly astonished when Olafur's comment
(which included the information that he is co-chair of DNSEXT)
included "...we (DNS community) want to encore [sic] that any
such allocations be published as RFC's for future references".  

So, once again and in short sentences:

(1) The present registration procedure does nothing to ensure
any such thing.

(2) There is nothing else in either IETF or RFC Editor
procedures that ensures RFC publication.  If a document
describing an already-registered RRTYPE is submitted and some AD
wants to sponsor it for publication as an individual submission
and puts it into a Last Call on that basis, the community may
pick at it, insist on changes, or even reach consensus that it
should not be published.

(3) I think the above is fine.  If someone (else) thinks that
RFC publication should be "ensured" for any RRTYPE allocation,
then they need to persuade whomever needs to be persuaded to
modify the registration procedure.   I would, personally, oppose
that change if it eliminated the possibility of quick,
lightweight, registrations but my opinion probably doesn't count
for much relative to the "DNS community" for which Olafur and/or
you are speaking.

best,
    john


From barryleiba.mailing.lists@gmail.com  Thu Jun 20 19:14:43 2013
Return-Path: <barryleiba.mailing.lists@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 BA78D21E80F8; Thu, 20 Jun 2013 19:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.004
X-Spam-Level: 
X-Spam-Status: No, score=-102.004 tagged_above=-999 required=5 tests=[AWL=-0.027, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 XBu2jDkl7r0F; Thu, 20 Jun 2013 19:14:43 -0700 (PDT)
Received: from mail-ve0-x22a.google.com (mail-ve0-x22a.google.com [IPv6:2607:f8b0:400c:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 0B66621E80EB; Thu, 20 Jun 2013 19:14:42 -0700 (PDT)
Received: by mail-ve0-f170.google.com with SMTP id 14so5766451vea.15 for <multiple recipients>; Thu, 20 Jun 2013 19:14:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=gh3oLRJY2BAYin8SjXHc465XL5E//azZEX0XudaAQ50=; b=bLtPA7q483X2xHgkbRJHLWs3fDhPg9RI1QuKwGcdP9K3xxsMTQFh0XWTx//VPA1SWa GAbOkc6W64HeOiUmEWq99hSCnhT7Ekz6diJ0eQhZUo4/DqMlVw2xS2RHqIhkjKhFJtRT 1jgec0Tg4HsZPqSZL10nzcYI+/dbbRwY5VA2AY34P8HdlKn86c+rZrMrQbsZC55R+c4/ rOJl1miEkN1AhgMZX+OXbYhECxVWYIv5+amUy5/coWGPbQir4qmBMdmVC+e4PPNc5lTq rG8B5JvWzyFT4abyopZLn+HsER6o5OdwtsOCWmiDRUfG1gxkY6eY2AKmeNilILQI7QfP eDbg==
MIME-Version: 1.0
X-Received: by 10.220.101.69 with SMTP id b5mr4329884vco.55.1371780882405; Thu, 20 Jun 2013 19:14:42 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.234.105 with HTTP; Thu, 20 Jun 2013 19:14:42 -0700 (PDT)
In-Reply-To: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>
Date: Thu, 20 Jun 2013 22:14:42 -0400
X-Google-Sender-Auth: SJobIzffGqcppGVo2ReD8PZsv7c
Message-ID: <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com>
Subject: Re: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
From: Barry Leiba <barryleiba@computer.org>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=047d7b3a7e9234b39804dfa0a0a6
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion 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: Fri, 21 Jun 2013 02:14:43 -0000

--047d7b3a7e9234b39804dfa0a0a6
Content-Type: text/plain; charset=ISO-8859-1

>
> -- Why does this need to be published as an IETF stream RFC?  If I
> understand correctly, this documents an existing protocol as implemented by
> commercial products. I agree with Martin's comment that there is value in
> publishing this sort of thing, but I applaud the Adobe and the author for
> publishing it so other implementations can interoperate with their
> products. But that could have done that in an independent stream document,
> or even in an Adobe published document. (Perhaps even in a prettier format
> ;-)  )  If we publish this as an IETF stream document, then I think it
> needs stronger clarification that it is not an IETF consensus doc than just
> its informational status.


 FWIW, the IESG has discussed this in the context of other documents, and
is looking at boilerplate that does not say that the document is a "product
of the IETF", and makes it clear that the content is not a matter of IETF
consensus.  If that sort of boilerplate was used, do you think that would
be sufficient?

Barry

--047d7b3a7e9234b39804dfa0a0a6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">-- Why does this need to be published as an =
IETF stream RFC? =A0If I understand correctly, this documents an existing p=
rotocol as implemented by commercial products. I agree with Martin&#39;s co=
mment that there is value in publishing this sort of thing, but I applaud t=
he Adobe and the author for publishing it so other implementations can inte=
roperate with their products. But that could have done that in an independe=
nt stream document, or even in an Adobe published document. (Perhaps even i=
n a prettier format ;-) =A0) =A0If we publish this as an IETF stream docume=
nt, then I think it needs stronger clarification that it is not an IETF con=
sensus doc than just its informational status.</blockquote>
<div><br></div><div>=A0FWIW, the IESG has discussed this in the context of =
other documents, and is looking at boilerplate that does not say that the d=
ocument is a &quot;product of the IETF&quot;, and makes it clear that the c=
ontent is not a matter of IETF consensus. =A0If that sort of boilerplate wa=
s used, do you think that would be sufficient?</div>
<div><br></div><div>Barry<span></span></div><div><br></div>

--047d7b3a7e9234b39804dfa0a0a6--

From john-ietf@jck.com  Thu Jun 20 20:12:32 2013
Return-Path: <john-ietf@jck.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 1152F21E80DF; Thu, 20 Jun 2013 20:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.494
X-Spam-Level: 
X-Spam-Status: No, score=-102.494 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 E+2TEg9MNYTp; Thu, 20 Jun 2013 20:12:16 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8819D21E80EB; Thu, 20 Jun 2013 20:12:16 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uprli-0005q2-Us; Thu, 20 Jun 2013 23:12:10 -0400
Date: Thu, 20 Jun 2013 23:12:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Message-ID: <BB60A472FABE3AE51CEFBE8C@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, draft-thornburgh-adobe-rtmfp.all@tools.ietf.org, IETF-Discussion 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: Fri, 21 Jun 2013 03:12:32 -0000

--On Thursday, June 20, 2013 22:14 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>  FWIW, the IESG has discussed this in the context of other
> documents, and is looking at boilerplate that does not say
> that the document is a "product of the IETF", and makes it
> clear that the content is not a matter of IETF consensus.  If
> that sort of boilerplate was used, do you think that would be
> sufficient?

FWIW, many IETF Stream Info documents definitely are "matters of
IETF consensus", even more so when those documents are the
consequence of a WG request to publish.   IMO, if a document
really isn't an IETf product in any way and has no relationship
to IETF consensus, it would be far more reasonable for ADs to
simply decline to sponsor it --leaving the document to the
Independent Submission Editor or outside the RFC Series-- rather
than trying to diddle around with boilerplate... especially
since we know that people rarely pay attention to stock
boilerplate.

The option of sponsoring individual submission informational
documents is one that the community granted the IESG in order to
give you folks a reasonable way to deal with circumstances that
were more or less unusual.  You don't need to use it.

   john

p.s. I started a much more detailed response to Ben, but I think
the essence of it is above.  IMO, a discussion that amounts to
whether or not an AD used bad judgment by choosing to sponsor an
individual Informational submission (or whether ADs should have
that power at all) should not become part of evaluating a
particular document's appropriateness.


From ben@nostrum.com  Thu Jun 20 20:54:28 2013
Return-Path: <ben@nostrum.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 0F98D21F9C9A; Thu, 20 Jun 2013 20:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 XVE+w5fPVwVy; Thu, 20 Jun 2013 20:54:27 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1DC21F9CA2; Thu, 20 Jun 2013 20:54:26 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5L3sMBT054389 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Jun 2013 22:54:23 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com>
Date: Thu, 20 Jun 2013 22:54:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B13E844-9B03-4398-8F38-2BE876C420D3@nostrum.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion 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: Fri, 21 Jun 2013 03:54:28 -0000

On Jun 20, 2013, at 9:14 PM, Barry Leiba <barryleiba@computer.org> =
wrote:

> -- Why does this need to be published as an IETF stream RFC?  If I =
understand correctly, this documents an existing protocol as implemented =
by commercial products. I agree with Martin's comment that there is =
value in publishing this sort of thing, but I applaud the Adobe and the =
author for publishing it so other implementations can interoperate with =
their products. But that could have done that in an independent stream =
document, or even in an Adobe published document. (Perhaps even in a =
prettier format ;-)  )  If we publish this as an IETF stream document, =
then I think it needs stronger clarification that it is not an IETF =
consensus doc than just its informational status.
>=20
>  FWIW, the IESG has discussed this in the context of other documents, =
and is looking at boilerplate that does not say that the document is a =
"product of the IETF", and makes it clear that the content is not a =
matter of IETF consensus.  If that sort of boilerplate was used, do you =
think that would be sufficient?
>=20

I think that would help, depending on the specific language. My concerns =
about change control, authoritative specs, etc might still apply =
depending on the boilerplate details.

Thanks!

Ben.



From ben@nostrum.com  Thu Jun 20 20:58:43 2013
Return-Path: <ben@nostrum.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 F30B021E80FE; Thu, 20 Jun 2013 20:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 wl4TTxIpQGuE; Thu, 20 Jun 2013 20:58:42 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id E5D6E21E80FD; Thu, 20 Jun 2013 20:58:41 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5L3wcYg054943 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Jun 2013 22:58:38 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <BB60A472FABE3AE51CEFBE8C@JcK-HP8200.jck.com>
Date: Thu, 20 Jun 2013 22:58:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <50EEE929-781D-4181-ABC6-F05783FD55B9@nostrum.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com> <BB60A472FABE3AE51CEFBE8C@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, Barry Leiba <barryleiba@computer.org>, draft-thornburgh-adobe-rtmfp.all@tools.ietf.org, IETF-Discussion 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: Fri, 21 Jun 2013 03:58:43 -0000

On Jun 20, 2013, at 10:12 PM, John C Klensin <john-ietf@jck.com> wrote:

> p.s. I started a much more detailed response to Ben, but I think
> the essence of it is above.  IMO, a discussion that amounts to
> whether or not an AD used bad judgment by choosing to sponsor an
> individual Informational submission (or whether ADs should have
> that power at all) should not become part of evaluating a
> particular document's appropriateness.

I certainly didn't mean this to be a discussion of AD judgement. I =
suspect this would not be the first time the IETF has published an =
informational RFC that describes a non-IETF protocol, so there's =
probably precedent for doing so. It might be worth discussing whether =
that's a good precedent.

I also recognize that the authors have done a _lot_ of work on this =
draft, so this entire discussion is probably a bit unfair to them. I =
actually do hope it gets published somewhere.

Thanks!

Ben.=

From narten@us.ibm.com  Thu Jun 20 23:03:41 2013
Return-Path: <narten@us.ibm.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 5EEDB21F9FFB for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 23:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.985
X-Spam-Level: 
X-Spam-Status: No, score=-109.985 tagged_above=-999 required=5 tests=[AWL=0.614, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 1bPw6Nw5tGsd for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 23:03:34 -0700 (PDT)
Received: from e37.co.us.ibm.com (e37.co.us.ibm.com [32.97.110.158]) by ietfa.amsl.com (Postfix) with ESMTP id 6226221F9FF8 for <ietf@ietf.org>; Thu, 20 Jun 2013 23:03:25 -0700 (PDT)
Received: from /spool/local by e37.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 20 Jun 2013 22:53:07 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e37.co.us.ibm.com (192.168.1.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 20 Jun 2013 22:53:05 -0600
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 957181FF001E for <ietf@ietf.org>; Thu, 20 Jun 2013 22:47:50 -0600 (MDT)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r5L4r5mh358490 for <ietf@ietf.org>; Thu, 20 Jun 2013 22:53:05 -0600
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r5L4r4mZ001438 for <ietf@ietf.org>; Thu, 20 Jun 2013 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r5L4r4pB001428 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 20 Jun 2013 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r5L4r3oC003478 for <ietf@ietf.org>; Fri, 21 Jun 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r5L4r3nB003439 for ietf@ietf.org; Fri, 21 Jun 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201306210453.r5L4r3nB003439@rotala.raleigh.ibm.com>
Date: Fri, 21 Jun 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13062104-7408-0000-0000-000011678568
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: Fri, 21 Jun 2013 06:03:41 -0000

Total of 164 messages in the last 7 days.
 
script run at: Fri Jun 21 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.93% |   13 |  6.46% |    83622 | stpeter@stpeter.im
  6.10% |   10 |  5.81% |    75305 | dougb@dougbarton.us
  4.88% |    8 |  3.91% |    50591 | melinda.shore@gmail.com
  4.27% |    7 |  4.48% |    58056 | john-ietf@jck.com
  3.05% |    5 |  4.91% |    63546 | david.black@emc.com
  3.05% |    5 |  3.70% |    47900 | hallam@gmail.com
  3.05% |    5 |  3.37% |    43652 | yding@cs.helsinki.fi
  3.66% |    6 |  2.68% |    34743 | dhc@dcrocker.net
  2.44% |    4 |  3.47% |    44982 | jsalowey@cisco.com
  2.44% |    4 |  2.11% |    27359 | sm@resistor.net
  2.44% |    4 |  2.03% |    26268 | ted.lemon@nominum.com
  2.44% |    4 |  2.01% |    26016 | joelja@bogus.com
  2.44% |    4 |  1.95% |    25313 | jari.arkko@piuha.net
  1.83% |    3 |  2.27% |    29410 | morrowc.lists@gmail.com
  1.83% |    3 |  2.01% |    25980 | abdussalambaryun@gmail.com
  1.83% |    3 |  1.83% |    23694 | paf@frobbit.se
  1.83% |    3 |  1.79% |    23217 | ben@nostrum.com
  1.83% |    3 |  1.56% |    20167 | ynir@checkpoint.com
  1.83% |    3 |  1.49% |    19314 | warren@kumari.net
  1.22% |    2 |  2.05% |    26509 | ed.lewis@neustar.biz
  1.83% |    3 |  1.42% |    18361 | hartmans@painless-security.com
  1.83% |    3 |  1.24% |    16039 | ajs@anvilwalrusden.com
  1.83% |    3 |  1.23% |    15972 | paul.hoffman@vpnc.org
  0.61% |    1 |  2.41% |    31232 | rjsparks@nostrum.com
  1.83% |    3 |  1.14% |    14763 | randy@psg.com
  1.22% |    2 |  1.68% |    21721 | suresh.krishnan@ericsson.com
  0.61% |    1 |  2.27% |    29379 | magnus.westerlund@ericsson.com
  1.22% |    2 |  1.42% |    18391 | doug.mtview@gmail.com
  1.22% |    2 |  1.40% |    18104 | arturo.servin@gmail.com
  1.22% |    2 |  1.36% |    17556 | narten@us.ibm.com
  1.22% |    2 |  1.35% |    17460 | carlosm3011@gmail.com
  1.22% |    2 |  1.27% |    16497 | kathleen.moriarty@emc.com
  1.22% |    2 |  1.19% |    15475 | fred@cisco.com
  1.22% |    2 |  1.02% |    13166 | brian@innovationslab.net
  1.22% |    2 |  0.86% |    11137 | aservin@lacnic.net
  1.22% |    2 |  0.70% |     9102 | jnc@mercury.lcs.mit.edu
  0.61% |    1 |  1.10% |    14193 | daedulus@btconnect.com
  0.61% |    1 |  0.85% |    10959 | presnick@qti.qualcomm.com
  0.61% |    1 |  0.83% |    10754 | dave@cridland.net
  0.61% |    1 |  0.81% |    10541 | shollenbeck@verisign.com
  0.61% |    1 |  0.78% |    10037 | chris.dearlove@baesystems.com
  0.61% |    1 |  0.74% |     9635 | tjc@ecs.soton.ac.uk
  0.61% |    1 |  0.73% |     9392 | mirja.kuehlewind@ikr.uni-stuttgart.de
  0.61% |    1 |  0.68% |     8857 | ford@isoc.org
  0.61% |    1 |  0.66% |     8528 | medel@globetel.com.ph
  0.61% |    1 |  0.61% |     7937 | barryleiba@computer.org
  0.61% |    1 |  0.59% |     7633 | hsantos@isdg.net
  0.61% |    1 |  0.59% |     7614 | scott.brim@gmail.com
  0.61% |    1 |  0.57% |     7422 | dromasca@avaya.com
  0.61% |    1 |  0.57% |     7367 | brian.e.carpenter@gmail.com
  0.61% |    1 |  0.55% |     7182 | housley@vigilsec.com
  0.61% |    1 |  0.54% |     7035 | nomcom-chair-2013@ietf.org
  0.61% |    1 |  0.53% |     6804 | adrian@olddog.co.uk
  0.61% |    1 |  0.52% |     6786 | jabley@hopcount.ca
  0.61% |    1 |  0.51% |     6609 | marka@isc.org
  0.61% |    1 |  0.51% |     6549 | johnl@taugh.com
  0.61% |    1 |  0.50% |     6442 | randy_presuhn@mindspring.com
  0.61% |    1 |  0.48% |     6250 | mehmet.ersue@nsn.com
  0.61% |    1 |  0.47% |     6147 | mnot@mnot.net
  0.61% |    1 |  0.46% |     5925 | turners@ieca.com
  0.61% |    1 |  0.45% |     5781 | johnl@iecc.com
  0.61% |    1 |  0.44% |     5733 | stephen.farrell@cs.tcd.ie
  0.61% |    1 |  0.44% |     5640 | ogud@ogud.com
  0.61% |    1 |  0.43% |     5549 | cabo@tzi.org
  0.61% |    1 |  0.41% |     5339 | dwm@xpasc.com
  0.61% |    1 |  0.40% |     5241 | drc@virtualized.org
  0.61% |    1 |  0.40% |     5212 | iad@ietf.org
--------+------+--------+----------+------------------------
100.00% |  164 |100.00% |  1295092 | Total


From arturo.servin@gmail.com  Fri Jun 21 02:07:00 2013
Return-Path: <arturo.servin@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 39DF911E8171 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 02:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ptSv9f1EjZoE for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 02:06:59 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5529A21F9AEB for <ietf@ietf.org>; Fri, 21 Jun 2013 02:06:59 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so7512934pbc.15 for <ietf@ietf.org>; Fri, 21 Jun 2013 02:06:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=T4eqzvFQdOkgohbh/1Zt96hGxPE9gVfSvFasXAMYp/Y=; b=UYLs4pn6bgRZLCkgO4Ram7BGicDh6Df4fUIvJe5qJFf2niL6wCut+fZD6dqveK7AN+ nzFHUL/qr34pqe6r9q6YVwxfddpNJF7mgXJWxnPR8sGAVGkNYQekawkZi0h/kMhfDMb5 1p8O84aWjC4WDh4gPii2akz5haTVERKT0++J28ABjwzaS8uPvZ83eYx9KIFNnSnXyASC kmuSxDC/2MK5lIpS/8S29vIj632OyrNazcXEaifgWspay84NgyxpYjMPPmaG2VRcvc2s 0SR3UIi+pOO9T1joshrd1l+xgvZYA44smK1hkMMKe5P5NXH/PPwbonqoeTA/OO0x04lB zB7w==
X-Received: by 10.66.135.18 with SMTP id po18mr15594304pab.1.1371805618996; Fri, 21 Jun 2013 02:06:58 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([202.183.168.2]) by mx.google.com with ESMTPSA id vu5sm4862505pab.10.2013.06.21.02.06.56 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Jun 2013 02:06:57 -0700 (PDT)
Message-ID: <51C417AE.6050902@gmail.com>
Date: Fri, 21 Jun 2013 16:06:54 +0700
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Policy makers
References: <20130620180046.12461.96111.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130620113213.0ce9b408@resistor.net>
In-Reply-To: <6.2.5.6.2.20130620113213.0ce9b408@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Fri, 21 Jun 2013 09:07:00 -0000

On 6/21/13 2:38 AM, SM wrote:
> At 11:00 20-06-2013, The IAOC wrote:
>> series of events and programs in South America. This would include:
>>
>>   - Increasing the IETF Fellows and policy makers from the region
>
> I don't see any policy makers reviewing Internet-Drafts.  I don't see
> any policy makers writing IETF RFCs.  Policy makers do not usually
> participate in IETF discussions.
>
    You haven't and probably won't. But they were invited (IMHO) not to
participate in the IETF to review or write I+D but to know the IETF,
what we do, how we work; and how governments and the IETF can collaborate.

    I think that ISOC should continue with that effort.

Regards,
as

    

From abdussalambaryun@gmail.com  Fri Jun 21 04:45:55 2013
Return-Path: <abdussalambaryun@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 54ECA21E80EE for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 04:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.044,  BAYES_00=-2.599, 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 uR6uwyNPYssP for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 04:45:54 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id A2C0621E80F1 for <ietf@ietf.org>; Fri, 21 Jun 2013 04:45:54 -0700 (PDT)
Received: by mail-pa0-f43.google.com with SMTP id hz11so7754100pad.30 for <ietf@ietf.org>; Fri, 21 Jun 2013 04:45:54 -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=Sv0CLyAdeQjMsR+b/PMuUsVL7f3FHFNIOxUTsNkR7Hk=; b=JvJf0yvCWvbohnHd30967UpTNE4uCb0vSTDqvOg1tDvyoth1jd4RA6jto1bsESXeHn iwsGhC0kOLw4iV2DLYCo1tn+NgHREuPQkZr6UQ7FSUSXxyUaSSbpMkdCx6zg1TZZAbcT Bv65gFPti14llb1dEMNRSwH22wag5PtwSTmqX5b7O15KkrpDPkyukBC0POkZju4mVTzN mtEvaWhywYYwA3zd3Q8Ex56+hrrF59WdTi1/DP7i7OlhPax0MnKH4h3clQMoKvCYnu6k ML0ws1z97FvLpFtAlvc2XLv/sUN9rymoYujW4R3CRk0coA14xHo7wq9/fECxABVWY0mk c+rg==
MIME-Version: 1.0
X-Received: by 10.68.203.103 with SMTP id kp7mr11639193pbc.165.1371815154360;  Fri, 21 Jun 2013 04:45:54 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Fri, 21 Jun 2013 04:45:54 -0700 (PDT)
In-Reply-To: <201306140453.r5E4r4q7002802@rotala.raleigh.ibm.com>
References: <201306140453.r5E4r4q7002802@rotala.raleigh.ibm.com>
Date: Fri, 21 Jun 2013 12:45:54 +0100
Message-ID: <CADnDZ8-_KsQnZYy7tih5feNr7DMXJKtivfxw5BSRTmCHM7FsmQ@mail.gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <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: Fri, 21 Jun 2013 11:45:55 -0000

* For Week 25 in 2013
About 17 subjects discussed, about 6 IETF LCs, about 3 Gen-Art Review.

On Fri, Jun 21, 2013 at 5:53 AM, Thomas Narten <narten@us.ibm.com> wrote:
>
> Messages | Bytes | Who
> --------+------+--------+----------+------------------------
> 1.83% | 3 | 2.01% | 25980 | abdussalambaryun@gmail.com
>
3 messages in same subject <IETF Diversity>

-------------------------------------------------------------------------------------------------
*For Week 24 in 2013

AB> total number of discussed subjects/threads on the IETF list are about 20.
AB> total number of discussed IETF LCs in this week are about 7.

On 6/14/13, Thomas Narten <narten@us.ibm.com> wrote:
> Total of 158 messages in the last 7 days.
>
> script run at: Fri Jun 14 00:53:03 EDT 2013
>
>     Messages   |      Bytes        | Who
> --------+------+--------+----------+------------------------
>   3.16% |    5 |  4.16% |    52840 | abdussalambaryun@gmail.com

AB> abdussalambaryun@gmail.com contributed to 4 subjects on the IETF
list, 2 IETF LC I-Ds and 2 general subjects.

--------------------------------------------------------------------------------------------------

Please note that I consider mentioning my input number with email
address in the list without number of subject as a comment on my input
to IETF list, therefore, I will have to reply, only if you exclude my
address from your report, or if you add the number of subjects at
least. Please note that I have not given any one a
permission/allowance to comment/count on my number of inputs, and that
I requested that the subject number to be added.

 Overall, if you have a permission from the community for this report
please provide me with a reference.

Best Regards
AB

From stbryant@cisco.com  Fri Jun 21 06:00:34 2013
Return-Path: <stbryant@cisco.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 A219021E8112 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 06:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.375
X-Spam-Level: 
X-Spam-Status: No, score=-110.375 tagged_above=-999 required=5 tests=[AWL=0.224, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 uaahhOtBAVcF for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 06:00:29 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id B7BA921E810B for <ietf@ietf.org>; Fri, 21 Jun 2013 06:00:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=636; q=dns/txt; s=iport; t=1371819625; x=1373029225; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=jolW6yr/bAIPORDQwwp+3r1JAUfR2U1iHcJby595DvA=; b=XTbkTKBXdL3dh0XP/1iTabdPrbNlZO2ZIXSjzBiX4809k9FuT+Pubgts Zd/67VOV0Ahn1KaN7QtkrBYkPbygpmi34YLL1RRfDtGG3V6ZqXbAVqBbv Reqs3VWRNhEs8TIqgnU23OMYZ+/Jm33FB3IWeMeWB7BdOmR8vRXbea7yn 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq0LAPhNxFGQ/khR/2dsb2JhbABbgwmDNrxvAQMBAwGBARZ0giQBAQQ4QAEQCyEWDwkDAgECAUUGDQEFAgEBEId6vGSPSQeDYQOXQ5FEgxA
X-IronPort-AV: E=Sophos;i="4.87,913,1363132800"; d="scan'208";a="14420589"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 21 Jun 2013 13:00:23 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r5LD0LOY020200 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jun 2013 13:00:21 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r5LD0KIx019729; Fri, 21 Jun 2013 14:00:20 +0100 (BST)
Message-ID: <51C44E64.1050203@cisco.com>
Date: Fri, 21 Jun 2013 14:00:20 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
References: <201306140453.r5E4r4q7002802@rotala.raleigh.ibm.com> <CADnDZ8-_KsQnZYy7tih5feNr7DMXJKtivfxw5BSRTmCHM7FsmQ@mail.gmail.com>
In-Reply-To: <CADnDZ8-_KsQnZYy7tih5feNr7DMXJKtivfxw5BSRTmCHM7FsmQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: Fri, 21 Jun 2013 13:00:34 -0000

AB

Thomas started posting these weekly reports many years
ago as a service to the community to remind us all that
posting to ietf@ietf.org contributes to the information
and work overload of the IETF community as a whole.

The numbers are a reminder to think carefully about what
you send to the list and to only send what you consider
to be sufficiently important that the community as
a whole needs to be aware of it.

Most members of the IETF community  try their best to
minimize their so called "Narten Number". Many
regard these postings as a useful service, and I for
one, thank him for doing it.

- Stewart

From loa@pi.nu  Fri Jun 21 06:04:23 2013
Return-Path: <loa@pi.nu>
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 6F2E121E8106 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 06:04:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 KqOUt2pI6zcB for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 06:04:17 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2F58D21E8113 for <ietf@ietf.org>; Fri, 21 Jun 2013 06:04:11 -0700 (PDT)
Received: from [95.209.177.12] (95.209.177.12.bredband.tre.se [95.209.177.12]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 68923180121E for <ietf@ietf.org>; Fri, 21 Jun 2013 15:03:59 +0200 (CEST)
Message-ID: <51C44F3F.6000100@pi.nu>
Date: Fri, 21 Jun 2013 15:03:59 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Weekly posting summary for ietf@ietf.org
References: <201306140453.r5E4r4q7002802@rotala.raleigh.ibm.com> <CADnDZ8-_KsQnZYy7tih5feNr7DMXJKtivfxw5BSRTmCHM7FsmQ@mail.gmail.com> <51C44E64.1050203@cisco.com>
In-Reply-To: <51C44E64.1050203@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Fri, 21 Jun 2013 13:04:23 -0000

+1 (and that will be my only posting on this subject, I suggest
that if you don't get Stewart's drift you stop sending mails to
the list until you do)

/Loa

On 2013-06-21 15:00, Stewart Bryant wrote:
>
> AB
>
> Thomas started posting these weekly reports many years
> ago as a service to the community to remind us all that
> posting to ietf@ietf.org contributes to the information
> and work overload of the IETF community as a whole.
>
> The numbers are a reminder to think carefully about what
> you send to the list and to only send what you consider
> to be sufficiently important that the community as
> a whole needs to be aware of it.
>
> Most members of the IETF community  try their best to
> minimize their so called "Narten Number". Many
> regard these postings as a useful service, and I for
> one, thank him for doing it.
>
> - Stewart

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From hannes.tschofenig@gmx.net  Fri Jun 21 07:48:45 2013
Return-Path: <hannes.tschofenig@gmx.net>
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 D02A321E8128 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 07:48:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 gE67Hfp5I9qw for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 07:48:41 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 50B0121E8126 for <ietf@ietf.org>; Fri, 21 Jun 2013 07:48:41 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.32]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MLlbJ-1UqraK36GZ-000re5 for <ietf@ietf.org>; Fri, 21 Jun 2013 16:48:35 +0200
Received: (qmail invoked by alias); 21 Jun 2013 14:48:35 -0000
Received: from host-94-101-1-228.igua.fi (EHLO [192.168.4.115]) [94.101.1.228] by mail.gmx.net (mp032) with SMTP; 21 Jun 2013 16:48:35 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19L7fxAvrhL3V/aBvwpjqcaoxzR414uBRbzRq2xx3 9q6hqMf4+F/wOW
Subject: Re: Policy makers
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <51C417AE.6050902@gmail.com>
Date: Fri, 21 Jun 2013 17:48:34 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <47F8BB06-CFD0-43C7-85F7-576AC131F5C1@gmx.net>
References: <20130620180046.12461.96111.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130620113213.0ce9b408@resistor.net> <51C417AE.6050902@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
X-Pgp-Agent: GPGMail 1.4.1
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 0
Cc: 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: Fri, 21 Jun 2013 14:48:45 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

A minor remark: The IAB had been interacting with different types of =
government bodies for a longer time.=20
While some of these efforts are not so visible just have a look at the =
upcoming IETF meeting. There is a BOF about STIR=20
and the problem statement document provides some context to activities =
that have received attention by the regulatory community.=20
Here is the pointer: =
http://tools.ietf.org/html/draft-peterson-secure-origin-ps-00

Of course, it would be a bit too much to expect regulators to work on =
the detailed protocol proposals. We do, however, point them to our work =
and some of them (either though ISOC or by themselves) will participate =
at the upcoming IETF meeting.

You can easily find many other examples in the IETF, such as ECRIT =
(emergency services), PAWS (about whitespace database access), or MILE =
(about security incident information sharing). On the last item we are =
organizing a workshop on the Friday before the IETF meeting and the =
topic itself is currently high on the agenda of CyberSecurity activities =
by various governments. Here is a link to the workshop info: =
http://siis.realmv6.org/

Ciao
Hannes

On Jun 21, 2013, at 12:06 PM, Arturo Servin wrote:

>=20
> On 6/21/13 2:38 AM, SM wrote:
>> At 11:00 20-06-2013, The IAOC wrote:
>>> series of events and programs in South America. This would include:
>>>=20
>>>  - Increasing the IETF Fellows and policy makers from the region
>>=20
>> I don't see any policy makers reviewing Internet-Drafts.  I don't see
>> any policy makers writing IETF RFCs.  Policy makers do not usually
>> participate in IETF discussions.
>>=20
>    You haven't and probably won't. But they were invited (IMHO) not to
> participate in the IETF to review or write I+D but to know the IETF,
> what we do, how we work; and how governments and the IETF can =
collaborate.
>=20
>    I think that ISOC should continue with that effort.
>=20
> Regards,
> as
>=20
>=20

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJRxGfCAAoJEGhJURNOOiAtfzcH/3jfmv2I9yf5JqUTkxWrzgCC
o+a69268JLzSSkqjJ3AoJeQTQpjTAI3FrvlJzJgW8+b5a1W0FFnlIVubSaLVCFqt
h1kbtFiQJCzQyra6qBP2eUUX8l26eQg1xwVhgrkIqgYSEfItW93aQt2Rzyodmb7O
R7XTdoDy+LwgtG+CL91bABNer4GBAvSlhgiuqpZLSjTmbMYONpbPPUw6xNtm9Nzz
S6T4N19po9mTtEMrH27bbiU1QioMoRSvTXuO0DCaYFwksMCyi+Lx8l9vvO0lgl/3
zxoxeaXss43U1YN//JGiKZq5BSIKeGmkvE3jIeFqBL8X8/+cauTXJ/bA0PsEOiI=3D
=3DXWQ4
-----END PGP SIGNATURE-----

From abdussalambaryun@gmail.com  Fri Jun 21 07:48:48 2013
Return-Path: <abdussalambaryun@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 35AA721E812C for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 07:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level: 
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.042,  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 XBo27EjU2FLg for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 07:48:47 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 74BF521E812A for <ietf@ietf.org>; Fri, 21 Jun 2013 07:48:47 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj3so7997230pad.28 for <ietf@ietf.org>; Fri, 21 Jun 2013 07:48:42 -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=Lfw2xxoC1vq6LyrNIc+LxbOWL84dEmcJzc+IqfztiK8=; b=dhMmgrrjIcyj5CP3EX00ffT3QuPe+gh7N5scZTT2CWFBOmVH658oMqA793Xdm2/1gK 9b2xIDxIPndRt63bTA3JS7X96fh0uYRD1IvZ+J74UsafIXgnH4yoJwkzROsQQ3smbC26 WuY5mSWznH0uQ5wX0980ydTfMi27od4KvhemKClp4J/imeTDyt4a1zBlEPfiZgKglckC PmxrWfvZRIk7ri5W2s2wFfoWkrxY83EpndEPQ/lSWdF8VGtOX+ZuBbZECaHCJwL8NGhO yFTGT80wOrlFySV1yAPkL0XHCd7H7vJJIcTFDJpV4MnNsoQAP3WGyvqFm2enTTnBm70z Nwvg==
MIME-Version: 1.0
X-Received: by 10.68.52.10 with SMTP id p10mr12833073pbo.92.1371826121988; Fri, 21 Jun 2013 07:48:41 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Fri, 21 Jun 2013 07:48:41 -0700 (PDT)
In-Reply-To: <51C44E64.1050203@cisco.com>
References: <201306140453.r5E4r4q7002802@rotala.raleigh.ibm.com> <CADnDZ8-_KsQnZYy7tih5feNr7DMXJKtivfxw5BSRTmCHM7FsmQ@mail.gmail.com> <51C44E64.1050203@cisco.com>
Date: Fri, 21 Jun 2013 15:48:41 +0100
Message-ID: <CADnDZ8-GkyGN4an+NfyncC07ov5RnYrvBjYxEC7VWS5TsuPQSQ@mail.gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: stbryant <stbryant@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec54307a0b1e03304dfab2821
Cc: Thomas Narten <narten@us.ibm.com>, ietf <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: Fri, 21 Jun 2013 14:48:48 -0000

--bcaec54307a0b1e03304dfab2821
Content-Type: text/plain; charset=ISO-8859-1

Hi Stewart,

I don't have any problem with the report/reminder only that it has missing
important information. The subjects of discussions are not counted, so I
counted them. Also the report does not distinguish between general-posting
and replying to IETF LCs.

AB


On Fri, Jun 21, 2013 at 2:00 PM, Stewart Bryant <stbryant@cisco.com> wrote:

>
> AB
>
> Thomas started posting these weekly reports many years
> ago as a service to the community to remind us all that
> posting to ietf@ietf.org contributes to the information
> and work overload of the IETF community as a whole.
>
> The numbers are a reminder to think carefully about what
> you send to the list and to only send what you consider
> to be sufficiently important that the community as
> a whole needs to be aware of it.
>
> Most members of the IETF community  try their best to
> minimize their so called "Narten Number". Many
> regard these postings as a useful service, and I for
> one, thank him for doing it.
>
> - Stewart
>

--bcaec54307a0b1e03304dfab2821
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Stewart,</div><div>=A0</div><div>I don&#39;t have =
any problem with the report/reminder only that it has missing important=A0i=
nformation. The subjects of discussions are not counted, so I counted them.=
 Also the report does not distinguish between general-posting and replying =
to IETF LCs.</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Fri, Jun 21, 2013 at 2:00 PM, Stewart Bryant <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:stbryant@cisco.com" target=3D"_blank">stbr=
yant@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
AB<br>
<br>
Thomas started posting these weekly reports many years<br>
ago as a service to the community to remind us all that<br>
posting to <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org=
</a> contributes to the information<br>
and work overload of the IETF community as a whole.<br>
<br>
The numbers are a reminder to think carefully about what<br>
you send to the list and to only send what you consider<br>
to be sufficiently important that the community as<br>
a whole needs to be aware of it.<br>
<br>
Most members of the IETF community =A0try their best to<br>
minimize their so called &quot;Narten Number&quot;. Many<br>
regard these postings as a useful service, and I for<br>
one, thank him for doing it.<span class=3D"HOEnZb"><font color=3D"#888888">=
<br>
<br>
- Stewart<br>
</font></span></blockquote></div><br></div>

--bcaec54307a0b1e03304dfab2821--

From richard@shockey.us  Fri Jun 21 08:25:03 2013
Return-Path: <richard@shockey.us>
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 6F34C11E819D for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 08:25:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.103
X-Spam-Level: 
X-Spam-Status: No, score=-102.103 tagged_above=-999 required=5 tests=[AWL=0.496, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 pZWqDK6fyjTN for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 08:24:59 -0700 (PDT)
Received: from oproxy12-pub.bluehost.com (oproxy12-pub.bluehost.com [50.87.16.10]) by ietfa.amsl.com (Postfix) with SMTP id 1340211E819C for <ietf@ietf.org>; Fri, 21 Jun 2013 08:24:59 -0700 (PDT)
Received: (qmail 1164 invoked by uid 0); 21 Jun 2013 15:24:36 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy12.bluehost.com with SMTP; 21 Jun 2013 15:24:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:To:From; bh=jveUlaFNg7eoUXL0kJuEvFOboBmQlBSVAWalq3nmBQ4=;  b=nZzy3v/KSBlH9PS+XoS6Mj5q+b/p1c43xf29MEoa+Zd4eGRhoZY7sOhwnBqYLMXm3n4urG1MM1sJBkxYVxg/qIte9xvieThebUzktn2MUpsWXYMG5saZeRseLffHPH0I;
Received: from [72.66.111.124] (port=51883 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.80) (envelope-from <richard@shockey.us>) id 1Uq3CV-0003QI-Bg; Fri, 21 Jun 2013 09:24:35 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Hannes Tschofenig'" <hannes.tschofenig@gmx.net>, <ietf@ietf.org>
References: <20130620180046.12461.96111.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20130620113213.0ce9b408@resistor.net>	<51C417AE.6050902@gmail.com> <47F8BB06-CFD0-43C7-85F7-576AC131F5C1@gmx.net>
In-Reply-To: <47F8BB06-CFD0-43C7-85F7-576AC131F5C1@gmx.net>
Subject: RE: Policy makers
Date: Fri, 21 Jun 2013 11:24:33 -0400
Message-ID: <002301ce6e93$6f543300$4dfc9900$@shockey.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJmw5Rt4G1a8Slq7O4oJKdx6uvAJwJYRZ5CAV/sZTECmap3jZfdDwOg
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 72.66.111.124 authed with richard@shockey.us}
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: Fri, 21 Jun 2013 15:25:03 -0000

+1  

IETF RFC's are quoted in Government Policy documents all the time.

The issue in STIR is particularly distressing. The regulators are actively
asking for help here and I'm convinced the IETF can make a substantial
contribution here. 

http://www.cs.columbia.edu/~hgs/papers/2013/2013-source-identity.pptx

PAWS is a particularly good example of where some policy people are actively
and productively participating  Providing insight as well as requirements to
the protocol development. 

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Hannes Tschofenig
Sent: Friday, June 21, 2013 10:49 AM
To: Arturo Servin
Cc: ietf@ietf.org
Subject: Re: Policy makers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

A minor remark: The IAB had been interacting with different types of
government bodies for a longer time. 
While some of these efforts are not so visible just have a look at the
upcoming IETF meeting. There is a BOF about STIR and the problem statement
document provides some context to activities that have received attention by
the regulatory community. 
Here is the pointer:
http://tools.ietf.org/html/draft-peterson-secure-origin-ps-00

Of course, it would be a bit too much to expect regulators to work on the
detailed protocol proposals. We do, however, point them to our work and some
of them (either though ISOC or by themselves) will participate at the
upcoming IETF meeting.

You can easily find many other examples in the IETF, such as ECRIT
(emergency services), PAWS (about whitespace database access), or MILE
(about security incident information sharing). On the last item we are
organizing a workshop on the Friday before the IETF meeting and the topic
itself is currently high on the agenda of CyberSecurity activities by
various governments. Here is a link to the workshop info:
http://siis.realmv6.org/

Ciao
Hannes

On Jun 21, 2013, at 12:06 PM, Arturo Servin wrote:

> 
> On 6/21/13 2:38 AM, SM wrote:
>> At 11:00 20-06-2013, The IAOC wrote:
>>> series of events and programs in South America. This would include:
>>> 
>>>  - Increasing the IETF Fellows and policy makers from the region
>> 
>> I don't see any policy makers reviewing Internet-Drafts.  I don't see 
>> any policy makers writing IETF RFCs.  Policy makers do not usually 
>> participate in IETF discussions.
>> 
>    You haven't and probably won't. But they were invited (IMHO) not to 
> participate in the IETF to review or write I+D but to know the IETF, 
> what we do, how we work; and how governments and the IETF can collaborate.
> 
>    I think that ISOC should continue with that effort.
> 
> Regards,
> as
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJRxGfCAAoJEGhJURNOOiAtfzcH/3jfmv2I9yf5JqUTkxWrzgCC
o+a69268JLzSSkqjJ3AoJeQTQpjTAI3FrvlJzJgW8+b5a1W0FFnlIVubSaLVCFqt
h1kbtFiQJCzQyra6qBP2eUUX8l26eQg1xwVhgrkIqgYSEfItW93aQt2Rzyodmb7O
R7XTdoDy+LwgtG+CL91bABNer4GBAvSlhgiuqpZLSjTmbMYONpbPPUw6xNtm9Nzz
S6T4N19po9mTtEMrH27bbiU1QioMoRSvTXuO0DCaYFwksMCyi+Lx8l9vvO0lgl/3
zxoxeaXss43U1YN//JGiKZq5BSIKeGmkvE3jIeFqBL8X8/+cauTXJ/bA0PsEOiI=
=XWQ4
-----END PGP SIGNATURE-----


From jcurran@istaff.org  Fri Jun 21 08:46:42 2013
Return-Path: <jcurran@istaff.org>
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 841C821F9D09 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 08:46:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 knFb732CUyZw for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 08:46:36 -0700 (PDT)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by ietfa.amsl.com (Postfix) with ESMTP id A3C9621F9C4D for <ietf@ietf.org>; Fri, 21 Jun 2013 08:46:36 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1Uq3Xn-000LeM-0h; Fri, 21 Jun 2013 15:46:35 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/NdkNjdtYc+Iq1j0lKS5sg
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] IETF, ICANN and Whois (Was Re: Last Call:	<draft-housley-rfc2050bis-01.txt>	(The Internet Numbers Registry	System) to Informational RFC)
From: John Curran <jcurran@istaff.org>
In-Reply-To: <BB52D64B1827B309BF7D9629@JcK-HP8200.jck.com>
Date: Fri, 21 Jun 2013 11:46:34 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <C13DA83D-FC43-4243-897F-3E6B17B3434D@istaff.org>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <51C21498.3020008@gmail.com> <C8EEFB02-5637-4247-98F6-3B414E045E0E@kumari.net> <BB52D64B1827B309BF7D9629@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Cc: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, ietf <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: Fri, 21 Jun 2013 15:46:42 -0000

On Jun 19, 2013, at 8:43 PM, John C Klensin <john-ietf@jck.com> wrote:
> ...
> The point, Warren (and others) is that all of these are "ICANN
> doing technical stuff" and even "technical standards" in a broad
> sense of that term.   Some of it is stuff that the IETF really
> should not want to do (I'm tempted to say "avoid like the
> plague").  Some of it probably should be here.  As an outsider
> to both, there is a certain amount of stuff that has ended up in
> SSAC and even RSAC that might have been better located in SAAG
> or some IETF or NOG DNS operations group.  I certainly won't
> argue that we've got the balance right.  And I think it is
> unfortunate that the very early redesign of the original PSO had
> the side effect of making it hard or impossible to work out
> optimal boundaries and cross-review mechanisms with ICANN and
> that we are instead having a discussion more than a dozen years
> later about keeping ICANN from doing technical work or making
> standards.

+1  (specifically -  it is unfortunate that a more operational
ICANN / IETF liaison did not emerge via the PSO structure)

> Let's not complicate things further by making the assumption
> that anything that reasonably looks like "technical stuff"
> belongs in the IETF and not in ICANN.  It is likely to just make
> having the right conversations even harder.

I believe that policy issues that are under active discussion in
ICANN can also be discussed in the IETF, but there is recognition 
that ICANN is likely the more appropriate place to lead the process
of consensus development and approval.

I believe that protocol development that is under active discussion
at the IETF can also discussed at ICANN, but there is recognition 
that the IETF is likely the appropriate place to lead the process 
of consensus development and approval.

Note that there are lots of things that are neither policy nor 
protocols (e.g. operational best practices and guidelines) and
while one can claim that either forum is valid, it really depends
on the particular situation and where those folks who are closest
to the problem actually choose to go with it (and depending on the 
protocol, that might not be either of the above...)

/John

Disclaimer: My views alone - YMMV.










From hsantos@isdg.net  Fri Jun 21 08:53:51 2013
Return-Path: <hsantos@isdg.net>
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 E8EEE21F9FD0 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 08:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.167
X-Spam-Level: 
X-Spam-Status: No, score=-102.167 tagged_above=-999 required=5 tests=[AWL=-0.432, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
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 ujeSivWithXo for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 08:53:43 -0700 (PDT)
Received: from mail.winserver.com (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0383D21F9E97 for <ietf@ietf.org>; Fri, 21 Jun 2013 08:53:42 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2790; t=1371830020; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=HH8lfHl 9KeqVr2hoN98agckJDFU=; b=gE2jP27eis1rVVBlnkD4ber20zxtr4FJQWpFOVh ytcWaAyrBDcNDjHweuYuFO9LNpnEmz9TZFIrp+/GjoXLdLSMbkCF/ZQ3oFPj31rl ndi48emW6bhv2Can4ZJwLAUxgsE+wUX+0g20Dau7BJovEErN15yxbPLlU2kzYalu BQxU=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 21 Jun 2013 11:53:40 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2587563530.6477.1932; Fri, 21 Jun 2013 11:53:39 -0400
Message-ID: <51C47669.1070106@isdg.net>
Date: Fri, 21 Jun 2013 11:51:05 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
References: <201306140453.r5E4r4q7002802@rotala.raleigh.ibm.com> <CADnDZ8-_KsQnZYy7tih5feNr7DMXJKtivfxw5BSRTmCHM7FsmQ@mail.gmail.com> <51C44E64.1050203@cisco.com> <CADnDZ8-GkyGN4an+NfyncC07ov5RnYrvBjYxEC7VWS5TsuPQSQ@mail.gmail.com>
In-Reply-To: <CADnDZ8-GkyGN4an+NfyncC07ov5RnYrvBjYxEC7VWS5TsuPQSQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, ietf <ietf@ietf.org>, stbryant <stbryant@cisco.com>
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: Fri, 21 Jun 2013 15:53:51 -0000

These are valid points. For a long time, I used a public forum support 
reporter for our support process which categorized daily and hourly 
messaging patterns, hottest threads and topics and reply efficiency 
concepts. Basically to see how many messages were replied to in general 
and how many were replied by the "technical support staff" (measured 
against a list of certain responders) and how many were missed (ignored) 
which you strived to minimized.   In the past, I considered using this 
reporter here just to see, but it already had a posting summary and it 
would be viewed more as an redundant annoyance.  Plus, I certainly do no 
want to step on anyone "shoes."

In my view, it offers little other than as other stated to mind your 
number of post, but clearly that doesn't apply to all folks. If you have 
something to say, this is not going to deter you.  Others may feel 
otherwise, but these folks don't care what you think and rightly so.

Based on what I see, most messages are during weekdays and during the 
day, normal working hours I suppose.  It does cut down by the weekend. 
While there is a high ignorance factor at the particular individual 
level, most messages have a high reply factor. IOW, most messages are 
not ignored.  Of course, that may just mean when a message is not 
interesting, it gets ignored. There is also a "Shutdown" factor too - 
when a certain individual post, people tend to stop posting. But I think 
overall, the "SUPPORT" factor per se is pretty good here and in the most 
IETF forums I've participating in. However, it does depend on who is 
doing the postings and this fact shouldn't be a surprise.


--
HLS

On 6/21/2013 10:48 AM, Abdussalam Baryun wrote:
> Hi Stewart,
>
> I don't have any problem with the report/reminder only that it has missing
> important information. The subjects of discussions are not counted, so I
> counted them. Also the report does not distinguish between general-posting
> and replying to IETF LCs.
>
> AB
>
>
> On Fri, Jun 21, 2013 at 2:00 PM, Stewart Bryant <stbryant@cisco.com> wrote:
>
>>
>> AB
>>
>> Thomas started posting these weekly reports many years
>> ago as a service to the community to remind us all that
>> posting to ietf@ietf.org contributes to the information
>> and work overload of the IETF community as a whole.
>>
>> The numbers are a reminder to think carefully about what
>> you send to the list and to only send what you consider
>> to be sufficiently important that the community as
>> a whole needs to be aware of it.
>>
>> Most members of the IETF community  try their best to
>> minimize their so called "Narten Number". Many
>> regard these postings as a useful service, and I for
>> one, thank him for doing it.
>>
>> - Stewart
>>
>


From farmer@umn.edu  Fri Jun 21 09:50:33 2013
Return-Path: <farmer@umn.edu>
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 BEAB021F9E94 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 09:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 RgbGkT+z7omQ for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 09:50:26 -0700 (PDT)
Received: from vs-a.tc.umn.edu (vs-a.tc.umn.edu [134.84.135.107]) by ietfa.amsl.com (Postfix) with ESMTP id F3D0F21F9E7D for <ietf@ietf.org>; Fri, 21 Jun 2013 09:50:24 -0700 (PDT)
Received: from mail-gh0-f169.google.com (mail-gh0-f169.google.com [209.85.160.169]) by vs-a.tc.umn.edu (UMN smtpd) with ESMTP for <ietf@ietf.org>; Fri, 21 Jun 2013 11:50:23 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-gh0-f169.google.com [209.85.160.169] #+LO+TR
X-Umn-Classification: local
Received: by mail-gh0-f169.google.com with SMTP id r1so2165837ghr.28 for <ietf@ietf.org>; Fri, 21 Jun 2013 09:50:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:reply-to:organization:user-agent:mime-version :to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=crS+iCMaAZZRrstcurMeASEYoGLh4OLgieI1kl5qQVQ=; b=dcG/8fS/ouwUdzgge3Xwci+soRHn0cjyG2AH5x59SRVwR+Abx4Cov8tAOHl4qU+75t 1sAX6ubMHBetKGCaQ1O7zjGGTyHUEsGuG18LgPoNFxmEEsB1eChvlqdMXaFQYSxyyr99 Zuvq75x2uyg053oHlWj/ev1+QrmLXZ/bdQydg2s6SviesBrfPkP8+qaKV50LDi2OThxS 0iNzHYOHiMqQdqR8+vVyLyOu8TBINnbl4Fqt24CficUFnTaLDNBd0spQjSB3DDqrdDFv g2w6BUJVohHvtg/nrt+BhOeCELU/mNu/Kted3o24vPVzyiLCLZgRRzQaWCWyBiD+5pGX 2NBw==
X-Received: by 10.236.148.163 with SMTP id v23mr7936911yhj.176.1371833423424;  Fri, 21 Jun 2013 09:50:23 -0700 (PDT)
X-Received: by 10.236.148.163 with SMTP id v23mr7936903yhj.176.1371833423335;  Fri, 21 Jun 2013 09:50:23 -0700 (PDT)
Received: from x-128-101-233-51.uofm-secure.wireless.umn.edu ([2607:ea00:104:2000:bd7b:7200:9906:ccd5]) by mx.google.com with ESMTPSA id l39sm9446936yhn.26.2013.06.21.09.50.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Jun 2013 09:50:22 -0700 (PDT)
Message-ID: <51C4844E.6040109@umn.edu>
Date: Fri, 21 Jun 2013 11:50:22 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: John Curran <jcurran@istaff.org>
Subject: Re: [IETF] IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry	System) to Informational RFC)
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <51C21498.3020008@gmail.com> <C8EEFB02-5637-4247-98F6-3B414E045E0E@kumari.net> <BB52D64B1827B309BF7D9629@JcK-HP8200.jck.com> <C13DA83D-FC43-4243-897F-3E6B17B3434D@istaff.org>
In-Reply-To: <C13DA83D-FC43-4243-897F-3E6B17B3434D@istaff.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQn1wMAwHY6kOcPmnmdo+tOOLR+XkI63QgxzXOlvEgYjT5bVWFLxuwCIDfyXPhvCKxlX98RIepA3sUUS5IKl0OC8FxT1n+MnnVvdIBqLM5d0MRouGKiJoH/Hth6CK7cA5AGMEQcE
Cc: John C Klensin <john-ietf@jck.com>, ietf <ietf@ietf.org>, =?ISO-8859-1?Q?Patrik_F=E4ltstr?= =?ISO-8859-1?Q?=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
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, 21 Jun 2013 16:50:33 -0000

On 6/21/13 10:46 , John Curran wrote:

> I believe that policy issues that are under active discussion in
> ICANN can also be discussed in the IETF, but there is recognition
> that ICANN is likely the more appropriate place to lead the process
> of consensus development and approval.
>
> I believe that protocol development that is under active discussion
> at the IETF can also discussed at ICANN, but there is recognition
> that the IETF is likely the appropriate place to lead the process
> of consensus development and approval.
>
> Note that there are lots of things that are neither policy nor
> protocols (e.g. operational best practices and guidelines) and
> while one can claim that either forum is valid, it really depends
> on the particular situation and where those folks who are closest
> to the problem actually choose to go with it (and depending on the
> protocol, that might not be either of the above...)
>
> /John
>
> Disclaimer: My views alone - YMMV.

A version of these three paragraphs would make an excellent executive 
summary for the 2050bis Draft itself.


-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================

From dwm@xpasc.com  Fri Jun 21 11:10:44 2013
Return-Path: <dwm@xpasc.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 44B7021F9EAE for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 11:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.405
X-Spam-Level: 
X-Spam-Status: No, score=-4.405 tagged_above=-999 required=5 tests=[AWL=-1.806, BAYES_00=-2.599]
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 eKFr+9QLYAMg for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 11:10:38 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 5DBFD21F9E3D for <ietf@ietf.org>; Fri, 21 Jun 2013 11:10:38 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id C641F3F708 for <ietf@ietf.org>; Fri, 21 Jun 2013 18:10:36 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id r5LIAaaK011481 for <ietf@ietf.org>; Fri, 21 Jun 2013 11:10:36 -0700
Date: Fri, 21 Jun 2013 11:10:36 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Weekly posting summary for ietf@ietf.org
In-Reply-To: <CADnDZ8-GkyGN4an+NfyncC07ov5RnYrvBjYxEC7VWS5TsuPQSQ@mail.gmail.com>
Message-ID: <alpine.LRH.2.01.1306211042390.3884@egate.xpasc.com>
References: <201306140453.r5E4r4q7002802@rotala.raleigh.ibm.com> <CADnDZ8-_KsQnZYy7tih5feNr7DMXJKtivfxw5BSRTmCHM7FsmQ@mail.gmail.com> <51C44E64.1050203@cisco.com> <CADnDZ8-GkyGN4an+NfyncC07ov5RnYrvBjYxEC7VWS5TsuPQSQ@mail.gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.87-g7939dec
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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, 21 Jun 2013 18:10:44 -0000

It seems to me that you have missed the fact that the IETF is a
volunteer organization. The vast majority of us appreciate that
Thomas creates this summary. If you feel different information
would be useful, then create your own report and share the results,
to at least to see if your version is desired. Thomas provided
a link in the earlier discussion to his code so I imagine you could
use that as a starting point. 

You might also find it helpful to review the terms of the IETF Note Well
which you agreed to when you joined this list. You lose control of
anything you contribute so making demands about how that information
is used is pointless.

On Fri, 21 Jun 2013, Abdussalam Baryun wrote:

> Hi Stewart,
> 
> I don't have any problem with the report/reminder only that it has missing
> important information. The subjects of discussions are not counted, so I
> counted them. Also the report does not distinguish between general-posting
> and replying to IETF LCs.
> 
> AB
> 
> 
> On Fri, Jun 21, 2013 at 2:00 PM, Stewart Bryant <stbryant@cisco.com> wrote:
> 
> >
> > AB
> >
> > Thomas started posting these weekly reports many years
> > ago as a service to the community to remind us all that
> > posting to ietf@ietf.org contributes to the information
> > and work overload of the IETF community as a whole.
> >
> > The numbers are a reminder to think carefully about what
> > you send to the list and to only send what you consider
> > to be sufficiently important that the community as
> > a whole needs to be aware of it.
> >
> > Most members of the IETF community  try their best to
> > minimize their so called "Narten Number". Many
> > regard these postings as a useful service, and I for
> > one, thank him for doing it.
> >
> > - Stewart
> >
> 

From dhc@dcrocker.net  Fri Jun 21 11:22:44 2013
Return-Path: <dhc@dcrocker.net>
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 4B57911E80AD for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 11:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.573
X-Spam-Level: 
X-Spam-Status: No, score=-6.573 tagged_above=-999 required=5 tests=[AWL=0.026,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 gvpdDD3D630h for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 11:22:40 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D9EEC21F9F79 for <ietf@ietf.org>; Fri, 21 Jun 2013 11:22:39 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5LIMaMx017254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 21 Jun 2013 11:22:39 -0700
Message-ID: <51C499D9.2060402@dcrocker.net>
Date: Fri, 21 Jun 2013 11:22:17 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Policy makers
References: <20130620180046.12461.96111.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20130620113213.0ce9b408@resistor.net>	<51C417AE.6050902@gmail.com> <47F8BB06-CFD0-43C7-85F7-576AC131F5C1@gmx.net> <002301ce6e93$6f543300$4dfc9900$@shockey.us>
In-Reply-To: <002301ce6e93$6f543300$4dfc9900$@shockey.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 21 Jun 2013 11:22:39 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 21 Jun 2013 18:22:44 -0000

On 6/21/2013 8:24 AM, Richard Shockey wrote:
> The issue in STIR is particularly distressing. The regulators are actively
> asking for help here and I'm convinced the IETF can make a substantial
> contribution here.
>
> http://www.cs.columbia.edu/~hgs/papers/2013/2013-source-identity.pptx
...
> http://tools.ietf.org/html/draft-peterson-secure-origin-ps-00



STIR is having an interesting discussion about viable architectural 
models.

The basic problem it seeks to solve is validating the authorization to 
use a given telephone number in the SIP From field.

The main proposal is for two mechanisms to be operated in parallel, for 
all SIP-originated calls (and maybe all SS7>SIP calls):

    1. In-band signing - package a signature in a separate field, that 
carries the semantics of authorization for the From field number. The 
proposal calls for the public key to be in a credential, managed in the 
same loose-trust bushy-root CA anchor model used for Web TLS server 
authentication.

    2. Out-of-band caching - store signature information in a public 
cache, to provide recovery from transit handling that destroys the 
in-band signature, such as transit over SS7 (SIP-SS7-SIP).  The 
validation agent checks the cache whenever a valid signature is not 
present.  A proposal for this is at:

 
https://github.com/ekr/ietf-drafts/blob/master/draft-rescorla-callerid-fallback.txt


Draft charter for the activity:

    http://www.ietf.org/mail-archive/web/stir/current/msg00200.html


Mailing list:

    Mailing List: â€‹https://www.ietf.org/mailman/listinfo/stir


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From john-ietf@jck.com  Fri Jun 21 11:57:15 2013
Return-Path: <john-ietf@jck.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 49E4421F9F06 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 11:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 L6WyUq04tzZy for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 11:57:09 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 61D2321F9E61 for <ietf@ietf.org>; Fri, 21 Jun 2013 11:57:09 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uq6W9-0007wv-1Q; Fri, 21 Jun 2013 14:57:05 -0400
Date: Fri, 21 Jun 2013 14:56:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Curran <jcurran@istaff.org>
Subject: Re: [IETF] IETF, ICANN and Whois (Was Re: Last Call:	<draft-housley-rfc2050bis-01.txt>	(The Internet Numbers Registry	System) to Informational RFC)
Message-ID: <E9D4C327CAB3DE4FF73FDC2F@JcK-HP8200.jck.com>
In-Reply-To: <C13DA83D-FC43-4243-897F-3E6B17B3434D@istaff.org>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <51C21498.3020008@gmail.com> <C8EEFB02-5637-4247-98F6-3B414E045E0E@kumari.net> <BB52D64B1827B309BF7D9629@JcK-HP8200.jck.com> <C13DA83D-FC43-4243-897F-3E6B17B3434D@istaff.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>, ietf <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: Fri, 21 Jun 2013 18:57:15 -0000

--On Friday, June 21, 2013 11:46 -0400 John Curran
<jcurran@istaff.org> wrote:

>...
>> Let's not complicate things further by making the assumption
>> that anything that reasonably looks like "technical stuff"
>> belongs in the IETF and not in ICANN.  It is likely to just
>> make having the right conversations even harder.
> 
> I believe that policy issues that are under active discussion
> in ICANN can also be discussed in the IETF, but there is
> recognition  that ICANN is likely the more appropriate place
> to lead the process of consensus development and approval.
> 
> I believe that protocol development that is under active
> discussion at the IETF can also discussed at ICANN, but there
> is recognition  that the IETF is likely the appropriate place
> to lead the process  of consensus development and approval.
>...

John,

While I agree with the above (and am still trying to avoid
carrying this conversation very far on the IETF list), I think
another part of the puzzle is that there are also situations in
which technical considerations imply real constraints on policy
alternatives.  Some obvious examples include physical constants
like the speed of light, others, only slightly less obvious,
include things like the design of the DNS as a simply hierarchy
that cannot support symmetric aliases (i.e., anything that would
support an actual "came from" function or a list of all of the
names that point to a given note).  The policy folks ignore
those constraints, or treat them as subject to policy-making
decisions at the risk of being ridiculous and/or causing
considerable harm to the Internet.  While they are less obvious
in this community, I suggest it works the other way too -- there
are policy and economic decisions and realities that are as much
constraints on the technical solution space as those technical
constrains are on the policy ones, with just about the same
risks of ridiculousness or damage if they are ignored.

That is, again, why it is so unfortunate that the original model
of the IAB/PSO as one of ICANN's three "everyone has to work
together" pillars was abandoned... and more unfortunate that it
was replaced on the ICANN side by approximately nothing other
than some committees and other bodies that could easily be
ignored and on the IETF side by depending on individuals with
feet in both camps to speak up.

   john


From mthornbu@adobe.com  Fri Jun 21 14:35:55 2013
Return-Path: <mthornbu@adobe.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 A26DD21F9E07; Fri, 21 Jun 2013 14:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 BbmM3J8yx4Mk; Fri, 21 Jun 2013 14:35:50 -0700 (PDT)
Received: from exprod6og127.obsmtp.com (exprod6og127.obsmtp.com [64.18.1.78]) by ietfa.amsl.com (Postfix) with ESMTP id B497921F9DFE; Fri, 21 Jun 2013 14:35:37 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob127.postini.com ([64.18.5.12]) with SMTP ID DSNKUcTHH7OHa+vqd0cXdk4JBM+aak5t8y6y@postini.com; Fri, 21 Jun 2013 14:35:38 PDT
Received: from inner-relay-2.corp.adobe.com (mail-321.sea.adobe.com [153.32.1.52]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5LLZOAI027283; Fri, 21 Jun 2013 14:35:25 -0700 (PDT)
Received: from nahub01.corp.adobe.com (nahub01.corp.adobe.com [10.8.189.97]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5LLZOw7015904; Fri, 21 Jun 2013 14:35:24 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by nahub01.corp.adobe.com ([10.8.189.97]) with mapi; Fri, 21 Jun 2013 14:35:23 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: Ben Campbell <ben@nostrum.com>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>
Date: Fri, 21 Jun 2013 14:35:19 -0700
Subject: RE: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Topic: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Index: Ac5uCtbZuRIVMk7LS0i+/E+T5vgcMwAoFJaA
Message-ID: <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>
In-Reply-To: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion 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: Fri, 21 Jun 2013 21:35:55 -0000

hi Ben. thanks for your review. comments/replies inline.

> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Thursday, June 20, 2013 4:07 PM
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document:  draft-thornburgh-adobe-rtmfp-07
> Reviewer: Ben Campbell
> Review Date:  2013-06-20
> IETF LC End Date: 2013-06-25
>=20
> Summary: This draft is almost ready for publication as an informational R=
FC. However, I have some
> concerns about the purpose and intended status of the document that I thi=
nk should be considered prior
> to publication.
>=20
>=20
> Note: This is an informational draft that describes what I understand to =
be an existing protocol as
> implemented by commercial products. Therefore, this review does not attem=
pt to evaluate the protocol
> itself. I assume the protocol is what it is, and it is not up to the IETF=
 to agree or disagree with
> it.
>=20
> *** Major issues:
>=20
> -- Why does this need to be published as an IETF stream RFC?  If I unders=
tand correctly, this
> documents an existing protocol as implemented by commercial products. I a=
gree with Martin's comment
> that there is value in publishing this sort of thing, but I applaud the A=
dobe and the author for
> publishing it so other implementations can interoperate with their produc=
ts. But that could have done
> that in an independent stream document, or even in an Adobe published doc=
ument. (Perhaps even in a
> prettier format ;-)  )  If we publish this as an IETF stream document, th=
en I think it needs stronger
> clarification that it is not an IETF consensus doc than just its informat=
ional status.

this memo documents an existing network transport protocol that is widely d=
eployed and in widespread use in the Internet.  we felt that the IETF commu=
nity (and in particular the participants in the Transport and Services Area=
) is the most appropriate community with which to share this work: 1) membe=
rs of this community have the necessary and relevant expertise not only to =
understand the protocol, but to make use of it potentially in new applicati=
ons beyond Flash; 2) it is a transport protocol similar in many ways to TCP=
 and SCTP and widely deployed and used; 3) Adobe is interested in pursuing =
standardization of this protocol (with all that entails) if there is commun=
ity interest, and the IETF is definitely the right place for that.

we are very grateful that Martin Stiemerling chose to sponsor this document=
.

with regard to comments in later messages in this thread, i'd be happy to i=
nclude some (IESG-supplied) boilerplate in the document to clarify that it =
is not the product of an IETF WG.  however, note that both the title and fi=
rst sentence of the Introduction indicate that this is "Adobe's blahblahbla=
h", consistent with other vendor-protocol RFCs and consistent with IESG edi=
torial insistence (as told to me by a former TSV AD).  see RFC 4332 and RFC=
 6802 for two examples of vendor-specific/supplied protocols.  see also the=
 IESG note in RFC 4332 as an example disclaimer that could be added.

> Along those lines:
>=20
> 	-- Is this document the authoritative specification? (I suspect not.) Wh=
o owns change control? I
> assume that to be Adobe and/or the authors. What expectation do readers o=
f this draft have that it
> represents the current version of RTMFP at any point in time?

this memo is the authoritative specification for Adobe's RTMFP.  Adobe owns=
 change control.  i believe the second and third paragraphs of the Introduc=
tion indicate to a reader that this draft represents RTMFP as deployed in t=
he named Adobe products at the time of writing.

> 	-- Under what circumstances would one desire to implement this? I can in=
fer that from the
> introduction, but it would be nice to see some sort of applicability stat=
ement making it explicitly
> clear that this is not an IETF protocol, and that one would implement it =
in order to interoperate with
> certain Adobe products. I know that some of this may be implied by the fa=
ct that this is informational
> rather than standards track. But I don't expect readers who are not IETF =
insiders to understand that
> subtlety without some explicit words to that effect. In particular, it wo=
uld be good to clarify the
> difference between this and the many "not quite accepted as standards tra=
ck by some working group"
> nature of a number of our informational RFCs that describe protocols.

i will expand on applicability beyond what i specify in the first paragraph=
 of the Introduction, in general terms such as the kinds of functionality w=
e use this protocol for in Flash. note that interoperation with certain Ado=
be products, such as Flash Player, requires additional information such as =
the Flash-specific Cryptography Profile and syntax/semantics of mapping Fla=
sh's "Real Time Messaging Protocol (RTMP)" messages onto RTMFP flows.  thes=
e Flash-specific profiles and mappings are application-layer for RTMFP, ana=
logous to HTTP over TCP.

> That all being said, this is overall a well written document. The rest of=
 my comments are mostly
> pedantic nits.
>=20
> *** Minor issues:
>=20
> -- section 1.2:
>=20
> I find the use of "MUST ONLY" confusing. I gather it means "you are _allo=
wed_ to do X only under
> certain conditions" rather than "you are _required_ to do X under certain=
 conditions." If correct, I
> think the words "MAY ONLY" would be more clear. If not, then I think the =
construct would be better
> handled using existing 2119 language.

you're not the first person to be confused by that construct. i will change=
 instances of "MUST ONLY" to "is allowed only if" (or similar) and remove t=
he definition for "MUST ONLY" from Section 1.2.

> -- section 3.2:
>=20
> Do I understand correctly that all endpoints are expected to be able to p=
resent certificates? Do you
> find that common in the field? I realize the nature of the certs will dep=
end on the security profiles.

yes, all endpoints have certificates. in the RTMFP-for-Flash world, these c=
ertificates are not X.509 certs, and are anonymous and ephemeral.

> -- sections 3.2 and 5
>=20
> Do I assume correctly that endpoints need a common crypto profile to comm=
unicate? Is there a
> repository where one might find crypto profile documentation? Is there a =
commonly implemented one to
> which this draft could refer?

yes, endpoints need a common cryptography profile to interoperate.  there i=
s no repository for crypto profile documentation at this time. currently, t=
here is one defined cryptography profile (the one used for Flash communicat=
ion) that is not publicly documented, because i do not yet have permission =
to publish it.  i (meaning me personally) hope that a memo documenting the =
crypto/application profile for Flash communication (as being a widely deplo=
yed and used profile for RTMFP) would also be published someday as an I-D a=
nd hopefully an Informational RFC.

> -- section 3.2: "Multiple endpoints SHOULD NOT have the same identity."
>=20
> Why not MUST? Will things not break if two endpoints do have the same ide=
ntity?

this should be "It is RECOMMENDED that multiple endpoints not have the same=
 identity."  if two endpoints have the same identity, then they will be ind=
istinguishable.  this will not break RTMFP, but might confuse an applicatio=
n.  that being said, there could potentially be reasons to have different e=
ndpoints with indistinguishable identities and that potential should not be=
 normatively prohibited.

> -- "Authenticity MAY comprise verifying an issuer signature chain in a pu=
blic key infrastructure"
>=20
> Is that really normative, or just an observation of fact?

that "MAY" should be "can".

> -- " Canonical Endpoint Discriminators for distinct identities SHOULD be =
distinct."
>=20
> What if they are not? Do things break? It might be worth making this a MU=
ST, or adding some additional
> guidance about what might happen if the SHOULD is violated.

i will add a note that if the canonical EPD is the same for two distinct id=
entities, then the "duplicate session" logic in section 3.5.1.1.1 (paragrap=
h 6 step 1) might abort a new opening session to the second identity, which=
 might not be desired.

> -- "A comparison function MAY comprise performing a lexicographic orderin=
g..."
>=20
> Is that really normative, or just an example of something one might do?

that "MAY" should be "can".

> -- "A test SHOULD comprise testing whether the certificates are identical=
."
>=20
> What if it doesn't? Also, what constitutes "identical"? All fields match =
values? Bitwise match?  Is it
> simply including the same identity or identities? Maybe an identity funct=
ion provided by the crypto
> profile?

again, that SHOULD should be reworded to RECOMMENDED.  i will change "ident=
ical" to "bitwise identical".

> -- 3.5, last paragraph:
>=20
> Can you offer guidance on reasonable buffer size and number ranges?

i assume you mean "3.4, last paragraph" (referring to packet reassembly buf=
fers).  i will add some guidance and a "for example".  the guidance will de=
pend on how that RTMFP will be used and the expected amount of resources av=
ailable to it.

> -- 3.5.1.1.1, 3rd paragraph:
>=20
> What are the consequences of having a tag with less than 8 bytes of lengt=
h? Is the SHOULD reasonable
> here?

both of those SHOULDs should be RECOMMENDEDs.

> -- 3.5.1.1.1 throughout, and following sections:
>=20
> Does the upper case AND have special meaning?

upper case is the closest to bold face available in this format.  the inten=
tion is to emphasize (since there are multiple conditionals) that all condi=
tionals are required to hold.

> -- 3.5.1.4, Deployment Note:
>=20
> How would a redirector know which endpoints might do this? Or should it n=
ever initiate a session?

this is guidance for designing and deploying an RTMFP system.  the redirect=
or wouldn't know -- the designer should design the system such that the des=
cribed circumstance doesn't happen (for example, by having the redirector n=
ever initiate a session).  this is properly a SHOULD NOT since doing so can=
 cause undesired behavior (as described).  it is not desirable to give a no=
rmative prohibition or recommendation against a redirector initiating any s=
essions.  i feel this paragraph gives the narrowest normative limitation an=
d an explanation for that limitation.

> -- 3.5.2:
>=20
> Do I infer correctly that two endpoints need not share the same congestio=
n control algorithm to
> communicate?

correct.  the timestamp echo facility, ack behavior (as described for flow =
receivers), and limitations on aggressiveness in 3.5.2/.* impose the normat=
ive envelope in which any congestion control algorithms should interoperate=
.

> -- 3.6.2.3.2, 2nd paragraph: "...an implementation SHOULD encode a Next U=
ser Data chunk instead of a
> User Data chunk"
>=20
> I'm not sure why this needs to be normative, as I assume its just normal =
behavior. But if it does need
> to be normative, why not a MUST?  Can the far endpoint reasonably handle =
things if the SHOULD is
> violated?

this should be a RECOMMENDED.  the far end will work just fine if Next User=
 Data is never used.

> *** Nits/editorial comments:
>=20
> -- General: There's quite a bit of inconsistent use of third-person vs se=
cond-person language.

i will try to clean that up.

> -- 3.1: It would be nice to see the overview earlier in the draft. I foun=
d it difficult to read
> through all the data format stuff prior to section 3 putting them into co=
ntext.

others have commented that they'd prefer sections 2 and 3 to be swapped. i =
resisted that as this order ("here are the pieces" and then "here's how the=
y fit together") is my preferred way of explaining stuff.  also swapping th=
ose sections would be a huge editorial change which might have significant =
cross-reference and forward/back reference implications and could introduce=
 hard-to-detect errors into the spec.  however, i think i can move the over=
view (or a summary thereof) to earlier in the spec (probably in Section 1).

> -- 3.5.1.4, Deployment Note:
>=20
> s/which/that

good catch.

> -- 3.5.1.6, last paragraph:
>=20
> Which diagram? (An explicit cross-ref would help.)

oops. that paragraph used to be the postamble of the figure, so it obviousl=
y meant "this figure".  i'll change "the figure" to "Figure 17".

> -- 3.5.2:
>=20
> What is meant by "aggressive" in this context? Aggressive in avoiding con=
gestion, or aggressive in
> sending data?

aggressive in sending data. i'll make that clarification.

> -- 3.6.2.3.1 and subsequent sections:
>=20
> Does the all-caps "FIRST" have special meaning?

it is all-caps for typographical emphasis.

thank you!

-michael thornburgh

From jcurran@istaff.org  Fri Jun 21 15:05:36 2013
Return-Path: <jcurran@istaff.org>
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 F113821F9962 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 15:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 274Y0o6p-L3O for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 15:05:30 -0700 (PDT)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by ietfa.amsl.com (Postfix) with ESMTP id E027021F9ADA for <ietf@ietf.org>; Fri, 21 Jun 2013 15:05:29 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1Uq9SL-000Ij6-Oo; Fri, 21 Jun 2013 22:05:21 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19Zzf+v2d8rStFgvLa5MLQW
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] IETF, ICANN and Whois (Was Re: Last Call:	<draft-housley-rfc2050bis-01.txt>	(The Internet Numbers Registry	System) to Informational RFC)
From: John Curran <jcurran@istaff.org>
In-Reply-To: <E9D4C327CAB3DE4FF73FDC2F@JcK-HP8200.jck.com>
Date: Fri, 21 Jun 2013 18:05:22 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <2E2038CA-2543-4DFE-B292-E66E50EB6575@istaff.org>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se> <51C21498.3020008@gmail.com> <C8EEFB02-5637-4247-98F6-3B414E045E0E@kumari.net> <BB52D64B1827B309BF7D9629@JcK-HP8200.jck.com> <C13DA83D-FC43-4243-897F-3E6B17B3434D@istaff.org> <E9D4C327CAB3DE4FF73FDC2F@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Cc: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, ietf <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: Fri, 21 Jun 2013 22:05:36 -0000

On Jun 21, 2013, at 2:56 PM, John C Klensin <john-ietf@jck.com> wrote:

> While I agree with the above (and am still trying to avoid
> carrying this conversation very far on the IETF list), I think
> another part of the puzzle is that there are also situations in
> which technical considerations imply real constraints on policy
> alternatives.  Some obvious examples include physical constants
> like the speed of light, others, only slightly less obvious,
> include things like the design of the DNS as a simply hierarchy
> that cannot support symmetric aliases (i.e., anything that would
> support an actual "came from" function or a list of all of the
> names that point to a given note).  The policy folks ignore
> those constraints, or treat them as subject to policy-making
> decisions at the risk of being ridiculous and/or causing
> considerable harm to the Internet.  While they are less obvious
> in this community, I suggest it works the other way too -- there
> are policy and economic decisions and realities that are as much
> constraints on the technical solution space as those technical
> constrains are on the policy ones, with just about the same
> risks of ridiculousness or damage if they are ignored.

Agreed.  I believe that there is a better understanding of this
situation now than in the earlier days (including among governments
who are beginning to seriously engage with ICANN's GAC.)

> That is, again, why it is so unfortunate that the original model
> of the IAB/PSO as one of ICANN's three "everyone has to work
> together" pillars was abandoned... and more unfortunate that it
> was replaced on the ICANN side by approximately nothing other
> than some committees and other bodies that could easily be
> ignored and on the IETF side by depending on individuals with
> feet in both camps to speak up.


It's difficult to lay blame anyone from walking away from the PSO approach;
in ICANN's early years it always seemed to be a vestigial structure serving
little purpose. The lack of apparent value was amplified when ICANN changed 
its proposed structure (from being oversight and coordination between true
independent supporting organizations) into a heavily DNS-focused direction 
by opting to absorb the DNSO internally in the initial Singapore meeting.
If ICANN were operating solely in a coordination and oversight role, with 
policy, process, and protocol development done in supporting organizations, 
then it would have been a lot easier to make the liaison and coordination 
function successful, both between pillars (DNSO, ASO, PSO) and to/from 
governmental types.  For some reason, doing that in the margin of a 97%
DNS-focused omnibus policy/oversight/coordination/operation organization 
doesn't provide the necessary level of attention.

FYI,
/John

Disclaimers: My views alone.  Apologies for length; I lacked the time to
write a shorter reply.






From fred@cisco.com  Fri Jun 21 16:04:41 2013
Return-Path: <fred@cisco.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 7C99E21F9E61 for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 16:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.449
X-Spam-Level: 
X-Spam-Status: No, score=-110.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 3ceFSKRPh7+E for <ietf@ietfa.amsl.com>; Fri, 21 Jun 2013 16:04:36 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id EC8BB21F9E5C for <ietf@ietf.org>; Fri, 21 Jun 2013 16:04:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=828; q=dns/txt; s=iport; t=1371855876; x=1373065476; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=4rROHp5O+EWgdEzXYotbw9B74SP6intnTmZmMBSingY=; b=Qx4D2CdmfFfsjrbsian+1lpy+bnfZcE6SjDecrLAOj2U7ZgFVHoeN0bs b36LLED4xfXpbi1VYZX+5msRAT5yRVKoOcFGVJDBBLanX+783SB9gAZzu 5QHp55a1MZ+6buWmGRLZ5KR2RVRw/sIvJpM2Al77WABHuKgTX1y1B59s9 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmAFAAXbxFGtJV2Z/2dsb2JhbABbgwl6gjy8eYECFnSCIwEBAQMBeQULAgEIIhkLMiUCBA4FCIgABrwwjxYCMQeDAGEDiGmgHoFYgTeCKA
X-IronPort-AV: E=Sophos;i="4.87,916,1363132800"; d="scan'208";a="226015496"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP; 21 Jun 2013 23:04:35 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r5LN4ZGV006477 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 21 Jun 2013 23:04:35 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.02.0318.004; Fri, 21 Jun 2013 18:04:34 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: IETF,	ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt>	(The Internet Numbers Registry System) to Informational RFC)
Thread-Topic: IETF,	ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt>	(The Internet Numbers Registry System) to Informational RFC)
Thread-Index: AQHObDyaqjV6wFd3/k2sXSlyLZPtU5k8BEAAgADilwCABDvlAA==
Date: Fri, 21 Jun 2013 23:04:34 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B922569@xmb-rcd-x09.cisco.com>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net> <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>
In-Reply-To: <D6B2DDFE-1C83-4FD0-9646-576F2F437239@frobbit.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.125]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <735413BB31725F4B91B1435690E99757@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John C Klensin <john-ietf@jck.com>, ietf <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: Fri, 21 Jun 2013 23:04:41 -0000

On Jun 18, 2013, at 11:25 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote:

> I think this is the correct strategy, BUT, I see as a very active partici=
pant in ICANN (chair of SSAC) that work in ICANN could be easier if some "m=
ore" technical standards where developed in IETF, and moved forward along s=
tandards track, that ICANN can reference. Same with some epp-related issues=
, and also DNS-related, which I must admit I think has stalled in the IETF.=
 When that happens, ICANN start to "invent" or at least discuss IETF relate=
d issues -- which I think is non optimal. But on the other hand, if IETF do=
 not move forward, then what should ICANN do?

Something ICANN can do is ask the IETF for specifications. I can't promise =
instant delivery, but it will be slower if we don't know what they need.=

From barryleiba.mailing.lists@gmail.com  Sat Jun 22 07:34:44 2013
Return-Path: <barryleiba.mailing.lists@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 DA00B21F9F7C; Sat, 22 Jun 2013 07:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.021
X-Spam-Level: 
X-Spam-Status: No, score=-102.021 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 SZK20FbIIacK; Sat, 22 Jun 2013 07:34:44 -0700 (PDT)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 084E021F9F71; Sat, 22 Jun 2013 07:34:43 -0700 (PDT)
Received: by mail-ve0-f173.google.com with SMTP id jw11so7320602veb.4 for <multiple recipients>; Sat, 22 Jun 2013 07:34:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=KRBFsJgI0SVHjXQyMS+fLmbHHjiWkZjdXQoD6DpCEts=; b=xis+vxJTfp7iun148PVi/h6ScY4y9Ko/OQvTqgtTDAawJzp5Ir9VMac/ehtf6BkKkW 57W7SUqIfuscX7pi2eIJDgw4i5TSZhNCbjYaxyHWlmZtnweT2PivS6gQrYMf472yO+/q SeoFw0lDm9ClJCiKqBUlv/CpXpXxQ6QzbiKGGOjh/sHkgpe0zDyH+E6HVWNvKy8ZcY0z 3PiF69s9XRBODo+Wh/0d4qX9QgZK10zWQOwQHYdD+q4/5xXhldt73oEyyFaF3chbspyF ZadbWhU3ZpatDgSk9eP3xpTGcpjKXWNsUDd3HXpQvwhFPZqpKopurK+OI81LDE9/mynq UCEg==
MIME-Version: 1.0
X-Received: by 10.58.80.38 with SMTP id o6mr8164214vex.69.1371911682406; Sat, 22 Jun 2013 07:34:42 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.234.105 with HTTP; Sat, 22 Jun 2013 07:34:42 -0700 (PDT)
In-Reply-To: <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>
Date: Sat, 22 Jun 2013 10:34:42 -0400
X-Google-Sender-Auth: XKrVgptU8dNXkmrFjo_aM0nWUR0
Message-ID: <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com>
Subject: Re: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
From: Barry Leiba <barryleiba@computer.org>
To: Michael Thornburgh <mthornbu@adobe.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion 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: Sat, 22 Jun 2013 14:34:45 -0000

> you're not the first person to be confused by that construct. i will change instances of
> "MUST ONLY" to "is allowed only if" (or similar) and remove the definition for "MUST
> ONLY" from Section 1.2.

I think this is an excellent idea.  RFC 6919 aside (ahem), it's rarely
a good idea to try to define new 2119-ish key words.

Speaking of which (my comments after a bunch of quotes)...

>> -- section 3.2: "Multiple endpoints SHOULD NOT have the same identity."
>>
>> Why not MUST? Will things not break if two endpoints do have the same identity?
>
> this should be "It is RECOMMENDED that multiple endpoints not have the same
> identity."  if two endpoints have the same identity, then they will be indistinguishable.
> this will not break RTMFP, but might confuse an application.  that being said, there
> could potentially be reasons to have different endpoints with indistinguishable identities
> and that potential should not be normatively prohibited.
...
>> -- "A test SHOULD comprise testing whether the certificates are identical."
>>
>> What if it doesn't?
>
> again, that SHOULD should be reworded to RECOMMENDED.
...
>> -- 3.5.1.1.1, 3rd paragraph:
>>
>> What are the consequences of having a tag with less than 8 bytes of length?
>> Is the SHOULD reasonable here?
>
> both of those SHOULDs should be RECOMMENDEDs.
...
>> -- 3.6.2.3.2, 2nd paragraph: "...an implementation SHOULD encode a Next
>> User Data chunk instead of a User Data chunk"
>>
>> I'm not sure why this needs to be normative, as I assume its just normal
>> behavior. But if it does need to be normative, why not a MUST?  Can the far
>> endpoint reasonably handle things if the SHOULD is violated?
>
> this should be a RECOMMENDED.  the far end will work just fine if Next User
> Data is never used.

In RFC 2119, "SHOULD" and "RECOMMENDED" are synonymous (they're just
covering different parts of speech; they fit differently into
sentences).  Changing "SHOULD" to "RECOMMENDED" (and, of course,
rewording the sentences accordingly) doesn't affect Ben's comments on
the points.

"MUST" means that the protocol will not work properly unless you do
this.  You just have to, without fail.

"SHOULD" (and "RECOMMENDED") is really only a *little* lighter: it
still means that the protocol requires that you do this, but that
there might be good reasons not to -- you have to fully understand
what will happen if you don't do this before you can consider not
doing it.

To my mind (and I consider this when I do IESG Evaluation on documents
with SHOULD), whenever a document uses SHOULD (or RECOMMENDED) it
needs to (one might say "SHOULD") make it very clear what will happen
if you don't do this, so that implementors can have that necessary
understanding.  Perhaps the protocol will fail in some unusual
situations.  Perhaps it will break compatibility with older clients.
Perhaps it will still work, but will adversely affect performance.

But without an explanation, there's no way for implementors to meet
the terms in RFC 2119:

   3. SHOULD   This word, or the adjective "RECOMMENDED", mean that
   there may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

If something is simply a suggested value or response, the text should
say it that way.  If it's a suggestion that really is a best-practice
recommendation that comes from a lot of experience with the protocol,
the text should say that, without the 2119 key words.

For the first item, in Section 3.2, for example, you say:

> this should be "It is RECOMMENDED that multiple endpoints not have the same
> identity."  if two endpoints have the same identity, then they will be indistinguishable.
> this will not break RTMFP, but might confuse an application.  that being said, there
> could potentially be reasons to have different endpoints with indistinguishable identities
> and that potential should not be normatively prohibited.

That might well be a valid "SHOULD".  Don't change it to "RECOMMENDED"
(or do, if you like), but put in the explanation that you have here.
It would be especially helpful if you can also include an example of a
reason, and/or say something about the consequences of the confusion
it will cause.

For the cases of 3.5.1.1.1 and 3.6.2.3.2, it seems that you don't want
2119 key words there at all: these look like recommendations (not in
the 2119 sense) that are based on what's been deployed already, and it
would simply be good to make that clear: "implementation experience
suggests [x]".

Barry

From ron.even.tlv@gmail.com  Sat Jun 22 08:00:50 2013
Return-Path: <ron.even.tlv@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 5371D21E8096; Sat, 22 Jun 2013 08:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 UwNEO1RGmsHx; Sat, 22 Jun 2013 08:00:49 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id BBB1021E809D; Sat, 22 Jun 2013 08:00:48 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id y10so1353262wgg.0 for <multiple recipients>; Sat, 22 Jun 2013 08:00:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=O7jBQJr9+Dr8ETOW8TflQqn+bG3ZHNrcmFkdn6pbaSE=; b=iBQBwGGIZSj5PYb1OQkxvzpHEeHl5NjnzyKuDDhqojU0GiNtRE+IKvmXwGZEsIdsn7 EkWBxkz8Q6jdD328w1FQl/OtIYhW1pZJQS2PnLsqbsqvbl9XOibb1lN6FdIdr055waFa V2tmJvDnHudwckOp7BF+yjfoD1ZhztnC2JAAor67YFqHHtRwOvIIKpTOsaHqe+8k1oCS Rn+zqlnhCLCCvAzhs2vf8lCihWVhdyPjxtee8b6Qn9bMKWjz1tYGStdhUeiZzNQl7kof 2VWrSllY/ed9azlEs67OqmP3SOQ1JpYw0I/DKxuhhU7M7W8U25HCBrdZsK4ozFYlcKTO RZAg==
X-Received: by 10.194.21.138 with SMTP id v10mr4099076wje.16.1371913247865; Sat, 22 Jun 2013 08:00:47 -0700 (PDT)
Received: from RoniE ([109.67.214.161]) by mx.google.com with ESMTPSA id r9sm4502588wik.1.2013.06.22.08.00.45 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 22 Jun 2013 08:00:47 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-pkix-est.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-pkix-est-07
Date: Sat, 22 Jun 2013 17:59:23 +0300
Message-ID: <075901ce6f59$170f3c50$452db4f0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_075A_01CE6F72.3C5D37A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5vWRUE/TjBkahtSoWxzN6PYKJhyw==
Content-Language: en-us
Cc: gen-art@ietf.org, 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: Sat, 22 Jun 2013 15:00:50 -0000

This is a multipart message in MIME format.

------=_NextPart_000_075A_01CE6F72.3C5D37A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-pkix-est-07

Reviewer: Roni Even

Review Date:2013-6-22

IETF LC End Date: 2013-6-24

IESG Telechat date: 2013-6-27

 

Summary: This draft is ready for publication as Standard track RFC.

 

This is not a comment, I read the draft and not being an expert in this area
I found it clear for me to read. The document structure made it easier to
read.

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.  In section 4.5.2 "to use the the secp384r1 elliptic curve" repeated
"the"

 


------=_NextPart_000_075A_01CE6F72.3C5D37A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:510795705;
	mso-list-type:hybrid;
	mso-list-template-ids:1559919828 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-pkix-est-07</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;6&#8211;22<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-6&#8211;24<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: 2013-6&#8211;27<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as Standard track RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>This is =
not a comment, I read the draft and not being an expert in this area I =
found it clear for me to read. The document structure made it easier to =
read.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>In section 4.5.2 =
&#8220;<span style=3D'font-family:"Courier New"'>to use the the =
secp384r1 elliptic curve&#8221; repeated =
&#8220;the&#8221;</span><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_075A_01CE6F72.3C5D37A0--


From john-ietf@jck.com  Sat Jun 22 09:59:51 2013
Return-Path: <john-ietf@jck.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 D583611E810B for <ietf@ietfa.amsl.com>; Sat, 22 Jun 2013 09:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 zRvwFG-mUPGN for <ietf@ietfa.amsl.com>; Sat, 22 Jun 2013 09:59:46 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id F30F611E810C for <ietf@ietf.org>; Sat, 22 Jun 2013 09:59:45 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UqRA7-00022C-DV; Sat, 22 Jun 2013 12:59:43 -0400
Date: Sat, 22 Jun 2013 12:59:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: SHOULD and RECOMMENDED (was: Re: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07)
Message-ID: <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.c om>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF-Discussion 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: Sat, 22 Jun 2013 16:59:51 -0000

--On Saturday, June 22, 2013 10:34 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

> In RFC 2119, "SHOULD" and "RECOMMENDED" are synonymous
> (they're just covering different parts of speech; they fit
> differently into sentences).  Changing "SHOULD" to
> "RECOMMENDED" (and, of course, rewording the sentences
> accordingly) doesn't affect Ben's comments on the points.

FWIW, 

While the above is certainly true, I believe that synonym
relationship is one of the poorer ideas in 2119.  The problem is
that 2026 assigns a rather different interpretation to
"recommended" in the context of Applicability Statements (A/Ss).
That was relatively unimportant when we were almost never using
explicit Applicability Statements but, now that we are doing so
again, I believe that it would be wise to discourage
"RECOMMENDED" and "NOT RECOMMENDED" as synonyms for "SHOULD" and
"SHOULD NOT" unless they are clearly necessary to avoid awkward
sentences and the non-A/S intent is completely clear.

   john



From barryleiba@gmail.com  Sat Jun 22 10:28:28 2013
Return-Path: <barryleiba@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 D27A011E811A for <ietf@ietfa.amsl.com>; Sat, 22 Jun 2013 10:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.02
X-Spam-Level: 
X-Spam-Status: No, score=-102.02 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 7uNLtAa4fDbV for <ietf@ietfa.amsl.com>; Sat, 22 Jun 2013 10:28:28 -0700 (PDT)
Received: from mail-qe0-x236.google.com (mail-qe0-x236.google.com [IPv6:2607:f8b0:400d:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 4BCEA21F9F3C for <ietf@ietf.org>; Sat, 22 Jun 2013 10:28:28 -0700 (PDT)
Received: by mail-qe0-f54.google.com with SMTP id ne12so96485qeb.13 for <ietf@ietf.org>; Sat, 22 Jun 2013 10:28:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NFRpgQEbcfvamEIcfEI8jv5+C0uACXylwqG8ZS1bR8o=; b=tIO4QaZlmFVpi7QrsLFeZe2r6psQz3dDB+OO8igpYJhRykLX0NCve51PDZbY1DgGTx BQmUwqM9P9/pkGQ87kc5GOYAm8NSh6Q2nEqhcSuAZAei4uYG6/yyUyGcTtaDgmEkjziR JLVpNEHHNTeS5iBoQe7e/SWJKed91e+dn/mFZBoABuMP/0GmUkpyWHTQPgWDpJuFaWbO O8gGv/1cTWPefL8uw1y33liPCJN+ZLVUbtDKfHL38fy3vrHOvNhJPIhpHbxTj4IE22SP gc/FhG/1r9+oclSaD41SWfb3sTNaROcpLROOGdgrIBCedCjORK0J38AeCi1q7tIDWKpA iswA==
MIME-Version: 1.0
X-Received: by 10.229.244.7 with SMTP id lo7mr2477065qcb.90.1371922107491; Sat, 22 Jun 2013 10:28:27 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.0.139 with HTTP; Sat, 22 Jun 2013 10:28:27 -0700 (PDT)
In-Reply-To: <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com>
Date: Sat, 22 Jun 2013 13:28:27 -0400
X-Google-Sender-Auth: FzjssTHTAnZUM2xTSESOijyA2A0
Message-ID: <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED (was: Re: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07)
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a11c2cab2e08cc904dfc18181
Cc: IETF-Discussion 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: Sat, 22 Jun 2013 17:28:28 -0000

--001a11c2cab2e08cc904dfc18181
Content-Type: text/plain; charset=ISO-8859-1

>
> I believe that it would be wise to discourage
> "RECOMMENDED" and "NOT RECOMMENDED" as synonyms for "SHOULD" and
> "SHOULD NOT" unless they are clearly necessary to avoid awkward
> sentences and the non-A/S intent is completely clear.
>

A fine suggestion, with which I agree.

Barry

--001a11c2cab2e08cc904dfc18181
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I believe that it would be wise to discourag=
e<br>
&quot;RECOMMENDED&quot; and &quot;NOT RECOMMENDED&quot; as synonyms for &qu=
ot;SHOULD&quot; and<br>
&quot;SHOULD NOT&quot; unless they are clearly necessary to avoid awkward<b=
r>
sentences and the non-A/S intent is completely clear.<br>
</blockquote><div><br></div><div>A fine suggestion, with which I agree.</di=
v><div><br></div><div>Barry<span></span>=A0</div>

--001a11c2cab2e08cc904dfc18181--

From hsantos@isdg.net  Sat Jun 22 11:36:54 2013
Return-Path: <hsantos@isdg.net>
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 0A6C821F99A5 for <ietf@ietfa.amsl.com>; Sat, 22 Jun 2013 11:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.991
X-Spam-Level: 
X-Spam-Status: No, score=-102.991 tagged_above=-999 required=5 tests=[AWL=-0.392, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 C4wdJiqkM9DD for <ietf@ietfa.amsl.com>; Sat, 22 Jun 2013 11:36:49 -0700 (PDT)
Received: from secure.winserver.com (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5AEB421F9017 for <ietf@ietf.org>; Sat, 22 Jun 2013 11:36:44 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1911; t=1371926197; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=HFIdiY7 Yn4d4BpDo/SfE0siSU5A=; b=Jo4tgYLP+pCYagB3y4Wj27kiVD+k/c9SjSxJzaJ TsM5M7r/XGqX/EJXFcwe3ZDD2zpneXF7BFiw44SS0nLBUXFJjqdoguEdd0rI/Jxu 8BGYGdMxXKBpk83kCDtNzJ77UsRqyXkTcPbeLi+0URhusClpBAeMlF4YzFGPJQjt 1RIM=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 22 Jun 2013 14:36:37 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2683739815.7997.2748; Sat, 22 Jun 2013 14:36:36 -0400
Message-ID: <51C5EE19.9020601@isdg.net>
Date: Sat, 22 Jun 2013 14:34:01 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com>
In-Reply-To: <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF-Discussion 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: Sat, 22 Jun 2013 18:36:54 -0000

Hi,

I think there are far too many debates on RFC2119 semantics and I think 
it can be reduced by focusing on better technical protocol writing 
skills.  A simple recommendation to always include (if possible) a 
Minimum Requirements table or section can go a long way in removing 
ambiguity.  Some of these docs are just too verbose and design concepts 
too spread out to extract all that is needed. Too easy to have semantic 
conflicts. Things are missed or fall thru the crack.

It should be possible to have an automated RFC parser that pulls and 
extracts the minimum protocol framework configuration. Its been done 
since the 80s with automated configuration/fitting tools.  It can be 
done with IETF protocols as well, perhaps if only to extract a minimum 
requirements table.

Personally, I think RECOMMENDED is closer to a SHOULD than MAY. IMV, a 
SHOULD is a RECOMMENDED, yet still OPTIONAL mode of operation.  So I 
agree the term RECOMMENDED can be used to inform readers what is the 
preferred mode of operation. I personally view it as a DEFAULT ON 
condition where it is programmed for local policy to decide, but it is 
ON out of the box because of the RECOMMENDED mode of operation.  A MAY 
on the other hand is also possible recommendation, but I see it as a 
DEFAULT OFF or ON condition.

    [o] SHOULD OPTION
    [_] MAY OPTION

None of this is concrete of cause, but it should be easier if authors 
were better skilled in writing more precise technical requirements 
outlines to reduce the ambiguity and debates.

--
HLS




On 6/22/2013 1:28 PM, Barry Leiba wrote:
>>
>> I believe that it would be wise to discourage
>> "RECOMMENDED" and "NOT RECOMMENDED" as synonyms for "SHOULD" and
>> "SHOULD NOT" unless they are clearly necessary to avoid awkward
>> sentences and the non-A/S intent is completely clear.
>>
>
> A fine suggestion, with which I agree.
>
> Barry
>


From dharkins@lounge.org  Sat Jun 22 22:36:21 2013
Return-Path: <dharkins@lounge.org>
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 3614B21F91CE for <ietf@ietfa.amsl.com>; Sat, 22 Jun 2013 22:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
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 zJrOsvv4u6xu for <ietf@ietfa.amsl.com>; Sat, 22 Jun 2013 22:36:16 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id 1464E11E80DC for <ietf@ietf.org>; Sat, 22 Jun 2013 22:36:16 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 6DC0DA88800E; Sat, 22 Jun 2013 22:36:14 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Sat, 22 Jun 2013 22:36:14 -0700 (PDT)
Message-ID: <37b1f0e97ec7182d9cb86e22b993b270.squirrel@www.trepanning.net>
In-Reply-To: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com>
Date: Sat, 22 Jun 2013 22:36:14 -0700 (PDT)
Subject: Re: IETF Diversity
From: "Dan Harkins" <dharkins@lounge.org>
To: "Phillip Hallam-Baker" <hallam@gmail.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: 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: Sun, 23 Jun 2013 05:36:21 -0000

On Tue, June 18, 2013 9:52 am, Phillip Hallam-Baker wrote:
> I am rather disappointed that there hasn't been any followup to the
> diversity discussion that took place at the plenary.
>
> I do applications and I do security and so having a diverse range of input
> is critical if the final product is going to be useful. There are no
> gender
> or cultural issues in packet routing that I am aware of. But once we get
> to
> the application layer they become central.

  Interesting. Can you explain what it is about the application layer
that introduces gender and cultural issues?

> We seem to have interminable discussions about how to help some
> hypothetical dissident in (pick your authoritarian state). But I can't
> remember the last time we discussed Internet stalking which has been an
> issue women have been complaining about since I started getting involved
> in
> IETF. This is just one security issues that has a big gender bias and it
> is
> a problem that I think can be usefully addressed in an open consensus
> seeking organization.

  Internet stalking? Maybe you should call for a BoF to address the issue.
I'm not sure what protocol can be developed, or modification to an existing
protocol, that can address the stalking problem but I'm all ears!

> It does not take 100 people to write a specification but it does take a
> large number of people to adequately gather requirements. Taking
> requirements from 100 people from almost the same background and
> perspective is not very productive. I am aware that I have a limited
> personal perspective which is why I actively seek out other perspectives.

  Some backgrounds and perspectives aren't all that helpful. Would you
like my liddite father's perspective? How about the brother of a friend
of mine who has been institutionalized and is quite insane? We need to
get requirements from people who understand and will use our protocols.
If those people are all the same background then oh well, but creating
"diversity" by just adding people of the correct background will not make
our standards better.

  Which says nothing about having more women in I* leadership positions.
That may be great. Or it might not be. It depends on whether the people
have clue or not.

  See, that's the thing. IETF needs people who have clue not people who
are members of some protected group that has been declared to be
underrepresented.

> At the plenary I pointed out that there have been women involved in IETF
> ever since I started in IETF over 20 years ago now. Yet we have an IAB and
> an IESG with only one female member who is not ex-officio (according to
> their Web sites)

  Can you restate that as a problem? And also explain why it is a problem?

> The IETF is a community known for valuing consensus rather than seeking
> diverse views. I see a real risk that the consensus being built here is a
> false consensus built by excluding opposing views rather than a real
> consensus built on reconciling them. Bringing opposing views to this forum
> is invariably a thankless task. The assumption is that if you can't hack
> it
> here well that is your fault and your problem. Case in point,  each time I
> get something wrong in RFC2HTML and I get the error message 'You Lose', my
> natural response is 'why the heck am I bothering wasting my time here'.

  An opposing view is one that thinks this whole diversity issue is crap.
Do you want to ensure that people who view the diversity issue as crap are
included in the consensus being built? How many people who are currently
on the diversity mailing list view the whole endeavor as crap? If it's zero
(which is my prediction), then isn't that a problem with the diversity of the
diversity group? Won't the output of that group suffer because they are
all of the same mindset?

> I do not think that gender is the only diversity problem in IETF but it is
> one that can be measured and the IETF is conspicuously failing. We also
> have a rather severe age problem, twenty years ago EKR and myself were
> among the youngest participants in most discussions and setting aside the
> grad students the same is usually true today.

  Gosh. I feel so left out. I'm as old as EKR (and probably you) and have
been
involved in the IETF for about as long as he has yet you do not include me in
your measure of diversity. Do you think that maybe you have a problem with
measurement of the problem?

> The perspective is going to need to change. Rather than looking for ways
> to
> encourage a few token women to work their way up through the existing
> selection regime we need to look at what sort of selection and
> participation and representation structures will encourage diversity.

  The IETF is a weird lot. We are predominantly "type A" personalities. There
are quite a few Asbergers cases and many more borderline functional
Asbergers cases. There are probably also quite a bit of people who have
OCD and maybe a mild case of Tourettes). So you have to explain how the
general studies of diversity mean anything here. How does having a
distribution of X:Y for some protected class increase the quality of an RFC?

  Dan.




From dharkins@lounge.org  Sat Jun 22 23:01:37 2013
Return-Path: <dharkins@lounge.org>
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 3BA3921F8F9E for <ietf@ietfa.amsl.com>; Sat, 22 Jun 2013 23:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
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 9KUKNrQ8Ocki for <ietf@ietfa.amsl.com>; Sat, 22 Jun 2013 23:01:32 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id 3200021F8E77 for <ietf@ietf.org>; Sat, 22 Jun 2013 23:01:32 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id C081EA88800E; Sat, 22 Jun 2013 23:01:31 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Sat, 22 Jun 2013 23:01:32 -0700 (PDT)
Message-ID: <b6ce0f7f3447c4b6d2dc871fe0163981.squirrel@www.trepanning.net>
In-Reply-To: <51C1DB74.9020409@gmail.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <51C1CD9A.2020004@stpeter.im> <51C1CE67.3020703@gmail.com> <51C1D4A5.5070205@stpeter.im> <51C1D59F.6010608@gmail.com> <51C1D873.9090303@stpeter.im> <51C1DB74.9020409@gmail.com>
Date: Sat, 22 Jun 2013 23:01:32 -0700 (PDT)
Subject: Re: IETF Diversity
From: "Dan Harkins" <dharkins@lounge.org>
To: "Melinda Shore" <melinda.shore@gmail.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: 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: Sun, 23 Jun 2013 06:01:37 -0000

On Wed, June 19, 2013 9:25 am, Melinda Shore wrote:
> On 6/19/13 8:12 AM, Peter Saint-Andre wrote:
>> On 6/19/13 10:00 AM, Melinda Shore wrote:
>>> On 6/19/13 7:56 AM, Peter Saint-Andre wrote:
>>>> Why do you believe that my opinions are unexamined? I have been
>>>> thinking and reading about social, cultural, and personal change
>>>> for a very long time.
>>>
>>> You made an assertion that's at least a little ahistorical,
>>
>> That depends on which historians you've been reading.
>
> Peter, it's a fact in the US and Canada that court cases preceded
> civil rights protections which preceded social change.  This has been
> true for racial minorities, women, glbt folk, etc.  I expect that
> there are historians who'd argue otherwise but allow me to suggest
> that if so they are very, very far out of the mainstream.

  Civil rights? A "whites only" lunch counter or drinking fountain is
a matter of civil rights. When there is active prohibition on a class
there is a matter of civil rights. But the mere fact that the numbers
are overwhelmingly one-sided does not make a civil rights issue.

  Between 1995 and 2008, 84% of the people killed by lighting strikes
were male. Is that evidence of discrimination? Is that a civil rights
issue? What do you propose to do to rectify that statistic?

  Dan.



From randy@psg.com  Sun Jun 23 02:39:57 2013
Return-Path: <randy@psg.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 9647221F9BAB for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 02:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599]
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 2mopBM7u1RKe for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 02:39:57 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 3D50421F9BAA for <ietf@ietf.org>; Sun, 23 Jun 2013 02:39:57 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Uqgm3-000MRG-JP; Sun, 23 Jun 2013 09:39:55 +0000
Date: Sun, 23 Jun 2013 18:39:54 +0900
Message-ID: <m2wqplnp1x.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Dan Harkins <dharkins@lounge.org>
Subject: Re: IETF Diversity
In-Reply-To: <b6ce0f7f3447c4b6d2dc871fe0163981.squirrel@www.trepanning.net>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <51C1CD9A.2020004@stpeter.im> <51C1CE67.3020703@gmail.com> <51C1D4A5.5070205@stpeter.im> <51C1D59F.6010608@gmail.com> <51C1D873.9090303@stpeter.im> <51C1DB74.9020409@gmail.com> <b6ce0f7f3447c4b6d2dc871fe0163981.squirrel@www.trepanning.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <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: Sun, 23 Jun 2013 09:39:57 -0000

there appears to be a problem with your mail system.  mail which is
clearly from the 1950s is appearing on the ietf list.  somehow it has
current dates, so something is header mashing.  you may need help with
your male system.

randy

From abdussalambaryun@gmail.com  Sun Jun 23 03:13:03 2013
Return-Path: <abdussalambaryun@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 9DBFA21F9B98 for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 03:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, 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 y-6aUCRKtYl6 for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 03:13:03 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 4787421F9B8F for <ietf@ietf.org>; Sun, 23 Jun 2013 03:12:55 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so9704448pbc.29 for <ietf@ietf.org>; Sun, 23 Jun 2013 03:12:55 -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 :content-type; bh=1fhhJYCY0BCDwBHarCVlE+I6PiyPazUquxis1MhnicQ=; b=h7NhWEKhJe5VJL9KP1tnv3sIVFHENK2LPLsVEo5QZLfJsENytbjouxiEpUKXXn2h7U EFnp5R/mZrPqrjKKB05ptSwQkWHcanK61jyeQhWOAKDtsBixtEIlHNVFbHWjLO5t6oIq psDW9PsSxe00ybPW1nAHz6LBzJo1O54d0GI30vhE4HDXVO9XEwz4GwaqsnyGDBS/uOC7 rFgHyltCwzC6V/u+5rCuT2w1Vofxy5r/RiDyW4gz2TyJP27ocssgbvqnYEUCNH787UGC rX70IuRs7khzyC2sGCRSlTz0ro/xChndn0ew5+p/Gt0WRqV+0oxfYCsmGHPch+DroYMj CrVQ==
MIME-Version: 1.0
X-Received: by 10.68.183.194 with SMTP id eo2mr19186341pbc.43.1371982374935; Sun, 23 Jun 2013 03:12:54 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Sun, 23 Jun 2013 03:12:54 -0700 (PDT)
In-Reply-To: <CADnDZ890QdPc+6J_hc7GXHr6i30XB5FENMb_BZT2OYOFNgO1gw@mail.gmail.com>
References: <CADnDZ890QdPc+6J_hc7GXHr6i30XB5FENMb_BZT2OYOFNgO1gw@mail.gmail.com>
Date: Sun, 23 Jun 2013 12:12:54 +0200
Message-ID: <CADnDZ892Ldv-bmuhXpNzQ7SyFtc1ChpQyYOr8S0wQs0370JkMw@mail.gmail.com>
Subject: Re: documenting feedback of meeting venues
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
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: Sun, 23 Jun 2013 10:13:03 -0000

Hi Bob Hinden, and IETF management

I attended a presentation of IAOC in IETF last-meeting. I have send
you the below message which you did not reply so far (was waiting for
three months). Please note that this is my last reminder (will wait
only two weeks). I was remotely attending your talk in the last IETF
meeting, and I asked a question but you or someone refered me to post
on the list and that I will get reply. Please note I still did not get
a reply and that I think was ignored by the presenters of such work. I
don't think the community can be ignored.

AB
I usually give a communication delay tolerance time for about three
months because people may be busy, but don't forget my requests :-)

On 3/10/13, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> To: Bob Hinden, (presented at IAOC overview)
>
>  My question to Bob; why not document the feedback (of meeting venues) of
> community of past for the future?
>
>  I recommend to change the IAOC procedure, to allow documentation?
>
> AB
>

From jnc@mercury.lcs.mit.edu  Sun Jun 23 05:27:24 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
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 3CB1A21F9AFA for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 05:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 GqwgDsbjZUt6 for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 05:27:19 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 2809221F9A95 for <ietf@ietf.org>; Sun, 23 Jun 2013 05:27:19 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 6BE3018C102; Sun, 23 Jun 2013 08:27:18 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IETF Diversity
Message-Id: <20130623122718.6BE3018C102@mercury.lcs.mit.edu>
Date: Sun, 23 Jun 2013 08:27:18 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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: Sun, 23 Jun 2013 12:27:24 -0000

    > From: Randy Bush <randy@psg.com>

    > there appears to be a problem with your mail system. mail which is
    > clearly from the 1950s is appearing on the ietf list.

You're right about it having fallen through a time warp - but you got the
sign wrong. It's from the future, not the past.

	Noel

From hallam@gmail.com  Sun Jun 23 05:53:33 2013
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 6370321F9D82 for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 05:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.53
X-Spam-Level: 
X-Spam-Status: No, score=-2.53 tagged_above=-999 required=5 tests=[AWL=0.069,  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 0w6mTe-iCXO6 for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 05:53:32 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0DABC21F99D3 for <ietf@ietf.org>; Sun, 23 Jun 2013 05:53:31 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id l18so7707672wgh.14 for <ietf@ietf.org>; Sun, 23 Jun 2013 05:53:31 -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=LwDEfSIJUgsy7xEArsk7yW7gedHV9yxZw+kk3nSwvLY=; b=p+5j+VCum4Jvit4+MsvlZFrRhgNuZmuaZbrfysVbZxJA4b4n4plBLCmV8kHNs0nAA/ to74S+4ghqMinJ+I+mXz+9I+ipYH6EivZYKuErveKyKcYjXlSgqf88Z5Cm4147tnAM+H kXcohBg0q7458ybM7U/cD0mHCyacrHGXLl+IwevS9ZIU9uRrrc568PWR3cpUdR1gR7wT 3/ahXNEgGVT5hvO0z22xO8FZ8a/9JNz+D7Xj2rOWfCWp53VEJVnWdRUq+yrKWmdK5xML FNtWlXYpRUKlW/a15HkhXWAKI6vdhTXd0vRiI4fdx8cx74VMM4lDUz4vXuxfdsxIXy+3 Z5gg==
MIME-Version: 1.0
X-Received: by 10.194.104.74 with SMTP id gc10mr13908774wjb.48.1371992011184;  Sun, 23 Jun 2013 05:53:31 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Sun, 23 Jun 2013 05:53:30 -0700 (PDT)
In-Reply-To: <37b1f0e97ec7182d9cb86e22b993b270.squirrel@www.trepanning.net>
References: <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <37b1f0e97ec7182d9cb86e22b993b270.squirrel@www.trepanning.net>
Date: Sun, 23 Jun 2013 08:53:30 -0400
Message-ID: <CAMm+LwjTk_rtPgU+Tp_A=L_SHYHV9OAoFHo3JOqtHkD47RDTqQ@mail.gmail.com>
Subject: Re: IETF Diversity
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dan Harkins <dharkins@lounge.org>
Content-Type: multipart/alternative; boundary=047d7bf10b4676219a04dfd1c804
Cc: 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: Sun, 23 Jun 2013 12:53:33 -0000

--047d7bf10b4676219a04dfd1c804
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Jun 23, 2013 at 1:36 AM, Dan Harkins <dharkins@lounge.org> wrote:

>
> On Tue, June 18, 2013 9:52 am, Phillip Hallam-Baker wrote:
> > I am rather disappointed that there hasn't been any followup to the
> > diversity discussion that took place at the plenary.
> >
> > I do applications and I do security and so having a diverse range of
> input
> > is critical if the final product is going to be useful. There are no
> > gender
> > or cultural issues in packet routing that I am aware of. But once we get
> > to
> > the application layer they become central.
>
>   Interesting. Can you explain what it is about the application layer
> that introduces gender and cultural issues?


Internationalization is not an issue for IPv6 or you are doing it really
wrong. If you get to the apps layer it becomes very important.

The IP layer does not interface to people, the apps layer does.


  Internet stalking? Maybe you should call for a BoF to address the issue.
> I'm not sure what protocol can be developed, or modification to an existing
> protocol, that can address the stalking problem but I'm all ears!


The issue is not necessarily lets build a protocol to stop stalking.

Rather it is a question of having that context in mind when we are
discussing privacy issues. Right now the only contexts we seem to consider
privacy in are 'how does a dissident stop the government seeing what they
are talking about to others' and 'how do we stop a government catching said
dissident'.

Since the answers to both involve steganography, I don't see an open venue
as a useful place to engage in such work. But it gets raised as it is the
sort of threat men can relate to. Meanwhile rather more common threats that
we can deal with are ignored.

It is a matter of priorities.

> At the plenary I pointed out that there have been women involved in IETF
> > ever since I started in IETF over 20 years ago now. Yet we have an IAB
> and
> > an IESG with only one female member who is not ex-officio (according to
> > their Web sites)
>
>   Can you restate that as a problem? And also explain why it is a problem?



It demonstrates that the IETF diversity problem is not due to a lack of
qualified people. There are other factors at work.

> I do not think that gender is the only diversity problem in IETF but it is
> > one that can be measured and the IETF is conspicuously failing. We also
> > have a rather severe age problem, twenty years ago EKR and myself were
> > among the youngest participants in most discussions and setting aside the
> > grad students the same is usually true today.
>
>   Gosh. I feel so left out. I'm as old as EKR (and probably you) and have
> been
> involved in the IETF for about as long as he has yet you do not include me
> in
> your measure of diversity. Do you think that maybe you have a problem with
> measurement of the problem?


My point was that there cohort ten years younger than ourselves is very
thin. The cohort ten years younger than that mostly grad students who we
seem to be unable to persuade to continue participating after they hand in
their thesis.


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

--047d7bf10b4676219a04dfd1c804
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sun, Jun 23, 2013 at 1:36 AM, Dan Harkins <span dir=3D"ltr">&lt;=
<a href=3D"mailto:dharkins@lounge.org" target=3D"_blank">dharkins@lounge.or=
g</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
On Tue, June 18, 2013 9:52 am, Phillip Hallam-Baker wrote:<br>
&gt; I am rather disappointed that there hasn&#39;t been any followup to th=
e<br>
&gt; diversity discussion that took place at the plenary.<br>
&gt;<br>
&gt; I do applications and I do security and so having a diverse range of i=
nput<br>
&gt; is critical if the final product is going to be useful. There are no<b=
r>
&gt; gender<br>
&gt; or cultural issues in packet routing that I am aware of. But once we g=
et<br>
&gt; to<br>
&gt; the application layer they become central.<br>
<br>
</div>=A0 Interesting. Can you explain what it is about the application lay=
er<br>
that introduces gender and cultural issues?</blockquote><div><br></div><div=
 style>Internationalization is not an issue for IPv6 or you are doing it re=
ally wrong. If you get to the apps layer it becomes very important.</div>
<div style><br></div><div style>The IP layer does not interface to people, =
the apps layer does.</div><div><br></div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
=A0 Internet stalking? Maybe you should call for a BoF to address the issue=
.<br>
I&#39;m not sure what protocol can be developed, or modification to an exis=
ting<br>
protocol, that can address the stalking problem but I&#39;m all ears!</bloc=
kquote><div><br></div><div style>The issue is not necessarily lets build a =
protocol to stop stalking.</div><div style><br></div><div style>Rather it i=
s a question of having that context in mind when we are discussing privacy =
issues. Right now the only contexts we seem to consider privacy in are &#39=
;how does a dissident stop the government seeing what they are talking abou=
t to others&#39; and &#39;how do we stop a government catching said disside=
nt&#39;.</div>
<div style><br></div><div style>Since the answers to both involve steganogr=
aphy, I don&#39;t see an open venue as a useful place to engage in such wor=
k. But it gets raised as it is the sort of threat men can relate to. Meanwh=
ile rather more common threats that we can deal with are ignored.</div>
<div style><br></div><div style>It is a matter of priorities.=A0</div><div =
style><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">&gt; At th=
e plenary I pointed out that there have been women involved in IETF<br>

&gt; ever since I started in IETF over 20 years ago now. Yet we have an IAB=
 and<br>
&gt; an IESG with only one female member who is not ex-officio (according t=
o<br>
&gt; their Web sites)<br>
<br>
</div>=A0 Can you restate that as a problem? And also explain why it is a p=
roblem?</blockquote><div><br></div><div><br></div><div style>It demonstrate=
s that the IETF diversity problem is not due to a lack of qualified people.=
 There are other factors at work.</div>
<div style><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">&gt; =
I do not think that gender is the only diversity problem in IETF but it is<=
br>

&gt; one that can be measured and the IETF is conspicuously failing. We als=
o<br>
&gt; have a rather severe age problem, twenty years ago EKR and myself were=
<br>
&gt; among the youngest participants in most discussions and setting aside =
the<br>
&gt; grad students the same is usually true today.<br>
<br>
</div>=A0 Gosh. I feel so left out. I&#39;m as old as EKR (and probably you=
) and have<br>
been<br>
involved in the IETF for about as long as he has yet you do not include me =
in<br>
your measure of diversity. Do you think that maybe you have a problem with<=
br>
measurement of the problem?</blockquote><div><br></div><div style>My point =
was that there cohort ten years younger than ourselves is very thin. The co=
hort ten years younger than that mostly grad students who we seem to be una=
ble to persuade to continue participating after they hand in their thesis.<=
/div>
<div><br></div></div><div><br></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br>
</div></div>

--047d7bf10b4676219a04dfd1c804--

From bob.hinden@gmail.com  Sun Jun 23 09:52:45 2013
Return-Path: <bob.hinden@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 8DCA521F9E17 for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 09:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ubxBGwbe3l00 for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 09:52:44 -0700 (PDT)
Received: from mail-ea0-x236.google.com (mail-ea0-x236.google.com [IPv6:2a00:1450:4013:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id F305C21F9BFC for <ietf@ietf.org>; Sun, 23 Jun 2013 09:52:43 -0700 (PDT)
Received: by mail-ea0-f182.google.com with SMTP id d10so5640704eaj.41 for <ietf@ietf.org>; Sun, 23 Jun 2013 09:52:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=E0LUhtdol4AFySuSDNJSauFWJVNu92DsEkZNHtqtDo8=; b=bVk/Ka8QatZp4DyEXw41bVUQJmIsvA9+fcwoTZuCyqP0d+PWMdVvxeqwghWG59Comx /34wkpH04HDUqIU1w7E0w1USN1RRmHOMk08EMrmO9F1qwpmDY8J0jdPiLSqe6sJDvCtY w6k85gUXpAJ2roYLjjf6rAr1EfYfTGfwNeBnsppB5YAB5xIraYNgi8kbSOguOS039SvS Kgnj9kuVVfrME1zNKJl+L5BEcXTLBY0lJ23G1N5VZKY7EIgnIzN1FhilLQfSyxJFni2d 4FN/gufjOXHs2EmsytZiTzehL6DUAofAk2pUCLd0v3s9AUdxYNJFS58vZC2U+3O64gWE KcRA==
X-Received: by 10.14.178.8 with SMTP id e8mr17783091eem.20.1372006354639; Sun, 23 Jun 2013 09:52:34 -0700 (PDT)
Received: from [192.168.126.217] (62-90-105-45.bb.netvision.net.il. [62.90.105.45]) by mx.google.com with ESMTPSA id p49sm22381320eeu.2.2013.06.23.09.52.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 23 Jun 2013 09:52:33 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: documenting feedback of meeting venues
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CADnDZ892Ldv-bmuhXpNzQ7SyFtc1ChpQyYOr8S0wQs0370JkMw@mail.gmail.com>
Date: Sun, 23 Jun 2013 19:52:32 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <8105707F-8782-43EF-864B-77F94B6F6B7C@gmail.com>
References: <CADnDZ890QdPc+6J_hc7GXHr6i30XB5FENMb_BZT2OYOFNgO1gw@mail.gmail.com> <CADnDZ892Ldv-bmuhXpNzQ7SyFtc1ChpQyYOr8S0wQs0370JkMw@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf <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: Sun, 23 Jun 2013 16:52:45 -0000

AB,

Thanks for the reminder.

We have starting putting the post meeting survey results online.  See:

  http://iaoc.ietf.org/surveys.html

IETF 70, 68, 65, 64 are there now.  The IAD will add IETF 80 through 86 =
later this week this week and earlier meetings after that.

Bob


On Jun 23, 2013, at 1:12 PM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> Hi Bob Hinden, and IETF management
>=20
> I attended a presentation of IAOC in IETF last-meeting. I have send
> you the below message which you did not reply so far (was waiting for
> three months). Please note that this is my last reminder (will wait
> only two weeks). I was remotely attending your talk in the last IETF
> meeting, and I asked a question but you or someone refered me to post
> on the list and that I will get reply. Please note I still did not get
> a reply and that I think was ignored by the presenters of such work. I
> don't think the community can be ignored.
>=20
> AB
> I usually give a communication delay tolerance time for about three
> months because people may be busy, but don't forget my requests :-)
>=20
> On 3/10/13, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
>> To: Bob Hinden, (presented at IAOC overview)
>>=20
>> My question to Bob; why not document the feedback (of meeting venues) =
of
>> community of past for the future?
>>=20
>> I recommend to change the IAOC procedure, to allow documentation?
>>=20
>> AB
>>=20


From sm@resistor.net  Sun Jun 23 12:30:23 2013
Return-Path: <sm@resistor.net>
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 6966121F9EC1 for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 12:30:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.536
X-Spam-Level: 
X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 HukrKgZB3lYA for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 12:30:21 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B72C621F9EA6 for <ietf@ietf.org>; Sun, 23 Jun 2013 12:30:21 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5NJUEYm008578; Sun, 23 Jun 2013 12:30:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372015820; bh=YxFjI8rNcYxyRFl7i6C4Sv3jazTvK0Vd+RjbxDPMOFM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=BV0G4g3RJeflqP2cZUS0rhKchb8DSb7/SdPg87g/3dLVRtrnSRtbVgb8bEnbrUa7R apXoU592+nxq6aPdwkwspS1hO7EWMb3M4qgYQGEM1wZNoCKzleeWEiyvcsmRELQV4y Y0JKOuSIBjqQBngotIJU63jqX7u8aG2ufaNiGnEU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1372015820; i=@resistor.net; bh=YxFjI8rNcYxyRFl7i6C4Sv3jazTvK0Vd+RjbxDPMOFM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Ds8QnzmQiN3qwfhitxyaio633Q+i548k+epVQEqKe8+sRbGol7Yn/OeJt36eP6zUd 6+KI+tmUcJ1K9/xgjdtWIOTOlwYXQpn5+WY0CUfb0IJLmGxbPFXe6pNm/kruM9EwT1 5kjobZzAcj/TZE0cb1cVIeKXh2L1VG2NqCEIWAnU=
Message-Id: <6.2.5.6.2.20130623073559.0c270d88@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 23 Jun 2013 12:21:21 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Back to the future (was: IETF Diversity)
In-Reply-To: <20130623122718.6BE3018C102@mercury.lcs.mit.edu>
References: <20130623122718.6BE3018C102@mercury.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>
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: Sun, 23 Jun 2013 19:30:23 -0000

At 05:27 23-06-2013, Noel Chiappa wrote:
>You're right about it having fallen through a time warp - but you got the
>sign wrong. It's from the future, not the past.

I went back to the future to play the repeated game and I read an 
(edited) extract of a message from Andy Cohen:

   "I've been struck by the intensity, the humour, pettiness, and grandeur.
    I haven't yet concluded whether this is a group of smaller alliances
    protecting vested interests...or a bunch of pretty remarkable folk
    working in remarkable ways -- maybe both."

There was something I did not know [1] about the Internet Engineering 
Tooth Fairy, i.e. why it was set up in such a way.  Please do not ask me why.

It seems that the current discussion is about morganatic marriages, 
i.e. that's all that the person got.  Solutionists recommend easy 
solutions which ignore complex human problems.  Oddly enough a 
solution was chosen many years ago.  As time went by people forgot 
what was chosen.  It is yet to be established whether that was out of 
convenience or something else.  That solution was likely chosen to 
avoid incestuous relationships where vested interests could flourish.

Meritocracy can degenerate into cronyism.  Diversity can also 
degenerate into cronyism.  Perceptions are what people believe and 
what people believe is reality.  The answer being sought might be in the above.

Regards,
-sm

1. I am not sure whether I actually knew about it.  There are many 
things which I do not know. 


From jmamodio@gmail.com  Sun Jun 23 14:53:57 2013
Return-Path: <jmamodio@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 7DADF21F9D7F for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 14:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 tN8z-QAnhIKE for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 14:53:57 -0700 (PDT)
Received: from mail-gh0-x22f.google.com (mail-gh0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id ECDEF21F9CDB for <ietf@ietf.org>; Sun, 23 Jun 2013 14:53:56 -0700 (PDT)
Received: by mail-gh0-f175.google.com with SMTP id z19so3137544ghb.6 for <ietf@ietf.org>; Sun, 23 Jun 2013 14:53:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=vN89kV0geK0sQJUnFzxsF0OxKQL2Qht8/A5kGt6B0Sk=; b=KevnnVluh5R90O7YMVPVqJOFRmCNSihitF5xfcsm8XZFklEJzBL1XWezaH5Fphcvqf bMwd6ssR88IC5+b3IPlasElHDFMWLc+R4Jdk/JK7cg8SAgvgLrcgoux8AzktYNC2BGG4 +6eLFriJY9/AiICNKwadtlhHIXvzFvD/q2qAh75s7ZSZZ9ST0iUvi2ZUA7nACZBf+res /IZVZtOXEtVbUdZPsOur8MkRrfNtHxz56n0E3SXy346Jr+kJovk656BZNL8Ktdk3+X4W zdxvYrUbTF3lH4kdrv0fP6fwmvGapvveAqbIqMg2WYnL9GEd0gx4KJlQ3UlhqxI/7OcY pW0w==
X-Received: by 10.236.201.79 with SMTP id a55mr11740265yho.33.1372024436481; Sun, 23 Jun 2013 14:53:56 -0700 (PDT)
Received: from [10.0.10.102] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id y70sm25958697yhe.15.2013.06.23.14.53.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 23 Jun 2013 14:53:55 -0700 (PDT)
References: <20130623122718.6BE3018C102@mercury.lcs.mit.edu>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20130623122718.6BE3018C102@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <23E97BB2-F808-4A8C-B61F-C146AAF5E096@gmail.com>
X-Mailer: iPad Mail (10B329)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: IETF Diversity
Date: Sun, 23 Jun 2013 16:53:57 -0500
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: "ietf@ietf.org" <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: Sun, 23 Jun 2013 21:53:57 -0000

Yup he didn't apply the Y2K patch ... those missing bits ...

-Jorge

On Jun 23, 2013, at 7:27 AM, jnc@mercury.lcs.mit.edu (Noel Chiappa) wrote:

>> From: Randy Bush <randy@psg.com>
> 
>> there appears to be a problem with your mail system. mail which is
>> clearly from the 1950s is appearing on the ietf list.
> 
> You're right about it having fallen through a time warp - but you got the
> sign wrong. It's from the future, not the past.
> 
>    Noel

From dhc@dcrocker.net  Sun Jun 23 15:00:24 2013
Return-Path: <dhc@dcrocker.net>
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 411FE21F9EF0 for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 15:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 OQeAz7abIsgn for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 15:00:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5344C21F9F32 for <ietf@ietf.org>; Sun, 23 Jun 2013 15:00:19 -0700 (PDT)
Received: from [192.168.6.161] (ip-64-134-234-85.public.wayport.net [64.134.234.85]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5NM0D1i017675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Jun 2013 15:00:16 -0700
Message-ID: <51C76FEC.9040009@dcrocker.net>
Date: Sun, 23 Jun 2013 15:00:12 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com>
In-Reply-To: <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 23 Jun 2013 15:00:17 -0700 (PDT)
Cc: John C Klensin <john-ietf@jck.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Sun, 23 Jun 2013 22:00:24 -0000

On 6/22/2013 10:28 AM, Barry Leiba wrote:
>     I believe that it would be wise to discourage
>     "RECOMMENDED" and "NOT RECOMMENDED" as synonyms for "SHOULD" and
>     "SHOULD NOT" unless they are clearly necessary to avoid awkward
>     sentences and the non-A/S intent is completely clear.
>
>
> A fine suggestion, with which I agree.


For normative vocabulary, synonyms are sinful.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From brian.e.carpenter@gmail.com  Sun Jun 23 21:36:36 2013
Return-Path: <brian.e.carpenter@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 D3B7E21F9A40 for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 21:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 owhJ8UR2dEbr for <ietf@ietfa.amsl.com>; Sun, 23 Jun 2013 21:36:36 -0700 (PDT)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0A321F9A2E for <ietf@ietf.org>; Sun, 23 Jun 2013 21:36:36 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r10so360758pdi.27 for <ietf@ietf.org>; Sun, 23 Jun 2013 21:36:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=H105xGh9zGdwcZQ2fNI+7bAhvV0MXgm77qX+xtUgIME=; b=T7Q32mEub4CYgsab8yqDXqFmqfY8+gn83eopnH23BcjlFsF2i/nTLsfpXkVBid1gEo X5xe1tZD9dEC+UVaqtmZLauT0LFGJYqg6ozirGaBtB7Smm+rx7OQzr28M+IOfG5U11lb Fwr3b4hFMKRNMfzXjEEdFG/z+GE2IsHw3878oVp7GwA/qsgX3cpfOerjoskpqPh0KJ2n C1K6/KoBRC8Pm1K+rAoVuOBIL1bX6zl6RLhJWBZT+CAAj2wNZXwRHpy9d8cdOcIkFXcw FS9dcCe82/XVrPFSsunJyg7a/70bp14MZSaqRBMT9OXELk5ptZRkO/ATnxS2AAyqfoZi 7qZQ==
X-Received: by 10.66.254.135 with SMTP id ai7mr18468303pad.185.1372048594968;  Sun, 23 Jun 2013 21:36:34 -0700 (PDT)
Received: from [192.168.178.22] (91.198.69.111.dynamic.snap.net.nz. [111.69.198.91]) by mx.google.com with ESMTPSA id iq6sm16226148pbc.1.2013.06.23.21.36.33 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 23 Jun 2013 21:36:34 -0700 (PDT)
Message-ID: <51C7CCD0.4090202@gmail.com>
Date: Mon, 24 Jun 2013 16:36:32 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAOC Website Updated
References: <20130620185914.19663.88097.idtracker@ietfa.amsl.com>
In-Reply-To: <20130620185914.19663.88097.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Mon, 24 Jun 2013 04:36:36 -0000

Hi Ray,

I think it's very good. One micro-comment: the menu at the left
is headed up by the IETF logo (which is in fact a link to
the main site). I did find that momentarily confusing - maybe
the first two items could be labelled "IASA Home" and "About IASA"
to make it clear which menu this is?

Best wishes
   Brian

On 21/06/2013 06:59, IETF Administrative Director wrote:
> One of the IAOC goals for 2013 was to update the IAOC website to improve
> consistency, organization, linkage, and ease of use.
> 
> I am pleased to announce that the IAOC site has been updated and is available 
> now for your use at <http://iaoc.ietf.org/>.
> 
> On the home page see a video of an Overview of the IAOC given by Chair Bob
> Hinden in Orlando that includes a discussion of venue selection and IETF 
> finances.  Also on the home page are recent announcements, as well as reports
> from IANA, the RFC Editor, the IETF Chair, the NomCom Chair, and more.
> 
> The navigation bar makes it easy to find financial statements, minutes,
> meeting sponsorship opportunities, and much more.
> 
> We hope you find this helpful, the IAOC as more transparent, and of course we
> welcome your feedback.
> 
> Ray
> IETF Administrative Director
> 
> PS:  Going to IETF 87 in Berlin?  The IAOC will be doing another overview
> session there, Sunday July 28 at 3:00 PM.  Hope to see you there!
> 

From hallam@gmail.com  Mon Jun 24 04:52:41 2013
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 46EE211E8129 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 04:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064,  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 1loegUIEvVlL for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 04:52:40 -0700 (PDT)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id F370021F9AE8 for <ietf@ietf.org>; Mon, 24 Jun 2013 04:52:39 -0700 (PDT)
Received: by mail-we0-f171.google.com with SMTP id m46so8095695wev.2 for <ietf@ietf.org>; Mon, 24 Jun 2013 04:52:39 -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=yfh8r0a/k7mUJcokxMsQuDxCzoLIfTc311Q1NsF2s/c=; b=cZWrPwGwq/Bd/DE5s9WZpoGkZyMllsrc2cWeTWsW+OJTzyND1chXFJuyisPJ4dTXY3 xYTmcVBFcx3ouKlW3Xr85dbkaehZwSHd/7ofwKRQrnhR3Ww2LV/hxdLpxXMde3QrO1DO cZEM1kj2AmN/KFf4FJ2u9NEXzgB27kEmScoB71rx3RxT4m72VGbtFsf/3zr5CJ56tg89 FalUAq8tDdNGFU4H/cU1DV6oLD7HWClCGVxZ22aQuB05XbOzZz2333oyJfQhQMUvgScG RrWjj9Rel67oXBjEz0qaCPvZgzT/JkaCvkfjhTgGx9lP9C3pUMoW4Yzwd87eDulmqgVK nblA==
MIME-Version: 1.0
X-Received: by 10.180.9.242 with SMTP id d18mr5705085wib.18.1372074759089; Mon, 24 Jun 2013 04:52:39 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Mon, 24 Jun 2013 04:52:39 -0700 (PDT)
In-Reply-To: <51C76FEC.9040009@dcrocker.net>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net>
Date: Mon, 24 Jun 2013 07:52:39 -0400
Message-ID: <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11c2228c9ef1ff04dfe50c67
Cc: John C Klensin <john-ietf@jck.com>, Barry Leiba <barryleiba@computer.org>, IETF-Discussion 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: Mon, 24 Jun 2013 11:52:41 -0000

--001a11c2228c9ef1ff04dfe50c67
Content-Type: text/plain; charset=ISO-8859-1

They are not synonyms

Lets go back to 1980:

Implementations SHOULD support DES
vs
RECOMMENDED encryption algorithms: DES, IDEA


There are many specifications that specify crypto algorithms that should
not. JOSE and XML Signature should not have required algorithms or even
SHOULD language. The protocols that are built on the specifications are
where the normative language belongs.




On Sun, Jun 23, 2013 at 6:00 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 6/22/2013 10:28 AM, Barry Leiba wrote:
>
>>     I believe that it would be wise to discourage
>>     "RECOMMENDED" and "NOT RECOMMENDED" as synonyms for "SHOULD" and
>>     "SHOULD NOT" unless they are clearly necessary to avoid awkward
>>     sentences and the non-A/S intent is completely clear.
>>
>>
>> A fine suggestion, with which I agree.
>>
>
>
> For normative vocabulary, synonyms are sinful.
>
> d/
>
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>



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

--001a11c2228c9ef1ff04dfe50c67
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">They are not synonyms<div><br></div><div style>Lets go bac=
k to 1980:</div><div style><br></div><div style>Implementations SHOULD supp=
ort DES</div><div style>vs</div><div style>RECOMMENDED encryption algorithm=
s: DES, IDEA</div>
<div style><br></div><div style><br></div><div style>There are many specifi=
cations that specify crypto algorithms that should not. JOSE and XML Signat=
ure should not have required algorithms or even SHOULD language. The protoc=
ols that are built on the specifications are where the normative language b=
elongs.=A0</div>
<div style><br></div><div style><br></div></div><div class=3D"gmail_extra">=
<br><br><div class=3D"gmail_quote">On Sun, Jun 23, 2013 at 6:00 PM, Dave Cr=
ocker <span dir=3D"ltr">&lt;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_=
blank">dhc@dcrocker.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 6/22/2013 10:28 AM, Bar=
ry Leiba wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 I believe that it would be wise to discourage<br>
=A0 =A0 &quot;RECOMMENDED&quot; and &quot;NOT RECOMMENDED&quot; as synonyms=
 for &quot;SHOULD&quot; and<br>
=A0 =A0 &quot;SHOULD NOT&quot; unless they are clearly necessary to avoid a=
wkward<br>
=A0 =A0 sentences and the non-A/S intent is completely clear.<br>
<br>
<br>
A fine suggestion, with which I agree.<br>
</blockquote>
<br>
<br></div>
For normative vocabulary, synonyms are sinful.<span class=3D"HOEnZb"><font =
color=3D"#888888"><br>
<br>
d/<br>
<br>
<br>
-- <br>
Dave Crocker<br>
Brandenburg InternetWorking<br>
<a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><=
br>
</div>

--001a11c2228c9ef1ff04dfe50c67--

From elwynd@dial.pipex.com  Mon Jun 24 05:29:57 2013
Return-Path: <elwynd@dial.pipex.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 545E321F9D3E for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 05:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 YVUeq8uWQ1uX for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 05:29:56 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id E0FDA21F9D5A for <ietf@ietf.org>; Mon, 24 Jun 2013 05:29:52 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1Ur5u2-00049T-LS; Mon, 24 Jun 2013 13:29:50 +0100
Subject: Re: IAOC Website Updated
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <51C7CCD0.4090202@gmail.com>
References: <20130620185914.19663.88097.idtracker@ietfa.amsl.com> <51C7CCD0.4090202@gmail.com>
Content-Type: text/plain
Date: Mon, 24 Jun 2013 13:28:31 +0100
Message-Id: <1372076911.4524.6416.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-ACL-Warn: Blacklisted URL in message. (ietf.org) in. See http://lookup.uribl.com.
Cc: 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: Mon, 24 Jun 2013 12:29:57 -0000

Hi, Ray.

I also think it's good.  On the same theme as Brian, the page is linked
to from the 'IASA' link on the main IETF page.  To make it clear what is
going on, it would be good to put the title:
IETF Administrative Support Activity
at the top of the page.

A couple of other nits:

It might also be useful to add 'IASA/IAOC' to the header of the
Announcements page.

The 'Legal' and 'Subpoenas' pages contain significant duplication:
The text in the 'Subpoenas' section of the 'Legal' page is a large
subset of the text on the 'Subpoenas' page.

Conversely, the 'Appeals' page under operations misses the text on the
appeals process in BCP101 that is hidden under the 'Legal' page.

Regards,
Elwyn 



On Mon, 2013-06-24 at 16:36 +1200, Brian E Carpenter wrote:
> Hi Ray,
> 
> I think it's very good. One micro-comment: the menu at the left
> is headed up by the IETF logo (which is in fact a link to
> the main site). I did find that momentarily confusing - maybe
> the first two items could be labelled "IASA Home" and "About IASA"
> to make it clear which menu this is?
> 
> Best wishes
>    Brian
> 
> On 21/06/2013 06:59, IETF Administrative Director wrote:
> > One of the IAOC goals for 2013 was to update the IAOC website to improve
> > consistency, organization, linkage, and ease of use.
> > 
> > I am pleased to announce that the IAOC site has been updated and is available 
> > now for your use at <http://iaoc.ietf.org/>.
> > 
> > On the home page see a video of an Overview of the IAOC given by Chair Bob
> > Hinden in Orlando that includes a discussion of venue selection and IETF 
> > finances.  Also on the home page are recent announcements, as well as reports
> > from IANA, the RFC Editor, the IETF Chair, the NomCom Chair, and more.
> > 
> > The navigation bar makes it easy to find financial statements, minutes,
> > meeting sponsorship opportunities, and much more.
> > 
> > We hope you find this helpful, the IAOC as more transparent, and of course we
> > welcome your feedback.
> > 
> > Ray
> > IETF Administrative Director
> > 
> > PS:  Going to IETF 87 in Berlin?  The IAOC will be doing another overview
> > session there, Sunday July 28 at 3:00 PM.  Hope to see you there!
> > 


From john-ietf@jck.com  Mon Jun 24 05:39:56 2013
Return-Path: <john-ietf@jck.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 A419521E80E9 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 05:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 uNDL-wQ4I2pF for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 05:39:50 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B115921E80DF for <ietf@ietf.org>; Mon, 24 Jun 2013 05:39:50 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ur63h-0005Tz-NX; Mon, 24 Jun 2013 08:39:49 -0400
Date: Mon, 24 Jun 2013 08:39:44 -0400
From: John C Klensin <john-ietf@jck.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: SHOULD and RECOMMENDED
Message-ID: <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com>
In-Reply-To: <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF-Discussion 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: Mon, 24 Jun 2013 12:39:56 -0000

--On Monday, June 24, 2013 07:52 -0400 Phillip Hallam-Baker
<hallam@gmail.com> wrote:

> They are not synonyms
> 
> Lets go back to 1980:
> 
> Implementations SHOULD support DES
> vs
> RECOMMENDED encryption algorithms: DES, IDEA

Actually, that is the point.  The usage above, although much
earlier, reflects the Protocol Specification/ Applicability
Statement split rather well.

But 2119's language makes the two terms substitutable for and
equivalent to each other, which is about as close a definition
of "synonyms" as one can find.  What I said is that making them
equivalent was probably a mistake and that treating them that
was should be discouraged. Others expressed agreement with that
assessment.  

Personally, I don't think the problem is severe enough to reopen
2119.  If others disagree and believe that 2119 is generating
enough problems to be worth an update, I await a draft.

So, other than quibbling about the "synonym" issue -- not
generally, which no one has claimed, but in context with 2119--
are you disagreeing and, if so, about what?

   john



From hallam@gmail.com  Mon Jun 24 05:43:31 2013
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 42B8A21E80EE for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 05:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.060,  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 T5RvD9zoKxRu for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 05:43:30 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 1490921E80EC for <ietf@ietf.org>; Mon, 24 Jun 2013 05:43:29 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id c10so2493974wiw.5 for <ietf@ietf.org>; Mon, 24 Jun 2013 05:43:29 -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=mqn95nuClzw8Hfzd3uWHHivYsupoK9I1DVtXyHaVV3w=; b=Xpfa++cFyBRno0Zipet/e2HLDecOFpyk97OCy11v6dXVjp94WerYRUsckd2jyzSiE5 BMk2/u/IHHHXuCH1lMyG9W1WuWswN4cmYiw1JvUQJW8TqschKWwOyBWldAX1pBsLec7C Zcuc+ap1CrCW4R0KFiiBV8iVt4evMikcJhCMSSX8+82REXscheGWWPh59OsDN0pV6SXq +vu7EQW2R0dLyMvqAtQFl4BBY/2PguusJBsC9iQF/H7YwE7WZ3TXsQiFRx3aqKWkN98/ 3QM2/2dblaAnIfqf6kUaziX9SE3BnopOGgZIi3JaK5SfbnACZ6mhoXgKc5hNCqb9sv+I egrg==
MIME-Version: 1.0
X-Received: by 10.194.104.74 with SMTP id gc10mr16389820wjb.48.1372077809184;  Mon, 24 Jun 2013 05:43:29 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Mon, 24 Jun 2013 05:43:28 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751E132F@mbx-01.win.nominum.com>
References: <51C09437.5040006@stpeter.im> <CAMm+LwhCyF=7VStP7Vkav3gESeVvfLs5sYToY2ePR7OwOEZStw@mail.gmail.com> <CAMm+LwiLvVxtH9O-k9vBjPj1Efm_hCbw+0VYsUFv0aOKZVMycA@mail.gmail.com> <51C14C06.1060207@cs.helsinki.fi> <CAMm+Lwg4CzuB4a4dxb4i8ZZZ4q1TgzYYA27WRtf=ttEYU8MaYA@mail.gmail.com> <2t0xiMKNOIudTjLczEne-KxRYX9oK6AXs7ljHaaAhiRgAJ7bs@smtp.gmail.com> <51C1CB4D.4030006@stpeter.im> <51C1CCCB.3060601@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751E0DC6@mbx-01.win.nominum.com> <51C1F277.8050902@dougbarton.us> <51C1F45E.2030805@gmail.com> <51C1F592.1060708@dougbarton.us> <51C1FB2B.7080205@cs.helsinki.fi> <6.2.5.6.2.20130619114856.0caa5ec0@resistor.net> <0D1D10FE-39B0-4C51-9283-715823CD4969@checkpoint.com> <8D23D4052ABE7A4490E77B1A012B6307751E132F@mbx-01.win.nominum.com>
Date: Mon, 24 Jun 2013 08:43:28 -0400
Message-ID: <CAMm+LwgSHuZeUqFiFwwqpCoCk-hj7TkpebBR-Oz7Ygkh1r+pOQ@mail.gmail.com>
Subject: Re: Is the IETF is an international organization? (was: IETF Diversity)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=047d7bf10b466bb90404dfe5c239
Cc: SM <sm@resistor.net>, "<ietf@ietf.org>" <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: Mon, 24 Jun 2013 12:43:31 -0000

--047d7bf10b466bb90404dfe5c239
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jun 19, 2013 at 4:40 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Jun 19, 2013, at 3:18 PM, Yoav Nir <ynir@checkpoint.com> wrote:
> > Yeah, and "act" is what Americans call statutes, and Selma is a city in
> Alabama where there was some controversy about voting rights. You sure need
> to know a lot of Americana to participate meaningfully in some of these
> discussions.
>
> Sorry.   That was directed largely at Melinda who is, to the best of my
> understanding, an American.   The point was that in fact the civil rights
> movement started with individuals, not the government.
>


It would have been easier to note that the technological terror we have
created has been one of the drivers behind the Arab Spring.

Before that Communism was defeated through a bottom up movement: People
just walked away.


I seem to remember that there is a country in North America where the
foundation myth is based on the claim of a bottom up revolt but I can't
quite recall which one. Something to do with tea.


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

--047d7bf10b466bb90404dfe5c239
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Jun 19, 2013 at 4:40 PM, Ted Lemon <span dir=3D"lt=
r">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com" target=3D"_blank">Ted.Lemon=
@nominum.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"im">On Jun 19, 2013, at 3:18 PM, Yoav Nir &l=
t;<a href=3D"mailto:ynir@checkpoint.com">ynir@checkpoint.com</a>&gt; wrote:=
<br>

&gt; Yeah, and &quot;act&quot; is what Americans call statutes, and Selma i=
s a city in Alabama where there was some controversy about voting rights. Y=
ou sure need to know a lot of Americana to participate meaningfully in some=
 of these discussions.<br>

<br>
</div>Sorry. =A0 That was directed largely at Melinda who is, to the best o=
f my understanding, an American. =A0 The point was that in fact the civil r=
ights movement started with individuals, not the government.<br></blockquot=
e>
<div><br></div><div><br></div><div>It would have been easier to note that t=
he technological terror we have created has been one of the drivers behind =
the Arab Spring.</div></div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra" style>
Before that Communism was defeated through a bottom up movement: People jus=
t walked away.</div><div class=3D"gmail_extra" style><br></div><div class=
=3D"gmail_extra" style><br></div><div class=3D"gmail_extra" style>I seem to=
 remember that there is a country in North America where the foundation myt=
h is based on the claim of a bottom up revolt but I can&#39;t quite recall =
which one. Something to do with tea.</div>
<br clear=3D"all"><div><br></div>-- <br>Website: <a href=3D"http://hallamba=
ker.com/">http://hallambaker.com/</a><br>
</div></div>

--047d7bf10b466bb90404dfe5c239--

From hartmans@mit.edu  Mon Jun 24 06:38:21 2013
Return-Path: <hartmans@mit.edu>
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 982A621F9EDE; Mon, 24 Jun 2013 06:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 RZ9Dkg3mpIku; Mon, 24 Jun 2013 06:38:15 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id B196421F9EC2; Mon, 24 Jun 2013 06:38:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 77E23200E0; Mon, 24 Jun 2013 09:34:06 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTy0ix9-IkPT; Mon, 24 Jun 2013 09:34:05 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 24 Jun 2013 09:34:05 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 9F93A80952; Mon, 24 Jun 2013 09:37:49 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: ietf@ietf.org,secdir@ietf.org
Subject: Secdir review of draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05
Date: Mon, 24 Jun 2013 09:37:49 -0400
Message-ID: <tslhagny6he.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: draft-ietf-xrblock-rtcp-xr-discard-rle-metrics.all@tools.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: Mon, 24 Jun 2013 13:38:21 -0000

Please treat these comments as normal last-call comments.

I've been asigned as a security directorate reviewer for this draft.

This draft specifies a mechanism to indicate which packets were
discarded in a RTP stream.  for the most part, this doesn't seem to have
any security implications, and the text is clear.  I do have one
concern.

Has the WG analyzed implications of providing feedback to an attacker on
what specific SRTP packets are discarded?  In the past we've run into
trouble with security systems that were too verbose in error reporting.
As an example, in certain public-key crypto constructions knowing
whether a packet produced a decoding error vs a signature error after
decryption can provide an attacker generating forged packets valuable
information to attack the system.

It's quite possible that SRTP doesn't have problems in this regard.  I
just want to confirm that the analysis has been done. 

From sm@resistor.net  Mon Jun 24 09:36:50 2013
Return-Path: <sm@resistor.net>
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 D5D4021F991F for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 09:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 SbRM3-GsrWez for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 09:36:49 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BEDDF21F93BA for <ietf@ietf.org>; Mon, 24 Jun 2013 09:36:49 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5OGai2l006585 for <ietf@ietf.org>; Mon, 24 Jun 2013 09:36:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372091808; bh=1ZhM9oD2NawDacvww6I/KgVsQnHZoG6ryw5CAVvyt8o=; h=Date:To:From:Subject:In-Reply-To:References; b=uhe0oq7axmoa97AJXYw8UwvBYOaVIZ+i5wJjaapBfT/8/YvnSPMQq6llYJy8qptlM m+nVojH7q8XEWCikD9MoeXaIVddJ5pilKY08CsE1Nt5oYXj+27XQDJ2OcPKsw6hnSl R+BDPN6eyYIyGkGF00mPy6RffgdP+8E8bflDASwE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1372091808; i=@resistor.net; bh=1ZhM9oD2NawDacvww6I/KgVsQnHZoG6ryw5CAVvyt8o=; h=Date:To:From:Subject:In-Reply-To:References; b=4cdMfvTjoiNzz1eUQ7wtFKTCLkEd7ZHEUV5lnJI++QvdsI3JesgFag/Fgv5DlcHHd V7Dw1tmR+dec675sguA+BHOz7tcyuMRKZF0ZNSepS3HR/cFuwzDscTbpalU0kg9S3A Q2SpV+E/kwLjcEaSSNAsMam14/72n+4el5vhR2mg=
Message-Id: <6.2.5.6.2.20130624083353.0cd2d900@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 24 Jun 2013 09:34:52 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: IASA contracts (was: IAOC Website Updated)
In-Reply-To: <1372076911.4524.6416.camel@mightyatom>
References: <20130620185914.19663.88097.idtracker@ietfa.amsl.com> <51C7CCD0.4090202@gmail.com> <1372076911.4524.6416.camel@mightyatom>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Mon, 24 Jun 2013 16:36:51 -0000

The IAOC states that "The IASA site is designed to provide the IETF 
community with transparency into the fiscal and administrative 
activities of the IAOC".

According to the IAOC minutes:

   "The IAOC approves a two-year extension of the Legal Services Contract with
    Contreras Legal Strategy LLC and requests the Internet Society to 
enter into
    such agreements as to effect this extension.

    The motion passed. Randy [Bush] abstained because he had not seen 
the contract."

The Contracts webpage ( http://iaoc.ietf.org/contracts.html ) does 
not contain most of the contracts which were signed by the IAD.  The 
IAD previously mentioned that the contracts will be published after 
the last meeting.

Regards,
-sm


From hsantos@isdg.net  Mon Jun 24 11:53:54 2013
Return-Path: <hsantos@isdg.net>
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 C0EBB21E815D for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 11:53:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.762
X-Spam-Level: 
X-Spam-Status: No, score=-102.762 tagged_above=-999 required=5 tests=[AWL=-1.027, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
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 4pYN0-Aq+ab4 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 11:53:45 -0700 (PDT)
Received: from ntbbs.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6849E21E8159 for <ietf@ietf.org>; Mon, 24 Jun 2013 11:53:44 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2365; t=1372100021; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=zpzfnAw VPMbx5CT9U9O7m+tKakA=; b=ARld3S6XJOkavJXhRlQ8lkLHl2KVF1rqtNY1Utj DNpnfnrQN0JHyhGyM5GXub8VkZqfMMB3kzD0UnzLlTGthDIu4PoAxz1eWFHZRSTb IB6WH1tbTPurXnHxSiqj/ZDG/xPM28QOhi2hntbtcSj4py0vGXKOIOdtTk8iFZIF T0Kw=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 24 Jun 2013 14:53:41 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2857561901.3.2568; Mon, 24 Jun 2013 14:53:40 -0400
Message-ID: <51C89517.1090603@isdg.net>
Date: Mon, 24 Jun 2013 14:51:03 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com>
In-Reply-To: <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion 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: Mon, 24 Jun 2013 18:53:54 -0000

On 6/24/2013 8:39 AM, John C Klensin wrote:
> --On Monday, June 24, 2013 07:52 -0400 Phillip Hallam-Baker
> <hallam@gmail.com> wrote:
>
>> They are not synonyms
>>
>> Lets go back to 1980:
>>
>> Implementations SHOULD support DES
>> vs
>> RECOMMENDED encryption algorithms: DES, IDEA
>
> Actually, that is the point.  The usage above, although much
> earlier, reflects the Protocol Specification/ Applicability
> Statement split rather well.
>
> But 2119's language makes the two terms substitutable for and
> equivalent to each other, which is about as close a definition
> of "synonyms" as one can find.  What I said is that making them
> equivalent was probably a mistake and that treating them that
> was should be discouraged. Others expressed agreement with that
> assessment.
>
> Personally, I don't think the problem is severe enough to reopen
> 2119.  If others disagree and believe that 2119 is generating
> enough problems to be worth an update, I await a draft.
>
> So, other than quibbling about the "synonym" issue -- not
> generally, which no one has claimed, but in context with 2119--
> are you disagreeing and, if so, about what?
>
>     john

In my view, a SHOULD is just a highly RECOMMENDED mode of operation, the 
preferred mode, the mode that SHOULD be enabled out of the box.

The conflicts I see is whether the usage of a SHOULD means it really is 
a MUST be implemented as described and the exception is when there is no 
other alternative available. A common reference is use EHLO first, 
fallback to HELO.

What is often forgotten is the ON/OFF configuration aspect. So even if 
there is a MUST implement SHOULD thinking, the question is whether there 
is an allowance to disable or turn off the feature, i.e. can an SMTP 
server disable EHLO and operate in pure RFC821 (STD10) mode?  The answer 
to the question is yes, its possible, and therefore all implementations 
MUST be ready in operate in SMTP (821) mode FIRST, ESMTP mode second.

I think the dilemma is that we have new integration needs and in some 
cases, one protocol or set of integrated protocols simple works better 
when a traditional optional technology i.e. SMTP extension, is used. So 
there is a mindset, it seems, a SHOULD is really a MUST and only under 
extreme situations,  the alternative can be used, if presented.

--
HLS


From rpelletier@isoc.org  Mon Jun 24 12:23:03 2013
Return-Path: <rpelletier@isoc.org>
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 59A3521E80FA for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 12:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.495
X-Spam-Level: 
X-Spam-Status: No, score=-102.495 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 TJQxKy8DunAl for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 12:22:53 -0700 (PDT)
Received: from smtp86.ord1c.emailsrvr.com (smtp86.ord1c.emailsrvr.com [108.166.43.86]) by ietfa.amsl.com (Postfix) with ESMTP id 98C1F21E8170 for <ietf@ietf.org>; Mon, 24 Jun 2013 12:22:31 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 669645010A; Mon, 24 Jun 2013 15:22:30 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 186E2500DB;  Mon, 24 Jun 2013 15:22:30 -0400 (EDT)
Subject: Re: IASA contracts (was: IAOC Website Updated)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <6.2.5.6.2.20130624083353.0cd2d900@resistor.net>
Date: Mon, 24 Jun 2013 15:22:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A5FF4E6-7954-4C23-BE7A-CFA826B32C13@isoc.org>
References: <20130620185914.19663.88097.idtracker@ietfa.amsl.com> <51C7CCD0.4090202@gmail.com> <1372076911.4524.6416.camel@mightyatom> <6.2.5.6.2.20130624083353.0cd2d900@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1085)
Cc: 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: Mon, 24 Jun 2013 19:23:04 -0000

On Jun 24, 2013, at 12:34 PM, SM wrote:

> The IAOC states that "The IASA site is designed to provide the IETF =
community with transparency into the fiscal and administrative =
activities of the IAOC".
>=20
> According to the IAOC minutes:
>=20
>  "The IAOC approves a two-year extension of the Legal Services =
Contract with
>   Contreras Legal Strategy LLC and requests the Internet Society to =
enter into
>   such agreements as to effect this extension.
>=20
>   The motion passed. Randy [Bush] abstained because he had not seen =
the contract."
>=20
> The Contracts webpage ( http://iaoc.ietf.org/contracts.html ) does not =
contain most of the contracts which were signed by the IAD.  The IAD =
previously mentioned that the contracts will be published after the last =
meeting.

Progress is being made.

The ICANN SLA for 2013 has been published.
The Verilan Master Services Agreement 2013 has been published.
Both the Secretariat and the RFC Production Center contracts are under =
review and I expect them published in the next two weeks

We have more to do and appreciate the continuing community interest in =
and feedback on what we do.
Thanks
Ray

PS Hope to see you in Berlin


>=20
> Regards,
> -sm
>=20


From mthornbu@adobe.com  Mon Jun 24 12:47:17 2013
Return-Path: <mthornbu@adobe.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 88AC611E8161 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 12:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 R04qq9XdXUgP for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 12:47:11 -0700 (PDT)
Received: from exprod6og120.obsmtp.com (exprod6og120.obsmtp.com [64.18.1.236]) by ietfa.amsl.com (Postfix) with ESMTP id 767E721F9AA9 for <ietf@ietf.org>; Mon, 24 Jun 2013 12:47:10 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob120.postini.com ([64.18.5.12]) with SMTP ID DSNKUciiO9/C20mgT+E/RAbFcwaL02TxM0kD@postini.com; Mon, 24 Jun 2013 12:47:10 PDT
Received: from inner-relay-2.corp.adobe.com (mail-321.pac.adobe.com [153.32.1.52]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5OJl6AI023844; Mon, 24 Jun 2013 12:47:06 -0700 (PDT)
Received: from nacas01.corp.adobe.com (nacas01.corp.adobe.com [10.8.189.99]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5OJl5w7014509; Mon, 24 Jun 2013 12:47:05 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by nacas01.corp.adobe.com ([10.8.189.99]) with mapi; Mon, 24 Jun 2013 12:47:05 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: John C Klensin <john-ietf@jck.com>, Phillip Hallam-Baker <hallam@gmail.com>, IETF-Discussion list <ietf@ietf.org>
Date: Mon, 24 Jun 2013 12:47:03 -0700
Subject: RE: SHOULD and RECOMMENDED
Thread-Topic: SHOULD and RECOMMENDED
Thread-Index: Ac5w1/feXy+iRoWhRBiQcHQ8zD1xpgAMZTXw
Message-ID: <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com>
In-Reply-To: <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Mon, 24 Jun 2013 19:47:17 -0000

my feeling and belief is that RFC 2119 only gives SHOULD and RECOMMENDED th=
e same normative requirement level, but that it does not override or change=
 the distinct meanings of these words in English.  sentences using each of =
these terms have different meanings in English, even when those sentences a=
ppear in RFCs.

-michael thornburgh


> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of J=
ohn C Klensin
> Sent: Monday, June 24, 2013 5:40 AM=20
>=20
> --On Monday, June 24, 2013 07:52 -0400 Phillip Hallam-Baker
> <hallam@gmail.com> wrote:
>=20
> > They are not synonyms
> >
> > Lets go back to 1980:
> >
> > Implementations SHOULD support DES
> > vs
> > RECOMMENDED encryption algorithms: DES, IDEA
>=20
> Actually, that is the point.  The usage above, although much
> earlier, reflects the Protocol Specification/ Applicability
> Statement split rather well.
>=20
> But 2119's language makes the two terms substitutable for and
> equivalent to each other, which is about as close a definition
> of "synonyms" as one can find.  What I said is that making them
> equivalent was probably a mistake and that treating them that
> was should be discouraged. Others expressed agreement with that
> assessment.
>=20
> Personally, I don't think the problem is severe enough to reopen
> 2119.  If others disagree and believe that 2119 is generating
> enough problems to be worth an update, I await a draft.
>=20
> So, other than quibbling about the "synonym" issue -- not
> generally, which no one has claimed, but in context with 2119--
> are you disagreeing and, if so, about what?
>=20
>    john
>=20


From stpeter@stpeter.im  Mon Jun 24 12:52:32 2013
Return-Path: <stpeter@stpeter.im>
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 E801C21E810B for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 12:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 80MGH+I29AN0 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 12:52:27 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C956E21E80FA for <ietf@ietf.org>; Mon, 24 Jun 2013 12:52:27 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 023C6412C3; Mon, 24 Jun 2013 13:52:41 -0600 (MDT)
Message-ID: <51C8A377.4020508@stpeter.im>
Date: Mon, 24 Jun 2013 13:52:23 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Michael Thornburgh <mthornbu@adobe.com>
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF-Discussion 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: Mon, 24 Jun 2013 19:52:33 -0000

On 6/24/13 1:47 PM, Michael Thornburgh wrote:
> my feeling and belief is that RFC 2119 only gives SHOULD and
> RECOMMENDED the same normative requirement level, but that it does
> not override or change the distinct meanings of these words in
> English.  sentences using each of these terms have different meanings
> in English, even when those sentences appear in RFCs.

I expect that the subtle differences between these words are lost on
non-native speakers, and even most native speakers, of English. I'd be
genuinely curious to hear that you think the distinct meanings are.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From hallam@gmail.com  Mon Jun 24 12:54:09 2013
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 A754621E80FA for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 12:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599]
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 S-pDk3M4Getd for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 12:53:58 -0700 (PDT)
Received: from mail-vb0-x229.google.com (mail-vb0-x229.google.com [IPv6:2607:f8b0:400c:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2B60F21F9BF0 for <ietf@ietf.org>; Mon, 24 Jun 2013 12:53:58 -0700 (PDT)
Received: by mail-vb0-f41.google.com with SMTP id p13so8546746vbe.14 for <ietf@ietf.org>; Mon, 24 Jun 2013 12:53:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=pHSQNNXUdMCFceF5fbufnM++z/2vdbebK/zFKlO2awo=; b=Puo19bkTSWXCgkHDbkkGoJCmDaDqBHBOUgFLTrnyEUULQzZVjU3aeGOH9QXlRlXN9Z kYI0pV0VAgLGFv8e+O0u6fh07G7PpyuiF6H8BzsiP1gset5uWJEi/Ym6SnbJZlcuFlk9 EEidS37XqjbgROR2QsnBg20tom6t499ytAmHU1+GiAM4tVDtXz/avB16doYWvSyN7SV6 764juR4jcLb4+ILS0GMAT71h4R3IvGGeOEFXxlD3sHCHNb8wCR71eJWpWoJJ6T3lrGVk IM/ZMVRVRN5AuJmUJaVDacFTuqJgKlkmk7IkX0QS/yDJa0CcpWPUvPGXMwul4ZSAvf9m BAig==
X-Received: by 10.52.121.42 with SMTP id lh10mr10435743vdb.39.1372103636611; Mon, 24 Jun 2013 12:53:56 -0700 (PDT)
Received: from retty.home (pool-108-7-229-221.bstnma.fios.verizon.net. [108.7.229.221]) by mx.google.com with ESMTPSA id io3sm20485646vdb.12.2013.06.24.12.53.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Jun 2013 12:53:55 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_CF0174C4-C688-40A2-BE6C-AA0EE2CA5AC0"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: SHOULD and RECOMMENDED
From: Phillip Hallam-Baker <hallam@gmail.com>
In-Reply-To: <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com>
Date: Mon, 24 Jun 2013 15:53:50 -0400
Message-Id: <A4496752-F575-43BD-B6A3-8FA67AB6F55A@gmail.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Cc: IETF-Discussion 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: Mon, 24 Jun 2013 19:54:09 -0000

--Apple-Mail=_CF0174C4-C688-40A2-BE6C-AA0EE2CA5AC0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

The mistake I was attempting to avoid here was concluding that =
RECOMMENDED should not be used.

It does have a necessary use that is distinct from SHOULD.

Given the number of citations it gets, I am sure someone will be willing =
to volunteer to do a revision if Scott Bradner is not interested.


On Jun 24, 2013, at 8:39 AM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Monday, June 24, 2013 07:52 -0400 Phillip Hallam-Baker
> <hallam@gmail.com> wrote:
>=20
>> They are not synonyms
>>=20
>> Lets go back to 1980:
>>=20
>> Implementations SHOULD support DES
>> vs
>> RECOMMENDED encryption algorithms: DES, IDEA
>=20
> Actually, that is the point.  The usage above, although much
> earlier, reflects the Protocol Specification/ Applicability
> Statement split rather well.
>=20
> But 2119's language makes the two terms substitutable for and
> equivalent to each other, which is about as close a definition
> of "synonyms" as one can find.  What I said is that making them
> equivalent was probably a mistake and that treating them that
> was should be discouraged. Others expressed agreement with that
> assessment. =20
>=20
> Personally, I don't think the problem is severe enough to reopen
> 2119.  If others disagree and believe that 2119 is generating
> enough problems to be worth an update, I await a draft.
>=20
> So, other than quibbling about the "synonym" issue -- not
> generally, which no one has claimed, but in context with 2119--
> are you disagreeing and, if so, about what?
>=20
>   john
>=20
>=20


--Apple-Mail=_CF0174C4-C688-40A2-BE6C-AA0EE2CA5AC0
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIPJDCCBN0w
ggPFoAMCAQICEHGS++YZX6xNEoV0cTSiGKcwDQYJKoZIhvcNAQEFBQAwezELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgMEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBwwHU2FsZm9yZDEaMBgGA1UECgwR
Q29tb2RvIENBIExpbWl0ZWQxITAfBgNVBAMMGEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczAeFw0w
NDAxMDEwMDAwMDBaFw0yODEyMzEyMzU5NTlaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQx
FzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsx
ITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJz
dC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVNNRm5pELlzkniii8efNIx
B8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQylbsMTzC9mKALi+VuG6JG+ni8
om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHG
TPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7Nl
yP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu9mIwFIws6wIDAQABo4IBJzCCASMwHwYDVR0j
BBgwFoAUoBEKIz6W8Qfs4q8p74Klf9AwpLQwHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59
MA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr
BgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAwewYDVR0fBHQwcjA4oDagNIYyaHR0cDovL2NybC5j
b21vZG9jYS5jb20vQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwNqA0oDKGMGh0dHA6Ly9jcmwu
Y29tb2RvLm5ldC9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDARBglghkgBhvhCAQEEBAMCAQYw
DQYJKoZIhvcNAQEFBQADggEBAJ2Vyzy4fqUJxB6/C8LHdo45PJTGEKpPDMngq4RdiVTgZTvzbRx8
NywlVF+WIfw3hJGdFdwUT4HPVB1rbEVgxy35l1FM+WbKPKCCjKbI8OLp1Er57D9Wyd12jMOCAU9s
APMeGmF0BEcDqcZAV5G8ZSLFJ2dPV9tkWtmNH7qGL/QGrpxp7en0zykX2OBKnxogL5dMUbtGB8SK
N04g4wkxaMeexIud6H4RvDJoEJYRmETYKlFgTYjrdDrfQwYyyDlWjDoRUtNBpEMD9O3vMyfbOeAU
TibJ2PU54om4k123KSZB6rObroP8d3XK6Mq1/uJlSmM+RMTQw16Hc6mYHK9/FX8wggUaMIIEAqAD
AgECAhBtGeqnGU9qMyLmIjJ6qnHeMA0GCSqGSIb3DQEBBQUAMIGuMQswCQYDVQQGEwJVUzELMAkG
A1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNU
IE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVRO
LVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMB4XDTExMDQyODAwMDAw
MFoXDTIwMDUzMDEwNDgzOFowgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNo
ZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYD
VQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwggEi
MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCShIRbS1eY1F4vi6ThQMijU1hfZmXxMk73nzJ9
VdB4TFW3QpTg+SdxB8XGaaS5MsTxQBqQzCdWYn8XtXFpruUgG+TLY15gyqJB9mrho/+43x9IbWVD
jCouK2M4d9+xF6zC2oIC1tQyatRnbyATj1w1+uVUgK/YcQodNwoCUFNslR2pEBS0mZVZEjH/CaLS
TNxS297iQAFbSGjdxUq04O0kHzqvcV8H46y/FDuwJXFoPfQP1hdYRhWBPGiLi4MPbXohV+Y0sNsy
fuNK4aVScmQmkU6lkg//4LFg/RpvaFGZY40ai6XMQpubfSJj06mg/M6ekN9EGfRcWzW6FvOnm//B
AgMBAAGjggFLMIIBRzAfBgNVHSMEGDAWgBSJgmd9xJ0mcABLtFBIfN49rgRufTAdBgNVHQ4EFgQU
ehNOAHRbxnhjZCfBL+KgW7x5xXswDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8CAQAw
EQYDVR0gBAowCDAGBgRVHSAAMFgGA1UdHwRRME8wTaBLoEmGR2h0dHA6Ly9jcmwudXNlcnRydXN0
LmNvbS9VVE4tVVNFUkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMHQGCCsG
AQUFBwEBBGgwZjA9BggrBgEFBQcwAoYxaHR0cDovL2NydC51c2VydHJ1c3QuY29tL1VUTkFkZFRy
dXN0Q2xpZW50X0NBLmNydDAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTAN
BgkqhkiG9w0BAQUFAAOCAQEAhda+eFdVbTN/RFL+QtUGqAEDgIr7DbL9Sr/2r0FJ9RtaxdKtG3Nu
PukmfOZMmMEwKN/L+0I8oSU+CnXW0D05hmbRoZu1TZtvryhsHa/l6nRaqNqxwPF1ei+eupN5yv7i
kR5WdLL4jdPgQ3Ib7Y/9YDkgR/uLrzplSDyYPaUlv73vYOBJ5RbI6z9Dg/Dg7g3B080zX5vQvWBq
szv++tTJOjwf7Zv/m0kzvkIpOYPuM2kugp1FTahp2oAbHj3SGl18R5mlmwhtEpmG1l1XBxunML5L
SUS4kH7K0Xk467Qz+qA6XSZYnmFVGLQh1ZnV4ENAQjC+6qXnlNKw/vN1+X9u5zCCBSEwggQJoAMC
AQICEAHh4bUBDKmoHPH4UN9yKcwwDQYJKoZIhvcNAQEFBQAwgZMxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9E
TyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBT
ZWN1cmUgRW1haWwgQ0EwHhcNMTMwMzA2MDAwMDAwWhcNMTQwMzA2MjM1OTU5WjAhMR8wHQYJKoZI
hvcNAQkBFhBoYWxsYW1AZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
2ZxWH01PFEm/F4D42jn7Uhy+zgICRTFKgKeE7k3AYMVonNwnd0hYe/U8BdthiC+Q6f2g+xPltDqJ
N+y4tvBWo3k6iks4T6JKPNxU0AKwknATSheF79LCaUb5hiF49gOTMoj8ac6aQoi3Qz7NU2zIP2/v
gEPU4EA+88ITw17QGQg7QSSok8jMgdRdUW+/QCNtD57qHcxxIbL9SpmMtSfISwx+TXTfe9G7RIg0
GZIH6agvzkQXFfczbKS49LLbJIlujJNjmxgSe38qXrwfRKq8kt84nBtHHAdw+adhemMu6cFh1WSG
/5g9bThkja7XEHW2gkjhTptRj/s4vi+WofrwSwIDAQABo4IB4DCCAdwwHwYDVR0jBBgwFoAUehNO
AHRbxnhjZCfBL+KgW7x5xXswHQYDVR0OBBYEFCons5YrIzdWMcDnoAcfvVeCgdN5MA4GA1UdDwEB
/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjAR
BglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcC
ARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwVwYDVR0fBFAwTjBMoEqgSIZGaHR0cDov
L2NybC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFp
bENBLmNybDCBiAYIKwYBBQUHAQEEfDB6MFIGCCsGAQUFBzAChkZodHRwOi8vY3J0LmNvbW9kb2Nh
LmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsG
AQUFBzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wGwYDVR0RBBQwEoEQaGFsbGFtQGdtYWls
LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAANoMWJKmPtci0s9rTOZfqwJAFw+Zba1E8a5xIk2WYYSe
MIQ7Ariil5IjRY4kDgLTIM4iYiTz14FyWUjFqZq1D2skR9FfV9HcYuDacD1sqnOGX1BJBmrmJlRV
hO8XnnyuajQD8a2B6hLBqmFpQbgvmVl3Pm80d+rCTrgMqHHKvchG/7rcie7W2cUEsFEElOm6XnZQ
v7sVe9BVgqcGM5pjyeIboEgNsTr1m45bkBbtYG3WTMarIHM0Nq6QL5gpUyabNuxdssJhZzs5FOyK
l+Ec7+U6sNuFu+HhvsITE3z2SqTdseLws/Q2QW+1mmCT6U4m6cTGZHdIzDyk/kyH4AIpYDGCA6sw
ggOnAgEBMIGoMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAw
DgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09N
T0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAB4eG1AQypqBzx
+FDfcinMMAkGBSsOAwIaBQCgggHXMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEzMDYyNDE5NTM1MVowIwYJKoZIhvcNAQkEMRYEFP4UbGuFr69ImEnkvsUjFKnRlbJl
MIG5BgkrBgEEAYI3EAQxgaswgagwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1h
bmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkw
NwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EC
EAHh4bUBDKmoHPH4UN9yKcwwgbsGCyqGSIb3DQEJEAILMYGroIGoMIGTMQswCQYDVQQGEwJHQjEb
MBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFD
T01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBh
bmQgU2VjdXJlIEVtYWlsIENBAhAB4eG1AQypqBzx+FDfcinMMA0GCSqGSIb3DQEBAQUABIIBANcQ
RVPzR9nXwomypPz4PYxF5klp5p7YGiDUPHtWLepPyHp3mSY9b+JB3l7aXEBfToS9gFM5C5Imxuo2
XwF4fpr2uxl97mC3y2tipwUzF7O/GIoUoU6USI4pq0OXkv74BGYe1zVwtcBslBju9JyOdLPK1fyJ
lQtWC5OFgct7YbTfnPm+G/Pv+MBduf5a4AoTtNcReknLdRqzFK0aqHdGaYShYTUaDMHWinmwUBvy
9E76OZMNHDcNz1biaP2u7eFfM0BB+Z/dSyFsxKY+vq77oFDEoON90ZGS3uZ2WVyYaBjOq5fWkF5f
CVLYvHSLXs23rx5BIheCgIHvrPRfxbDMUYgAAAAAAAA=

--Apple-Mail=_CF0174C4-C688-40A2-BE6C-AA0EE2CA5AC0--

From dhc@dcrocker.net  Mon Jun 24 13:08:43 2013
Return-Path: <dhc@dcrocker.net>
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 B7A0B11E8185 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.575
X-Spam-Level: 
X-Spam-Status: No, score=-6.575 tagged_above=-999 required=5 tests=[AWL=0.024,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 y9WcImPOzgUA for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:08:38 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C51E621F9AE8 for <ietf@ietf.org>; Mon, 24 Jun 2013 13:08:38 -0700 (PDT)
Received: from [192.168.6.161] (ip-64-134-234-85.public.wayport.net [64.134.234.85]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5OK8YVm006824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Jun 2013 13:08:38 -0700
Message-ID: <51C8A740.1030907@dcrocker.net>
Date: Mon, 24 Jun 2013 13:08:32 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im>
In-Reply-To: <51C8A377.4020508@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 24 Jun 2013 13:08:38 -0700 (PDT)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Mon, 24 Jun 2013 20:08:43 -0000

On 6/24/2013 12:52 PM, Peter Saint-Andre wrote:
> I expect that the subtle differences between these words are lost on
> non-native speakers, and even most native speakers, of English. I'd be
> genuinely curious to hear that you think the distinct meanings are.


I suspect you are wrong...

In your implication that there is /any/ meaningful distinction made by 
native English speakers when reading an RFC...

For the times I've seen the different words used normatively in RFC, I 
have not discerned any semantic difference.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From ynir@checkpoint.com  Mon Jun 24 13:18:23 2013
Return-Path: <ynir@checkpoint.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 9194721F9FC5 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.606
X-Spam-Level: 
X-Spam-Status: No, score=-10.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 aeQe2VII2jYT for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:18:17 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 5115C21F9F36 for <ietf@ietf.org>; Mon, 24 Jun 2013 13:18:16 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r5OKI38J029119; Mon, 24 Jun 2013 23:18:03 +0300
X-CheckPoint: {51C8A97B-2C-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.180]) with mapi id 14.02.0342.003; Mon, 24 Jun 2013 23:18:03 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: SHOULD and RECOMMENDED
Thread-Topic: SHOULD and RECOMMENDED
Thread-Index: AQHOcF0a1G3Lf6PjA0SszxqYCRTGUZlEj6GAgAANKACAAHdkgIAAAX6AgAAHLwA=
Date: Mon, 24 Jun 2013 20:18:03 +0000
Message-ID: <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im>
In-Reply-To: <51C8A377.4020508@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.170]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 1159fc793a547d660443dd16b7516dd012858aa6d9
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <402634F6C8EACB4381CBD16568CA1596@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF-Discussion 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: Mon, 24 Jun 2013 20:18:23 -0000

On Jun 24, 2013, at 10:52 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:

> On 6/24/13 1:47 PM, Michael Thornburgh wrote:
>> my feeling and belief is that RFC 2119 only gives SHOULD and
>> RECOMMENDED the same normative requirement level, but that it does
>> not override or change the distinct meanings of these words in
>> English.  sentences using each of these terms have different meanings
>> in English, even when those sentences appear in RFCs.
>=20
> I expect that the subtle differences between these words are lost on
> non-native speakers, and even most native speakers, of English. I'd be
> genuinely curious to hear that you think the distinct meanings are.
>=20

"It is RECOMMENDED that implementations send the AUTH_LIFETIME notification=
 at least 4 minutes before the SA is to be deleted, to facilitate the user =
entering credentials in time."

"The implementation SHOULD send the AUTH_LIFETIME notification at least 4 m=
inutes before the SA is to be deleted, to facilitate the user entering cred=
entials in time."

- What are the subtle differences in meaning between these two sentences?

- Would an implementation written by a native speaker be any different depe=
nding on which of the above sentences was in the RFC?

Yoav



From stpeter@stpeter.im  Mon Jun 24 13:21:36 2013
Return-Path: <stpeter@stpeter.im>
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 871B221E8114 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 eXZGygzB0TkT for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:21:22 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0CE11E8173 for <ietf@ietf.org>; Mon, 24 Jun 2013 13:21:22 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B01C5412E7; Mon, 24 Jun 2013 14:21:36 -0600 (MDT)
Message-ID: <51C8AA3F.2000500@stpeter.im>
Date: Mon, 24 Jun 2013 14:21:19 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <51C8A740.1030907@dcrocker.net>
In-Reply-To: <51C8A740.1030907@dcrocker.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion 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: Mon, 24 Jun 2013 20:21:36 -0000

On 6/24/13 2:08 PM, Dave Crocker wrote:
> On 6/24/2013 12:52 PM, Peter Saint-Andre wrote:
>> I expect that the subtle differences between these words are lost on
>> non-native speakers, and even most native speakers, of English. I'd be
>> genuinely curious to hear that you think the distinct meanings are.
> 
> 
> I suspect you are wrong...
> 
> In your implication that there is /any/ meaningful distinction made by
> native English speakers when reading an RFC...
> 
> For the times I've seen the different words used normatively in RFC, I
> have not discerned any semantic difference.

I agree. (It would have been better for me to say "subtle differences,
if any".)

I'm open to an argument that in standard English "should" has a shade of
obligation and "recommended" has a shade of suggestion, but in practice
(especially in RFCs) those shades are lost.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From melinda.shore@gmail.com  Mon Jun 24 13:23:47 2013
Return-Path: <melinda.shore@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 4F28E21E8129 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 r3+eo1nZZTeM for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:23:47 -0700 (PDT)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 68BD221E8159 for <ietf@ietf.org>; Mon, 24 Jun 2013 13:23:45 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id kp12so11524525pab.35 for <ietf@ietf.org>; Mon, 24 Jun 2013 13:23:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=b++nw6/qdkAVLHnYkNBZoTyzz8cx8eQ6VcKFvK91s/o=; b=gGljD3zwIfbznUG5GkQeh0/8Okpp/lnDmWjvGqV0mMREcXQF3K6QdkfcfofOM+HBlK apcm2Vd/HvduWXrRbMfozZ8RO93xEUGBXxfQQW8js12L8UjBLIVbCUK/An6lDvEVX5Dq QjpTrqyG0g8uLupUsPG6KmGuZjgIMd8QlOQ+VLXyUxefzCIFPVoHiMAmBt7C1SFoPLdN DRe5QYefu0zgoYcxmhfsHB3kvLr+QACWF6045aZeMCgTnclqbTO8gf5bmy515cEC+gtK JVzH5qtEcQagSd7apoxRJv57QrHGsTAzlXsk+y0epboElGbRmolQ/fYxRLrzjdUzEBJ3 Ylmw==
X-Received: by 10.68.113.2 with SMTP id iu2mr19542659pbb.108.1372105425208; Mon, 24 Jun 2013 13:23:45 -0700 (PDT)
Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id xj9sm19601603pbc.16.2013.06.24.13.23.43 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Jun 2013 13:23:44 -0700 (PDT)
Message-ID: <51C8AACE.8040005@gmail.com>
Date: Mon, 24 Jun 2013 12:23:42 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com>
In-Reply-To: <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Mon, 24 Jun 2013 20:23:47 -0000

On 6/24/13 12:18 PM, Yoav Nir wrote:
> - What are the subtle differences in meaning between these two
> sentences?

I think "I recommend" is rather clearly different from "you should,"
in terms of strength and (in the case of normative text) obligation.
I don't think that "recommend" is useful in the context of an RFC,
may be confusing and a bit subtle, and is probably best avoided.

Melinda

From akatlas@gmail.com  Mon Jun 24 13:28:54 2013
Return-Path: <akatlas@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 7CF6821E810C for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 GKVV0jmx-SnW for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:28:52 -0700 (PDT)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 277A321E80F4 for <ietf@ietf.org>; Mon, 24 Jun 2013 13:28:48 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id a13so26138087iee.34 for <ietf@ietf.org>; Mon, 24 Jun 2013 13:28:47 -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=+FIUk+aF2eqmeT0dMMVm/Ntj9kdyhdlKqQE6i2+u4y4=; b=pFFzCAr9t66iJSnYsEd/gQs3Qwa7ONYCfYE843sTIKrbO2M08W6ODTm2vNr2GSIaKY iE4tXlEDp7dhSXynhJ3Uc80flRHsAUt8lbqUh4NfDcpbcfNBcztALD3U4z20cH2iOjfM /IYmT7BX5s++5YdeTKnhInedRFxLtw4vLL6U31yQDOrnN6+qeRiw3yHMiZotO5T1pPGf ROEMOlP76zCF09rgUD1geoTwPG6DDtbwooYBmNqIysff3UgAlBs1hKhR+JmT0sMdg+sC 2YRYvN+fnmJV7Qiog9Un+cFduZP1ZLvzya8lV4yDHrEbw+4cEY+I9ZlFhqcVcW2RMhdE +M5Q==
MIME-Version: 1.0
X-Received: by 10.43.12.198 with SMTP id pj6mr9221611icb.68.1372105727726; Mon, 24 Jun 2013 13:28:47 -0700 (PDT)
Received: by 10.64.47.168 with HTTP; Mon, 24 Jun 2013 13:28:47 -0700 (PDT)
In-Reply-To: <51C8AACE.8040005@gmail.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <51C8AACE.8040005@gmail.com>
Date: Mon, 24 Jun 2013 16:28:47 -0400
Message-ID: <CAG4d1rfg=EHY5XQbahYnzTKFDV8PB7u5tPFA2L3Qy1Thj1oTUA@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED
From: Alia Atlas <akatlas@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec518701c7edcbe04dfec4249
Cc: 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: Mon, 24 Jun 2013 20:28:55 -0000

--bcaec518701c7edcbe04dfec4249
Content-Type: text/plain; charset=ISO-8859-1

I read SHOULD and RECOMMENDED as different.

SHOULD is how a implementation ought to behave unless there are special
circumstances (deployment, additional functionality, better idea).  MUST
says that there are no circumstances special enough to change the behavior.

RECOMMENDED is closer to a Best Current Practice (BCP); so I might write
"It is RECOMMENDED that the network-converged timer have a minimum value of
2 seconds."  but in 10 years, maybe it'll only take 2 microseconds - so
that'll become a bad recommendation!

Alia


On Mon, Jun 24, 2013 at 4:23 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 6/24/13 12:18 PM, Yoav Nir wrote:
> > - What are the subtle differences in meaning between these two
> > sentences?
>
> I think "I recommend" is rather clearly different from "you should,"
> in terms of strength and (in the case of normative text) obligation.
> I don't think that "recommend" is useful in the context of an RFC,
> may be confusing and a bit subtle, and is probably best avoided.
>
> Melinda
>

--bcaec518701c7edcbe04dfec4249
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I read SHOULD and RECOMMENDED as different.<div><br></div>=
<div>SHOULD is how a implementation ought to behave unless there are specia=
l circumstances (deployment, additional functionality, better idea). =A0MUS=
T says that there are no circumstances special enough to change the behavio=
r.</div>
<div><br></div><div style>RECOMMENDED is closer to a Best Current Practice =
(BCP); so I might write &quot;It is RECOMMENDED that the network-converged =
timer have a minimum value of 2 seconds.&quot; =A0but in 10 years, maybe it=
&#39;ll only take 2 microseconds - so that&#39;ll become a bad recommendati=
on!</div>
<div style><br></div><div style>Alia</div></div><div class=3D"gmail_extra">=
<br><br><div class=3D"gmail_quote">On Mon, Jun 24, 2013 at 4:23 PM, Melinda=
 Shore <span dir=3D"ltr">&lt;<a href=3D"mailto:melinda.shore@gmail.com" tar=
get=3D"_blank">melinda.shore@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 6/24/13 12:18 PM, Yoav =
Nir wrote:<br>
&gt; - What are the subtle differences in meaning between these two<br>
&gt; sentences?<br>
<br>
</div>I think &quot;I recommend&quot; is rather clearly different from &quo=
t;you should,&quot;<br>
in terms of strength and (in the case of normative text) obligation.<br>
I don&#39;t think that &quot;recommend&quot; is useful in the context of an=
 RFC,<br>
may be confusing and a bit subtle, and is probably best avoided.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Melinda<br>
</font></span></blockquote></div><br></div>

--bcaec518701c7edcbe04dfec4249--

From john-ietf@jck.com  Mon Jun 24 13:38:22 2013
Return-Path: <john-ietf@jck.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 785AE21E8108 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 bbnwC2VVIXEe for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 13:38:16 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9F35121E80E0 for <ietf@ietf.org>; Mon, 24 Jun 2013 13:38:16 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UrDWh-00068M-Rt; Mon, 24 Jun 2013 16:38:15 -0400
Date: Mon, 24 Jun 2013 16:38:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alia Atlas <akatlas@gmail.com>, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: SHOULD and RECOMMENDED
Message-ID: <CF44951B554F7B412F395C53@JcK-HP8200.jck.com>
In-Reply-To: <CAG4d1rfg=EHY5XQbahYnzTKFDV8PB7u5tPFA2L3Qy1Thj1oTUA@mail.gmail.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <51C8AACE.8040005@gmail.com> <CAG4d1rfg=EHY5XQbahYnzTKFDV8PB7u5tPFA2L3Qy1Thj1oTUA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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: Mon, 24 Jun 2013 20:38:22 -0000

--On Monday, June 24, 2013 16:28 -0400 Alia Atlas
<akatlas@gmail.com> wrote:

> I read SHOULD and RECOMMENDED as different.
> 
> SHOULD is how a implementation ought to behave unless there
> are special circumstances (deployment, additional
> functionality, better idea).  MUST says that there are no
> circumstances special enough to change the behavior.
> 
> RECOMMENDED is closer to a Best Current Practice (BCP); so I
> might write "It is RECOMMENDED that the network-converged
> timer have a minimum value of 2 seconds."  but in 10 years,
> maybe it'll only take 2 microseconds - so that'll become a bad
> recommendation!

And that, again, is close to the distinction that a reasonable
person might read into 2026.  But not into 2119 which appears
(at least to me) to make them fully-substitutable alternatives.

The distinction doesn't make the comments made by Peter, Dave,
or others any less valid.  If we told ourselves that readers
should (lower case) infer conformance statements from SHOULD and
applicability ones from RECOMMENDED... well, we would be pretty
delusional.

   john



From sob@harvard.edu  Mon Jun 24 14:03:03 2013
Return-Path: <sob@harvard.edu>
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 E725011E8143 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 14:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 iTWhf2BAEXTH for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 14:02:58 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA5021F9F0B for <ietf@ietf.org>; Mon, 24 Jun 2013 14:02:49 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000004.university.harvard.edu [10.35.202.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id E1D1DE9E0A for <ietf@ietf.org>; Mon, 24 Jun 2013 17:02:48 -0400 (EDT)
Received: from ENTWHUBT0000006.university.harvard.edu (192.168.236.26) by entwedge0000004.university.harvard.edu (10.35.202.51) with Microsoft SMTP Server (TLS) id 14.2.342.3; Mon, 24 Jun 2013 17:02:29 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.137]) by ENTWHUBT0000006.university.harvard.edu ([192.168.236.28]) with mapi id 14.02.0342.003; Mon, 24 Jun 2013 17:02:48 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: SHOULD and RECOMMENDED
Thread-Topic: SHOULD and RECOMMENDED
Thread-Index: AQHOcR4ucoJQiU61AE60u3/tDt4UZQ==
Date: Mon, 24 Jun 2013 21:02:48 +0000
Message-ID: <0862693F-3B8A-4178-8EB9-46E93241BBF4@harvard.edu>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <51C8AACE.8040005@gmail.com> <CAG4d1rfg=EHY5XQbahYnzTKFDV8PB7u5tPFA2L3Qy1Thj1oTUA@mail.gmail.com> <CF44951B554F7B412F395C53@JcK-HP8200.jck.com>
In-Reply-To: <CF44951B554F7B412F395C53@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [173.166.5.69]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1237D4411E607C49AC12592B4860BBF3@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Mon, 24 Jun 2013 21:03:04 -0000

while I like to take credit for the good things in RFC 2119 (and disclaim t=
he bad things) - the
term RECOMMENDED (good or bad)  comes from RFC 1122=20

basically I copied the definition section from RFC 1122 for the 1st version=
 of what became RFC 2119.
(see http://www.sobco.com/ids/draft-bradner-key-words-00.txt)=20

based on mailing list discussion I produced two revisions of the ID (mostly=
 to add guidance on usage)
http://www.sobco.com/ids/draft-bradner-key-words-01.txt
and
http://www.sobco.com/ids/draft-bradner-key-words-02.txt

the 02 version is what was approved by the IESG as RFC 2119

all of the above is to say that I can not help in this discussion about the=
 difference between SHOULD &=20
RECOMMENDED other than the fact they represent  different parts of speech

maybe Bob Braden has an idea since I do find  not a usage of RECOMMENDED in=
 the RFC series before RFC 1122

Scott

On Jun 24, 2013, at 4:38 PM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Monday, June 24, 2013 16:28 -0400 Alia Atlas
> <akatlas@gmail.com> wrote:
>=20
>> I read SHOULD and RECOMMENDED as different.
>>=20
>> SHOULD is how a implementation ought to behave unless there
>> are special circumstances (deployment, additional
>> functionality, better idea).  MUST says that there are no
>> circumstances special enough to change the behavior.
>>=20
>> RECOMMENDED is closer to a Best Current Practice (BCP); so I
>> might write "It is RECOMMENDED that the network-converged
>> timer have a minimum value of 2 seconds."  but in 10 years,
>> maybe it'll only take 2 microseconds - so that'll become a bad
>> recommendation!
>=20
> And that, again, is close to the distinction that a reasonable
> person might read into 2026.  But not into 2119 which appears
> (at least to me) to make them fully-substitutable alternatives.
>=20
> The distinction doesn't make the comments made by Peter, Dave,
> or others any less valid.  If we told ourselves that readers
> should (lower case) infer conformance statements from SHOULD and
> applicability ones from RECOMMENDED... well, we would be pretty
> delusional.
>=20
>   john
>=20
>=20


From sm@resistor.net  Mon Jun 24 14:36:50 2013
Return-Path: <sm@resistor.net>
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 AF87F21F9452 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 14:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 0rsjAzRCIUtR for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 14:36:50 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 01E0C21F93DA for <ietf@ietf.org>; Mon, 24 Jun 2013 14:36:49 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5OLaiea016599; Mon, 24 Jun 2013 14:36:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372109809; bh=z8dc4VNQUtSRWE04Jqbt3ZC2lshUjrWozkNdooOzlXQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4G1pFA5oAXNzjxbHS17/29+dVjnuGz8mJSYzM3lVPICRZ/mrmY73BAfQs8+OqjSq6 RTWoqhUd/12xF1g5Lujz5JHkrHIFwwBr13xxH7kr0n3u3ddN3oEtlsFKhIXegEGqEm DBuwfrb3BnpC534o93zLZ5FaVHDaBx+LPl5VHcOk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1372109809; i=@resistor.net; bh=z8dc4VNQUtSRWE04Jqbt3ZC2lshUjrWozkNdooOzlXQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hOBYFPlnD/6zDeypsMJ4AwzkX1dut4qmSV0Q8OECHqhjpeUDK/xsJOuTgjjKYls/q SdBVYyFH/gsj8+KCRfjwNG/tNQpvLrwunsOF1R3V9j8W38/pOJ12SS/Cbh/Lpldki5 0m/eg7DIyRiLEB0k269lr1k8lTgqOjm9stK3wuc0=
Message-Id: <6.2.5.6.2.20130624131310.0bc57b08@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 24 Jun 2013 14:35:18 -0700
To: Ray Pelletier <rpelletier@isoc.org>
From: SM <sm@resistor.net>
Subject: Re: IASA contracts (was: IAOC Website Updated)
In-Reply-To: <0A5FF4E6-7954-4C23-BE7A-CFA826B32C13@isoc.org>
References: <20130620185914.19663.88097.idtracker@ietfa.amsl.com> <51C7CCD0.4090202@gmail.com> <1372076911.4524.6416.camel@mightyatom> <6.2.5.6.2.20130624083353.0cd2d900@resistor.net> <0A5FF4E6-7954-4C23-BE7A-CFA826B32C13@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Mon, 24 Jun 2013 21:36:50 -0000

Hi Ray,
At 12:22 24-06-2013, Ray Pelletier wrote:
>Progress is being made.
>
>The ICANN SLA for 2013 has been published.

That's a zero-cost contract.  I don't have any problem with the IANA 
folks I interact with.  They are nice and they do what they say they 
will do.  That's more important to me than a SLA.

>The Verilan Master Services Agreement 2013 has been published.
>Both the Secretariat and the RFC Production Center contracts are 
>under review and I expect them published in the next two weeks

Thanks.  I prefer specific dates instead of ambiguous time frames.

>We have more to do and appreciate the continuing community interest 
>in and feedback on what we do.

I presume that this message is from IASA.  What I find unusual is 
that a member of the IAOC is being asked to agree to a contract 
without being given the opportunity to read the contract ( 
http://www.ietf.org/mail-archive/web/ietf/current/msg80269.html ).  I 
note that the member was selected by NomCom and that the person is 
doing the IAOC work as a volunteer.  According to RFC 4333 
"Candidates for these IAOC positions should have knowledge of the 
IETF, knowledge of contracts and financial procedures".  I don't know 
which procedures IASA is following that make it acceptable to blindly 
agree to contracts.

There was a RFP for "Remote Participation Services Specifications 
Development".  There were the IDIQ contracts which were mentioned 
over two years ago.  There was the "Requirements for Data Tracker 
Extensions for Working Group Chairs and Author" contract.  I did not 
elaborate about all the contracts in my previous message as I assumed 
that it was about all the contracts.

I do not have any vested interest in those contracts.  I am okay 
about answering any questions the IETF Community may have about my 
vested interests.

>PS Hope to see you in Berlin

It's unlikely that I will be able to make it to Germany.

Regards,
-sm 


From dhc@dcrocker.net  Mon Jun 24 15:06:03 2013
Return-Path: <dhc@dcrocker.net>
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 A968511E81A4 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 15:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.932
X-Spam-Level: 
X-Spam-Status: No, score=-5.932 tagged_above=-999 required=5 tests=[AWL=-0.625, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4]
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 cw4mn+xOdQGj for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 15:05:58 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BAB1A11E819E for <ietf@ietf.org>; Mon, 24 Jun 2013 15:05:58 -0700 (PDT)
Received: from [192.168.6.161] (ip-64-134-234-85.public.wayport.net [64.134.234.85]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5OM5sUY009228 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 24 Jun 2013 15:05:58 -0700
Message-ID: <51C8C2BF.5000302@dcrocker.net>
Date: Mon, 24 Jun 2013 15:05:51 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <51C8AACE.8040005@gmail.com>
In-Reply-To: <51C8AACE.8040005@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 24 Jun 2013 15:05:58 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Mon, 24 Jun 2013 22:06:03 -0000

On 6/24/2013 1:23 PM, Melinda Shore wrote:
> I think "I recommend" is rather clearly different from "you should,"
> in terms of strength and (in the case of normative text) obligation.
> I don't think that "recommend" is useful in the context of an RFC,
> may be confusing and a bit subtle, and is probably best avoided.


A number of the notes have offered personal views about the differences 
between the two words.  No doubt each of us could offer such comments. 
And perhaps some of us might even offer similar meanings.

Unfortunately, the ability of one person to impart their own semantic 
distinction is irrelevant to the current discussion, which is about 
normative language used for global standards that are read by widely and 
wildly different people around the world, with extreme differences in 
English language skills.

This is technical specification, not literature.  Subtlety and nuance -- 
especially of a linguistic nature -- is wholly inappropriate.

Just as we find simpler technology propagates better across the 
Internet, so does simpler specification language.

MAY/SHOULD/MUST has proved simple and sufficient.  Any gradations beyond 
that have demonstrated no utility for IETF specifications.

Hell, we still debate the differences of just /those/ 3 words...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From brian.e.carpenter@gmail.com  Mon Jun 24 15:30:58 2013
Return-Path: <brian.e.carpenter@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 F410211E81A0 for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 15:30:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 18OdFTY+PhFr for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 15:30:57 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 77D6B11E817C for <ietf@ietf.org>; Mon, 24 Jun 2013 15:30:57 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id um15so11508007pbc.24 for <ietf@ietf.org>; Mon, 24 Jun 2013 15:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DeZ18d+V9oV8MXYKwLfJh0HI4GMginnWM9TUoG8PQK0=; b=stXh9dWvIwLGZta1vepEeVR0/giPrv8tYJMJoOoun9dREA6E9yXUOuIeq48zrzkl18 ERLum1jPMD7AeyLskHOXtTepVEcH72KzYo++/Rdnpbbb9voiEhZQeVRqre2GBgmdcEKI cb2zN8ux/snhMer1AAemhqKuR/6mhoUT5eZXaWH3oOHCRfE9MFKof2tc3MCl5yEQ2dXw 9zuMpdJXGEHiig7hbm/0KL9LcU57ERSV4D2FiuhsDKeNY7vNx/sKCXN0W46y/dhDU+ur SLnTD8TBTSdU2xCD5a389RRzljzfsvnxwJvKClzZnE9fTwS6C2mePCoYiOwEHKMDn9GC Al5Q==
X-Received: by 10.68.164.97 with SMTP id yp1mr25528405pbb.77.1372113057214; Mon, 24 Jun 2013 15:30:57 -0700 (PDT)
Received: from [192.168.178.22] (115.198.69.111.dynamic.snap.net.nz. [111.69.198.115]) by mx.google.com with ESMTPSA id kq2sm21765985pab.19.2013.06.24.15.30.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Jun 2013 15:30:56 -0700 (PDT)
Message-ID: <51C8C89A.3000505@gmail.com>
Date: Tue, 25 Jun 2013 10:30:50 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>	<D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>	<CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com>	<06F3E21A0F7B70C591083973@JcK-HP8200.jck.com>	<CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com>	<51C76FEC.9040009@dcrocker.net>	<CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com>	<0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com>	<D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com>	<51C8A377.4020508@stpeter.im>	<630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com>	<51C8AACE.8040005@gmail.com>	<CAG4d1rfg=EHY5XQbahYnzTKFDV8PB7u5tPFA2L3Qy1Thj1oTUA@mail.gmail.com> <CF44951B554F7B412F395C53@JcK-HP8200.jck.com>
In-Reply-To: <CF44951B554F7B412F395C53@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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: Mon, 24 Jun 2013 22:30:58 -0000

On 25/06/2013 08:38, John C Klensin wrote:
> 
> --On Monday, June 24, 2013 16:28 -0400 Alia Atlas
> <akatlas@gmail.com> wrote:
> 
>> I read SHOULD and RECOMMENDED as different.
>>
>> SHOULD is how a implementation ought to behave unless there
>> are special circumstances (deployment, additional
>> functionality, better idea).  MUST says that there are no
>> circumstances special enough to change the behavior.
>>
>> RECOMMENDED is closer to a Best Current Practice (BCP); so I
>> might write "It is RECOMMENDED that the network-converged
>> timer have a minimum value of 2 seconds."  but in 10 years,
>> maybe it'll only take 2 microseconds - so that'll become a bad
>> recommendation!
> 
> And that, again, is close to the distinction that a reasonable
> person might read into 2026.  But not into 2119 which appears
> (at least to me) to make them fully-substitutable alternatives.
> 
> The distinction doesn't make the comments made by Peter, Dave,
> or others any less valid.  If we told ourselves that readers
> should (lower case) infer conformance statements from SHOULD and
> applicability ones from RECOMMENDED... well, we would be pretty
> delusional.

Also, issuing 2119bis with a subtle difference between the two
would create a horrible problem of interpretation for all existing
documents (including numerous documents from other SDOs) that
explicitly cite 2119. This has ramifications that make my head hurt.

   Brian

From hallam@gmail.com  Mon Jun 24 17:33:19 2013
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 E1AC321F9EAE for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 17:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 qXeTZJVwR1yV for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 17:33:19 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 90B0D21F9EA9 for <ietf@ietf.org>; Mon, 24 Jun 2013 17:33:18 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id l18so8918940wgh.14 for <ietf@ietf.org>; Mon, 24 Jun 2013 17:33:17 -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=XT15WU0p3h9SOFptNZR066P68qUyRlUHSYtXZ1y6+rc=; b=yBPoCFsKKmVoYblkBeYOe47Ydp8EavO6CFQ8HvWzjDBFXrBSpg8byzX16Xe1G59ylO ZO4FwEbeuZEr/xbibSLaymK54fPKNrYEL34u/tFjVVbaR5hgJtmclPe0rWeHp11Oj1DR 3jReCq3ELtZoh1oX5KKX55VOvT95EMz9n1FmHM8dv5/obOUONafoeG7lfrTeIyamCoMK P1I5CXs9mxeU1g3Rb1RxFnU+DiWTo5f6zR1qJxLX0HNaCUyaFEufzyFBtNI29jMN9HzH JzGfAobD89BOYHKD63fNjgPbtz27lTc4i2VTau5tjXC/F5naIZnFyZ/+Z8X26qVr0TPP aHmg==
MIME-Version: 1.0
X-Received: by 10.194.104.74 with SMTP id gc10mr18081540wjb.48.1372120397279;  Mon, 24 Jun 2013 17:33:17 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Mon, 24 Jun 2013 17:33:16 -0700 (PDT)
In-Reply-To: <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com>
Date: Mon, 24 Jun 2013 20:33:16 -0400
Message-ID: <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: multipart/alternative; boundary=047d7bf10b46de781904dfefacf6
Cc: IETF-Discussion 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: Tue, 25 Jun 2013 00:33:20 -0000

--047d7bf10b46de781904dfefacf6
Content-Type: text/plain; charset=ISO-8859-1

RECOMMENDED is a strong suggestion that the implementation may override at
the discretion of the implementer. SHOULD is normative.

So the first tells me that I can make up my own mind, the second says that
I should give a reason if I don't comply.


On Mon, Jun 24, 2013 at 4:18 PM, Yoav Nir <ynir@checkpoint.com> wrote:

>
> On Jun 24, 2013, at 10:52 PM, Peter Saint-Andre <stpeter@stpeter.im>
> wrote:
>
> > On 6/24/13 1:47 PM, Michael Thornburgh wrote:
> >> my feeling and belief is that RFC 2119 only gives SHOULD and
> >> RECOMMENDED the same normative requirement level, but that it does
> >> not override or change the distinct meanings of these words in
> >> English.  sentences using each of these terms have different meanings
> >> in English, even when those sentences appear in RFCs.
> >
> > I expect that the subtle differences between these words are lost on
> > non-native speakers, and even most native speakers, of English. I'd be
> > genuinely curious to hear that you think the distinct meanings are.
> >
>
> "It is RECOMMENDED that implementations send the AUTH_LIFETIME
> notification at least 4 minutes before the SA is to be deleted, to
> facilitate the user entering credentials in time."
>
> "The implementation SHOULD send the AUTH_LIFETIME notification at least 4
> minutes before the SA is to be deleted, to facilitate the user entering
> credentials in time."
>
> - What are the subtle differences in meaning between these two sentences?
>
> - Would an implementation written by a native speaker be any different
> depending on which of the above sentences was in the RFC?
>
> Yoav
>
>
>


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

--047d7bf10b46de781904dfefacf6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><br></div>RECOMMENDED is a strong suggestion that the=
 implementation may override at the discretion of the implementer. SHOULD i=
s normative.<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"=
 style>
So the first tells me that I can make up my own mind, the second says that =
I should give a reason if I don&#39;t comply.</div><div class=3D"gmail_extr=
a"><br><br><div class=3D"gmail_quote">On Mon, Jun 24, 2013 at 4:18 PM, Yoav=
 Nir <span dir=3D"ltr">&lt;<a href=3D"mailto:ynir@checkpoint.com" target=3D=
"_blank">ynir@checkpoint.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><br>
On Jun 24, 2013, at 10:52 PM, Peter Saint-Andre &lt;<a href=3D"mailto:stpet=
er@stpeter.im">stpeter@stpeter.im</a>&gt; wrote:<br>
<br>
&gt; On 6/24/13 1:47 PM, Michael Thornburgh wrote:<br>
&gt;&gt; my feeling and belief is that RFC 2119 only gives SHOULD and<br>
&gt;&gt; RECOMMENDED the same normative requirement level, but that it does=
<br>
&gt;&gt; not override or change the distinct meanings of these words in<br>
&gt;&gt; English. =A0sentences using each of these terms have different mea=
nings<br>
&gt;&gt; in English, even when those sentences appear in RFCs.<br>
&gt;<br>
&gt; I expect that the subtle differences between these words are lost on<b=
r>
&gt; non-native speakers, and even most native speakers, of English. I&#39;=
d be<br>
&gt; genuinely curious to hear that you think the distinct meanings are.<br=
>
&gt;<br>
<br>
</div></div>&quot;It is RECOMMENDED that implementations send the AUTH_LIFE=
TIME notification at least 4 minutes before the SA is to be deleted, to fac=
ilitate the user entering credentials in time.&quot;<br>
<br>
&quot;The implementation SHOULD send the AUTH_LIFETIME notification at leas=
t 4 minutes before the SA is to be deleted, to facilitate the user entering=
 credentials in time.&quot;<br>
<br>
- What are the subtle differences in meaning between these two sentences?<b=
r>
<br>
- Would an implementation written by a native speaker be any different depe=
nding on which of the above sentences was in the RFC?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Yoav<br>
<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><=
br>
</div></div>

--047d7bf10b46de781904dfefacf6--

From iab-chair@iab.org  Mon Jun 24 17:35:33 2013
Return-Path: <iab-chair@iab.org>
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 04D2321F9EBA; Mon, 24 Jun 2013 17:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 v9ZLY8YOmE6L; Mon, 24 Jun 2013 17:35:32 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id AF4A121F9EB9; Mon, 24 Jun 2013 17:35:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 1C3DDA8979; Mon, 24 Jun 2013 17:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M2Rz0hywdsT6; Mon, 24 Jun 2013 17:35:11 -0700 (PDT)
Received: from [192.168.2.108] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) by c9a.amsl.com (Postfix) with ESMTPSA id A2C5EA8978; Mon, 24 Jun 2013 17:35:10 -0700 (PDT)
From: IAB Chair <iab-chair@iab.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: RSOC Appointments
Date: Mon, 24 Jun 2013 20:35:20 -0400
Message-Id: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <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: Tue, 25 Jun 2013 00:35:33 -0000

The IAB extends many thanks to the community members that were willing =
to serve on the RSOC for their ongoing support of the RFC Series and the =
RFC Series Editor.  The IAB especially thanks the current RSOC members =
for their many contributions.

After reviewing the strong list of individuals who offered to serve on =
the RSOC, the IAB is appointing the following people to serve on the =
RSOC:

	Nevil Brownlee,
	Tony Hansen,
	Joe Hildebrandt,
	Bob Hinden,
	Alexey Melnikov,
	Bernard Aboba (an IAB member), and
	Joel Halpern (an IAB member).

In addition, Ray Pelletier will continue to serve as liaison from the =
IAOC to the RSOC.

The IAB sincerely thanks all of the people that offered to serve on the =
RSOC.  The IAB particularly thanks the following current RSOC members =
that will be stepping off the committee during IETF 87 in Berlin:

	Fred Baker,
	Ole Jacobsen,
	John Klensin, and
	Olaf Kolkman.

On behalf of the IAB,
   Russ Housley
   IAB Chair

From fred@cisco.com  Mon Jun 24 22:20:38 2013
Return-Path: <fred@cisco.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 1BF5511E810F for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 22:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.582
X-Spam-Level: 
X-Spam-Status: No, score=-110.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 2XM0YjMnKITC for <ietf@ietfa.amsl.com>; Mon, 24 Jun 2013 22:20:32 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 70FBA11E8108 for <ietf@ietf.org>; Mon, 24 Jun 2013 22:20:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=268; q=dns/txt; s=iport; t=1372137632; x=1373347232; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=4tQe5DFsRXa4QutZ6xEnCHFHSdFNLJf+KH4wKJW/65M=; b=GHYKird0ZFOnCsjIYpolE4VUVa/HcIUXXBdbWBnOTAUzlLIEgYVakc99 MA/mjbu8VWYN5ZtCok7DQYXlxR53zIiw3nB0HFcKlcM3+1isJb4giLhSH YtDE4jLw0z8ToX5qlXkPbkfDH3kyG+AOt9/jTWRyfdRYdUjsGDHu9VPEc Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAOQnyVGtJV2c/2dsb2JhbABagwl6gj68eIEDFnSCIwEBAQMBOj8FCwIBCA4UFBAyJQIEAQ0FCIgABrp2jx4xB4MCYQOpB4MQgig
X-IronPort-AV: E=Sophos;i="4.87,933,1363132800"; d="scan'208";a="226996242"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP; 25 Jun 2013 05:20:32 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r5P5KVEx005916 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 25 Jun 2013 05:20:31 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Tue, 25 Jun 2013 00:20:31 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Nevil Brownlee <rfc-ise@rfc-editor.org>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, Bob Hinden <bob.hinden@gmail.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Tony Hansen <tony@att.com>, Bernard Aboba <bernard.aboba@gmail.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: RSOC Appointments
Thread-Topic: RSOC Appointments
Thread-Index: AQHOcTvw9SYPjt/oe0Gy0+ckSFH+W5lGOMQA
Date: Tue, 25 Jun 2013 05:20:30 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com>
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org>
In-Reply-To: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.125]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EE1F0CEA2600E2419FA0E4A10C9F29C7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IAB <iab@iab.org>, ietf 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: Tue, 25 Jun 2013 05:20:38 -0000

Congratulations, gentlemen.

On Jun 24, 2013, at 5:35 PM, IAB Chair <iab-chair@iab.org> wrote:

> 	Nevil Brownlee,
> 	Tony Hansen,
> 	Joe Hildebrandt,
> 	Bob Hinden,
> 	Alexey Melnikov,
> 	Bernard Aboba (an IAB member), and
> 	Joel Halpern (an IAB member).


From lars@netapp.com  Tue Jun 25 00:25:55 2013
Return-Path: <lars@netapp.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 3DD4711E80D1 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 00:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.648
X-Spam-Level: 
X-Spam-Status: No, score=-4.648 tagged_above=-999 required=5 tests=[AWL=-2.049, BAYES_00=-2.599]
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 xT30MTC3Ottl for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 00:25:50 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 0216A21F9FC8 for <ietf@ietf.org>; Tue, 25 Jun 2013 00:25:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,934,1363158000"; d="scan'208";a="29246852"
Received: from vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) by mx11-out.netapp.com with ESMTP; 25 Jun 2013 00:25:48 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.03.0123.003; Tue, 25 Jun 2013 00:25:48 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Randy Bush <randy@psg.com>
Subject: Re: [IAB] RSOC Appointments
Thread-Topic: [IAB] RSOC Appointments
Thread-Index: AQHOcTv3NgfJVAnaKkWdQcbrx35oYJlGWksAgAAJUACAABm3AA==
Date: Tue, 25 Jun 2013 07:25:47 +0000
Message-ID: <988A872C-CCD7-4353-A85F-FBF200AD3A4B@netapp.com>
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com> <m261x291n5.wl%randy@psg.com>
In-Reply-To: <m261x291n5.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8037DEB9BBE92E46B95990CB56B31555@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf list <ietf@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, IAB <iab@iab.org>, Nevil Brownlee <rfc-ise@rfc-editor.org>, Alexey Melnikov <alexey.melnikov@isode.com>, "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>
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: Tue, 25 Jun 2013 07:25:55 -0000

On Jun 25, 2013, at 7:53, Randy Bush <randy@psg.com> wrote:
>> Congratulations, gentlemen.
>=20
> and they are all male

Well, all the volunteers were male, so no real surprise here.

(And yes, I wish the volunteer pool had been more diverse. But it wasn't.)

Lars

From lars@netapp.com  Tue Jun 25 00:25:59 2013
Return-Path: <lars@netapp.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 695A821F9F8D for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 00:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.648
X-Spam-Level: 
X-Spam-Status: No, score=-4.648 tagged_above=-999 required=5 tests=[AWL=-2.049, BAYES_00=-2.599]
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 KrCixU+EzdiS for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 00:25:59 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 5813F21F9FDD for <ietf@ietf.org>; Tue, 25 Jun 2013 00:25:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,934,1363158000"; d="scan'208";a="68596073"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx12-out.netapp.com with ESMTP; 25 Jun 2013 00:25:44 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Tue, 25 Jun 2013 00:25:44 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Randy Bush <randy@psg.com>
Subject: Re: [IAB] RSOC Appointments
Thread-Topic: [IAB] RSOC Appointments
Thread-Index: AQHOcTv3NgfJVAnaKkWdQcbrx35oYJlGWksAgAAJUACAABmyAA==
Date: Tue, 25 Jun 2013 07:25:43 +0000
Message-ID: <7CFB8AAE-DE07-49AB-BE77-E440C4EF5396@netapp.com>
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com> <m261x291n5.wl%randy@psg.com>
In-Reply-To: <m261x291n5.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F431D2686183AF4A93CC9FC0FF64831A@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf list <ietf@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, IAB <iab@iab.org>, Nevil Brownlee <rfc-ise@rfc-editor.org>, Alexey Melnikov <alexey.melnikov@isode.com>, "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>
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: Tue, 25 Jun 2013 07:25:59 -0000

On Jun 25, 2013, at 7:53, Randy Bush <randy@psg.com> wrote:
>> Congratulations, gentlemen.
>=20
> and they are all male

Well, all the volunteers were male, so no real surprise here.

(And yes, I wish the volunteer pool had been more diverse. But it wasn't.)

Lars

From jari.arkko@piuha.net  Tue Jun 25 03:24:43 2013
Return-Path: <jari.arkko@piuha.net>
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 A24B011E80E0; Tue, 25 Jun 2013 03:24:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ir+3P-DSHblI; Tue, 25 Jun 2013 03:24:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 8716C21F9D4B; Tue, 25 Jun 2013 03:24:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D05172CC56; Tue, 25 Jun 2013 13:24:32 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJ3-HPecDH-A; Tue, 25 Jun 2013 13:24:32 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id DD5802CC48; Tue, 25 Jun 2013 13:24:31 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <031901ce61a9$04af7ce0$0e0e76a0$@gmail.com>
Date: Tue, 25 Jun 2013 13:24:31 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1E1A8BF-088A-47A6-B4FE-A973586C7B0B@piuha.net>
References: <000301ce5c98$278d0220$76a70660$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com> <027001ce60b1$ba2ecbf0$2e8c63d0$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2406EA58@008-AM1MPN1-025.mgdnok.nokia.com> <031901ce61a9$04af7ce0$0e0e76a0$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: Simo.Veikkolainen@nokia.com, ietf@ietf.org, gen-art@ietf.org, draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.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: Tue, 25 Jun 2013 10:24:43 -0000

Roni, Simo - thank you for the review and for addressing the issue. I =
plan to ballot a No-Objection for this draft.

Jari


From daedulus@btconnect.com  Tue Jun 25 03:49:09 2013
Return-Path: <daedulus@btconnect.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 52A3D21F9FC6; Tue, 25 Jun 2013 03:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 0ee+LOR0ypf8; Tue, 25 Jun 2013 03:49:04 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe004.messaging.microsoft.com [216.32.180.14]) by ietfa.amsl.com (Postfix) with ESMTP id 0A58521F94DF; Tue, 25 Jun 2013 03:49:03 -0700 (PDT)
Received: from mail109-va3-R.bigfish.com (10.7.14.233) by VA3EHSOBE010.bigfish.com (10.7.40.12) with Microsoft SMTP Server id 14.1.225.23; Tue, 25 Jun 2013 10:49:03 +0000
Received: from mail109-va3 (localhost [127.0.0.1])	by mail109-va3-R.bigfish.com (Postfix) with ESMTP id EE3A82A00DF; Tue, 25 Jun 2013 10:49:02 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(zz9371I1462I542Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz2dh2a8h5a9h668h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail109-va3 (localhost.localdomain [127.0.0.1]) by mail109-va3 (MessageSwitch) id 1372157341657445_28100; Tue, 25 Jun 2013 10:49:01 +0000 (UTC)
Received: from VA3EHSMHS015.bigfish.com (unknown [10.7.14.229])	by mail109-va3.bigfish.com (Postfix) with ESMTP id 92B19120057; Tue, 25 Jun 2013 10:49:01 +0000 (UTC)
Received: from AMSPRD0711HT001.eurprd07.prod.outlook.com (157.56.250.181) by VA3EHSMHS015.bigfish.com (10.7.99.25) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 25 Jun 2013 10:48:53 +0000
Received: from DBXPRD0611HT001.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.242.14.162) with Microsoft SMTP Server (TLS) id 14.16.324.0; Tue, 25 Jun 2013 10:48:47 +0000
Message-ID: <04d001ce7191$a5f4bf00$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: ietf <ietf@ietf.org>
References: <20130620185914.19663.88097.idtracker@ietfa.amsl.com>
Subject: Re: IAOC Website Updated
Date: Tue, 25 Jun 2013 11:48:57 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
Cc: iaoc@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: Tue, 25 Jun 2013 10:49:09 -0000

----- Original Message -----
From: "IETF Administrative Director" <iad@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Sent: Thursday, June 20, 2013 7:59 PM

One of the IAOC goals for 2013 was to update the IAOC website to improve
consistency, organization, linkage, and ease of use.

I am pleased to announce that the IAOC site has been updated and is
available
now for your use at <http://iaoc.ietf.org/>.

On the home page see a video of an Overview of the IAOC given by Chair
Bob
Hinden in Orlando that includes a discussion of venue selection and IETF
finances.  Also on the home page are recent announcements, as well as
reports
from IANA, the RFC Editor, the IETF Chair, the NomCom Chair, and more.

The navigation bar makes it easy to find financial statements, minutes,
meeting sponsorship opportunities, and much more.

We hope you find this helpful, the IAOC as more transparent, and of
course we
welcome your feedback.

<tp>

"Could Do Better".

The main impression that this page has on me is that this is a part of
the IETF, because that is the style of the page and that is what the
navigation on the left tells me; perhaps this is one of those Working
Groups I have never heard of:-(

The very brief description - "the fiscal and administrative support" -
makes me think of taxes (and tax avoidance) while the link to an RFC,
which starts with loads of irrelevant - to the likely reader of this
page (I assume someone relatively new to the work of this SDO) -
boilerplate is enough to make anyone reach for the off-switch, and
guaranteed to do so if they get as far as IAD, IASA, ISOC, etc.
Alphabet
soup indeed!

I have tried - and failed - to produce a paragraph which summarises what
IAOC is.  I would start with the need of the IETF for e-mail and web
servers, and a few other bits and pieces such as legal advice and
ownership of rights, then the need for money to fund that, where the
money comes from and how the expenditure is supervised and where ISOC
fits into that - but not an RFC in sight - or site.  This would not need
to mention the IAD but cannot, IMO, avoid IASA.

Tom Petch

</tp>







Ray
IETF Administrative Director

PS:  Going to IETF 87 in Berlin?  The IAOC will be doing another
overview
session there, Sunday July 28 at 3:00 PM.  Hope to see you there!



From tony@att.com  Tue Jun 25 04:05:20 2013
Return-Path: <tony@att.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 54EC321F9DC1 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 04:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.059
X-Spam-Level: 
X-Spam-Status: No, score=-106.059 tagged_above=-999 required=5 tests=[AWL=0.541, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 TJKW2WgPZuvs for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 04:05:13 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 7E3B921F9DED for <ietf@ietf.org>; Tue, 25 Jun 2013 04:05:12 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 86979c15.0.3901894.00-293.10824030.nbfkord-smmo06.seg.att.com (envelope-from <tony@att.com>);  Tue, 25 Jun 2013 11:05:12 +0000 (UTC)
X-MXL-Hash: 51c97968511b3b18-9c3661449b003b75fd185ad27a8234eedbb3971f
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r5PB5CIq011183 for <ietf@ietf.org>; Tue, 25 Jun 2013 07:05:12 -0400
Received: from alpi133.aldc.att.com (alpi133.aldc.att.com [130.8.217.3]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r5PB59q5011180 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 25 Jun 2013 07:05:11 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi133.aldc.att.com (RSA Interceptor) for <ietf@ietf.org>; Tue, 25 Jun 2013 11:05:03 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r5PB53HO030331 for <ietf@ietf.org>; Tue, 25 Jun 2013 07:05:03 -0400
Received: from dns.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r5PB4tp7029893 for <ietf@ietf.org>; Tue, 25 Jun 2013 07:04:55 -0400
Received: from [135.70.3.126] (vpn-135-70-3-126.vpn.west.att.com[135.70.3.126]) by maillennium.att.com (mailgw1) with ESMTP id <20130625110450gw100bhhbje> (Authid: tony); Tue, 25 Jun 2013 11:04:54 +0000
X-Originating-IP: [135.70.3.126]
Message-ID: <51C97959.7080808@att.com>
Date: Tue, 25 Jun 2013 07:04:57 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: RSOC Appointments
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=2.0 cv=VapAyiV9 c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=ejDPqqJihJkA:10 a=bfzWQn4VrGAA:10 a=ofMgfj31e3cA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=zQP7CpKOAAAA:8 a=cwnNT4OZ]
X-AnalysisOut: [AKcA:10 a=PVlkjBJtAAAA:8 a=wDU3L2s_HeycLkWVX88A:9 a=wPNLvf]
X-AnalysisOut: [GTeEIA:10 a=M1DkEnbHmpQA:10]
Cc: ietf list <ietf@ietf.org>, Nevil Brownlee <rfc-ise@rfc-editor.org>, Bob Hinden <bob.hinden@gmail.com>, IAB <iab@iab.org>, "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Bernard Aboba <bernard.aboba@gmail.com>
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: Tue, 25 Jun 2013 11:05:20 -0000

Thank you, Fred.

    Tony

On 6/25/2013 1:20 AM, Fred Baker (fred) wrote:
> Congratulations, gentlemen.
>
> On Jun 24, 2013, at 5:35 PM, IAB Chair <iab-chair@iab.org> wrote:
>
>> 	Nevil Brownlee,
>> 	Tony Hansen,
>> 	Joe Hildebrandt,
>> 	Bob Hinden,
>> 	Alexey Melnikov,
>> 	Bernard Aboba (an IAB member), and
>> 	Joel Halpern (an IAB member).


From arturo.servin@gmail.com  Tue Jun 25 04:10:35 2013
Return-Path: <arturo.servin@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 DDBF511E80E6 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 04:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599]
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 FzYsD99tzp0C for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 04:10:35 -0700 (PDT)
Received: from mail-bk0-x22a.google.com (mail-bk0-x22a.google.com [IPv6:2a00:1450:4008:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 395FD21F9E70 for <ietf@ietf.org>; Tue, 25 Jun 2013 04:10:28 -0700 (PDT)
Received: by mail-bk0-f42.google.com with SMTP id jk13so4453554bkc.1 for <ietf@ietf.org>; Tue, 25 Jun 2013 04:10:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=CFcEqNq0NgzYP0u63Y7R3VxBt/SnnFjTxhJWzXQdVUU=; b=g7sDriJXvg7o6ZwyEzLpDxwKoZ5+BcBc3gBSYATt+o2fPwaazVKKKmYkCnG5BRrLNr nbEV+CPNZA7SgoQvvxoHGXz6nlH4v2fHsADwSea4m4satTl41bv5IOyUl+L8yB3WsxVk s6VhnRPlc/yLBrkuJLaxi5yPUyv8C0nk7FlRQ3sdjv77ej0punEhHzIIO7qAUQb2d3zl wB/nuw2lYlCwojk+IRv/XSAvmYjyZPJ9uLDingTQwh6QYFMgRaGLr+FTJJHEA/HRnbsH vE7ipMppyfLub0Iltu+gllqSmO4w9pvP/jCzhaB3Ta84QoPVtvtXciAWwnlwMPRcxy80 X1pQ==
X-Received: by 10.204.2.200 with SMTP id 8mr3722bkk.92.1372158627270; Tue, 25 Jun 2013 04:10:27 -0700 (PDT)
Received: from [192.168.0.5] ([90.214.33.42]) by mx.google.com with ESMTPSA id kv3sm5918471bkb.10.2013.06.25.04.10.26 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Jun 2013 04:10:26 -0700 (PDT)
Message-ID: <51C97AA1.1080603@gmail.com>
Date: Tue, 25 Jun 2013 12:10:25 +0100
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IAB] RSOC Appointments
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com> <m261x291n5.wl%randy@psg.com> <988A872C-CCD7-4353-A85F-FBF200AD3A4B@netapp.com>
In-Reply-To: <988A872C-CCD7-4353-A85F-FBF200AD3A4B@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Tue, 25 Jun 2013 11:10:36 -0000

    I checked the call for nommitantios (Sent on april 24th 2013 on the
ietf-announce) and it does not describe what should be the
qualifications of the candidates. I think that this enough to alienate
new people (as they may think that they are not good candidates for the
position because of lack of experience in the IETF, not being an RFC
author, etc.)

    I would recommend that future announcement of kind of positions have
a very clear profile of what it is expected from the candidates in IETF
experience, general requirements, etc. In the end, it is like we were
filling a job positions in an organization, the difference here is that
we are not receiving a salary.

my 20 cents.
/as

On 6/25/13 8:25 AM, Eggert, Lars wrote:
> On Jun 25, 2013, at 7:53, Randy Bush <randy@psg.com> wrote:
>>> Congratulations, gentlemen.
>> and they are all male
> Well, all the volunteers were male, so no real surprise here.
>
> (And yes, I wish the volunteer pool had been more diverse. But it wasn't.)
>
> Lars


From dave@cridland.net  Tue Jun 25 05:28:11 2013
Return-Path: <dave@cridland.net>
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 2F59F11E80E6 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 05:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 pXE9BIYqpgx8 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 05:28:10 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 9724721F8EAE for <ietf@ietf.org>; Tue, 25 Jun 2013 05:28:00 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id v19so11955592obq.35 for <ietf@ietf.org>; Tue, 25 Jun 2013 05:27:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6QiyWEZFL5YpJ29NJI97Nu9NhPKWw6l4ihqs3J5nAZo=; b=V1z3EkY7JLbHDKwiMU2AOcf0e2muTQe4q0Gyi8LZza+Ji5fAq7Add1koaONfGIhP61 4gsFWeoIEhmY5AK6vnF6ij7qW6WVMEi6oQY66E3QrWgAXGKPNRwb4sO/Y6bLkWR+GsvQ Y1HAbh96lh13QXD1yNeu7QsIY5v7fpbQWnuGc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=6QiyWEZFL5YpJ29NJI97Nu9NhPKWw6l4ihqs3J5nAZo=; b=gZ3etpjD7FcYfEdYqydEj9LuW0PoR5EuyAuq5rQXPQo24u1oquD5LvD5OJKiCmItPr L+V5Jjb1264SJHJ4KZ8ObMihNpzBJpDvcUC2KhJO8bYnJCVA4Jce95mKovsQK1qJUy4U ed9XS6quPyINbSiYMudaSwu71zimmBAzmIgS4khvTTjEq9z+sz/SNOPfR9qBYCGARvRW CWpO2Mp1rIfaKPDWIxP3v9I0mOl7LkKqYmCRHhi2zkXN1v270Wuc9zfPn/tDDRsxAKxb H7kU7n4uLIklD8hteNMzxVjpMoHiV5hMVHCd//rUJhHNvcJWy4ke8MeyfYlQ5VWgXGlJ eGCg==
MIME-Version: 1.0
X-Received: by 10.60.102.6 with SMTP id fk6mr13341382oeb.43.1372163277715; Tue, 25 Jun 2013 05:27:57 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Tue, 25 Jun 2013 05:27:57 -0700 (PDT)
In-Reply-To: <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com>
Date: Tue, 25 Jun 2013 13:27:57 +0100
Message-ID: <CAKHUCzxtiXOgXwYmn+viq88r--Rs2vHk-0v85y4TyJzzQhDBtg@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED
From: Dave Cridland <dave@cridland.net>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary=089e0111bae2be0d0604dff9a8c7
X-Gm-Message-State: ALoCoQm2YhmhpI3mtB6pneVYxH9YdLAa5lRyoCteNW7srSbnjlWfSrFMo4bPvBdZz1e+qfJmDQ/O
Cc: IETF-Discussion 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: Tue, 25 Jun 2013 12:28:11 -0000

--089e0111bae2be0d0604dff9a8c7
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 25, 2013 at 1:33 AM, Phillip Hallam-Baker <hallam@gmail.com>wrote:

>
> RECOMMENDED is a strong suggestion that the implementation may override at
> the discretion of the implementer. SHOULD is normative.
>
>
Of course, they both mean the same, because the author has (one assumes)
explicitly said that it means what it says in RFC 2119. Applying your own
meanings to words used in specifications is never going to work, because
otherwise I could start waxing lyrical on what exactly a credential meant
(and in traditional spoken English, it relates to authorization rather than
authentication as here).

In ordinary English, without specific guidance as RFC 2119 gives, I'd
consider "should" and "must" as having virtually the same strength, and
"recommended" being far lower. "Should", however, is used for third parties
and also when a requirement has exceptions, conditions, and so on - it's
also used for general conditional statements, too, such as "I'd like that",
which really expands to "I should like that" rather than "I would like
that". Another case is that if I say "Phillip must have read RFC 2119",
I've made an incorrect statement if he hasn't, whereas if I say "Phillip
should have read RFC 2119", then it's clear Phillip would be the one at
fault.

Much of the problem with actual English in specifications comes from the
fact that specifications are written to tell people what something else
should do, and English as a language is more adept at telling you what you
must do, and ideally by using the imperative form instead.

So while I can write, "You must read RFC 2119. Do not attempt to derive
implied meaning not present in RFC 2119", I can only express a desire that
Phillip should do the same.

Dave.

--089e0111bae2be0d0604dff9a8c7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jun 25, 2013 at 1:33 AM, Phillip Hallam-Baker <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:hallam@gmail.com" target=3D"_blank">hal=
lam@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><br></div>RECOMMENDED =
is a strong suggestion that the implementation may override at the discreti=
on of the implementer. SHOULD is normative.<div class=3D"gmail_extra">
<br></div></div></blockquote><div><br></div><div style>Of course, they both=
 mean the same, because the author has (one assumes) explicitly said that i=
t means what it says in RFC 2119. Applying your own meanings to words used =
in specifications is never going to work, because otherwise I could start w=
axing lyrical on what exactly a credential meant (and in traditional spoken=
 English, it relates to authorization rather than authentication as here).<=
/div>
<div style><br></div><div style>In ordinary English, without specific guida=
nce as RFC 2119 gives, I&#39;d consider &quot;should&quot; and &quot;must&q=
uot; as having virtually the same strength, and &quot;recommended&quot; bei=
ng far lower. &quot;Should&quot;, however, is used for third parties and al=
so when a requirement has exceptions, conditions, and so on - it&#39;s also=
 used for general conditional statements, too, such as &quot;I&#39;d like t=
hat&quot;, which really expands to &quot;I should like that&quot; rather th=
an &quot;I would like that&quot;. Another case is that if I say &quot;Phill=
ip must have read RFC 2119&quot;, I&#39;ve made an incorrect statement if h=
e hasn&#39;t, whereas if I say &quot;Phillip should have read RFC 2119&quot=
;, then it&#39;s clear Phillip would be the one at fault.</div>
<div style><br></div><div style>Much of the problem with actual English in =
specifications comes from the fact that specifications are written to tell =
people what something else should do, and English as a language is more ade=
pt at telling you what you must do, and ideally by using the imperative for=
m instead.</div>
<div style><br></div><div style>So while I can write, &quot;You must read R=
FC 2119. Do not attempt to derive implied meaning not present in RFC 2119&q=
uot;, I can only express a desire that Phillip should do the same.</div>
<div style><br></div><div style>Dave.=A0</div></div></div></div>

--089e0111bae2be0d0604dff9a8c7--

From mrex@sap.com  Tue Jun 25 05:32:06 2013
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 D165F21F96EF for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 05:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.917
X-Spam-Level: 
X-Spam-Status: No, score=-9.917 tagged_above=-999 required=5 tests=[AWL=0.332,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 GEqdemF5tsKu for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 05:32:01 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 52A0E21F9307 for <ietf@ietf.org>; Tue, 25 Jun 2013 05:31:59 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r5PCVnkr023042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 25 Jun 2013 14:31:50 +0200 (MEST)
Subject: Re: SHOULD and RECOMMENDED
In-Reply-To: <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Date: Tue, 25 Jun 2013 14:31:49 +0200 (CEST)
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: <20130625123149.D919E1A852@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF-Discussion list <ietf@ietf.org>
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: Tue, 25 Jun 2013 12:32:07 -0000

Phillip Hallam-Baker wrote:
>
> RECOMMENDED is a strong suggestion that the implementation may override at
> the discretion of the implementer. SHOULD is normative.
> 
> So the first tells me that I can make up my own mind, the second says that
> I should give a reason if I don't comply.

This is only half of the story.

PKIX (rfc5280) defines the concept of a "minimum requirements RP",
i.e. an implementation which implements only MUSTs, and potentially not
a single SHOULD.  Essentially, this waters down all SHOULDs to MAYs.

-Martin

From stpeter@stpeter.im  Tue Jun 25 05:37:45 2013
Return-Path: <stpeter@stpeter.im>
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 6111221F9ED8 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 05:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Zn6x5pPWv1DA for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 05:37:40 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 4F99C21F99DC for <ietf@ietf.org>; Tue, 25 Jun 2013 05:37:40 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 5FF47412E2; Tue, 25 Jun 2013 06:37:57 -0600 (MDT)
Message-ID: <51C98F14.6090606@stpeter.im>
Date: Tue, 25 Jun 2013 06:37:40 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: [IAB] RSOC Appointments
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com> <m261x291n5.wl%randy@psg.com> <988A872C-CCD7-4353-A85F-FBF200AD3A4B@netapp.com> <51C97AA1.1080603@gmail.com>
In-Reply-To: <51C97AA1.1080603@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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: Tue, 25 Jun 2013 12:37:45 -0000

On 6/25/13 5:10 AM, Arturo Servin wrote:
> 
>     I checked the call for nommitantios (Sent on april 24th 2013 on the
> ietf-announce) and it does not describe what should be the
> qualifications of the candidates. I think that this enough to alienate
> new people (as they may think that they are not good candidates for the
> position because of lack of experience in the IETF, not being an RFC
> author, etc.)
> 
>     I would recommend that future announcement of kind of positions have
> a very clear profile of what it is expected from the candidates in IETF
> experience, general requirements, etc. In the end, it is like we were
> filling a job positions in an organization, the difference here is that
> we are not receiving a salary.

Agreed. Hiring without a job description is just silly...

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From hallam@gmail.com  Tue Jun 25 05:52:49 2013
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 5DFBF21F964C for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 05:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 tRHOhxdyFusr for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 05:52:48 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5302A21F9302 for <ietf@ietf.org>; Tue, 25 Jun 2013 05:52:47 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id z11so745597wgg.3 for <ietf@ietf.org>; Tue, 25 Jun 2013 05:52:45 -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=9y8oZN2sUkEZycsvlD6mkAs0a1BvwCGMXv8XCfrqjiw=; b=lwbizJIZwd3Hv6mb6hnW+e/bxHXvYakw/JpOqktIw0cSAjgGAQfM65cYNJeoTOSX5A CMqgKIAPZoJQhu7iKr3tXc1bpKuk6gdpkjxbhvnh9oEWQPKapEB7mw3O7uKWc8P9TOVr ugHvWAZfC5NAv8YYd2/UoE+xaW02Hxq0YemVRgC13MjMBmp1xJUpjRTtORyVn/ZZqNTg uIJCf0LdxY2CHbu/81V2Rh7ydFCX7vs0aOO3i3WwzHHxHm517VkTtTTuyQPxvN2s/9EF 7eIoP/I4Q5yLZi1IIJdehm3nfEJFKlAIlGbF/QhWG+HrQ7Yz/SkxehaMePs7ds2wYeB1 L4Yw==
MIME-Version: 1.0
X-Received: by 10.194.122.71 with SMTP id lq7mr953162wjb.77.1372164765252; Tue, 25 Jun 2013 05:52:45 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Tue, 25 Jun 2013 05:52:45 -0700 (PDT)
In-Reply-To: <CAKHUCzxtiXOgXwYmn+viq88r--Rs2vHk-0v85y4TyJzzQhDBtg@mail.gmail.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com> <CAKHUCzxtiXOgXwYmn+viq88r--Rs2vHk-0v85y4TyJzzQhDBtg@mail.gmail.com>
Date: Tue, 25 Jun 2013 08:52:45 -0400
Message-ID: <CAMm+Lwg3re0Ok39b5COoO8M5pTW-eNT5ifpkrSuqNdSEGkveHg@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=089e0122975068044604dffa018f
Cc: IETF-Discussion 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: Tue, 25 Jun 2013 12:52:49 -0000

--089e0122975068044604dffa018f
Content-Type: text/plain; charset=ISO-8859-1

I DO NOT agree that 2119 is the only source of consequence here.

Perhaps if I showed Dave Cridland an article on netiquete he could try to
be less patronizing. Unlike some here I do not regard the RFC series as
having divine inspiration.


Many other standards organizations use normative language. Though at this
point who is following whom is difficult to determine.

RECOMMENDED is a very useful term to have. Particularly when writing specs
for middleware.


The IETF document describing use of the term is WRONG it needs to be
corrected. Any corrections would only apply to new specs that reference the
new RFC.



On Tue, Jun 25, 2013 at 8:27 AM, Dave Cridland <dave@cridland.net> wrote:

> On Tue, Jun 25, 2013 at 1:33 AM, Phillip Hallam-Baker <hallam@gmail.com>wrote:
>
>>
>> RECOMMENDED is a strong suggestion that the implementation may override
>> at the discretion of the implementer. SHOULD is normative.
>>
>>
> Of course, they both mean the same, because the author has (one assumes)
> explicitly said that it means what it says in RFC 2119. Applying your own
> meanings to words used in specifications is never going to work, because
> otherwise I could start waxing lyrical on what exactly a credential meant
> (and in traditional spoken English, it relates to authorization rather than
> authentication as here).
>
> In ordinary English, without specific guidance as RFC 2119 gives, I'd
> consider "should" and "must" as having virtually the same strength, and
> "recommended" being far lower. "Should", however, is used for third parties
> and also when a requirement has exceptions, conditions, and so on - it's
> also used for general conditional statements, too, such as "I'd like that",
> which really expands to "I should like that" rather than "I would like
> that". Another case is that if I say "Phillip must have read RFC 2119",
> I've made an incorrect statement if he hasn't, whereas if I say "Phillip
> should have read RFC 2119", then it's clear Phillip would be the one at
> fault.
>
> Much of the problem with actual English in specifications comes from the
> fact that specifications are written to tell people what something else
> should do, and English as a language is more adept at telling you what you
> must do, and ideally by using the imperative form instead.
>
> So while I can write, "You must read RFC 2119. Do not attempt to derive
> implied meaning not present in RFC 2119", I can only express a desire that
> Phillip should do the same.
>
> Dave.
>



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

--089e0122975068044604dffa018f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I DO NOT agree that 2119 is the only source of consequence=
 here.<div><br></div><div style>Perhaps if I showed Dave Cridland an articl=
e on netiquete he could try to be less patronizing. Unlike some here I do n=
ot regard the RFC series as having divine inspiration.</div>
<div><br><div><br></div><div style>Many other standards organizations use n=
ormative language. Though at this point who is following whom is difficult =
to determine.=A0</div><div style><br></div><div style>RECOMMENDED is a very=
 useful term to have. Particularly when writing specs for middleware.</div>
<div style><br></div></div><div style><br></div><div style>The IETF documen=
t describing use of the term is WRONG it needs to be corrected. Any correct=
ions would only apply to new specs that reference the new RFC.</div><div st=
yle>
<br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quot=
e">On Tue, Jun 25, 2013 at 8:27 AM, Dave Cridland <span dir=3D"ltr">&lt;<a =
href=3D"mailto:dave@cridland.net" target=3D"_blank">dave@cridland.net</a>&g=
t;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"im">On Tue, J=
un 25, 2013 at 1:33 AM, Phillip Hallam-Baker <span dir=3D"ltr">&lt;<a href=
=3D"mailto:hallam@gmail.com" target=3D"_blank">hallam@gmail.com</a>&gt;</sp=
an> wrote:<br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"i=
m">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><br></div>RECOMMENDED =
is a strong suggestion that the implementation may override at the discreti=
on of the implementer. SHOULD is normative.<div class=3D"gmail_extra">

<br></div></div></blockquote><div><br></div></div><div>Of course, they both=
 mean the same, because the author has (one assumes) explicitly said that i=
t means what it says in RFC 2119. Applying your own meanings to words used =
in specifications is never going to work, because otherwise I could start w=
axing lyrical on what exactly a credential meant (and in traditional spoken=
 English, it relates to authorization rather than authentication as here).<=
/div>

<div><br></div><div>In ordinary English, without specific guidance as RFC 2=
119 gives, I&#39;d consider &quot;should&quot; and &quot;must&quot; as havi=
ng virtually the same strength, and &quot;recommended&quot; being far lower=
. &quot;Should&quot;, however, is used for third parties and also when a re=
quirement has exceptions, conditions, and so on - it&#39;s also used for ge=
neral conditional statements, too, such as &quot;I&#39;d like that&quot;, w=
hich really expands to &quot;I should like that&quot; rather than &quot;I w=
ould like that&quot;. Another case is that if I say &quot;Phillip must have=
 read RFC 2119&quot;, I&#39;ve made an incorrect statement if he hasn&#39;t=
, whereas if I say &quot;Phillip should have read RFC 2119&quot;, then it&#=
39;s clear Phillip would be the one at fault.</div>

<div><br></div><div>Much of the problem with actual English in specificatio=
ns comes from the fact that specifications are written to tell people what =
something else should do, and English as a language is more adept at tellin=
g you what you must do, and ideally by using the imperative form instead.</=
div>

<div><br></div><div>So while I can write, &quot;You must read RFC 2119. Do =
not attempt to derive implied meaning not present in RFC 2119&quot;, I can =
only express a desire that Phillip should do the same.</div><span class=3D"=
HOEnZb"><font color=3D"#888888">
<div><br></div><div>Dave.=A0</div></font></span></div></div></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Website: <a =
href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div>

--089e0122975068044604dffa018f--

From hallam@gmail.com  Tue Jun 25 06:03:54 2013
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 D403E21F9FD1 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 06:03:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 oX51WlM2MVDi for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 06:03:54 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id E972321F9D79 for <ietf@ietf.org>; Tue, 25 Jun 2013 06:03:53 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id l18so9415400wgh.14 for <ietf@ietf.org>; Tue, 25 Jun 2013 06:03:53 -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=+PXdrtmXr5e5GC/6Oveefe+XCDZHSN55xU0zng7D1AU=; b=V5mBHxwXdI/oGUg7dk42nFgxEm4AhouN2jW08ofXF1ww/eKM+WTBexzgNLMOKETBEU H6aJTdqJZpQhIK9mb4GrzMbNh+qANvVTudbieH6hb//XIgDmjizsCbUgsgdCsm+rhzm8 EyQCn5YgZxhq3B50v4RBk06+xy50OGcNvrDu7g+nISvfGeDq1aeDsjnzHfnhfJIsEALf K7/JaqHloYBaHzb+bkysLjDM6twOMqs95GGu6VRh/xBvePFNKKs1HyLCctUfl4RXI2IS umgqTtoBkYYWS/4ZO7rp4oXO9NZpKoiXE9mu9jtP0ZNJnpQpUBt4Gmvh/maV5sZoMBVh RsHw==
MIME-Version: 1.0
X-Received: by 10.180.13.5 with SMTP id d5mr9074837wic.56.1372165433026; Tue, 25 Jun 2013 06:03:53 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Tue, 25 Jun 2013 06:03:52 -0700 (PDT)
In-Reply-To: <20130625123149.D919E1A852@ld9781.wdf.sap.corp>
References: <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com> <20130625123149.D919E1A852@ld9781.wdf.sap.corp>
Date: Tue, 25 Jun 2013 09:03:52 -0400
Message-ID: <CAMm+LwgBe1OzW_N2E8XkVSeKfpj8gxYX58+455CPw0=_R1zUBw@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Martin Rex <mrex@sap.com>
Content-Type: multipart/alternative; boundary=001a11c23fba35750f04dffa295e
Cc: IETF-Discussion 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: Tue, 25 Jun 2013 13:03:54 -0000

--001a11c23fba35750f04dffa295e
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 25, 2013 at 8:31 AM, Martin Rex <mrex@sap.com> wrote:

> Phillip Hallam-Baker wrote:
> >
> > RECOMMENDED is a strong suggestion that the implementation may override
> at
> > the discretion of the implementer. SHOULD is normative.
> >
> > So the first tells me that I can make up my own mind, the second says
> that
> > I should give a reason if I don't comply.
>
> This is only half of the story.
>
> PKIX (rfc5280) defines the concept of a "minimum requirements RP",
> i.e. an implementation which implements only MUSTs, and potentially not
> a single SHOULD.  Essentially, this waters down all SHOULDs to MAYs.
>

>From a minimum implementation point of view MAY, RECOMMENDED and SHOULD all
have the same effect. They are not identical from other points of view.

MAY tells the implementer that there is behavior that they are required to
accept from other implementations they interact with. So it creates an
implicit MUST NOT.

SHOULD tells the implementer that there is behavior that cannot be
compliance checked that is important.


I would like to see more clarity in IETF specs and the minimum use of MUST,
SHOULD and MAY since they all create compliance requirements.
Distinguishing RECOMMENDED from SHOULD properly would help here.


I suggest that if specs want to use RECOMMENDED and SHOULD as not being
synonyms that they follow the reference to 2119 with a statement explaining
the difference.




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

--001a11c23fba35750f04dffa295e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jun 25, 2013 at 8:31 AM, Martin Rex <span dir=3D"l=
tr">&lt;<a href=3D"mailto:mrex@sap.com" target=3D"_blank">mrex@sap.com</a>&=
gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div class=3D"im">Phillip Hallam-Baker wrote:<br>
&gt;<br>
&gt; RECOMMENDED is a strong suggestion that the implementation may overrid=
e at<br>
&gt; the discretion of the implementer. SHOULD is normative.<br>
&gt;<br>
&gt; So the first tells me that I can make up my own mind, the second says =
that<br>
&gt; I should give a reason if I don&#39;t comply.<br>
<br>
</div>This is only half of the story.<br>
<br>
PKIX (rfc5280) defines the concept of a &quot;minimum requirements RP&quot;=
,<br>
i.e. an implementation which implements only MUSTs, and potentially not<br>
a single SHOULD. =A0Essentially, this waters down all SHOULDs to MAYs.<br><=
/blockquote><div><br></div><div style>From a minimum implementation point o=
f view MAY, RECOMMENDED and SHOULD all have the same effect. They are not i=
dentical from other points of view.</div>
<div style><br></div><div style>MAY tells the implementer that there is beh=
avior that they are required to accept from other implementations they inte=
ract with. So it creates an implicit MUST NOT.=A0</div><div style><br></div=
>
<div style>SHOULD tells the implementer that there is behavior that cannot =
be compliance checked that is important.</div><div style><br></div><div sty=
le><br></div><div style>I would like to see more clarity in IETF specs and =
the minimum use of MUST, SHOULD and MAY since they all create compliance re=
quirements. Distinguishing RECOMMENDED from SHOULD properly would help here=
.</div>
<div style><br></div><div style><br></div><div style>I suggest that if spec=
s want to use RECOMMENDED and SHOULD as not being synonyms that they follow=
 the reference to 2119 with a statement explaining the difference.</div>
<div><br></div><div><br></div><div>=A0</div></div><div><br></div>-- <br>Web=
site: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c23fba35750f04dffa295e--

From hallam@gmail.com  Tue Jun 25 06:35:30 2013
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 9206121E80AA; Tue, 25 Jun 2013 06:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 EqF66jqTrkag; Tue, 25 Jun 2013 06:35:29 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id C8C5E21E80A8; Tue, 25 Jun 2013 06:35:28 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id k10so756553wiv.11 for <multiple recipients>; Tue, 25 Jun 2013 06:35:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=MhTbweCKCpr4O45QgrqGFp79BRI//1MD7U8fzAAYpeQ=; b=fEGs0+WyRiEQCKvbW2NEw60NN5oUnZ1gvCy1BrUuScmmoSu033Bq4o3DovNgUVhMh0 /r48Yhorqu5VR+W44RE9sp57yxCu3EqA3UuwuxnFLjN8c5DKWNU2p4I0+Mdym5iBjbj/ vzd9rX1mG72+QUWHmIb2iD3TbKW0DPD07EL7HKWmRbTE3jKSSIQB7ygs+s1jf3vxOiDS V7zBpkKpxlwwUOrSH259O54oRq2rVZiFMGtyJSquzC+63j5Gt2nfY/Y1bAPk7KEjvkXB AWwsDTyLMbYFH7T4yOKmWnlFzbxuoNG5UHTF8bpFiFs5OLftT8jqt5xsj9fD6OFqB2dQ /NHg==
MIME-Version: 1.0
X-Received: by 10.194.240.201 with SMTP id wc9mr12417371wjc.1.1372167327918; Tue, 25 Jun 2013 06:35:27 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Tue, 25 Jun 2013 06:35:27 -0700 (PDT)
Date: Tue, 25 Jun 2013 09:35:27 -0400
Message-ID: <CAMm+LwiT0B744XbN02FQ7UniHOYmJg0=KQUNyQq8MTHWCZBtFQ@mail.gmail.com>
Subject: SECDIR review of draft-ietf-l2vpn-pbb-vpls-pe-model
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "iesg@ietf.org" <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>,  draft-ietf-l2vpn-pbb-vpls-pe-model@ietf.org
Content-Type: multipart/alternative; boundary=089e013d1bea27333f04dffa9a9c
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: Tue, 25 Jun 2013 13:35:30 -0000

--089e013d1bea27333f04dffa9a9c
Content-Type: text/plain; charset=ISO-8859-1

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG. These
comments were written primarily for the benefit of the security area
directors.  Document editors and WG chairs should treat these comments just
like any other last call comments.


The draft is an informational document describing an architecture for
moving packets about based on MAC addresses.


While the existence of such architectures and devices is likely relevant to
Internet Protocol networking, the draft does not explain how the
architecture described is relevant.

The draft does not contain a substantive Security Considerations, there is
instead a reference:

  No new security issues are introduced beyond those that are described

   in [RFC4761 <http://tools.ietf.org/html/rfc4761>] and [RFC4762
<http://tools.ietf.org/html/rfc4762>].


The references in turn contain references

   A more comprehensive description of the security issues involved in
   L2VPNs is covered in [RFC4111 <http://tools.ietf.org/html/rfc4111>].



This is a pity if the principle purpose of the document is to explain the
differences between IP layer inter-networking and Layer 2 (aka Ethernet
layer) networking and the main differences are in the area of security and
scalability.

One of the main reasons to prefer L2 networking over IP is the dependence
certain LAN protocols still have on the use of broadcast techniques. But
broadcast techniques are by their very nature unscalable. Given n nodes the
cost of broadcast traffic rises as n^2 as every machine on the network has
to process the spam from all the rest.

>From a security point of view the L2 approach results in a true peered
network which has unfortunate effects on security. Absent mechanisms to
authenticate network control messages, every additional machine added to
the network is an additional potential point of pollution.





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

--089e013d1bea27333f04dffa9a9c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:12.7=
27272033691406px">I have reviewed this document as part of the security dir=
ectorate&#39;s ongoing effort to review all IETF documents being processed =
by the IESG. These comments were written primarily for the benefit of the s=
ecurity area directors. =A0Document editors and WG chairs should treat thes=
e comments just like any other last call comments.</span><br clear=3D"all">
<div><br></div><div><br></div><div style>The draft is an informational docu=
ment describing an architecture for moving packets about based on MAC addre=
sses.</div><div style><br></div><div style><br></div><div style>While the e=
xistence of such architectures and devices is likely relevant to Internet P=
rotocol networking, the draft does not explain how the architecture describ=
ed is relevant.=A0</div>
<div style><br></div><div style>The draft does not contain a substantive Se=
curity Considerations, there is instead a reference:</div><div style><br></=
div><div style>=A0<span style=3D"font-size:1em;color:rgb(0,0,0)">   No new =
security issues are introduced beyond those that are described</span><br>
</div><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0=
px;color:rgb(0,0,0)">   in [<a href=3D"http://tools.ietf.org/html/rfc4761">=
RFC4761</a>] and [<a href=3D"http://tools.ietf.org/html/rfc4762" title=3D"&=
quot;Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (=
LDP) Signaling&quot;">RFC4762</a>].</pre>
<div><br></div><div style>The references in turn contain references</div><d=
iv style><br></div><div style><pre class=3D"" style=3D"font-size:1em;margin=
-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   A more comprehensive descri=
ption of the security issues involved in
   L2VPNs is covered in [<a href=3D"http://tools.ietf.org/html/rfc4111" tit=
le=3D"&quot;Security Framework for Provider-Provisioned Virtual Private Net=
works (PPVPNs)&quot;">RFC4111</a>]. </pre><pre class=3D"" style=3D"font-siz=
e:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
<br></pre></div><div style><br></div><div style>This is a pity if the princ=
iple purpose of the document is to explain the differences between IP layer=
 inter-networking and Layer 2 (aka Ethernet layer) networking and the main =
differences are in the area of security and scalability.</div>
<div style><br></div><div style>One of the main reasons to prefer L2 networ=
king over IP is the dependence certain LAN protocols still have on the use =
of broadcast techniques. But broadcast techniques are by their very nature =
unscalable. Given n nodes the cost of broadcast traffic rises as n^2 as eve=
ry machine on the network has to process the spam from all the rest.</div>
<div style><br></div><div style>From a security point of view the L2 approa=
ch results in a true peered network which has unfortunate effects on securi=
ty. Absent mechanisms to authenticate network control messages, every addit=
ional machine added to the network is an additional potential point of poll=
ution.</div>
<div style><br></div><div style><br></div><div style><br></div><div style><=
br></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/"=
>http://hallambaker.com/</a><br>
</div>

--089e013d1bea27333f04dffa9a9c--

From housley@vigilsec.com  Tue Jun 25 06:46:23 2013
Return-Path: <housley@vigilsec.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 9C2D921E8090 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 06:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 aRMOrEN47kxZ for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 06:46:17 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 4E37621E8098 for <ietf@ietf.org>; Tue, 25 Jun 2013 06:46:15 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 029ABF2407E; Tue, 25 Jun 2013 09:46:25 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id SijzVuSnY-Bz; Tue, 25 Jun 2013 09:46:06 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3F2DDF24070; Tue, 25 Jun 2013 09:46:24 -0400 (EDT)
Subject: Re: [IAB] RSOC Appointments
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <51C97AA1.1080603@gmail.com>
Date: Tue, 25 Jun 2013 09:46:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C04DF52F-6E79-4512-8467-867ADC1B03F1@vigilsec.com>
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com> <m261x291n5.wl%randy@psg.com> <988A872C-CCD7-4353-A85F-FBF200AD3A4B@netapp.com> <51C97AA1.1080603@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: 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: Tue, 25 Jun 2013 13:46:23 -0000

Arturo:

The original call for nominations did this in two ways.  First, it =
pointed to RFC 6635, which defines the role of the RSOC.  Second, it =
included a list of the top four items that the RSOC is focusing on right =
now.

> The current focus of the RSOC is on:
>=20
> 1) Overseeing and assisting the RSE in the process of determining how =
to
> best meet the requirements in draft-iab-rfcformatreq.
>=20
> 2) Working with the RSE and the IAB to develop policies n the creation =
of
> new RFC Series streams.
>=20
> 3) Periodic reviews of the RFSE performance.
>=20
> 4) Working with the RSE and the IETF Administrative Oversight =
Committee
> (IAOC) on the statements of work for contracts related to the RFC
> Production Center and RFC Publisher.


Russ


On 6/25/13 5:10 AM, Arturo Servin wrote:
>=20
>    I checked the call for nommitantios (Sent on april 24th 2013 on the
> ietf-announce) and it does not describe what should be the
> qualifications of the candidates. I think that this enough to alienate
> new people (as they may think that they are not good candidates for =
the
> position because of lack of experience in the IETF, not being an RFC
> author, etc.)
>=20
>    I would recommend that future announcement of kind of positions =
have
> a very clear profile of what it is expected from the candidates in =
IETF
> experience, general requirements, etc. In the end, it is like we were
> filling a job positions in an organization, the difference here is =
that
> we are not receiving a salary.


From arturo.servin@gmail.com  Tue Jun 25 06:51:55 2013
Return-Path: <arturo.servin@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 E155721F9A95 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 06:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.266
X-Spam-Level: 
X-Spam-Status: No, score=-3.266 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599]
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 tBBSI5wtJsrp for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 06:51:54 -0700 (PDT)
Received: from mail-bk0-x229.google.com (mail-bk0-x229.google.com [IPv6:2a00:1450:4008:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 1BEAB21F9808 for <ietf@ietf.org>; Tue, 25 Jun 2013 06:51:53 -0700 (PDT)
Received: by mail-bk0-f41.google.com with SMTP id jc3so4547467bkc.28 for <ietf@ietf.org>; Tue, 25 Jun 2013 06:51:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bjq/sRv9Pn7PR+q8hPM5VfYJQ1QAYKE7n2GQEZM+WTA=; b=PoaD0eAN+V77Cjtc9Q+ELVWAFuu+NzqOlRb5lByUjKhJ6uwJREz2HnRfLEFbBhg70H uyvHExZpOs8QHK4GSg/BWBAAGeyD1XjIiq+ozpMLwpdUfmC0P2HGoBT6nn25u86xJD82 wDimrxshXnjeJO8uZ4ex3xWuRlLhUhZ7Hg/Cz7mjipUydpijsZEfYbUSTftKRxXei9K2 nq7WeqDWBMmKwMi4dUjO6iQB+haIufXCnj0hq4v2ZwIAPIve1dsqzE1OPmbUt9p8DMI1 +oS4DaUJIEyrTENmFlvOqrz88v1yxUckDOk578Whcu8+994Eeq7nqgJjruRDxKCzmEyF BT7Q==
X-Received: by 10.204.77.72 with SMTP id f8mr63167bkk.28.1372168313121; Tue, 25 Jun 2013 06:51:53 -0700 (PDT)
Received: from [192.168.0.5] ([90.214.33.42]) by mx.google.com with ESMTPSA id eu16sm6276378bkc.0.2013.06.25.06.51.52 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Jun 2013 06:51:52 -0700 (PDT)
Message-ID: <51C9A077.8030202@gmail.com>
Date: Tue, 25 Jun 2013 14:51:51 +0100
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IAB] RSOC Appointments
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com> <m261x291n5.wl%randy@psg.com> <988A872C-CCD7-4353-A85F-FBF200AD3A4B@netapp.com> <51C97AA1.1080603@gmail.com> <C04DF52F-6E79-4512-8467-867ADC1B03F1@vigilsec.com>
In-Reply-To: <C04DF52F-6E79-4512-8467-867ADC1B03F1@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Tue, 25 Jun 2013 13:51:55 -0000

Russ,

    Thanks.

    I see it now.

    Nevertheless for the untrained eye as mine (and that only scans the
important parts of some emails), it would be good to add something like:

"Requirements for the position are stated in RFC 6635".

    And probably it won't hurt to add at least a summary of those "job"
requirements.

Cheers,
as

   
On 6/25/13 2:46 PM, Russ Housley wrote:
> Arturo:
>
> The original call for nominations did this in two ways.  First, it pointed to RFC 6635, which defines the role of the RSOC.  Second, it included a list of the top four items that the RSOC is focusing on right now.
>
>> The current focus of the RSOC is on:
>>
>> 1) Overseeing and assisting the RSE in the process of determining how to
>> best meet the requirements in draft-iab-rfcformatreq.
>>
>> 2) Working with the RSE and the IAB to develop policies n the creation of
>> new RFC Series streams.
>>
>> 3) Periodic reviews of the RFSE performance.
>>
>> 4) Working with the RSE and the IETF Administrative Oversight Committee
>> (IAOC) on the statements of work for contracts related to the RFC
>> Production Center and RFC Publisher.
>
> Russ
>
>
> On 6/25/13 5:10 AM, Arturo Servin wrote:
>>    I checked the call for nommitantios (Sent on april 24th 2013 on the
>> ietf-announce) and it does not describe what should be the
>> qualifications of the candidates. I think that this enough to alienate
>> new people (as they may think that they are not good candidates for the
>> position because of lack of experience in the IETF, not being an RFC
>> author, etc.)
>>
>>    I would recommend that future announcement of kind of positions have
>> a very clear profile of what it is expected from the candidates in IETF
>> experience, general requirements, etc. In the end, it is like we were
>> filling a job positions in an organization, the difference here is that
>> we are not receiving a salary.


From scott.brim@gmail.com  Tue Jun 25 07:08:45 2013
Return-Path: <scott.brim@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 8D5EB21E80BE for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 07:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 GGUUwa58W2Ib for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 07:08:45 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id DBFFE21E80BF for <ietf@ietf.org>; Tue, 25 Jun 2013 07:08:44 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id k7so13390989oag.37 for <ietf@ietf.org>; Tue, 25 Jun 2013 07:08:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=u8DUikOBCKQokr8spYxtY01NkuBG/FvjeGCnDPJnXXM=; b=sYxgy7KKYCKXwKSFqM+rRMCLo8FSsfNtcJNZOAcNn/CFtgptTuQ8KwqlBeDw+lF9u9 vuPJsZEHFVV8Pb/WYLoJ46bbcKo4Vo0/3/lZbXUyTtH5DqkV27WnrT8HL/o5+kyrFhTn Nwv+22ClklGV6bd6GtIEPsh4xTQGtJQfYDQUE5EjS5Nqghp3CzQOnM/YRN+wi+8D/y2C vR/CP/3NPcOzl42VIIFbxbH/K1w1CK9FApTsdd3rExjtZSOzzoON0ew2i44PrnR70vt5 UKK6HwzKveMpKL3o4pwYZ3zxSccsMDdS4jpfp1Mh2c+iQSJmOqEuicBs4/vgEqh7Jr2r NNIQ==
X-Received: by 10.60.174.111 with SMTP id br15mr12883508oec.130.1372169324452;  Tue, 25 Jun 2013 07:08:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.97.37 with HTTP; Tue, 25 Jun 2013 07:08:24 -0700 (PDT)
In-Reply-To: <CAMm+Lwg3re0Ok39b5COoO8M5pTW-eNT5ifpkrSuqNdSEGkveHg@mail.gmail.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com> <CAKHUCzxtiXOgXwYmn+viq88r--Rs2vHk-0v85y4TyJzzQhDBtg@mail.gmail.com> <CAMm+Lwg3re0Ok39b5COoO8M5pTW-eNT5ifpkrSuqNdSEGkveHg@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 25 Jun 2013 10:08:24 -0400
Message-ID: <CAPv4CP_NDvRPSFa-aZKBVykWg5vgRL6-5zkv0NNLORSqsgDQHw@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion 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: Tue, 25 Jun 2013 14:08:45 -0000

On Tue, Jun 25, 2013 at 8:52 AM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> I DO NOT agree that 2119 is the only source of consequence here.

Sorry.  RFCs are not written in English, they are written in RFCish, a
language based in English but with modifications (specified in RFCs).
2119 overrides anything you might think you know about what words
mean.

From dave@cridland.net  Tue Jun 25 07:24:19 2013
Return-Path: <dave@cridland.net>
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 B74B921F9E98 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 07:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.963
X-Spam-Level: 
X-Spam-Status: No, score=-1.963 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 0om2nMwBrUw6 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 07:24:19 -0700 (PDT)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 9B96711E811B for <ietf@ietf.org>; Tue, 25 Jun 2013 07:24:18 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id e11so9239913wgh.18 for <ietf@ietf.org>; Tue, 25 Jun 2013 07:24:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=content-type:mime-version:in-reply-to:references:subject:x-mailer :date:message-id:from:to:cc; bh=CsTmsLeWp24hohcXWaGEumVh7GjYAfR27cM4sHnPGcE=; b=OQp39VcURDZMKyxMjPgPM1rk7pYTJZAwznZo0MvnLSLx/DQl50150xywy9kIdrN6zy A8NG+58uWBGq0Er3LVDdTSxP9ZLj/fRj70Z6s0Cpefd98e7lASOTN5w3yl7MILhzhD9W eujjULLtxWIlE/Ehgy3959wZzh0jXj1FqUNP4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:in-reply-to:references:subject:x-mailer :date:message-id:from:to:cc:x-gm-message-state; bh=CsTmsLeWp24hohcXWaGEumVh7GjYAfR27cM4sHnPGcE=; b=BFg9luAOwCtox4X563SYIfhSe4ZIyA+1t9Rwsz4LstYx+6BfUaa/sQ9eDIVRQqGFcB IuYQ1xHXKR0hHLUT6+hoSYiXE1sSGgPlzjwEvB2Ga7r0cKs9pUihmzeIHrk7Uj2YmHTf ixi17Op8N/3lW8EyhIRyHqvcji4DSRE8UI4S9ZAT45s7ozAsvvXwNpw0WsjYK2QBAWDd fa2yoOgW4MEtiQSp1Cwk1moRrJWI/ScpSVIxlM6x8vQWlm6go5V73C17GNUIwt2sL5XO 6JxbMfSBuw9LhcHZCAJHStGdnzOpjYJv7OkfFX2mJdf2PyHorWQB66wvP89ESi2Qwuvw zS6g==
X-Received: by 10.180.11.194 with SMTP id s2mr9381235wib.7.1372170255547; Tue, 25 Jun 2013 07:24:15 -0700 (PDT)
Received: from [10.42.211.62] (peirce.dave.cridland.net. [217.155.137.61]) by mx.google.com with ESMTPSA id fd3sm4413047wic.10.2013.06.25.07.24.13 for <multiple recipients> (version=TLSv1.1 cipher=RC4-SHA bits=128/128); Tue, 25 Jun 2013 07:24:14 -0700 (PDT)
Content-Type: multipart/alternative; boundary="===============1968145806=="
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwg3re0Ok39b5COoO8M5pTW-eNT5ifpkrSuqNdSEGkveHg@mail.gmail.com>
References: <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <CAKHUCzxtiXOgXwYmn+viq88r--Rs2vHk-0v85y4TyJzzQhDBtg@mail.gmail.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CAMm+Lwg3re0Ok39b5COoO8M5pTW-eNT5ifpkrSuqNdSEGkveHg@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com>
Subject: Re:  SHOULD and RECOMMENDED
X-Mailer: Inky (TM) v1.0.51C8.C025 ("Epoch")
Date: Tue, 25 Jun 2013 14:24:13 -0000
Message-Id: <D6OO59PmqHXt-2EiDExefKb0U9ItY8c952s3NkA87gdwcGAX8@smtp.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: "Phillip Hallam-Baker" <hallam@gmail.com>
X-Gm-Message-State: ALoCoQks7MQtuT8WQ3rHzUKCGj54H81d0t7ofIvL2h9lnsARyZuNZ+tC3Fpwj3WjE/ZP/uLOFakd
Cc: IETF-Discussion 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: Tue, 25 Jun 2013 14:24:19 -0000

--===============1968145806==
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Phillip Hallam-Baker wrote:


I DO NOT agree that 2119 is the only source of consequence here.

If a document explicitly states that the term "RECOMMENDED" is to be
interpreted as in RFC 2119, then that really is the only
interpretation, and RFC 2119 does then become the only source of
consequence. This is beyond personal opinions.





Perhaps if I showed Dave Cridland an article on netiquete he could try
to be less patronizing. Unlike some here I do not regard the RFC
series as having divine inspiration.



I'm not claiming it's the traditional meaning of the term, just that
RFCs do tend to be explicit in what they mean by it..

I've no idea how I'm being patronizing, but I'm certainly not claiming
any kind of divine inspiration for the RFCs. I'm merely suggesting
that if a document says "This word means X", we should accept that and
move on.







RECOMMENDED is a very useful term to have. Particularly when writing
specs for middleware.

That's an interesting debate to have, but it has no bearing on what
the term means in the context of documents citing RFC 2119.

For what it's worth, I entirely agree that a term with force somewhere
between MAY and SHOULD would be very useful in some cases, but in
general we can work around this, such as saying "implementations are
encouraged to use channel binding", or some such.







The IETF document describing use of the term is WRONG it needs to be
corrected. Any corrections would only apply to new specs that
reference the new RFC.



It's not wrong, it clearly gives a meaning to the term. That meaning
is not in line with the implications it might have if used in spoken
English, certainly, but it's clearly stated, and used in that sense as
far as I can tell.

Dave.


Sent with [inky: <http://inky.com?kme=3Dsignature>]


--===============1968145806==
Content-Type: text/html; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<body><div class=3D"inlined-message" id=3D"message-coda" name=3D"message-co=
da">
	<span class=3D"message-attribution">Phillip Hallam-Baker wrote:</span>
	<div class=3D"quoted" style=3D"border-left: 1px solid black; margin: 0pt 0=
pt 0pt 0.25em; padding-left: 1em; padding-top: 1ex;">
		<div class=3D"sanitized-message">
			<div dir=3D"ltr">
				I DO NOT agree that 2119 is the only source of consequence here.</div>
		</div>
	</div>
</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inline-text">
	If a document explicitly states that the term "RECOMMENDED" is to be inter=
preted as in RFC 2119, then that really is the only interpretation, and RFC=
 2119 does then become the only source of consequence. This is beyond perso=
nal opinions.</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inlined-message" name=3D"message-coda">
	<div class=3D"quoted" style=3D"border-left: 1px solid black; margin: 0pt 0=
pt 0pt 0.25em; padding-left: 1em; padding-top: 1ex;">
		<div class=3D"sanitized-message">
			<div dir=3D"ltr">
				<div>
					Perhaps if I showed Dave Cridland an article on netiquete he could try=
 to be less patronizing. Unlike some here I do not regard the RFC series as=
 having divine inspiration.</div>
				<div>
					<p style=3D"margin: 0px; padding: 0px; ">
						=A0</p>
				</div>
			</div>
		</div>
	</div>
</div>
<p class=3D"inline-text" style=3D"margin: 0px; padding: 0px; ">
	=A0</p>
<p class=3D"inline-text" style=3D"margin: 0px; padding: 0px; ">
	I'm not claiming it's the traditional meaning of the term, just that RFCs =
do tend to be explicit in what they mean by it..</p>
<p class=3D"inline-text" style=3D"margin: 0px; padding: 0px; ">
	=A0</p>
<p class=3D"inline-text" style=3D"margin: 0px; padding: 0px; ">
	I've no idea how I'm being patronizing, but I'm certainly not claiming any=
 kind of divine inspiration for the RFCs. I'm merely suggesting that if a d=
ocument says "This word means X", we should accept that and move on.</p>
<p class=3D"inline-text" style=3D"margin: 0px; padding: 0px; ">
	=A0</p>
<div class=3D"inlined-message" name=3D"message-coda">
	<div class=3D"quoted" style=3D"border-left: 1px solid black; margin: 0pt 0=
pt 0pt 0.25em; padding-left: 1em; padding-top: 1ex;">
		<div class=3D"sanitized-message">
			<div dir=3D"ltr">
				<div>
					<div>
						=A0</div>
					<div>
						RECOMMENDED is a very useful term to have. Particularly when writing =
specs for middleware.</div>
				</div>
			</div>
		</div>
	</div>
</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inline-text">
	That's an interesting debate to have, but it has no bearing on what the te=
rm means in the context of documents citing RFC 2119.</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inline-text">
	For what it's worth, I entirely agree that a term with force somewhere bet=
ween MAY and SHOULD would be very useful in some cases, but in general we c=
an work around this, such as saying "implementations are encouraged to use =
channel binding", or some such.</div>
<div class=3D"inline-text">
	=A0</div>
<div class=3D"inlined-message" name=3D"message-coda">
	<div class=3D"quoted" style=3D"border-left: 1px solid black; margin: 0pt 0=
pt 0pt 0.25em; padding-left: 1em; padding-top: 1ex;">
		<div class=3D"sanitized-message">
			<div dir=3D"ltr">
				<div>
					=A0</div>
				<div>
					=A0</div>
				<div>
					The IETF document describing use of the term is WRONG it needs to be c=
orrected. Any corrections would only apply to new specs that reference the =
new RFC.</div>
				<div>
					=A0</div>
			</div>
		</div>
	</div>
</div>
<div class=3D"message-gap">
	<p style=3D"margin: 0px; padding: 0px; ">
		=A0</p>
	<p style=3D"margin: 0px; padding: 0px; ">
		It's not wrong, it clearly gives a meaning to the term. That meaning is n=
ot in line with the implications it might have if used in spoken English, c=
ertainly, but it's clearly stated, and used in that sense as far as I can t=
ell.</p>
	<p style=3D"margin: 0px; padding: 0px; ">
		=A0</p>
	<p style=3D"margin: 0px; padding: 0px; ">
		Dave.</p>
	<p style=3D"margin: 0px; padding: 0px; ">
		=A0</p>
</div>
<div class=3D"message-signature" id=3D"signature_1372169402509-1760395130" =
name=3D"signature_1372169402509-1760395130">
	<div>
		<span style=3D"font-family: Arial, Helvetica Neue, Helvetica, sans-serif;=
 color: rgb(153, 153, 153);">Sent with=A0<a href=3D"http://inky.com?kme=3Ds=
ignature"><span style=3D"color: rgb(51, 150, 192); text-decoration: underli=
ne;">inky</span></a></span></div>
</div>
<p style=3D"margin: 0px; padding: 0px; ">
	=A0</p>
</body>
--===============1968145806==--

From john-ietf@jck.com  Tue Jun 25 07:42:58 2013
Return-Path: <john-ietf@jck.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 30A3221F9D6C; Tue, 25 Jun 2013 07:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level: 
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 YSxhxBqSQFEs; Tue, 25 Jun 2013 07:42:52 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E13BD21F9D71; Tue, 25 Jun 2013 07:42:51 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UrUSA-0007gU-GI; Tue, 25 Jun 2013 10:42:42 -0400
Date: Tue, 25 Jun 2013 10:42:37 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Eggert, Lars" <lars@netapp.com>, Randy Bush <randy@psg.com>, Peter Saint-Andre <stpeter@stpeter.im>, Arturo Servin <arturo.servin@gmail.com>
Subject: Re: [IAB] RSOC Appointments
Message-ID: <3249B3EDB3E4AEB92BF9CC26@JcK-HP8200.jck.com>
In-Reply-To: <988A872C-CCD7-4353-A85F-FBF200AD3A4B@netapp.com>
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com> <m261x291n5.wl%randy@psg.com> <988A872C-CCD7-4353-A85F-FBF200AD3A4B@netapp.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IAB <iab@iab.org>, ietf 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: Tue, 25 Jun 2013 14:42:58 -0000

--On Tuesday, June 25, 2013 07:25 +0000 "Eggert, Lars"
<lars@netapp.com> wrote:

> On Jun 25, 2013, at 7:53, Randy Bush <randy@psg.com> wrote:
>>> Congratulations, gentlemen.
>> 
>> and they are all male
> 
> Well, all the volunteers were male, so no real surprise here.
> 
> (And yes, I wish the volunteer pool had been more diverse. But
> it wasn't.)

I haven't looked at the volunteer pool, but all of the new
appointees are also North American or European.  

Lars,

As an outgoing member of the RSOC, it would be inappropriate for
me to comment here on the new membership, but I think your
comment summarizes a critical issue in the ongoing diversity
discussion.  Personally, I think there are lessons to be learned
for the future... and I wonder how many more times the community
needs to discuss them before they are considered normal
practice.  In particular...

Arturo and Peter,

There is at least an outline of a job description.  It appears
in Section 3.1.1 of RFC 6635 and includes: 

	"The IAB will designate the membership of the RSOC with
	the following goals: preserving effective stability;
	keeping it small enough to be effective, and keeping it
	large enough to provide general Internet community
	expertise, specific IETF expertise, publication
	expertise, and stream expertise.  Members [...] are
	expected to bring a balance between  short- and
	long-term perspectives."

One can sensibly argue that the above description, possibly
accompanied by comments from the IAB and/or current RSOC
members, should have been in the announcement but not that it
was somehow missing or secret.   My personal view is that more
explicitness about the description would have made little or no
difference in the applicant pool as long as the announcement
itself was made exclusively within IETF community mailing lists.

More broadly, anyone in the community with real interest in the
topics that the RSOC addresses would presumably have followed at
least some of the contents of RFC 6635, 4844, and related
documents; the rfc-interest list; a few recent BOFs or their
minutes; RFC Editor reports in plenaries; etc.  While I have no
idea what the IAB did, if I were still on the IAB I certainly
would have tried to determine what an applicant already knew
about the work of the RSOC and the RFC Series and dropped anyone
from within the community who wasn't moderately well-informed
from consideration.  It would be easy to deduce From those
sources that the RFC Series (and hence the RSOC) face major
policy and strategic challenges with authors whose technical
English writing skills are not up to a professional standard for
quality, with internationalization of the documents, with
preserving the properties of the RFC Series as an archival
collection, with document production and the relationship
between generic and format markup, with increased credibility of
the Series for academic publication and reference, and so on.
Presumably the RSOC, as a group, should have sufficient
expertise to be able to oversee investigations and decisions in
those areas although RFC 6635 leaves it up to the IAB to
determine how important that expertise is relative to other
considerations.

However, the more general issue is that the description above
calls for a wide range of expertise, not all of which need to
come from the same person or subset of people.  While recruiting
candidate IESG members from outside the IETF community would be,
IMO, pretty silly, that constraint doesn't apply to the RSOC
(give the description above and actual experience).  It would
have been, at least IMO, reasonable for the IAB to try to
recruit potential RSOC members from broader communities,
communities in which some of that expertise would be more
broadly available than it is among "normal" IETF participants or
the subset of us that carefully track IETF-announce or are
active on this list.   As people have commented in other
contexts, if one cares, in practice, about diversity then part
of the solution to issues of underrepresentation is broadening
the applicant pool to include additional populations.

Now, the IAB, in its wisdom, chose to not engage in such a
broader recruiting effort.   I have no idea whether they
considered and discussed that option.  

If the community thinks that diversity is really important
enough, then the various appointing bodies (including the
Nomcom) should to told to consider --and maybe even report back
on-- whether particular positions justify a broader search
because posting announcements to IETF lists may not inform the
best range of potential candidates.  If the community believes
that diversity is important and that members of appointing
bodies aren't taking it seriously enough, that should be made
clear to the Nomcom (remembering that the Nomcom has the right
to recruit rather than waiting passively for nominations and the
right --and maybe the obligation-- to inquire, when considering
incumbents, about why particular decisions were made and what
positions individuals took on them). 

In the case of bodies like the RSOC, if the community believes
that the body is important (I do, but I'm biased) and that
effectiveness is likely to be significantly diminished by lack
of diversity in gender, expertise, and/or geography (I'm not
completely convinced, but YMMD), remember that 6635 gives the
IAB the power to increase the RSOC's size (or otherwise change
its composition) at any time, balancing "small enough to be
effective" against other perceived needs.    I presume the IAB
would listen to community input on that sort of subject.  If
they would not, the problems run much deeper than appointments
to the RSOC.

Or we can keep whining each time appointments are made that
don't include a sufficient number of women, residents above the
Arctic Circle or below the Antarctic one, or other groups that
are perceived as underrepresented.  The problem with whining (or
wishing that things were different), no matter how
well-intentioned and justified, is that it doesn't lead directly
to changes that are actionable and for which the members of the
appointing bodies can be held accountable.

best,
   john






From sm@resistor.net  Tue Jun 25 07:44:56 2013
Return-Path: <sm@resistor.net>
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 B32FA21F9E21 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 07:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 aPOwRl2qlC3z for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 07:44:55 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DBBCB21F9E07 for <ietf@ietf.org>; Tue, 25 Jun 2013 07:44:55 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5PEijBM020660; Tue, 25 Jun 2013 07:44:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372171490; bh=iz8PbZ2NJqYtCkpWQ3EwUKMOuzqGPRiBZ/RmWk4wbMM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=E5i+Sm9b4Ol28NNZwSYXrlPhU7YxEjv6cNIFsSKb3Jp5546WLQp4nVHP7/s+SKwzE m4TL064gDVIqLeqaiBjn6MbqTdzblI3/R+abdvzteB9VrcGIBX706zlCbc/oZveRZr ev+VixEhg2ae63hPidsHExP+Wj39oswecPCUKPQM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1372171490; i=@resistor.net; bh=iz8PbZ2NJqYtCkpWQ3EwUKMOuzqGPRiBZ/RmWk4wbMM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PDgvvgcOTwHfDYWYYgAEKD+0x5I/kazsL8JdKI8qkMWBDUERdwOk/Yd7405f070xh Mq7JEOdOUAaz7FenSmau74b4WHB3WNktkYFJ6a7Wj2vvOOlnb7n7bUUDjRN0isXOYy PD4txp3B/T/WV/y57g8SmadNNeUFIQ0lU52sxhtE=
Message-Id: <6.2.5.6.2.20130625065752.0dc68310@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 25 Jun 2013 07:42:24 -0700
To: Russ Housley <housley@vigilsec.com>
From: SM <sm@resistor.net>
Subject: Re: [IAB] RSOC Appointments
In-Reply-To: <C04DF52F-6E79-4512-8467-867ADC1B03F1@vigilsec.com>
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com> <m261x291n5.wl%randy@psg.com> <988A872C-CCD7-4353-A85F-FBF200AD3A4B@netapp.com> <51C97AA1.1080603@gmail.com> <C04DF52F-6E79-4512-8467-867ADC1B03F1@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Arturo Servin <arturo.servin@gmail.com>, 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: Tue, 25 Jun 2013 14:44:56 -0000

Hola Russ,
At 06:46 25-06-2013, Russ Housley wrote:
>The original call for nominations did this in two ways.  First, it 
>pointed to RFC 6635, which defines the role of the RSOC.  Second, it 
>included a list of the top four items that the RSOC is focusing on right now.

What Mr Servin is trying to understand is how can people who are not 
part of the "good ol' boys network" (see 
http://www.ietf.org/mail-archive/web/diversity/current/msg00018.html 
) know the desirable experience and general requirements to have a 
fair chance when they apply for the job.

If the suggestion is that people read RFC 6635 I don't think that it 
is not good enough.  I understand that the IAB may be reluctant [1] 
to talk to the Internet Community about all this.

Regards,
-sm

1. http://www.youtube.com/watch?v=lhmjnYKlVnM 


From doug@ewellic.org  Tue Jun 25 08:52:26 2013
Return-Path: <doug@ewellic.org>
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 20D2C11E8104 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 08:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
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 awquGTz-7vNt for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 08:52:10 -0700 (PDT)
Received: from p3plwbeout03-02.prod.phx3.secureserver.net (p3plsmtp03-02-2.prod.phx3.secureserver.net [72.167.218.214]) by ietfa.amsl.com (Postfix) with ESMTP id 87C3B11E810F for <ietf@ietf.org>; Tue, 25 Jun 2013 08:51:59 -0700 (PDT)
Received: from localhost ([72.167.218.244]) by p3plwbeout03-02.prod.phx3.secureserver.net with bizsmtp id sfrv1l0025GyNsw01frvGs; Tue, 25 Jun 2013 08:51:55 -0700
X-SID: sfrv1l0025GyNsw01
Received: (qmail 5266 invoked by uid 99); 25 Jun 2013 15:51:55 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.190
User-Agent: Workspace Webmail 5.6.39
Message-Id: <20130625085154.665a7a7059d7ee80bb4d670165c8327d.eedfe20d31.wbe@email03.secureserver.net>
From: "Doug Ewell" <doug@ewellic.org>
To: ietf@ietf.org
Subject: Re: SHOULD and RECOMMENDED
Date: Tue, 25 Jun 2013 08:51:54 -0700
Mime-Version: 1.0
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: Tue, 25 Jun 2013 15:52:27 -0000

Scott Brim <scott dot brim at gmail dot com> wrote:=0A=0A> 2119 overrides a=
nything you might think you know about what words=0A> mean.=0A=0Aand Dave C=
ridland <dave at cridland dot net> wrote:=0A=0A> If a document explicitly s=
tates that the term "RECOMMENDED" is to=0A> be interpreted as in RFC 2119, =
then that really is the only=0A> interpretation, and RFC 2119 does then bec=
ome the only source of=0A> consequence. This is beyond personal opinions.=
=0A=0ADocuments that intend these magic words to have their RFC 2119 meanin=
gs=0Ainclude boilerplate text:=0A=0A"The key words 'MUST', 'MUST NOT', 'REQ=
UIRED', 'SHALL', 'SHALL NOT',=0A'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY=
', and 'OPTIONAL' in this=0Adocument are to be interpreted as described in =
RFC 2119."=0A=0AIf a document wants to impart different meaning to one or m=
ore of the=0Awords, wouldn't a simple list of the exceptions, immediately f=
ollowing=0Athe boilerplate, solve the problem?=0A=0A--=0ADoug Ewell | Thorn=
ton, CO, USA=0Ahttp://ewellic.org | @DougEwell =C2=AD=0A

From randy@psg.com  Mon Jun 24 22:53:58 2013
Return-Path: <randy@psg.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 9BFAD11E810C; Mon, 24 Jun 2013 22:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599]
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 9O2l3YZKygMv; Mon, 24 Jun 2013 22:53:58 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 49FE011E80CC; Mon, 24 Jun 2013 22:53:58 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UrMCO-0009c7-Rt; Tue, 25 Jun 2013 05:53:52 +0000
Date: Tue, 25 Jun 2013 14:53:50 +0900
Message-ID: <m261x291n5.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: RSOC Appointments
In-Reply-To: <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com>
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Tue, 25 Jun 2013 09:23:10 -0700
Cc: ietf list <ietf@ietf.org>, Nevil Brownlee <rfc-ise@rfc-editor.org>, Bob Hinden <bob.hinden@gmail.com>, IAB <iab@iab.org>, "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Bernard Aboba <bernard.aboba@gmail.com>
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: Tue, 25 Jun 2013 05:53:58 -0000

> Congratulations, gentlemen.

and they are all male

From jdrake@juniper.net  Tue Jun 25 09:32:09 2013
Return-Path: <jdrake@juniper.net>
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 223E521F9C1E for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 09:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.825
X-Spam-Level: 
X-Spam-Status: No, score=0.825 tagged_above=-999 required=5 tests=[AWL=-1.500,  RCVD_IN_DNSWL_LOW=-1, UNRESOLVED_TEMPLATE=3.325]
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 J2n-iKokABMi for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 09:32:02 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe003.messaging.microsoft.com [216.32.180.186]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC1621F99DA for <ietf@ietf.org>; Tue, 25 Jun 2013 09:32:02 -0700 (PDT)
Received: from mail77-co1-R.bigfish.com (10.243.78.242) by CO1EHSOBE018.bigfish.com (10.243.66.81) with Microsoft SMTP Server id 14.1.225.23; Tue, 25 Jun 2013 16:32:01 +0000
Received: from mail77-co1 (localhost [127.0.0.1])	by mail77-co1-R.bigfish.com (Postfix) with ESMTP id 6D88F2A0436	for <ietf@ietf.org>; Tue, 25 Jun 2013 16:32:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.53; KIP:(null); UIP:(null); IPV:NLI; H:P-EMHUB02-HQ.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: PS-23(z569dhz9371I542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL8275dhz2fh2a8h683h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1155h)
Received-SPF: pass (mail77-co1: domain of juniper.net designates 66.129.224.53 as permitted sender) client-ip=66.129.224.53; envelope-from=jdrake@juniper.net; helo=P-EMHUB02-HQ.jnpr.net ; -HQ.jnpr.net ; 
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT005.namprd05.prod.outlook.com; R:internal; EFV:INT
Received: from mail77-co1 (localhost.localdomain [127.0.0.1]) by mail77-co1 (MessageSwitch) id 1372177918969425_3886; Tue, 25 Jun 2013 16:31:58 +0000 (UTC)
Received: from CO1EHSMHS013.bigfish.com (unknown [10.243.78.242])	by mail77-co1.bigfish.com (Postfix) with ESMTP id EAC19B800B9	for <ietf@ietf.org>; Tue, 25 Jun 2013 16:31:58 +0000 (UTC)
Received: from P-EMHUB02-HQ.jnpr.net (66.129.224.53) by CO1EHSMHS013.bigfish.com (10.243.66.23) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 25 Jun 2013 16:31:55 +0000
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 25 Jun 2013 09:31:53 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Tue, 25 Jun 2013 09:31:53 -0700
Received: from va3outboundpool.messaging.microsoft.com (216.32.180.31) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 25 Jun 2013 09:36:10 -0700
Received: from mail184-va3-R.bigfish.com (10.7.14.240) by VA3EHSOBE013.bigfish.com (10.7.40.63) with Microsoft SMTP Server id 14.1.225.23; Tue, 25 Jun 2013 16:31:51 +0000
Received: from mail184-va3 (localhost [127.0.0.1])	by mail184-va3-R.bigfish.com (Postfix) with ESMTP id A808A20BB3	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Tue, 25 Jun 2013 16:31:51 +0000 (UTC)
Received: from mail184-va3 (localhost.localdomain [127.0.0.1]) by mail184-va3 (MessageSwitch) id 1372177908792790_4899; Tue, 25 Jun 2013 16:31:48 +0000 (UTC)
Received: from VA3EHSMHS010.bigfish.com (unknown [10.7.14.240])	by mail184-va3.bigfish.com (Postfix) with ESMTP id AE987240113; Tue, 25 Jun 2013 16:31:48 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS010.bigfish.com (10.7.99.20) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 25 Jun 2013 16:31:46 +0000
Received: from BL2PRD0510MB349.namprd05.prod.outlook.com ([169.254.1.110]) by BL2PRD0510HT005.namprd05.prod.outlook.com ([10.255.100.40]) with mapi id 14.16.0324.000; Tue, 25 Jun 2013 16:31:46 +0000
From: John E Drake <jdrake@juniper.net>
To: Randy Bush <randy@psg.com>, "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: RSOC Appointments
Thread-Topic: RSOC Appointments
Thread-Index: AQHOcTv2BERZXePVVk2uAHAOTSvQ2JlF5PIAgAAJUQCAALH/UA==
Date: Tue, 25 Jun 2013 16:31:45 +0000
Message-ID: <0182DEA5604B3A44A2EE61F3EE3ED69E1D53F973@BL2PRD0510MB349.namprd05.prod.outlook.com>
References: <6E5C520D-F79C-45CC-AC74-6E4F67833BE8@iab.org> <8C48B86A895913448548E6D15DA7553B924D4C@xmb-rcd-x09.cisco.com> <m261x291n5.wl%randy@psg.com>
In-Reply-To: <m261x291n5.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.224.52]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%PSG.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%CISCO.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%RFC-EDITOR.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%GMAIL.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IAB.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%ISODE.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-OriginatorOrg: juniper.net
Cc: ietf list <ietf@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, IAB <iab@iab.org>, Nevil Brownlee <rfc-ise@rfc-editor.org>, Alexey Melnikov <alexey.melnikov@isode.com>, "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>, Bernard Aboba <bernard.aboba@gmail.com>
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: Tue, 25 Jun 2013 16:32:09 -0000

But they have different ages, IQs, and shoe sizes.

Yours Irrespectively,

John

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Randy Bush
> Sent: Monday, June 24, 2013 10:54 PM
> To: Fred Baker (fred)
> Cc: ietf list; Nevil Brownlee; Bob Hinden; IAB; Joe Hildebrand
> (jhildebr); Alexey Melnikov; Bernard Aboba
> Subject: Re: RSOC Appointments
>=20
> > Congratulations, gentlemen.
>=20
> and they are all male
>=20




From hsantos@isdg.net  Tue Jun 25 10:16:02 2013
Return-Path: <hsantos@isdg.net>
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 9482F21F9B10 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 10:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_72=0.6, USER_IN_WHITELIST=-100]
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 lC5Mog6gHjrn for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 10:15:54 -0700 (PDT)
Received: from groups.winserver.com (ntbbs.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id B2D6621F99C7 for <ietf@ietf.org>; Tue, 25 Jun 2013 10:15:53 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2892; t=1372180551; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=qnXSxw0 lyiU/qPZaqeymbiKEIg4=; b=RtDQTvpOpGr5WAyqw6TS0BdLYv814nYackHIoyo QatppQkrKmQ7P30loVJYzIfoybdvLQEKLaKSPo4awnslhPhFkTRPaNdOrLJJZ04w bSV7ooQ0K8DZ/QSWGnq6RdAzwp5EgsodvdNDqy4S5DaM7bTkqdtf2IuYRVV9AiTA 73us=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 25 Jun 2013 13:15:51 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2938091193.705.3452; Tue, 25 Jun 2013 13:15:51 -0400
Message-ID: <51C9CFA8.7080708@isdg.net>
Date: Tue, 25 Jun 2013 13:13:12 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com>
In-Reply-To: <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion 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: Tue, 25 Jun 2013 17:16:02 -0000

I want to know more what it translates to as a technical specification 
for CODING.   To me, it means this:

    o Authorization Lift Time
      [X] Send Notification
          Time to send: __4__ mins (default)


The problem as I experienced thus far is whether one MUST IMPLEMENT this 
protocol feature,in this case code for AUTH_LIFETIME and make it 
flexible with a default 4 mins timeout.

At the end of the day, this feature is not functionally described as a 
MUST protocol requirement, therefore as a product producer I have two 
design options:

   1) Don't implement, possible less feature than competitors.
      See if others implement it.

   2) Implement and make it optional as the UI shows above.

So I don't think its a really a language or native culture thing, its 
just poor functional/technical specification writing.  Of course, if one 
does not implement AUTH_LIFETIME and they later find out there are 
interoperability issues with other products in the market, then there is 
a "BUG" in the specification.  It may need to be fixed in a BIS as a 
MUST or maybe the products that failed when a peer did not support it, 
then its considered buggy because it read the above as a MUST.

I would like to see a focus to produce more protocol writing guidelines, 
outline examples and tips on how to best reduce the ambiguity.   I think 
the available RFC templates should include a new section:

    1.x Minimum Requirements

This should help writers focus on these type of issues for the multiple 
discipline readers out there.

--
HLS



On 6/24/2013 4:18 PM, Yoav Nir wrote:
>
> On Jun 24, 2013, at 10:52 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
>
>> On 6/24/13 1:47 PM, Michael Thornburgh wrote:
>>> my feeling and belief is that RFC 2119 only gives SHOULD and
>>> RECOMMENDED the same normative requirement level, but that it does
>>> not override or change the distinct meanings of these words in
>>> English.  sentences using each of these terms have different meanings
>>> in English, even when those sentences appear in RFCs.
>>
>> I expect that the subtle differences between these words are lost on
>> non-native speakers, and even most native speakers, of English. I'd be
>> genuinely curious to hear that you think the distinct meanings are.
>>
>
> "It is RECOMMENDED that implementations send the AUTH_LIFETIME notification at least 4 minutes before the SA is to be deleted, to facilitate the user entering credentials in time."
>
> "The implementation SHOULD send the AUTH_LIFETIME notification at least 4 minutes before the SA is to be deleted, to facilitate the user entering credentials in time."
>
> - What are the subtle differences in meaning between these two sentences?
>
> - Would an implementation written by a native speaker be any different depending on which of the above sentences was in the RFC?
>
> Yoav
>
>
>
>


From hsantos@isdg.net  Tue Jun 25 10:43:19 2013
Return-Path: <hsantos@isdg.net>
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 DBACC11E810F for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 10:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Ltsvpu3J1+Rm for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 10:43:14 -0700 (PDT)
Received: from pop3.winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9648A11E8114 for <ietf@ietf.org>; Tue, 25 Jun 2013 10:43:14 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1807; t=1372182185; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=lzJ8BYH jg/tDeg0gkt6daxXQhGY=; b=IuSuknAhd3QCzeSt5sSJq83T6y7eJoRs0kKyZbl 9q7JcnCwYrOPks0B4hm/ON1u2klrPF81LdsK5qSnuXryGPtXDoEgcui9ovkQSd6J GYhYlfNjpVnDDe7K7+bs8zwDrE4UodWF9y9HqI9Cj/iJNY1C0u39AtTYd2S8T/PK kM70=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 25 Jun 2013 13:43:05 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2939725522.705.3552; Tue, 25 Jun 2013 13:43:05 -0400
Message-ID: <51C9D60A.30007@isdg.net>
Date: Tue, 25 Jun 2013 13:40:26 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com> <CAKHUCzxtiXOgXwYmn+viq88r--Rs2vHk-0v85y4TyJzzQhDBtg@mail.gmail.com> <CAMm+Lwg3re0Ok39b5COoO8M5pTW-eNT5ifpkrSuqNdSEGkveHg@mail.gmail.com> <CAPv4CP_NDvRPSFa-aZKBVykWg5vgRL6-5zkv0NNLORSqsgDQHw@mail.gmail.com>
In-Reply-To: <CAPv4CP_NDvRPSFa-aZKBVykWg5vgRL6-5zkv0NNLORSqsgDQHw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion 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: Tue, 25 Jun 2013 17:43:20 -0000

Sounds like an never ending loop. 2119 is an RFC too and thus written in 
"RFCish" as well.

To me, it only matters in terms of implementation - should we waste time 
and money on implementing a SHOULD/RECOMMENDED feature?  Is it required 
to be coded?  Can it be delayed, for version 2.0?  Is it really needed, 
competitively? Will something break if we don't add it?

A good example was the DKIM and BIT8MIME issue.

BIT8MIME is an SMTP extension, therefore NOT REQUIRED by SMTP servers to 
support it.

It was determined the conversion and translation recommendations in 
BIT8MIME helps DKIM function better with less integrity errors, 
therefore there was an argument that all SMTP servers MUST support 
BIT8MIME if they claim to support DKIM. There was an attempt to mandate 
this in DKIM-BIS:

         SMTP Servers MUST support BIT8MIME.

This created an immediate, resounding uproar and negative response 
simply because not every SMTP server supported BIT8 MIME conversions. 
So it was changed back to:

         SMTP Servers SHOULD support BIT8MIME.

This shows the growing integration design and requirements pressure we 
are in, especially with newer protocols that depend on other OPTIONAL 
protocols in order to function correctly.  The same is true with other 
things like international conversions and translations, all currently 
optional for the most part.

--

On 6/25/2013 10:08 AM, Scott Brim wrote:
> On Tue, Jun 25, 2013 at 8:52 AM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>> I DO NOT agree that 2119 is the only source of consequence here.
>
> Sorry.  RFCs are not written in English, they are written in RFCish, a
> language based in English but with modifications (specified in RFCs).
> 2119 overrides anything you might think you know about what words
> mean.
>
>


From hallam@gmail.com  Tue Jun 25 10:58:16 2013
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 5B73911E8114 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 10:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 F91Ig6KCeZoo for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 10:58:15 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id DC4BA21F9AA9 for <ietf@ietf.org>; Tue, 25 Jun 2013 10:58:14 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id c11so9542168wgh.25 for <ietf@ietf.org>; Tue, 25 Jun 2013 10:58:13 -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=SQDIrcOrBQ1TzxE7tH+9t+6ZYZ6FEGVWKPlpydcb+Hk=; b=FLQGS6ubT7U/bk5VR2zge5NsbFZFTB6TOQz12wkNGPARiCBel/fF4zoeRj2DTCk1P7 w4hexkP15b7kGHtRfz7Mm8A+0RcnHR1VjXLnESpA8DS9KFsIbnv+WqPwYAhdxJbBOzvV uTEiLpU9RDIeUFIe30KjAOma6nW7PHHDYmePnCYB2vyFFzGh1TTWlsi+BQToCtXXnh55 1cQAmGPNgc9eBlNr5l+qTwzOQGQeQNGGEho48TPPyBFwf5UFCPsqjkXdiDe3+Q5UC22n cxnZAS/zQv1ZojM8xNjVyE687gYgo7aW6qqP380h8oYHZw8lRoUFs7Vgysl6sRXtT1mr A0sA==
MIME-Version: 1.0
X-Received: by 10.180.9.242 with SMTP id d18mr9897321wib.18.1372183093861; Tue, 25 Jun 2013 10:58:13 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Tue, 25 Jun 2013 10:58:13 -0700 (PDT)
In-Reply-To: <20130625085154.665a7a7059d7ee80bb4d670165c8327d.eedfe20d31.wbe@email03.secureserver.net>
References: <20130625085154.665a7a7059d7ee80bb4d670165c8327d.eedfe20d31.wbe@email03.secureserver.net>
Date: Tue, 25 Jun 2013 13:58:13 -0400
Message-ID: <CAMm+Lwg0L4T3F_SR-AYPFuF0nqFOE-nwBOiNc_fvsCo2JjPOwg@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Doug Ewell <doug@ewellic.org>
Content-Type: multipart/alternative; boundary=001a11c2228ce0662b04dffe45ee
Cc: 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: Tue, 25 Jun 2013 17:58:16 -0000

--001a11c2228ce0662b04dffe45ee
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 25, 2013 at 11:51 AM, Doug Ewell <doug@ewellic.org> wrote:

> Scott Brim <scott dot brim at gmail dot com> wrote:
>
> > 2119 overrides anything you might think you know about what words
> > mean.
>

No, 2119 PURPORTs to do that. It can try but it probably isn't going to
succeed.

The purpose of RFCs is to communicate ideas. In ordinary language there is
a clear distinction between RECOMMENDED and SHOULD. There is a useful
distinction between them in the context of writing a standard.

There are in fact standards bodies apart from the IETF. I have always
interpreted 2119 the same way I interpret the RFC describing ASCII: it is
the local source of a convention that has been established collectively by
the standards organizations as a whole.

RFCs make local definitions all the time, that does not mean that an RFC is
free to make any definitions it chooses. For example:

White: The color that is seen in the absence of any light source whatsoever.


The point I was making is that RECOMMENDED is used with a distinct meaning
by a large fraction of the standards community and the IETF could benefit
from the same approach.


> and Dave Cridland <dave at cridland dot net> wrote:
>
> > If a document explicitly states that the term "RECOMMENDED" is to
> > be interpreted as in RFC 2119, then that really is the only
> > interpretation, and RFC 2119 does then become the only source of
> > consequence. This is beyond personal opinions.
>
> Documents that intend these magic words to have their RFC 2119 meanings
> include boilerplate text:
>
> "The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT',
> 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in this
> document are to be interpreted as described in RFC 2119."
>
> If a document wants to impart different meaning to one or more of the
> words, wouldn't a simple list of the exceptions, immediately following
> the boilerplate, solve the problem?
>

Since SHOULD and RECOMMENDED are treated as being strictly equivalent, it
seems to me that a document that uses the terms with distinct meanings that
are compatible with the 2119 use should say so.

If an implementer finds language of the form "Implementations SHOULD
support AES-128" I expect them to implement unless they have a good reason
not to.

If on the other hand the language is "RECOMMENDED algorithms: AES-128", I
expect them to take that as a warning signal that the basis for the
author's recommendation may be dependent on assumptions that may not hold
for a particular circumstance (e.g. Moores law continues to 2050 and we all
have heptaflop computing engines in our shoe.)


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

--001a11c2228ce0662b04dffe45ee
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jun 25, 2013 at 11:51 AM, Doug Ewell <span dir=3D"ltr">&lt;=
<a href=3D"mailto:doug@ewellic.org" target=3D"_blank">doug@ewellic.org</a>&=
gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">Scott Brim &lt;scott dot b=
rim at gmail dot com&gt; wrote:<br>
<br>
&gt; 2119 overrides anything you might think you know about what words<br>
&gt; mean.<br></div></blockquote><div><br></div><div style>No, 2119 PURPORT=
s to do that. It can try but it probably isn&#39;t going to succeed.</div><=
div style><br></div><div style>The purpose of RFCs is to communicate ideas.=
 In ordinary language there is a clear distinction between RECOMMENDED and =
SHOULD. There is a useful distinction between them in the context of writin=
g a standard.</div>
<div style><br></div><div style>There are in fact standards bodies apart fr=
om the IETF. I have always interpreted 2119 the same way I interpret the RF=
C describing ASCII: it is the local source of a convention that has been es=
tablished collectively by the standards organizations as a whole.</div>
<div style><br></div><div style>RFCs make local definitions all the time, t=
hat does not mean that an RFC is free to make any definitions it chooses. F=
or example:</div><div style><br></div><div style>White: The color that is s=
een in the absence of any light source whatsoever.</div>
<div style><br></div><div style><br></div><div style>The point I was making=
 is that RECOMMENDED is used with a distinct meaning by a large fraction of=
 the standards community and the IETF could benefit from the same approach.=
</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">
</div><div class=3D"im">and Dave Cridland &lt;dave at cridland dot net&gt; =
wrote:<br>
<br>
&gt; If a document explicitly states that the term &quot;RECOMMENDED&quot; =
is to<br>
&gt; be interpreted as in RFC 2119, then that really is the only<br>
&gt; interpretation, and RFC 2119 does then become the only source of<br>
&gt; consequence. This is beyond personal opinions.<br>
<br>
</div>Documents that intend these magic words to have their RFC 2119 meanin=
gs<br>
include boilerplate text:<br>
<br>
&quot;The key words &#39;MUST&#39;, &#39;MUST NOT&#39;, &#39;REQUIRED&#39;,=
 &#39;SHALL&#39;, &#39;SHALL NOT&#39;,<br>
&#39;SHOULD&#39;, &#39;SHOULD NOT&#39;, &#39;RECOMMENDED&#39;, &#39;MAY&#39=
;, and &#39;OPTIONAL&#39; in this<br>
document are to be interpreted as described in RFC 2119.&quot;<br>
<br>
If a document wants to impart different meaning to one or more of the<br>
words, wouldn&#39;t a simple list of the exceptions, immediately following<=
br>
the boilerplate, solve the problem?<br></blockquote><div>=A0</div></div>Sin=
ce SHOULD and RECOMMENDED are treated as being strictly equivalent, it seem=
s to me that a document that uses the terms with distinct meanings that are=
 compatible with the 2119 use should say so.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra" style>If an=
 implementer finds language of the form &quot;Implementations SHOULD suppor=
t AES-128&quot; I expect them to implement unless they have a good reason n=
ot to.</div>
<div class=3D"gmail_extra" style><br></div><div class=3D"gmail_extra" style=
>If on the other hand the language is &quot;RECOMMENDED algorithms: AES-128=
&quot;, I expect them to take that as a warning signal that the basis for t=
he author&#39;s recommendation may be dependent on assumptions that may not=
 hold for a particular circumstance (e.g. Moores law continues to 2050 and =
we all have heptaflop computing engines in our shoe.)</div>
<div class=3D"gmail_extra"><br clear=3D"all"><div><br></div>-- <br>Website:=
 <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c2228ce0662b04dffe45ee--

From scott.brim@gmail.com  Tue Jun 25 11:13:36 2013
Return-Path: <scott.brim@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 04B8821E80B1 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 11:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 BSjJKBl1fyd1 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 11:13:35 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 885C811E812B for <ietf@ietf.org>; Tue, 25 Jun 2013 11:13:35 -0700 (PDT)
Received: by mail-ob0-f179.google.com with SMTP id xk17so12282566obc.24 for <ietf@ietf.org>; Tue, 25 Jun 2013 11:13:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1Q7O9H6aGCQQYfhK4mfTwcfIWRjLSgDJ8Nl48WKc+jI=; b=tpZGTCaVfotsmiuuL7KcVtlXj6F1yxwNyjpLppMpxOGfVaLoHQWaXioh9d2v63w4Ne AngqKH2+UoJ5B/QrOl2i5sZ+cwzB3H4cylxUlyjhL2pybBeD02k5Rpo1LSkL3trdHOiP DHAdnM/+lhNjjML+G8WydzPoLW3zB47+bSkZ/kRGvqfuCfgISCYgRwPCxVusX5a4z3wm mRvEWnLFlP+l9oUtuiKzF31IlRu4Mqk1uMg2oiX5wEvo5UxrarSo7IbXkcyZcH1Q11r3 LKRjG+MVADTsJTDlIo1GJNSvywgetzh5vmBywSe2e1J1wYhwx+tLeP6Sx+2ZXuc96pts tV1g==
X-Received: by 10.60.47.108 with SMTP id c12mr63838oen.126.1372184015079; Tue, 25 Jun 2013 11:13:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.97.37 with HTTP; Tue, 25 Jun 2013 11:13:15 -0700 (PDT)
In-Reply-To: <51C9D60A.30007@isdg.net>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com> <CAKHUCzxtiXOgXwYmn+viq88r--Rs2vHk-0v85y4TyJzzQhDBtg@mail.gmail.com> <CAMm+Lwg3re0Ok39b5COoO8M5pTW-eNT5ifpkrSuqNdSEGkveHg@mail.gmail.com> <CAPv4CP_NDvRPSFa-aZKBVykWg5vgRL6-5zkv0NNLORSqsgDQHw@mail.gmail.com> <51C9D60A.30007@isdg.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 25 Jun 2013 14:13:15 -0400
Message-ID: <CAPv4CP8iRG=QH29irfeW2saD-gkAxjxfYbRKn_b6VivfEyckiQ@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED
To: Hector Santos <hsantos@isdg.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion 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: Tue, 25 Jun 2013 18:13:36 -0000

On Tue, Jun 25, 2013 at 1:40 PM, Hector Santos <hsantos@isdg.net> wrote:
> To me, it only matters in terms of implementation - should we waste time and
> money on implementing a SHOULD/RECOMMENDED feature?  Is it required to be
> coded?  Can it be delayed, for version 2.0?  Is it really needed,

Every vendor goes through that decision process.  Some operators make
SHOULDs required in their RFIs.  The IETF WG decides on what it feels
is a necessary level of interoperability and leaves the rest up to
them.  The IETF is not going to make decisions for you about things it
thinks are optional.

> competitively? Will something break if we don't add it?

If leaving it out breaks something that's required, then it should be
a MUST and you should (not must) say so.

From mthornbu@adobe.com  Tue Jun 25 12:03:17 2013
Return-Path: <mthornbu@adobe.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 9322411E8127; Tue, 25 Jun 2013 12:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.19
X-Spam-Level: 
X-Spam-Status: No, score=-6.19 tagged_above=-999 required=5 tests=[AWL=0.409,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 TNx59Z5YSi6g; Tue, 25 Jun 2013 12:03:12 -0700 (PDT)
Received: from exprod6og125.obsmtp.com (exprod6og125.obsmtp.com [64.18.1.218]) by ietfa.amsl.com (Postfix) with ESMTP id A76FA21E80CE; Tue, 25 Jun 2013 12:02:49 -0700 (PDT)
Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob125.postini.com ([64.18.5.12]) with SMTP ID DSNKUcnpWPQKiupo8VqxN3hqCsTKJn7aDI5B@postini.com; Tue, 25 Jun 2013 12:02:55 PDT
Received: from inner-relay-2.corp.adobe.com ([153.32.1.52]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5PIxSD8010923; Tue, 25 Jun 2013 11:59:28 -0700 (PDT)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5PJ2mw7003179; Tue, 25 Jun 2013 12:02:48 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Tue, 25 Jun 2013 12:02:48 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: IETF-Discussion list <ietf@ietf.org>, "<gen-art@ietf.org> Team" <gen-art@ietf.org>, Ben Campbell <ben@nostrum.com>
Date: Tue, 25 Jun 2013 12:02:45 -0700
Subject: RE: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Topic: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Index: Ac5uCtbZuRIVMk7LS0i+/E+T5vgcMwAoFJaAAMp4DhA=
Message-ID: <D9D602D39A98E34D9C43E965BEC74398261AAC6F@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.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: Tue, 25 Jun 2013 19:03:17 -0000

hi Ben, all.

i have uploaded a new revision -08 of this draft that addresses comments ra=
ised during the IETF Last Call, which has now concluded.

Ben: i believe the "second-person" voice in this memo is used exclusively f=
or detailing algorithms that are to be performed. i believe the imperative =
"do it like this" voice is appropriate to that use, so i did not change it.=
  i also feel that the change in voice helps indicate that the implementati=
on is being addressed/instructed.

thank you for helping to improve the quality of this document.

-michael thornburgh


> From: Michael Thornburgh
> Sent: Friday, June 21, 2013 2:35 PM
>=20
> hi Ben. thanks for your review. comments/replies inline.
>=20
> > From: Ben Campbell [mailto:ben@nostrum.com]
> > Sent: Thursday, June 20, 2013 4:07 PM
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document:  draft-thornburgh-adobe-rtmfp-07
> > Reviewer: Ben Campbell
> > Review Date:  2013-06-20
> > IETF LC End Date: 2013-06-25
> >
> > Summary: This draft is almost ready for publication as an informational=
 RFC. However, I have some
> > concerns about the purpose and intended status of the document that I t=
hink should be considered
> prior
> > to publication.
> >
> >
> > Note: This is an informational draft that describes what I understand t=
o be an existing protocol as
> > implemented by commercial products. Therefore, this review does not att=
empt to evaluate the protocol
> > itself. I assume the protocol is what it is, and it is not up to the IE=
TF to agree or disagree with
> > it.
> >
> > *** Major issues:
> >
> > -- Why does this need to be published as an IETF stream RFC?  If I unde=
rstand correctly, this
> > documents an existing protocol as implemented by commercial products. I=
 agree with Martin's comment
> > that there is value in publishing this sort of thing, but I applaud the=
 Adobe and the author for
> > publishing it so other implementations can interoperate with their prod=
ucts. But that could have
> done
> > that in an independent stream document, or even in an Adobe published d=
ocument. (Perhaps even in a
> > prettier format ;-)  )  If we publish this as an IETF stream document, =
then I think it needs
> stronger
> > clarification that it is not an IETF consensus doc than just its inform=
ational status.
>=20
> this memo documents an existing network transport protocol that is widely=
 deployed and in widespread
> use in the Internet.  we felt that the IETF community (and in particular =
the participants in the
> Transport and Services Area) is the most appropriate community with which=
 to share this work: 1)
> members of this community have the necessary and relevant expertise not o=
nly to understand the
> protocol, but to make use of it potentially in new applications beyond Fl=
ash; 2) it is a transport
> protocol similar in many ways to TCP and SCTP and widely deployed and use=
d; 3) Adobe is interested in
> pursuing standardization of this protocol (with all that entails) if ther=
e is community interest, and
> the IETF is definitely the right place for that.
>=20
> we are very grateful that Martin Stiemerling chose to sponsor this docume=
nt.
>=20
> with regard to comments in later messages in this thread, i'd be happy to=
 include some (IESG-supplied)
> boilerplate in the document to clarify that it is not the product of an I=
ETF WG.  however, note that
> both the title and first sentence of the Introduction indicate that this =
is "Adobe's blahblahblah",
> consistent with other vendor-protocol RFCs and consistent with IESG edito=
rial insistence (as told to
> me by a former TSV AD).  see RFC 4332 and RFC 6802 for two examples of ve=
ndor-specific/supplied
> protocols.  see also the IESG note in RFC 4332 as an example disclaimer t=
hat could be added.
>=20
> > Along those lines:
> >
> > 	-- Is this document the authoritative specification? (I suspect not.) =
Who owns change control? I
> > assume that to be Adobe and/or the authors. What expectation do readers=
 of this draft have that it
> > represents the current version of RTMFP at any point in time?
>=20
> this memo is the authoritative specification for Adobe's RTMFP.  Adobe ow=
ns change control.  i believe
> the second and third paragraphs of the Introduction indicate to a reader =
that this draft represents
> RTMFP as deployed in the named Adobe products at the time of writing.
>=20
> > 	-- Under what circumstances would one desire to implement this? I can =
infer that from the
> > introduction, but it would be nice to see some sort of applicability st=
atement making it explicitly
> > clear that this is not an IETF protocol, and that one would implement i=
t in order to interoperate
> with
> > certain Adobe products. I know that some of this may be implied by the =
fact that this is
> informational
> > rather than standards track. But I don't expect readers who are not IET=
F insiders to understand that
> > subtlety without some explicit words to that effect. In particular, it =
would be good to clarify the
> > difference between this and the many "not quite accepted as standards t=
rack by some working group"
> > nature of a number of our informational RFCs that describe protocols.
>=20
> i will expand on applicability beyond what i specify in the first paragra=
ph of the Introduction, in
> general terms such as the kinds of functionality we use this protocol for=
 in Flash. note that
> interoperation with certain Adobe products, such as Flash Player, require=
s additional information such
> as the Flash-specific Cryptography Profile and syntax/semantics of mappin=
g Flash's "Real Time
> Messaging Protocol (RTMP)" messages onto RTMFP flows.  these Flash-specif=
ic profiles and mappings are
> application-layer for RTMFP, analogous to HTTP over TCP.
>=20
> > That all being said, this is overall a well written document. The rest =
of my comments are mostly
> > pedantic nits.
> >
> > *** Minor issues:
> >
> > -- section 1.2:
> >
> > I find the use of "MUST ONLY" confusing. I gather it means "you are _al=
lowed_ to do X only under
> > certain conditions" rather than "you are _required_ to do X under certa=
in conditions." If correct, I
> > think the words "MAY ONLY" would be more clear. If not, then I think th=
e construct would be better
> > handled using existing 2119 language.
>=20
> you're not the first person to be confused by that construct. i will chan=
ge instances of "MUST ONLY"
> to "is allowed only if" (or similar) and remove the definition for "MUST =
ONLY" from Section 1.2.
>=20
> > -- section 3.2:
> >
> > Do I understand correctly that all endpoints are expected to be able to=
 present certificates? Do you
> > find that common in the field? I realize the nature of the certs will d=
epend on the security
> profiles.
>=20
> yes, all endpoints have certificates. in the RTMFP-for-Flash world, these=
 certificates are not X.509
> certs, and are anonymous and ephemeral.
>=20
> > -- sections 3.2 and 5
> >
> > Do I assume correctly that endpoints need a common crypto profile to co=
mmunicate? Is there a
> > repository where one might find crypto profile documentation? Is there =
a commonly implemented one to
> > which this draft could refer?
>=20
> yes, endpoints need a common cryptography profile to interoperate.  there=
 is no repository for crypto
> profile documentation at this time. currently, there is one defined crypt=
ography profile (the one used
> for Flash communication) that is not publicly documented, because i do no=
t yet have permission to
> publish it.  i (meaning me personally) hope that a memo documenting the c=
rypto/application profile for
> Flash communication (as being a widely deployed and used profile for RTMF=
P) would also be published
> someday as an I-D and hopefully an Informational RFC.
>=20
> > -- section 3.2: "Multiple endpoints SHOULD NOT have the same identity."
> >
> > Why not MUST? Will things not break if two endpoints do have the same i=
dentity?
>=20
> this should be "It is RECOMMENDED that multiple endpoints not have the sa=
me identity."  if two
> endpoints have the same identity, then they will be indistinguishable.  t=
his will not break RTMFP, but
> might confuse an application.  that being said, there could potentially b=
e reasons to have different
> endpoints with indistinguishable identities and that potential should not=
 be normatively prohibited.
>=20
> > -- "Authenticity MAY comprise verifying an issuer signature chain in a =
public key infrastructure"
> >
> > Is that really normative, or just an observation of fact?
>=20
> that "MAY" should be "can".
>=20
> > -- " Canonical Endpoint Discriminators for distinct identities SHOULD b=
e distinct."
> >
> > What if they are not? Do things break? It might be worth making this a =
MUST, or adding some
> additional
> > guidance about what might happen if the SHOULD is violated.
>=20
> i will add a note that if the canonical EPD is the same for two distinct =
identities, then the
> "duplicate session" logic in section 3.5.1.1.1 (paragraph 6 step 1) might=
 abort a new opening session
> to the second identity, which might not be desired.
>=20
> > -- "A comparison function MAY comprise performing a lexicographic order=
ing..."
> >
> > Is that really normative, or just an example of something one might do?
>=20
> that "MAY" should be "can".
>=20
> > -- "A test SHOULD comprise testing whether the certificates are identic=
al."
> >
> > What if it doesn't? Also, what constitutes "identical"? All fields matc=
h values? Bitwise match?  Is
> it
> > simply including the same identity or identities? Maybe an identity fun=
ction provided by the crypto
> > profile?
>=20
> again, that SHOULD should be reworded to RECOMMENDED.  i will change "ide=
ntical" to "bitwise
> identical".
>=20
> > -- 3.5, last paragraph:
> >
> > Can you offer guidance on reasonable buffer size and number ranges?
>=20
> i assume you mean "3.4, last paragraph" (referring to packet reassembly b=
uffers).  i will add some
> guidance and a "for example".  the guidance will depend on how that RTMFP=
 will be used and the
> expected amount of resources available to it.
>=20
> > -- 3.5.1.1.1, 3rd paragraph:
> >
> > What are the consequences of having a tag with less than 8 bytes of len=
gth? Is the SHOULD reasonable
> > here?
>=20
> both of those SHOULDs should be RECOMMENDEDs.
>=20
> > -- 3.5.1.1.1 throughout, and following sections:
> >
> > Does the upper case AND have special meaning?
>=20
> upper case is the closest to bold face available in this format.  the int=
ention is to emphasize (since
> there are multiple conditionals) that all conditionals are required to ho=
ld.
>=20
> > -- 3.5.1.4, Deployment Note:
> >
> > How would a redirector know which endpoints might do this? Or should it=
 never initiate a session?
>=20
> this is guidance for designing and deploying an RTMFP system.  the redire=
ctor wouldn't know -- the
> designer should design the system such that the described circumstance do=
esn't happen (for example, by
> having the redirector never initiate a session).  this is properly a SHOU=
LD NOT since doing so can
> cause undesired behavior (as described).  it is not desirable to give a n=
ormative prohibition or
> recommendation against a redirector initiating any sessions.  i feel this=
 paragraph gives the
> narrowest normative limitation and an explanation for that limitation.
>=20
> > -- 3.5.2:
> >
> > Do I infer correctly that two endpoints need not share the same congest=
ion control algorithm to
> > communicate?
>=20
> correct.  the timestamp echo facility, ack behavior (as described for flo=
w receivers), and limitations
> on aggressiveness in 3.5.2/.* impose the normative envelope in which any =
congestion control algorithms
> should interoperate.
>=20
> > -- 3.6.2.3.2, 2nd paragraph: "...an implementation SHOULD encode a Next=
 User Data chunk instead of a
> > User Data chunk"
> >
> > I'm not sure why this needs to be normative, as I assume its just norma=
l behavior. But if it does
> need
> > to be normative, why not a MUST?  Can the far endpoint reasonably handl=
e things if the SHOULD is
> > violated?
>=20
> this should be a RECOMMENDED.  the far end will work just fine if Next Us=
er Data is never used.
>=20
> > *** Nits/editorial comments:
> >
> > -- General: There's quite a bit of inconsistent use of third-person vs =
second-person language.
>=20
> i will try to clean that up.
>=20
> > -- 3.1: It would be nice to see the overview earlier in the draft. I fo=
und it difficult to read
> > through all the data format stuff prior to section 3 putting them into =
context.
>=20
> others have commented that they'd prefer sections 2 and 3 to be swapped. =
i resisted that as this order
> ("here are the pieces" and then "here's how they fit together") is my pre=
ferred way of explaining
> stuff.  also swapping those sections would be a huge editorial change whi=
ch might have significant
> cross-reference and forward/back reference implications and could introdu=
ce hard-to-detect errors into
> the spec.  however, i think i can move the overview (or a summary thereof=
) to earlier in the spec
> (probably in Section 1).
>=20
> > -- 3.5.1.4, Deployment Note:
> >
> > s/which/that
>=20
> good catch.
>=20
> > -- 3.5.1.6, last paragraph:
> >
> > Which diagram? (An explicit cross-ref would help.)
>=20
> oops. that paragraph used to be the postamble of the figure, so it obviou=
sly meant "this figure".
> i'll change "the figure" to "Figure 17".
>=20
> > -- 3.5.2:
> >
> > What is meant by "aggressive" in this context? Aggressive in avoiding c=
ongestion, or aggressive in
> > sending data?
>=20
> aggressive in sending data. i'll make that clarification.
>=20
> > -- 3.6.2.3.1 and subsequent sections:
> >
> > Does the all-caps "FIRST" have special meaning?
>=20
> it is all-caps for typographical emphasis.
>=20
> thank you!
>=20
> -michael thornburgh

From brian.e.carpenter@gmail.com  Tue Jun 25 13:26:35 2013
Return-Path: <brian.e.carpenter@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 9BB9B21E8099; Tue, 25 Jun 2013 13:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 qj+4QjNQikr8; Tue, 25 Jun 2013 13:26:34 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 27F1921F9D64; Tue, 25 Jun 2013 13:26:32 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id mc8so13165957pbc.18 for <multiple recipients>; Tue, 25 Jun 2013 13:26:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=pkT6grNsKddCG8jBoCqIHFd/K3kdsqceNsFSR0nHExY=; b=ZQ95A6FSN3quWNdZ8PZiqA7td9NBwOUnHHp8m/LFjO4nSD2rN34+eu87n3GNZ+7MkF 49dNJ65cLyX8sraiitr3ynw4yGORlBhqAkJM/F/c172gb0OA8lxYBOGNHSXkQnzoHIn4 RyYI3BxMz3FnXIj39OKKTgW0dl+fNvPA7QKRe96lbfL3WhnbAV7Wx6LMWGwpfqEKdte0 e/jKo9V4CJxvbc59PGUlgZuTzlKTGKO84m3Zq3e1vo+dIxixAAeP7BnJSclSZtpfYGD0 o82ozs9WeGsYefzlNkQrTvSwYRcNvQuw4L3xpg63XQ/ZwjPbV1BM58UiWz7jCCaPhivo LxYQ==
X-Received: by 10.68.219.70 with SMTP id pm6mr667766pbc.154.1372191991832; Tue, 25 Jun 2013 13:26:31 -0700 (PDT)
Received: from [192.168.178.22] (15.198.69.111.dynamic.snap.net.nz. [111.69.198.15]) by mx.google.com with ESMTPSA id pb5sm24643825pbc.29.2013.06.25.13.26.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Jun 2013 13:26:30 -0700 (PDT)
Message-ID: <51C9FCFA.2070808@gmail.com>
Date: Wed, 26 Jun 2013 08:26:34 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>
Subject: Re: IAOC Website Updated
References: <20130620185914.19663.88097.idtracker@ietfa.amsl.com> <04d001ce7191$a5f4bf00$4001a8c0@gateway.2wire.net>
In-Reply-To: <04d001ce7191$a5f4bf00$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: iaoc@ietf.org, ietf <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: Tue, 25 Jun 2013 20:26:35 -0000

Tom,

On 25/06/2013 22:48, t.p. wrote:
...
> The main impression that this page has on me is that this is a part of
> the IETF, 

Yes. It is a committee set up by the IETF (with help from ISOC).
...

> The very brief description - "the fiscal and administrative support" -
> makes me think of taxes (and tax avoidance) 

The word "fiscal" means either pertaining to taxes or pertaining to
financial matters. It's quite appropriate - the IAOC oversees the budget,
and would undoubtedly oversee the handling of any tax matters that came
up despite ISOC's not-for-profit status.

> while the link to an RFC,
> which starts with loads of irrelevant - to the likely reader of this
> page (I assume someone relatively new to the work of this SDO) -

I don't see that at all. The Introduction of the RFC gives a
pretty good summary of IASA's job and the IAOC's role. Anyway,
this is not particularly intended for newcomers. We don't even
mention IASA on the newcomers page. Do you think we should?

> boilerplate is enough to make anyone reach for the off-switch, and
> guaranteed to do so if they get as far as IAD, IASA, ISOC, etc.
> Alphabet
> soup indeed!
> 
> I have tried - and failed - to produce a paragraph which summarises what
> IAOC is.  

To my mind the phrase "The IETF Administrative Oversight Committee"
is completely self defining, as in "The IETF Administrative Oversight
Committee oversees the administration of the IETF."

OOPS Ray - fix that "Oversite" typo!!!! And the sentence should
also state that IAOC is part of IASA.

> I would start with the need of the IETF for e-mail and web
> servers, and a few other bits and pieces such as legal advice and
> ownership of rights, then the need for money to fund that, where the
> money comes from and how the expenditure is supervised and where ISOC
> fits into that - but not an RFC in sight - or site.  This would not need
> to mention the IAD but cannot, IMO, avoid IASA.

That belongs on the About page rather than the Home page. I agree it would
make sense to mention technical support there as well as pure admin support.

   Brian

From ynir@checkpoint.com  Tue Jun 25 13:41:58 2013
Return-Path: <ynir@checkpoint.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 0812211E814E for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 13:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_HI=-8]
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 5SR0MOHEaqCp for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 13:41:52 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 5F3CF21E809F for <ietf@ietf.org>; Tue, 25 Jun 2013 13:41:49 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r5PKfZSX012140; Tue, 25 Jun 2013 23:41:47 +0300
X-CheckPoint: {51CA007F-E-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.180]) with mapi id 14.02.0342.003; Tue, 25 Jun 2013 23:41:35 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: SHOULD and RECOMMENDED
Thread-Topic: SHOULD and RECOMMENDED
Thread-Index: AQHOcF0a1G3Lf6PjA0SszxqYCRTGUZlEj6GAgAANKACAAHdkgIAAAX6AgAAHLwCAAV6sAIAAOjaA
Date: Tue, 25 Jun 2013 20:41:35 +0000
Message-ID: <5E39AEFE-44A6-4371-83AE-C54AB0A7A0FE@checkpoint.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <51C9CFA8.7080708@isdg.net>
In-Reply-To: <51C9CFA8.7080708@isdg.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.88]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 110110b926727491825d5ab46f5a3d3a26998a2781
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4487092056B675468F185549F65853D1@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF-Discussion 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: Tue, 25 Jun 2013 20:41:58 -0000

Those sentences are here without the context given in RFC 4478. But that RF=
C is entirely about AUTH_LIFETIME, so if you're not sending it, you're just=
 not implementing the RFC.=20

Those sentences are about the timing of sending the message. Upon receipt o=
f the message, the client software prompts the user for credentials, so we'=
d like to have that message sent soon enough so that a human user will have=
 enough time to enter the credentials before the SA expires. So is specifyi=
ng 4 minutes a "recommendation" or a "should-level requirement"?

IMO, in normal English this would be a recommendation. But in an RFC this i=
s also a should-level requirement, one that a particular implementation mig=
ht ignore (if the implementers know that the client in this case has no hum=
an user). In terms of code, you do the same thing with both sentences: you =
make sure your VPN gateway sends AUTH_LIFETIME at least 4 minutes before th=
e SA is scheduled to expire. You might even do 15 if you find out that your=
 users tend to take coffee breaks that last that long.


On Jun 25, 2013, at 8:13 PM, Hector Santos <hsantos@isdg.net> wrote:

> I want to know more what it translates to as a technical specification fo=
r CODING.   To me, it means this:
>=20
>   o Authorization Lift Time
>     [X] Send Notification
>         Time to send: __4__ mins (default)
>=20
>=20
> The problem as I experienced thus far is whether one MUST IMPLEMENT this =
protocol feature,in this case code for AUTH_LIFETIME and make it flexible w=
ith a default 4 mins timeout.
>=20
> At the end of the day, this feature is not functionally described as a MU=
ST protocol requirement, therefore as a product producer I have two design =
options:
>=20
>  1) Don't implement, possible less feature than competitors.
>     See if others implement it.
>=20
>  2) Implement and make it optional as the UI shows above.
>=20
> So I don't think its a really a language or native culture thing, its jus=
t poor functional/technical specification writing.  Of course, if one does =
not implement AUTH_LIFETIME and they later find out there are interoperabil=
ity issues with other products in the market, then there is a "BUG" in the =
specification.  It may need to be fixed in a BIS as a MUST or maybe the pro=
ducts that failed when a peer did not support it, then its considered buggy=
 because it read the above as a MUST.
>=20
> I would like to see a focus to produce more protocol writing guidelines, =
outline examples and tips on how to best reduce the ambiguity.   I think th=
e available RFC templates should include a new section:
>=20
>   1.x Minimum Requirements
>=20
> This should help writers focus on these type of issues for the multiple d=
iscipline readers out there.
>=20
> --
> HLS
>=20
>=20
>=20
> On 6/24/2013 4:18 PM, Yoav Nir wrote:
>>=20
>> On Jun 24, 2013, at 10:52 PM, Peter Saint-Andre <stpeter@stpeter.im> wro=
te:
>>=20
>>> On 6/24/13 1:47 PM, Michael Thornburgh wrote:
>>>> my feeling and belief is that RFC 2119 only gives SHOULD and
>>>> RECOMMENDED the same normative requirement level, but that it does
>>>> not override or change the distinct meanings of these words in
>>>> English.  sentences using each of these terms have different meanings
>>>> in English, even when those sentences appear in RFCs.
>>>=20
>>> I expect that the subtle differences between these words are lost on
>>> non-native speakers, and even most native speakers, of English. I'd be
>>> genuinely curious to hear that you think the distinct meanings are.
>>>=20
>>=20
>> "It is RECOMMENDED that implementations send the AUTH_LIFETIME notificat=
ion at least 4 minutes before the SA is to be deleted, to facilitate the us=
er entering credentials in time."
>>=20
>> "The implementation SHOULD send the AUTH_LIFETIME notification at least =
4 minutes before the SA is to be deleted, to facilitate the user entering c=
redentials in time."
>>=20
>> - What are the subtle differences in meaning between these two sentences=
?
>>=20
>> - Would an implementation written by a native speaker be any different d=
epending on which of the above sentences was in the RFC?
>>=20
>> Yoav
>>=20
>>=20


From brian.e.carpenter@gmail.com  Tue Jun 25 13:43:17 2013
Return-Path: <brian.e.carpenter@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 A84DC11E814B for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 13:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 AoCS9fEr6mNv for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 13:43:15 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 664BA11E814C for <ietf@ietf.org>; Tue, 25 Jun 2013 13:43:13 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id lj1so13219916pab.3 for <ietf@ietf.org>; Tue, 25 Jun 2013 13:43:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7pFeVhLjPGAJaiFqIXz45H/SdhikVhdoVIYePkr3oSs=; b=Qaq5AtvA7rxJGHcsGrVR/QNUO/FM318w/1SXFiAL3XHZYiDmHtLIY1qxjPZFO74Nfn j4PoAn+HHqsv9QMymroF1VRWvPrYQYnw6ey+sjuL+k8i64jSa2a53sS2C9zp0L32ZeFj ZdfpccbKmjVoRD88M7MQ/bwdcjS+g/BtxETi6To5wb8Vb3u4C+sE9IL7UvCc8HrmK8pc kzqzIq/3XHRc0eg3UkfLtG99Zt6+dFALobceQL2FxBSOXffNqSdYPQzlGwoPGhJCwsjf 0yxJ9taENxD30ScBYrmgKt+6onjGTURNgX0jMDom5P9jK8GW3Upecc1+OIIy78VLBsU7 vy1w==
X-Received: by 10.66.160.97 with SMTP id xj1mr1651805pab.5.1372192993096; Tue, 25 Jun 2013 13:43:13 -0700 (PDT)
Received: from [192.168.178.22] (15.198.69.111.dynamic.snap.net.nz. [111.69.198.15]) by mx.google.com with ESMTPSA id at1sm24726656pbc.10.2013.06.25.13.43.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Jun 2013 13:43:12 -0700 (PDT)
Message-ID: <51CA00E3.4040106@gmail.com>
Date: Wed, 26 Jun 2013 08:43:15 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: SHOULD and RECOMMENDED
References: <20130625085154.665a7a7059d7ee80bb4d670165c8327d.eedfe20d31.wbe@email03.secureserver.net> <CAMm+Lwg0L4T3F_SR-AYPFuF0nqFOE-nwBOiNc_fvsCo2JjPOwg@mail.gmail.com>
In-Reply-To: <CAMm+Lwg0L4T3F_SR-AYPFuF0nqFOE-nwBOiNc_fvsCo2JjPOwg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Doug Ewell <doug@ewellic.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: Tue, 25 Jun 2013 20:43:17 -0000

On 26/06/2013 05:58, Phillip Hallam-Baker wrote:
> On Tue, Jun 25, 2013 at 11:51 AM, Doug Ewell <doug@ewellic.org> wrote:
> 
>> Scott Brim <scott dot brim at gmail dot com> wrote:
>>
>>> 2119 overrides anything you might think you know about what words
>>> mean.
> 
> No, 2119 PURPORTs to do that. It can try but it probably isn't going to
> succeed.
> 
> The purpose of RFCs is to communicate ideas. In ordinary language there is
> a clear distinction between RECOMMENDED and SHOULD. There is a useful
> distinction between them in the context of writing a standard.
> 
> There are in fact standards bodies apart from the IETF. 

Yes, and when they explicitly cite RFC 2119, they accept the definitions
therein, one of which equates SHOULD and RECOMMENDED. You can dislike
that equation but it becomes an axiom. They both mean "there
may exist valid reasons in particular circumstances to ignore a
particular item, but the full implications must be understood and
carefully weighed before choosing a different course."

If you don't like this, it's easy to avoid: don't cite RFC 2119.

    Brian

From ben@nostrum.com  Tue Jun 25 16:10:04 2013
Return-Path: <ben@nostrum.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 9FD0911E8185; Tue, 25 Jun 2013 16:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.145
X-Spam-Level: 
X-Spam-Status: No, score=-100.145 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 LscOZ3VJv1yV; Tue, 25 Jun 2013 16:10:02 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id CBF2911E8183; Tue, 25 Jun 2013 16:10:01 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5PN9xMD035207 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 25 Jun 2013 18:09:59 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>
Date: Tue, 25 Jun 2013 18:09:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>
To: Michael Thornburgh <mthornbu@adobe.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion 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: Tue, 25 Jun 2013 23:10:04 -0000

Thanks for the response! Comments inline:

Thanks!

Ben.


On Jun 21, 2013, at 4:35 PM, Michael Thornburgh <mthornbu@adobe.com> =
wrote:

> hi Ben. thanks for your review. comments/replies inline.
>=20
>> From: Ben Campbell [mailto:ben@nostrum.com]
>> Sent: Thursday, June 20, 2013 4:07 PM
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>=20
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document:  draft-thornburgh-adobe-rtmfp-07
>> Reviewer: Ben Campbell
>> Review Date:  2013-06-20
>> IETF LC End Date: 2013-06-25
>>=20
>> Summary: This draft is almost ready for publication as an =
informational RFC. However, I have some
>> concerns about the purpose and intended status of the document that I =
think should be considered prior
>> to publication.
>>=20
>>=20
>> Note: This is an informational draft that describes what I understand =
to be an existing protocol as
>> implemented by commercial products. Therefore, this review does not =
attempt to evaluate the protocol
>> itself. I assume the protocol is what it is, and it is not up to the =
IETF to agree or disagree with
>> it.
>>=20
>> *** Major issues:
>>=20
>> -- Why does this need to be published as an IETF stream RFC?  If I =
understand correctly, this
>> documents an existing protocol as implemented by commercial products. =
I agree with Martin's comment
>> that there is value in publishing this sort of thing, but I applaud =
the Adobe and the author for
>> publishing it so other implementations can interoperate with their =
products. But that could have done
>> that in an independent stream document, or even in an Adobe published =
document. (Perhaps even in a
>> prettier format ;-)  )  If we publish this as an IETF stream =
document, then I think it needs stronger
>> clarification that it is not an IETF consensus doc than just its =
informational status.
>=20
> this memo documents an existing network transport protocol that is =
widely deployed and in widespread use in the Internet.  we felt that the =
IETF community (and in particular the participants in the Transport and =
Services Area) is the most appropriate community with which to share =
this work: 1) members of this community have the necessary and relevant =
expertise not only to understand the protocol, but to make use of it =
potentially in new applications beyond Flash; 2) it is a transport =
protocol similar in many ways to TCP and SCTP and widely deployed and =
used; 3) Adobe is interested in pursuing standardization of this =
protocol (with all that entails) if there is community interest, and the =
IETF is definitely the right place for that.
>=20
> we are very grateful that Martin Stiemerling chose to sponsor this =
document.
>=20
> with regard to comments in later messages in this thread, i'd be happy =
to include some (IESG-supplied) boilerplate in the document to clarify =
that it is not the product of an IETF WG.  however, note that both the =
title and first sentence of the Introduction indicate that this is =
"Adobe's blahblahblah", consistent with other vendor-protocol RFCs and =
consistent with IESG editorial insistence (as told to me by a former TSV =
AD).  see RFC 4332 and RFC 6802 for two examples of =
vendor-specific/supplied protocols.  see also the IESG note in RFC 4332 =
as an example disclaimer that could be added.

Some additional text (whether IESG boilerplate or otherwise) that =
clarifies the purpose of the draft would help a lot.


>=20
>> Along those lines:
>>=20
>> 	-- Is this document the authoritative specification? (I suspect =
not.) Who owns change control? I
>> assume that to be Adobe and/or the authors. What expectation do =
readers of this draft have that it
>> represents the current version of RTMFP at any point in time?
>=20
> this memo is the authoritative specification for Adobe's RTMFP.  Adobe =
owns change control.  i believe the second and third paragraphs of the =
Introduction indicate to a reader that this draft represents RTMFP as =
deployed in the named Adobe products at the time of writing.

At the time of writing yes. My concern is how a future implementor can =
be confident that this doc describes RTMFP as used by Adobe at points in =
the future. When you say this is the authoritative specification, does =
that mean that Adobe does not plan to modify the protocol without timely =
publication of an update to this document?

>=20
>> 	-- Under what circumstances would one desire to implement this? =
I can infer that from the
>> introduction, but it would be nice to see some sort of applicability =
statement making it explicitly
>> clear that this is not an IETF protocol, and that one would implement =
it in order to interoperate with
>> certain Adobe products. I know that some of this may be implied by =
the fact that this is informational
>> rather than standards track. But I don't expect readers who are not =
IETF insiders to understand that
>> subtlety without some explicit words to that effect. In particular, =
it would be good to clarify the
>> difference between this and the many "not quite accepted as standards =
track by some working group"
>> nature of a number of our informational RFCs that describe protocols.
>=20
> i will expand on applicability beyond what i specify in the first =
paragraph of the Introduction, in general terms such as the kinds of =
functionality we use this protocol for in Flash. note that =
interoperation with certain Adobe products, such as Flash Player, =
requires additional information such as the Flash-specific Cryptography =
Profile and syntax/semantics of mapping Flash's "Real Time Messaging =
Protocol (RTMP)" messages onto RTMFP flows.  these Flash-specific =
profiles and mappings are application-layer for RTMFP, analogous to HTTP =
over TCP.

Okay

>=20
>> That all being said, this is overall a well written document. The =
rest of my comments are mostly
>> pedantic nits.
>>=20
>> *** Minor issues:
>>=20
>> -- section 1.2:
>>=20
>> I find the use of "MUST ONLY" confusing. I gather it means "you are =
_allowed_ to do X only under
>> certain conditions" rather than "you are _required_ to do X under =
certain conditions." If correct, I
>> think the words "MAY ONLY" would be more clear. If not, then I think =
the construct would be better
>> handled using existing 2119 language.
>=20
> you're not the first person to be confused by that construct. i will =
change instances of "MUST ONLY" to "is allowed only if" (or similar) and =
remove the definition for "MUST ONLY" from Section 1.2.

Works for me.

>=20
>> -- section 3.2:
>>=20
>> Do I understand correctly that all endpoints are expected to be able =
to present certificates? Do you
>> find that common in the field? I realize the nature of the certs will =
depend on the security profiles.
>=20
> yes, all endpoints have certificates. in the RTMFP-for-Flash world, =
these certificates are not X.509 certs, and are anonymous and ephemeral.

Okay.

>=20
>> -- sections 3.2 and 5
>>=20
>> Do I assume correctly that endpoints need a common crypto profile to =
communicate? Is there a
>> repository where one might find crypto profile documentation? Is =
there a commonly implemented one to
>> which this draft could refer?
>=20
> yes, endpoints need a common cryptography profile to interoperate.  =
there is no repository for crypto profile documentation at this time. =
currently, there is one defined cryptography profile (the one used for =
Flash communication) that is not publicly documented, because i do not =
yet have permission to publish it.  i (meaning me personally) hope that =
a memo documenting the crypto/application profile for Flash =
communication (as being a widely deployed and used profile for RTMFP) =
would also be published someday as an I-D and hopefully an Informational =
RFC.

I understand the issue about permission to publish, but does this =
document serve its purpose until you are ready to publish the crypto =
profile? Ideally they would be published together and this document =
would reference that one. Do I infer correctly that there is no way =
someone could create an implementation that interops with Adobe products =
based on the documents available at this time?

>=20
>> -- section 3.2: "Multiple endpoints SHOULD NOT have the same =
identity."
>>=20
>> Why not MUST? Will things not break if two endpoints do have the same =
identity?
>=20
> this should be "It is RECOMMENDED that multiple endpoints not have the =
same identity."  if two endpoints have the same identity, then they will =
be indistinguishable.  this will not break RTMFP, but might confuse an =
application.  that being said, there could potentially be reasons to =
have different endpoints with indistinguishable identities and that =
potential should not be normatively prohibited.

As Barry mentioned, RECOMMENDED is a synonym for SHOULD. Adding some =
text the effect of your additional explanation would solve my concern.

>=20
>> -- "Authenticity MAY comprise verifying an issuer signature chain in =
a public key infrastructure"
>>=20
>> Is that really normative, or just an observation of fact?
>=20
> that "MAY" should be "can".

Okay.

>=20
>> -- " Canonical Endpoint Discriminators for distinct identities SHOULD =
be distinct."
>>=20
>> What if they are not? Do things break? It might be worth making this =
a MUST, or adding some additional
>> guidance about what might happen if the SHOULD is violated.
>=20
> i will add a note that if the canonical EPD is the same for two =
distinct identities, then the "duplicate session" logic in section =
3.5.1.1.1 (paragraph 6 step 1) might abort a new opening session to the =
second identity, which might not be desired.

Okay.

>=20
>> -- "A comparison function MAY comprise performing a lexicographic =
ordering..."
>>=20
>> Is that really normative, or just an example of something one might =
do?
>=20
> that "MAY" should be "can".

Okay.

>=20
>> -- "A test SHOULD comprise testing whether the certificates are =
identical."
>>=20
>> What if it doesn't? Also, what constitutes "identical"? All fields =
match values? Bitwise match?  Is it
>> simply including the same identity or identities? Maybe an identity =
function provided by the crypto
>> profile?
>=20
> again, that SHOULD should be reworded to RECOMMENDED.  i will change =
"identical" to "bitwise identical".

See my earlier comment on SHOULD vs RECOMMENDED. The important thing is =
to clarify the implications of violating the SHOULD.

>=20
>> -- 3.5, last paragraph:
>>=20
>> Can you offer guidance on reasonable buffer size and number ranges?
>=20
> i assume you mean "3.4, last paragraph" (referring to packet =
reassembly buffers).  i will add some guidance and a "for example".  the =
guidance will depend on how that RTMFP will be used and the expected =
amount of resources available to it.

That would probably help. The important thing is to help implementers =
avoid bad decisions on buffer size ranges.

>=20
>> -- 3.5.1.1.1, 3rd paragraph:
>>=20
>> What are the consequences of having a tag with less than 8 bytes of =
length? Is the SHOULD reasonable
>> here?
>=20
> both of those SHOULDs should be RECOMMENDEDs.

See previous comment

>=20
>> -- 3.5.1.1.1 throughout, and following sections:
>>=20
>> Does the upper case AND have special meaning?
>=20
> upper case is the closest to bold face available in this format.  the =
intention is to emphasize (since there are multiple conditionals) that =
all conditionals are required to hold.

Understood. I'm not sure if there is a convention for that--I guess the =
RFC editor will either leave it or advise something else.

>=20
>> -- 3.5.1.4, Deployment Note:
>>=20
>> How would a redirector know which endpoints might do this? Or should =
it never initiate a session?
>=20
> this is guidance for designing and deploying an RTMFP system.  the =
redirector wouldn't know -- the designer should design the system such =
that the described circumstance doesn't happen (for example, by having =
the redirector never initiate a session).  this is properly a SHOULD NOT =
since doing so can cause undesired behavior (as described).  it is not =
desirable to give a normative prohibition or recommendation against a =
redirector initiating any sessions.  i feel this paragraph gives the =
narrowest normative limitation and an explanation for that limitation.


Okay. Some words to that effect would help.

>=20
>> -- 3.5.2:
>>=20
>> Do I infer correctly that two endpoints need not share the same =
congestion control algorithm to
>> communicate?
>=20
> correct.  the timestamp echo facility, ack behavior (as described for =
flow receivers), and limitations on aggressiveness in 3.5.2/.* impose =
the normative envelope in which any congestion control algorithms should =
interoperate.

Okay.

>=20
>> -- 3.6.2.3.2, 2nd paragraph: "...an implementation SHOULD encode a =
Next User Data chunk instead of a
>> User Data chunk"
>>=20
>> I'm not sure why this needs to be normative, as I assume its just =
normal behavior. But if it does need
>> to be normative, why not a MUST?  Can the far endpoint reasonably =
handle things if the SHOULD is
>> violated?
>=20
> this should be a RECOMMENDED.  the far end will work just fine if Next =
User Data is never used.


See previous comments on SHOULD vs RECOMMENDED.

>=20
>> *** Nits/editorial comments:
>>=20
>> -- General: There's quite a bit of inconsistent use of third-person =
vs second-person language.
>=20
> i will try to clean that up.

Okay.

>=20
>> -- 3.1: It would be nice to see the overview earlier in the draft. I =
found it difficult to read
>> through all the data format stuff prior to section 3 putting them =
into context.
>=20
> others have commented that they'd prefer sections 2 and 3 to be =
swapped. i resisted that as this order ("here are the pieces" and then =
"here's how they fit together") is my preferred way of explaining stuff. =
 also swapping those sections would be a huge editorial change which =
might have significant cross-reference and forward/back reference =
implications and could introduce hard-to-detect errors into the spec.  =
however, i think i can move the overview (or a summary thereof) to =
earlier in the spec (probably in Section 1).

Okay.

>=20
>> -- 3.5.1.4, Deployment Note:
>>=20
>> s/which/that
>=20
> good catch.
>=20
>> -- 3.5.1.6, last paragraph:
>>=20
>> Which diagram? (An explicit cross-ref would help.)
>=20
> oops. that paragraph used to be the postamble of the figure, so it =
obviously meant "this figure".  i'll change "the figure" to "Figure 17".

Okay.

>=20
>> -- 3.5.2:
>>=20
>> What is meant by "aggressive" in this context? Aggressive in avoiding =
congestion, or aggressive in
>> sending data?
>=20
> aggressive in sending data. i'll make that clarification.

Okay.

>=20
>> -- 3.6.2.3.1 and subsequent sections:
>>=20
>> Does the all-caps "FIRST" have special meaning?
>=20
> it is all-caps for typographical emphasis.
>=20
> thank you!
>=20
> -michael thornburgh


From hsantos@isdg.net  Tue Jun 25 17:19:04 2013
Return-Path: <hsantos@isdg.net>
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 D0DB221E80C9 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 17:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_72=0.6, USER_IN_WHITELIST=-100]
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 wzIiLTaMwoV1 for <ietf@ietfa.amsl.com>; Tue, 25 Jun 2013 17:18:59 -0700 (PDT)
Received: from dkim.winserver.com (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 8ABE311E816B for <ietf@ietf.org>; Tue, 25 Jun 2013 17:18:58 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5505; t=1372205914; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=gKfHggH U8xEElCiRDhSmVD5WqgU=; b=e5paZhM0c+X7437JAsETJGsAhtKCttowuhB6PsW 1YFLA7ezblhl3rPHzSX+SsT9RxRMhkBm2/XMyV1RyFyLbDXtcwhlnnFLPJ8gnSc1 0tzsG1ssBbL0tLYDPENp0g/N81T235KU0aAv0l/LjYcI1Fz+2k77TBU8I4WYVWwS SP7I=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 25 Jun 2013 20:18:34 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2963453711.705.3588; Tue, 25 Jun 2013 20:18:33 -0400
Message-ID: <51CA32BA.5060704@isdg.net>
Date: Tue, 25 Jun 2013 20:15:54 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: SHOULD and RECOMMENDED
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <51C9CFA8.7080708@isdg.net> <5E39AEFE-44A6-4371-83AE-C54AB0A7A0FE@checkpoint.com>
In-Reply-To: <5E39AEFE-44A6-4371-83AE-C54AB0A7A0FE@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion 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, 26 Jun 2013 00:19:04 -0000

Good point, timeouts are important and we know in practice, they vary 
for many reasons, and in many cases, there are different functional 
needs depending on human versus automated interfaces/handlers.

Nonetheless, I always prefer being specific when all possible.  I still 
believe this is universal and global and readers will "get it." Give 
them the benefit of the doubt. Its a matter of having better written 
specifications and understanding there are multiple disciplined readers 
and conflicts between administrators (sysops) vs developers (coders).

IMO, in this case because it is related to a required time property 
(including the idea that it could be infinite, forever, zero, -1 or 
otherwise ), it would be up to the protocol specification to clearly 
define what are the boundary conditions for success and failure;

     The implementator MUST offer a reasonable timeout value for the
     AUTH_LIFETIME notification. A RECOMMENDED timeout value is
     4 minutes.  Anything less risk X, Y and Z and anything more has
     shown to cause this or that.

etc, "Being specific is Terrific"

(Note, I am not aware of RFC 4478. I am provided general input because 
this is a general problem.  Maybe its too late for existing specs but 
future specifications can benefit from better guidelines.)

--
HLS



On 6/25/2013 4:41 PM, Yoav Nir wrote:
> Those sentences are here without the context given in RFC 4478. But that RFC is entirely about AUTH_LIFETIME, so if you're not sending it, you're just not implementing the RFC.
>
> Those sentences are about the timing of sending the message. Upon receipt of the message, the client software prompts the user for credentials, so we'd like to have that message sent soon enough so that a human user will have enough time to enter the credentials before the SA expires. So is specifying 4 minutes a "recommendation" or a "should-level requirement"?
>
> IMO, in normal English this would be a recommendation. But in an RFC this is also a should-level requirement, one that a particular implementation might ignore (if the implementers know that the client in this case has no human user). In terms of code, you do the same thing with both sentences: you make sure your VPN gateway sends AUTH_LIFETIME at least 4 minutes before the SA is scheduled to expire. You might even do 15 if you find out that your users tend to take coffee breaks that last that long.
>
>
> On Jun 25, 2013, at 8:13 PM, Hector Santos <hsantos@isdg.net> wrote:
>
>> I want to know more what it translates to as a technical specification for CODING.   To me, it means this:
>>
>>    o Authorization Lift Time
>>      [X] Send Notification
>>          Time to send: __4__ mins (default)
>>
>>
>> The problem as I experienced thus far is whether one MUST IMPLEMENT this protocol feature,in this case code for AUTH_LIFETIME and make it flexible with a default 4 mins timeout.
>>
>> At the end of the day, this feature is not functionally described as a MUST protocol requirement, therefore as a product producer I have two design options:
>>
>>   1) Don't implement, possible less feature than competitors.
>>      See if others implement it.
>>
>>   2) Implement and make it optional as the UI shows above.
>>
>> So I don't think its a really a language or native culture thing, its just poor functional/technical specification writing.  Of course, if one does not implement AUTH_LIFETIME and they later find out there are interoperability issues with other products in the market, then there is a "BUG" in the specification.  It may need to be fixed in a BIS as a MUST or maybe the products that failed when a peer did not support it, then its considered buggy because it read the above as a MUST.
>>
>> I would like to see a focus to produce more protocol writing guidelines, outline examples and tips on how to best reduce the ambiguity.   I think the available RFC templates should include a new section:
>>
>>    1.x Minimum Requirements
>>
>> This should help writers focus on these type of issues for the multiple discipline readers out there.
>>
>> --
>> HLS
>>
>>
>>
>> On 6/24/2013 4:18 PM, Yoav Nir wrote:
>>>
>>> On Jun 24, 2013, at 10:52 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
>>>
>>>> On 6/24/13 1:47 PM, Michael Thornburgh wrote:
>>>>> my feeling and belief is that RFC 2119 only gives SHOULD and
>>>>> RECOMMENDED the same normative requirement level, but that it does
>>>>> not override or change the distinct meanings of these words in
>>>>> English.  sentences using each of these terms have different meanings
>>>>> in English, even when those sentences appear in RFCs.
>>>>
>>>> I expect that the subtle differences between these words are lost on
>>>> non-native speakers, and even most native speakers, of English. I'd be
>>>> genuinely curious to hear that you think the distinct meanings are.
>>>>
>>>
>>> "It is RECOMMENDED that implementations send the AUTH_LIFETIME notification at least 4 minutes before the SA is to be deleted, to facilitate the user entering credentials in time."
>>>
>>> "The implementation SHOULD send the AUTH_LIFETIME notification at least 4 minutes before the SA is to be deleted, to facilitate the user entering credentials in time."
>>>
>>> - What are the subtle differences in meaning between these two sentences?
>>>
>>> - Would an implementation written by a native speaker be any different depending on which of the above sentences was in the RFC?
>>>
>>> Yoav
>>>
>>>
>
>
>


From daedulus@btconnect.com  Wed Jun 26 02:49:00 2013
Return-Path: <daedulus@btconnect.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 AF47D21E8129 for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2013 02:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 MBiDl8wndr09 for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2013 02:48:54 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe010.messaging.microsoft.com [216.32.180.30]) by ietfa.amsl.com (Postfix) with ESMTP id C9A1421E8120 for <ietf@ietf.org>; Wed, 26 Jun 2013 02:48:53 -0700 (PDT)
Received: from mail143-va3-R.bigfish.com (10.7.14.240) by VA3EHSOBE013.bigfish.com (10.7.40.63) with Microsoft SMTP Server id 14.1.225.23; Wed, 26 Jun 2013 09:48:52 +0000
Received: from mail143-va3 (localhost [127.0.0.1])	by mail143-va3-R.bigfish.com (Postfix) with ESMTP id 0C73380062; Wed, 26 Jun 2013 09:48:53 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.197; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0711HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zzbb2dI98dI9371I146fI542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail143-va3 (localhost.localdomain [127.0.0.1]) by mail143-va3 (MessageSwitch) id 1372240129976307_19390; Wed, 26 Jun 2013 09:48:49 +0000 (UTC)
Received: from VA3EHSMHS003.bigfish.com (unknown [10.7.14.228])	by mail143-va3.bigfish.com (Postfix) with ESMTP id E2D10E0067; Wed, 26 Jun 2013 09:48:49 +0000 (UTC)
Received: from DB3PRD0711HT002.eurprd07.prod.outlook.com (157.56.254.197) by VA3EHSMHS003.bigfish.com (10.7.99.13) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 26 Jun 2013 09:48:45 +0000
Received: from DBXPRD0411HT005.eurprd04.prod.outlook.com (157.56.253.165) by pod51017.outlook.com (10.255.183.35) with Microsoft SMTP Server (TLS) id 14.16.324.0; Wed, 26 Jun 2013 09:48:30 +0000
Message-ID: <022b01ce7252$63ceb920$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20130620185914.19663.88097.idtracker@ietfa.amsl.com> <04d001ce7191$a5f4bf00$4001a8c0@gateway.2wire.net> <51C9FCFA.2070808@gmail.com>
Subject: Re: IAOC Website Updated
Date: Wed, 26 Jun 2013 10:43:45 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.165]
X-OriginatorOrg: btconnect.com
Cc: ietf <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, 26 Jun 2013 09:49:00 -0000

---- Original Message -----
From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
To: "t.p." <daedulus@btconnect.com>
Cc: "ietf" <ietf@ietf.org>; <iaoc@ietf.org>
Sent: Tuesday, June 25, 2013 9:26 PM
> Tom,
>
> On 25/06/2013 22:48, t.p. wrote:
> ...
> > The main impression that this page has on me is that this is a part
of
> > the IETF,
>
> Yes. It is a committee set up by the IETF (with help from ISOC).

but then I read
"The IETF Administrative Oversight Committee (IAOC) ...is housed within
the Internet Society"
which makes it part of the ISOC and so I would expect the web site to
reflect
that, with an ISOC logo somewhere.

And when I click on the navigation, IETF-Home, I get .... IAOC!!!
whereas on all other pages with that style of navigation I get, well ,
IETF-Home (what should I expect)

Also, from the (real) IETF-Home, a natural starting point for the
uninitiated, there are six links to related sites, one of which is
tagged IASA/IAOC/Trust which leads direct to this site which is then
IAOC only.  Poor navigation IMO; I think it should lead to something
that
clarifies the existence and relationship of those three (which could
well be this web page expanded a little).

In passing, the IETF Trust home page may lack fancy bells and whistles
but is so much clearer.  It is what a web page should be (when judged by
content).

> ...
> > The very brief description - "the fiscal and administrative
support" -
> > makes me think of taxes (and tax avoidance)
>
> The word "fiscal" means either pertaining to taxes or pertaining to
> financial matters. It's quite appropriate - the IAOC oversees the
budget,
> and would undoubtedly oversee the handling of any tax matters that
came
> up despite ISOC's not-for-profit status.

Disagree.  The last five years have seen extensive use of fiscal in the
media, and it there refers to tax and expenditure, the contrast being
with monetary, interest rates and printing money; there are plenty of
other words in our language that I think more generic - financial (as
you just used:-)?

> > while the link to an RFC,
> > which starts with loads of irrelevant - to the likely reader of this
> > page (I assume someone relatively new to the work of this SDO) -
>
> I don't see that at all. The Introduction of the RFC gives a
> pretty good summary of IASA's job and the IAOC's role. Anyway,
> this is not particularly intended for newcomers. We don't even
> mention IASA on the newcomers page. Do you think we should?

If you get to the Introduction..  Try to look at this with uninitiated
eyes - you know it is boiler plate and pass over it probably without
realising that you are doing so.  An innocent eye may see ... what a
load of *** and switch off.

(I am not uninitiated in these matters, but would like others who are to
find it easier to understand what it is that I am involved with, which
is what is driving me in this).

> > boilerplate is enough to make anyone reach for the off-switch, and
> > guaranteed to do so if they get as far as IAD, IASA, ISOC, etc.
> > Alphabet
> > soup indeed!
> >
> > I have tried - and failed - to produce a paragraph which summarises
what
> > IAOC is.
>
> To my mind the phrase "The IETF Administrative Oversight Committee"
> is completely self defining, as in "The IETF Administrative Oversight
> Committee oversees the administration of the IETF."

Well no, oversight of what?  An administrative committee (if that is not
prolix) that "oversights" the IETF or a committee that "oversights" the
IETF Administrative.  Your second formulation
"The IETF Administrative Oversight Committee oversees the administration
of the IETF."
is so much clearer (to the uninitiated).

Tom Petch

> OOPS Ray - fix that "Oversite" typo!!!! And the sentence should
> also state that IAOC is part of IASA.
>
> > I would start with the need of the IETF for e-mail and web
> > servers, and a few other bits and pieces such as legal advice and
> > ownership of rights, then the need for money to fund that, where the
> > money comes from and how the expenditure is supervised and where
ISOC
> > fits into that - but not an RFC in sight - or site.  This would not
need
> > to mention the IAD but cannot, IMO, avoid IASA.
>
> That belongs on the About page rather than the Home page. I agree it
would
> make sense to mention technical support there as well as pure admin
support.
>
>    Brian
>



From presnick@qti.qualcomm.com  Wed Jun 26 08:18:15 2013
Return-Path: <presnick@qti.qualcomm.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 E3E4121E8090 for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2013 08:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 1JkR8ebOBJ9p for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2013 08:18:11 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id B039121F9B3E for <ietf@ietf.org>; Wed, 26 Jun 2013 08:18:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1372259891; x=1403795891; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=yuLONL6veZz5LRAzuLjFSJwZ+GQApzA5E90gvU61wjE=; b=hT+vHTyPzKftoHdUmwJN7PbYWcT9nHQ1xOAc/s7unc4i6xVPbLFgQO2s SHzkOL9EgX0wMg1lGr9/G7dFJZh/EzGAq7P69c528PXNo7ebA3q2ldU6r iJRDcOZ9OJs/wTc/krpx2KtzakhVuD6JS9C7AAOnEUP1tPSD9nZ8tblX3 o=;
X-IronPort-AV: E=Sophos;i="4.87,944,1363158000"; d="scan'208";a="46253913"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth02.qualcomm.com with ESMTP; 26 Jun 2013 08:18:11 -0700
X-IronPort-AV: E=Sophos;i="4.87,944,1363158000"; d="scan'208";a="496265958"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 26 Jun 2013 08:18:11 -0700
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 26 Jun 2013 08:18:11 -0700
Message-ID: <51CB0631.4050406@qti.qualcomm.com>
Date: Wed, 26 Jun 2013 10:18:09 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch? (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com>	<5153571C.9070800@nostrum.com>	<CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu>	<6.2.5.6.2.20130328111022.0ceeb7d8@resistor.net> <5159FF0E.9080202@nostrum.com>
In-Reply-To: <5159FF0E.9080202@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org, Alexey Melnikov <Alexey.Melnikov@isode.com>, SM <sm@resistor.net>, Burger Eric <eburger@cs.georgetown.edu>, Sam Hartman <hartmans-ietf@mit.edu>
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, 26 Jun 2013 15:18:16 -0000

On 4/1/13 4:41 PM, Robert Sparks wrote:
> On 3/28/13 1:17 PM, SM wrote:
>> At 05:13 28-03-2013, Burger Eric wrote:
>>> I use the IMAP interface once, mark a bunch of things as read, and 
>>> then decide never to use the IMAP interface ever again. How long 
>>> does the server need to keep my (per-user) marking metadata? E.g., 
>>> besides CPU and I/O issues, there is a potentially unbounded storage 
>>> problem as well. It is unbounded because in IMAP I can assign any 
>>> kind of label (marking) to a message, even ones I make up.
>>>
>>> One thought for an approach to a solution:
>>> 1. per-user markings expire after X time units (six months?)
>>> 2. per-user markings may take up at most X storage units (512KB?)
>>
>> I would go for both.
>
> Instead, I propose that we make it possible to notice an abuser and 
> turn off access (this is what -06 will contain).
>
> I don't believe we could come to a consensus on an automatic expiry of 
> state - there are use cases I can think of where any short
> expiration (like 6-months) would be infuriating.
>
> If keeping this state for normal use turns out to be too expensive for 
> us, then we will have learned something, and can start talking about 
> future IMAP work in general to help systems mitigate that expense.

During my IESG Evaluation review of the document, I noticed the 
resultant paragraph for this. I don't know how I missed it before. Here 
is what I said in my ballot:

---

    o  It must be possible for administrators, on a per-user basis, to
       disable setting read/unread marks and other annotations and to
       delete any such marks or annotations.

I don't think that's the appropriate requirement. A perfectly reasonable 
way to address the issue of annotations taking up too much space is to 
use per-user storage quotas. I would prefer not to give administrators 
the ability or the need to decide which users get to use annotations and 
which users' annotations they get to delete. And I can imagine servers 
for which implementing this requirement would be a significant pain. 
Quotas solve the problem in a much more general way.

---

I wanted to post here to make sure that folks who were involved in the 
earlier discussion saw what I was suggesting and had a chance to object 
if they thought I was full of crap.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From alexey.melnikov@isode.com  Wed Jun 26 09:03:35 2013
Return-Path: <alexey.melnikov@isode.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 A5F3E21F965B for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2013 09:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 F4NIGvGvgRzU for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2013 09:03:30 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 9645E11E80F2 for <ietf@ietf.org>; Wed, 26 Jun 2013 09:03:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1372262607; d=isode.com; s=selector; i=@isode.com; bh=/hFmFkr7EE1GokVxZcQPunB6tuASMOkzbklLFGfEB5I=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Bfs6JasL28qtY6TjmOCmuAABJuTFXqi5YjioBdFCnMwD9y2HVzry+qwp/lV733oyKy4pqf ejVmQ7dTbojbBwBWtgSPijfGMQxqO+w/uwq5fL1TwDRcj/qKY7kOt4moBpZpbWjDj+huu0 YQYB1YRQkaBjUmFP7pJBzmGSUjGCZko=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <UcsQrQB9nmqW@statler.isode.com>; Wed, 26 Jun 2013 17:03:27 +0100
Message-ID: <51CB10D5.2030800@isode.com>
Date: Wed, 26 Jun 2013 17:03:33 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch?  (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu> <6.2.5.6.2.20130328111022.0ceeb7d8@resistor.net> <5159FF0E.9080202@nostrum.com> <51CB0631.4050406@qti.qualcomm.com>
In-Reply-To: <51CB0631.4050406@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, SM <sm@resistor.net>, Burger Eric <eburger@cs.georgetown.edu>, Sam Hartman <hartmans-ietf@mit.edu>
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, 26 Jun 2013 16:03:35 -0000

On 26/06/2013 16:18, Pete Resnick wrote:
> On 4/1/13 4:41 PM, Robert Sparks wrote:
>> On 3/28/13 1:17 PM, SM wrote:
>>> At 05:13 28-03-2013, Burger Eric wrote:
>>>> I use the IMAP interface once, mark a bunch of things as read, and 
>>>> then decide never to use the IMAP interface ever again. How long 
>>>> does the server need to keep my (per-user) marking metadata? E.g., 
>>>> besides CPU and I/O issues, there is a potentially unbounded 
>>>> storage problem as well. It is unbounded because in IMAP I can 
>>>> assign any kind of label (marking) to a message, even ones I make up.
>>>>
>>>> One thought for an approach to a solution:
>>>> 1. per-user markings expire after X time units (six months?)
>>>> 2. per-user markings may take up at most X storage units (512KB?)
>>>
>>> I would go for both.
>>
>> Instead, I propose that we make it possible to notice an abuser and 
>> turn off access (this is what -06 will contain).
>>
>> I don't believe we could come to a consensus on an automatic expiry 
>> of state - there are use cases I can think of where any short
>> expiration (like 6-months) would be infuriating.
>>
>> If keeping this state for normal use turns out to be too expensive 
>> for us, then we will have learned something, and can start talking 
>> about future IMAP work in general to help systems mitigate that expense.
>
> During my IESG Evaluation review of the document, I noticed the 
> resultant paragraph for this. I don't know how I missed it before. 
> Here is what I said in my ballot:
>
> ---
>
>    o  It must be possible for administrators, on a per-user basis, to
>       disable setting read/unread marks and other annotations and to
>       delete any such marks or annotations.
>
> I don't think that's the appropriate requirement. A perfectly 
> reasonable way to address the issue of annotations taking up too much 
> space is to use per-user storage quotas. I would prefer not to give 
> administrators the ability or the need to decide which users get to 
> use annotations and which users' annotations they get to delete. And I 
> can imagine servers for which implementing this requirement would be a 
> significant pain. Quotas solve the problem in a much more general way.

Yes, this requirement is a bit of a pain. Quotas would make it easier 
for my implementation.

> ---
>
> I wanted to post here to make sure that folks who were involved in the 
> earlier discussion saw what I was suggesting and had a chance to 
> object if they thought I was full of crap.


From mthornbu@adobe.com  Wed Jun 26 12:01:26 2013
Return-Path: <mthornbu@adobe.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 E999821F896D; Wed, 26 Jun 2013 12:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.065
X-Spam-Level: 
X-Spam-Status: No, score=-5.065 tagged_above=-999 required=5 tests=[AWL=-0.921, BAYES_00=-2.599, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_MED=-4]
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 OJFaAjsPYiz1; Wed, 26 Jun 2013 12:01:20 -0700 (PDT)
Received: from exprod6og124.obsmtp.com (exprod6og124.obsmtp.com [64.18.1.242]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7E711E820E; Wed, 26 Jun 2013 12:00:59 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob124.postini.com ([64.18.5.12]) with SMTP ID DSNKUcs6YcNu3WzllMTzhf8lldRnkH3LXeSk@postini.com; Wed, 26 Jun 2013 12:00:59 PDT
Received: from inner-relay-2.corp.adobe.com (inner-relay-2.adobe.com [153.32.1.52]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5QJ0lAI005391; Wed, 26 Jun 2013 12:00:48 -0700 (PDT)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5QJ08w8007320; Wed, 26 Jun 2013 12:00:44 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Wed, 26 Jun 2013 12:00:20 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: Ben Campbell <ben@nostrum.com>
Date: Wed, 26 Jun 2013 12:00:19 -0700
Subject: RE: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Topic: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Index: Ac5x+SBftgN/0Q0LQ5ilW3KpWz9woAAoI3ow
Message-ID: <D9D602D39A98E34D9C43E965BEC74398261AAE1D@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com>
In-Reply-To: <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion 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, 26 Jun 2013 19:01:27 -0000

comments inline.

> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Tuesday, June 25, 2013 4:10 PM
> =09
> Thanks for the response! Comments inline:
>=20
> Thanks!
>=20
> Ben.
>=20
> On Jun 21, 2013, at 4:35 PM, Michael Thornburgh <mthornbu@adobe.com> wrot=
e:
>=20
> > hi Ben. thanks for your review. comments/replies inline.
> >
> >> From: Ben Campbell [mailto:ben@nostrum.com]
> >> Sent: Thursday, June 20, 2013 4:07 PM

[...]

> > with regard to comments in later messages in this thread, i'd be happy =
to include some (IESG-
> supplied) boilerplate in the document to clarify that it is not the produ=
ct of an IETF WG.  however,
> note that both the title and first sentence of the Introduction indicate =
that this is "Adobe's
> blahblahblah", consistent with other vendor-protocol RFCs and consistent =
with IESG editorial
> insistence (as told to me by a former TSV AD).  see RFC 4332 and RFC 6802=
 for two examples of vendor-
> specific/supplied protocols.  see also the IESG note in RFC 4332 as an ex=
ample disclaimer that could
> be added.
>=20
> Some additional text (whether IESG boilerplate or otherwise) that clarifi=
es the purpose of the draft
> would help a lot.

the sponsoring AD has proposed an additional statement that will be inserte=
d by the RFC Editor on publication.  note that draft -08 has additional cla=
rification that this is an Adobe protocol and is not the product of an IETF=
 activity.

> >> Along those lines:
> >>
> >> 	-- Is this document the authoritative specification? (I suspect not.)=
 Who owns change control? I
> >> assume that to be Adobe and/or the authors. What expectation do reader=
s of this draft have that it
> >> represents the current version of RTMFP at any point in time?
> >
> > this memo is the authoritative specification for Adobe's RTMFP.  Adobe =
owns change control.  i
> believe the second and third paragraphs of the Introduction indicate to a=
 reader that this draft
> represents RTMFP as deployed in the named Adobe products at the time of w=
riting.
>=20
> At the time of writing yes. My concern is how a future implementor can be=
 confident that this doc
> describes RTMFP as used by Adobe at points in the future. When you say th=
is is the authoritative
> specification, does that mean that Adobe does not plan to modify the prot=
ocol without timely
> publication of an update to this document?

this is a problem for *any* published protocol.  RTMFP (as documented in th=
is memo) hasn't changed substantially in many years.  i have every expectat=
ion that, should a change be made to the protocol, we would publish an upda=
ted specification.

[...]

> >> -- sections 3.2 and 5
> >>
> >> Do I assume correctly that endpoints need a common crypto profile to c=
ommunicate? Is there a
> >> repository where one might find crypto profile documentation? Is there=
 a commonly implemented one
> to
> >> which this draft could refer?
> >
> > yes, endpoints need a common cryptography profile to interoperate.  the=
re is no repository for
> crypto profile documentation at this time. currently, there is one define=
d cryptography profile (the
> one used for Flash communication) that is not publicly documented, becaus=
e i do not yet have
> permission to publish it.  i (meaning me personally) hope that a memo doc=
umenting the
> crypto/application profile for Flash communication (as being a widely dep=
loyed and used profile for
> RTMFP) would also be published someday as an I-D and hopefully an Informa=
tional RFC.
>=20
> I understand the issue about permission to publish, but does this documen=
t serve its purpose until you
> are ready to publish the crypto profile? Ideally they would be published =
together and this document
> would reference that one. Do I infer correctly that there is no way someo=
ne could create an
> implementation that interops with Adobe products based on the documents a=
vailable at this time?

additional documentation is needed to interoperate (at the application laye=
r) with the Adobe products that implement RTMFP. i hope that the successful=
 publication of this memo will help me in getting the necessary approval to=
 publish the higher layer details of Adobe's RTMFP ecosystem.

the situation is analogous to having published TCP, but there's a lot more =
you need to know to talk to a web server with HTTPS (like TLS and HTTP).  i=
t's still useful to know how TCP works, and plenty more to do with it than =
talk to web servers.

> >> -- section 3.2: "Multiple endpoints SHOULD NOT have the same identity.=
"
> >>
> >> Why not MUST? Will things not break if two endpoints do have the same =
identity?
> >
> > this should be "It is RECOMMENDED that multiple endpoints not have the =
same identity."  if two
> endpoints have the same identity, then they will be indistinguishable.  t=
his will not break RTMFP, but
> might confuse an application.  that being said, there could potentially b=
e reasons to have different
> endpoints with indistinguishable identities and that potential should not=
 be normatively prohibited.
>=20
> As Barry mentioned, RECOMMENDED is a synonym for SHOULD. Adding some text=
 the effect of your
> additional explanation would solve my concern.

i changed this to RECOMMENDED (because while i agree that RECOMMENDED and S=
HOULD impart the same force of normative requirement for an implementer, th=
e words' different English meanings help the reader understand the reason f=
or the normative constraint).  see draft -08 for additional explanation i a=
dded for this constraint.

[...]

> >> *** Nits/editorial comments:
> >>
> >> -- General: There's quite a bit of inconsistent use of third-person vs=
 second-person language.
> >
> > i will try to clean that up.
>=20
> Okay.

as i mentioned in a separate message: """i believe the "second-person" voic=
e in this memo is used exclusively for detailing algorithms that are to be =
performed. i believe the imperative "do it like this" voice is appropriate =
to that use, so i did not change it. i also feel that the change in voice h=
elps indicate that the implementation is being addressed/instructed."""

[...]

thanks.

-michael thornburgh


From ben@nostrum.com  Wed Jun 26 13:03:50 2013
Return-Path: <ben@nostrum.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 C36E811E8205; Wed, 26 Jun 2013 13:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.145
X-Spam-Level: 
X-Spam-Status: No, score=-100.145 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 Crq3PO7XGjsG; Wed, 26 Jun 2013 13:03:50 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DCBE011E8203; Wed, 26 Jun 2013 13:03:49 -0700 (PDT)
Received: from [172.20.10.7] (mobile-166-147-070-136.mycingular.net [166.147.70.136]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5QK3i61077390 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 26 Jun 2013 15:03:46 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC74398261AAE1D@nambx08.corp.adobe.com>
Date: Wed, 26 Jun 2013 15:03:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F184F54-61DA-44D3-A705-A12F224E716A@nostrum.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com> <D9D602D39A98E34D9C43E965BEC74398261AAE1D@nambx08.corp.adobe.com>
To: Michael Thornburgh <mthornbu@adobe.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 166.147.70.136 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion 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, 26 Jun 2013 20:03:50 -0000

Hi Michael,

Thanks for the continued responses. A few more comments inline. I =
deleted sections that did not seem to need further comment. In summary, =
all of my concerns are resolved except for the crypto profile question.

Thanks!

Ben.

On Jun 26, 2013, at 2:00 PM, Michael Thornburgh <mthornbu@adobe.com> =
wrote:

[...]

>>> with regard to comments in later messages in this thread, i'd be =
happy to include some (IESG-
>> supplied) boilerplate in the document to clarify that it is not the =
product of an IETF WG.  however,
>> note that both the title and first sentence of the Introduction =
indicate that this is "Adobe's
>> blahblahblah", consistent with other vendor-protocol RFCs and =
consistent with IESG editorial
>> insistence (as told to me by a former TSV AD).  see RFC 4332 and RFC =
6802 for two examples of vendor-
>> specific/supplied protocols.  see also the IESG note in RFC 4332 as =
an example disclaimer that could
>> be added.
>>=20
>> Some additional text (whether IESG boilerplate or otherwise) that =
clarifies the purpose of the draft
>> would help a lot.
>=20
> the sponsoring AD has proposed an additional statement that will be =
inserted by the RFC Editor on publication.  note that draft -08 has =
additional clarification that this is an Adobe protocol and is not the =
product of an IETF activity.

The additional statement in 08 resolves my concern in the context of =
this specific document. (I have mixed feelings about the idea of =
documenting proprietary protocols in IETF stream drafts at all, but it's =
not reasonable to hold any particular draft hostage over a larger policy =
question.)

>> At the time of writing yes. My concern is how a future implementor =
can be confident that this doc
>> describes RTMFP as used by Adobe at points in the future. When you =
say this is the authoritative
>> specification, does that mean that Adobe does not plan to modify the =
protocol without timely
>> publication of an update to this document?
>=20
> this is a problem for *any* published protocol.
>  RTMFP (as documented in this memo) hasn't changed substantially in =
many years.  i have every expectation that, should a change be made to =
the protocol, we would publish an updated specification.
>=20

(Let me preface this comment: This is also an issue with the general =
idea of publishing proprietary protocols in IETF stream documents. I'm =
not picking on this draft in particular, and we can consider this issue =
closed for the purposes of my Gen-ART review.)

I disagree that this is an issue for any published protocol. In the case =
of an IETF produced protocol, an RFC is the definitive specification. If =
the IETF chooses to revise the protocol in the future, it does so by =
publishing a new RFC that updates or obsoletes the original.=20

You indicate Adobe plans to do the same, and that this protocol is =
pretty stable. You mentioned previously that this document would be the =
authoritative specification. So, then maybe there's not an issue.  But =
if Adobe maintains internal documentation that an Adobe engineer would =
consult to understand and implement the protocol, and you revise that =
documentation internally, it's going to be pretty tricky keeping the =
IETF -published specification in sync.



>>>=20
>>> yes, endpoints need a common cryptography profile to interoperate.  =
there is no repository for
>> crypto profile documentation at this time. currently, there is one =
defined cryptography profile (the
>> one used for Flash communication) that is not publicly documented, =
because i do not yet have
>> permission to publish it.  i (meaning me personally) hope that a memo =
documenting the
>> crypto/application profile for Flash communication (as being a widely =
deployed and used profile for
>> RTMFP) would also be published someday as an I-D and hopefully an =
Informational RFC.
>>=20
>> I understand the issue about permission to publish, but does this =
document serve its purpose until you
>> are ready to publish the crypto profile? Ideally they would be =
published together and this document
>> would reference that one. Do I infer correctly that there is no way =
someone could create an
>> implementation that interops with Adobe products based on the =
documents available at this time?
>=20
> additional documentation is needed to interoperate (at the application =
layer) with the Adobe products that implement RTMFP. i hope that the =
successful publication of this memo will help me in getting the =
necessary approval to publish the higher layer details of Adobe's RTMFP =
ecosystem.
>=20
> the situation is analogous to having published TCP, but there's a lot =
more you need to know to talk to a web server with HTTPS (like TLS and =
HTTP).  it's still useful to know how TCP works, and plenty more to do =
with it than talk to web servers.

I don't think that's a fair analogy. I can use TCP for many purposes =
other than talking to web servers. It can even be useful all itself. But =
if I understand correctly, you can't expect to use RTMFP _at_all_ until =
you publish they crypto-profile(s). Is that correct? If so, a better =
analogy would be to publish TLS without any published cryptosuites.

If I am correct on the inability to use the protocol at all without more =
documentation that does not currently exist, then I think it would be =
reasonable to put a clearly worded assertion to that effect early in the =
draft, along with a comment that you intend to publish at least one =
crypto profile in the future. (Perhaps an applicability statement would =
be helpful here.)


>=20
>>>> -- section 3.2: "Multiple endpoints SHOULD NOT have the same =
identity."
>>>>=20
>>>> Why not MUST? Will things not break if two endpoints do have the =
same identity?
>>>=20
>>> this should be "It is RECOMMENDED that multiple endpoints not have =
the same identity."  if two
>> endpoints have the same identity, then they will be =
indistinguishable.  this will not break RTMFP, but
>> might confuse an application.  that being said, there could =
potentially be reasons to have different
>> endpoints with indistinguishable identities and that potential should =
not be normatively prohibited.
>>=20
>> As Barry mentioned, RECOMMENDED is a synonym for SHOULD. Adding some =
text the effect of your
>> additional explanation would solve my concern.
>=20
> i changed this to RECOMMENDED (because while i agree that RECOMMENDED =
and SHOULD impart the same force of normative requirement for an =
implementer, the words' different English meanings help the reader =
understand the reason for the normative constraint).  see draft -08 for =
additional explanation i added for this constraint.

The added text in 08 resolves my concerns. (I'm not going to get into =
the RECOMMENDED vs SHOULD argument other than to note that the thread on =
the IETF discussion list tells me that English speakers don't =
necessarily agree on the difference :-) )



>=20
> [...]
>=20
>>>> *** Nits/editorial comments:
>>>>=20
>>>> -- General: There's quite a bit of inconsistent use of third-person =
vs second-person language.
>>>=20
>>> i will try to clean that up.
>>=20
>> Okay.
>=20
> as i mentioned in a separate message: """i believe the "second-person" =
voice in this memo is used exclusively for detailing algorithms that are =
to be performed. i believe the imperative "do it like this" voice is =
appropriate to that use, so i did not change it. i also feel that the =
change in voice helps indicate that the implementation is being =
addressed/instructed."""

Oops, sorry, I meant to cut that part out of my previous reply after =
seeing your other email. I seem to recall finding 2nd person language in =
sections that were not clearly identified as algorithm specifications, =
but on re-review I can't find it--so consider it dropped.


From mthornbu@adobe.com  Wed Jun 26 14:09:27 2013
Return-Path: <mthornbu@adobe.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 7969121F9B19; Wed, 26 Jun 2013 14:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.88
X-Spam-Level: 
X-Spam-Status: No, score=-4.88 tagged_above=-999 required=5 tests=[AWL=-0.736,  BAYES_00=-2.599, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_MED=-4]
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 8cUgS7DO9-Py; Wed, 26 Jun 2013 14:09:09 -0700 (PDT)
Received: from exprod6og112.obsmtp.com (exprod6og112.obsmtp.com [64.18.1.29]) by ietfa.amsl.com (Postfix) with ESMTP id 6C85C21F9B0F; Wed, 26 Jun 2013 14:08:39 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob112.postini.com ([64.18.5.12]) with SMTP ID DSNKUctYT0KPr9/OJqS8eThBCw2NY9ORPz2P@postini.com; Wed, 26 Jun 2013 14:08:39 PDT
Received: from inner-relay-1.corp.adobe.com (ms-exchange.macromedia.com [153.32.1.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5QL8PAI021519; Wed, 26 Jun 2013 14:08:26 -0700 (PDT)
Received: from SJ1SWM219.corp.adobe.com (sj1swm219.corp.adobe.com [10.5.77.61]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5QL8P6A018936; Wed, 26 Jun 2013 14:08:25 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by SJ1SWM219.corp.adobe.com ([fe80::d55c:7209:7a34:fcf7%11]) with mapi; Wed, 26 Jun 2013 14:08:24 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: Ben Campbell <ben@nostrum.com>
Date: Wed, 26 Jun 2013 14:08:24 -0700
Subject: RE: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Topic: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Index: Ac5yqEjda+NG/nO7S76BMoYlgBj5ugAAyT6g
Message-ID: <D9D602D39A98E34D9C43E965BEC74398261AAE61@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com> <D9D602D39A98E34D9C43E965BEC74398261AAE1D@nambx08.corp.adobe.com> <3F184F54-61DA-44D3-A705-A12F224E716A@nostrum.com>
In-Reply-To: <3F184F54-61DA-44D3-A705-A12F224E716A@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion 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, 26 Jun 2013 21:09:27 -0000

hi Ben. comment inline.

> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Wednesday, June 26, 2013 1:04 PM
>=20
> Hi Michael,
>=20
> Thanks for the continued responses. A few more comments inline. I deleted=
 sections that did not seem
> to need further comment. In summary, all of my concerns are resolved exce=
pt for the crypto profile
> question.
>=20
> Thanks!
>=20
> Ben.
>=20
> On Jun 26, 2013, at 2:00 PM, Michael Thornburgh <mthornbu@adobe.com> wrot=
e:

[...]

> >>> yes, endpoints need a common cryptography profile to interoperate.  t=
here is no repository for
> >> crypto profile documentation at this time. currently, there is one def=
ined cryptography profile
> (the
> >> one used for Flash communication) that is not publicly documented, bec=
ause i do not yet have
> >> permission to publish it.  i (meaning me personally) hope that a memo =
documenting the
> >> crypto/application profile for Flash communication (as being a widely =
deployed and used profile for
> >> RTMFP) would also be published someday as an I-D and hopefully an Info=
rmational RFC.
> >>
> >> I understand the issue about permission to publish, but does this docu=
ment serve its purpose until
> you
> >> are ready to publish the crypto profile? Ideally they would be publish=
ed together and this document
> >> would reference that one. Do I infer correctly that there is no way so=
meone could create an
> >> implementation that interops with Adobe products based on the document=
s available at this time?
> >
> > additional documentation is needed to interoperate (at the application =
layer) with the Adobe
> products that implement RTMFP. i hope that the successful publication of =
this memo will help me in
> getting the necessary approval to publish the higher layer details of Ado=
be's RTMFP ecosystem.
> >
> > the situation is analogous to having published TCP, but there's a lot m=
ore you need to know to talk
> to a web server with HTTPS (like TLS and HTTP).  it's still useful to kno=
w how TCP works, and plenty
> more to do with it than talk to web servers.
>=20
> I don't think that's a fair analogy. I can use TCP for many purposes othe=
r than talking to web
> servers. It can even be useful all itself. But if I understand correctly,=
 you can't expect to use
> RTMFP _at_all_ until you publish they crypto-profile(s). Is that correct?=
 If so, a better analogy
> would be to publish TLS without any published cryptosuites.
>=20
> If I am correct on the inability to use the protocol at all without more =
documentation that does not
> currently exist, then I think it would be reasonable to put a clearly wor=
ded assertion to that effect
> early in the draft, along with a comment that you intend to publish at le=
ast one crypto profile in the
> future. (Perhaps an applicability statement would be helpful here.)

interoperating with the Flash ecosystem requires additional documentation. =
i agree that a better analogy is publishing TLS without any published crypt=
osuites.

using RTMFP requires _a_ cryptography profile. this memo describes the requ=
ired semantics of a cryptography profile.  the first bullet of Section 1.1 =
"Design Highlights" (which occurs on the first page after the TOC), Section=
 2.2.3 "Encryption", and the first paragraph of the Security Considerations=
 section all indicate that this protocol defines a general framework for se=
curity, and that the application designer chooses/defines the algorithms an=
d data formats to be used within that framework.  an application designer c=
ould, using only this memo (and knowledge of security and cryptography prin=
ciples), define her own cryptography profile suitable for her application o=
f RTMFP, and create a correct and useful RTMFP application.

since i don't yet have permission, i can't make a commitment in this memo t=
hat Adobe will (or intends to) publicly document any additional layers of t=
he RTMFP-in-Flash ecosystem.  just for extra clarification: it is my *perso=
nal* hope that i will be able to do so in the future.

[...]

thanks!

-michael thornburgh

From dougb@dougbarton.us  Wed Jun 26 17:26:42 2013
Return-Path: <dougb@dougbarton.us>
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 9166F21F997E for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2013 17:26:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Aud-GN7zs19S for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2013 17:26:42 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 70BE421F93C4 for <ietf@ietf.org>; Wed, 26 Jun 2013 17:26:36 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 8CA7722B0F for <ietf@ietf.org>; Thu, 27 Jun 2013 00:26:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1372292792; bh=QLaTsvJmhik3fXHKEpfjP6/jvmaLW8+tYbS2KiyrTf0=; h=Date:From:To:Subject:References:In-Reply-To; b=NFs/blSD1a82pdWtoAxiIBSWuhLQtLM0w1fb1Lw+FHwGMIqSPUmwzpDHXLimyMBd9 JCe+ujNSnVVV3UrJVC8Gszx7wQegPPcR9z4RzZt1T/uur16+7tl5rDdlnpjqaJlcNh HTgAqknKKSqf4V/LyLgn0nIUL1DL1IBKa5/HSkuM=
Message-ID: <51CB86B8.9030603@dougbarton.us>
Date: Wed, 26 Jun 2013 17:26:32 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: SHOULD and RECOMMENDED
References: <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <CAKHUCzxtiXOgXwYmn+viq88r--Rs2vHk-0v85y4TyJzzQhDBtg@mail.gmail.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CAMm+Lwg3re0Ok39b5COoO8M5pTW-eNT5ifpkrSuqNdSEGkveHg@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <D6OO59PmqHXt-2EiDExefKb0U9ItY8c952s3NkA87gdwcGAX8@smtp.gmail.com>
In-Reply-To: <D6OO59PmqHXt-2EiDExefKb0U9ItY8c952s3NkA87gdwcGAX8@smtp.gmail.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 27 Jun 2013 00:26:42 -0000

In English as it is commonly spoken "recommended," and "should" do 
indeed mean different things. Arguably it's unfortunate that 2119 
conflated them, but that's the landscape we're living in.

So if the question is, "How do we improve the normative language in 
RFCs?" we should probably be thinking along the lines of giving more 
details about the conditions related to the things should/recommended 
apply to. I think it was Brian that said a while back that there should 
never be a SHOULD in a doc without an accompanied "unless ..." that 
spells out when the SHOULD can safely not be followed. It's not hard to 
imagine a similar guideline for "RECOMMENDED, because ..." that explains 
why something is recommended, and ideally also spells out the 
consequences if it is not done.

The idea being that 10 years from now a document can stand on its own as 
the repository of information about the topic it describes without 
having to fall back on WG discussions, anecdotes, etc. Another way to 
look at it is to ask the question, "Does this document have everything 
necessary for someone to create an interoperable implementation from 
scratch?"

thoughts?

Doug

From hallam@gmail.com  Wed Jun 26 18:27:36 2013
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 8BCCA21F9A47 for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2013 18:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 1NtpKgRps87v for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2013 18:27:35 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3643E21F95DD for <ietf@ietf.org>; Wed, 26 Jun 2013 18:27:35 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id t59so98842wes.34 for <ietf@ietf.org>; Wed, 26 Jun 2013 18:27: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=TrzJPYf69gPOF63iHyASFlUrNTevUW26GMFzHEmkO3s=; b=y7fwDzI3oC2+PUZgVhJw7lH8kz/mddKRv0tQHeTRRHXt4HhemkMLZMOVs97YiKA3Vz /TN9/ydn7XlXdeeARrUhdvhnJ70np1je52dLeED8exAeldvRxCF/rVYsmHk3eI9v2zz5 aajXf+m+WLLI6gqDVmaLxRQAu6oQqY52xnTEBpewKlpesyInGcpNpE5+dkkvIhvBUYoc vdvsVnayg/0vUy3Uiwf0WxhIHM4e+HcStzWInEuB2YiIXYPb0e6LlghWzhfyXqz9IUBG kkE6iUTCk9rlrnv0viMJ6nG3+/B0uObIuymM1NLPRvrE73St1L4mGXwMXzuG1pP86Wkp zdjw==
MIME-Version: 1.0
X-Received: by 10.180.108.129 with SMTP id hk1mr2799647wib.56.1372296452020; Wed, 26 Jun 2013 18:27:32 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Wed, 26 Jun 2013 18:27:31 -0700 (PDT)
In-Reply-To: <51CB86B8.9030603@dougbarton.us>
References: <D9D602D39A98E34D9C43E965BEC7439825F20E73@nambx08.corp.adobe.com> <51C8A377.4020508@stpeter.im> <630CAEAF-DAD6-4043-986B-E0CA8DAF56E8@checkpoint.com> <CAMm+LwjQZW4bxtDi-iYS=RZFxNwKNKqOo=Vk5rDS0wyZqc3RCg@mail.gmail.com> <CAMm+LwiUMTSMCr2oo6xgODaJJ=HfBdDeiynzV+JUQk2tZgbxEg@mail.gmail.com> <0835FA6B8B3FF6A934B375A0@JcK-HP8200.jck.com> <CAKHUCzxtiXOgXwYmn+viq88r--Rs2vHk-0v85y4TyJzzQhDBtg@mail.gmail.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <06F3E21A0F7B70C591083973@JcK-HP8200.jck.com> <CAMm+Lwg3re0Ok39b5COoO8M5pTW-eNT5ifpkrSuqNdSEGkveHg@mail.gmail.com> <51C76FEC.9040009@dcrocker.net> <CALaySJKS8X_Wn1sZQmsjFGiSyurc3a0KVsrLk7x7KhzptWvcNQ@mail.gmail.com> <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com> <D6OO59PmqHXt-2EiDExefKb0U9ItY8c952s3NkA87gdwcGAX8@smtp.gmail.com> <51CB86B8.9030603@dougbarton.us>
Date: Wed, 26 Jun 2013 21:27:31 -0400
Message-ID: <CAMm+Lwj8V4qaq4-STB-u-8kyT+5Efj0efwKdbCT72t4r1hDjqA@mail.gmail.com>
Subject: Re: SHOULD and RECOMMENDED
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Doug Barton <dougb@dougbarton.us>
Content-Type: multipart/alternative; boundary=e89a8f3bb04f8ca16a04e018aaf6
Cc: 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: Thu, 27 Jun 2013 01:27:36 -0000

--e89a8f3bb04f8ca16a04e018aaf6
Content-Type: text/plain; charset=ISO-8859-1

+1

I think SHOULD and RECOMMENDED should both be used when there is a strong
suggestion that implementations comply with the following statement unless
there are reasons not to.

Where I think it is time to go beyond 2119 is that we can distinguish two
circumstances:

SHOULD is the preferred term when the reasons are objective, e.g. certain
platforms don't support green flidgets.

RECOMMENDED is the preferred term when the reasons are subjective or
subject to change. I can recommend AES but only on the basis of current
knowledge.


I really don't see hotlinks from other institutions to RFC 2119 as any
problem at all. RFC 2119 will not change even if the IETF updates it. A
document that references 2119 for normative language will continue to do so
unless reissued with a new RFC number.



On Wed, Jun 26, 2013 at 8:26 PM, Doug Barton <dougb@dougbarton.us> wrote:

> In English as it is commonly spoken "recommended," and "should" do indeed
> mean different things. Arguably it's unfortunate that 2119 conflated them,
> but that's the landscape we're living in.
>
> So if the question is, "How do we improve the normative language in RFCs?"
> we should probably be thinking along the lines of giving more details about
> the conditions related to the things should/recommended apply to. I think
> it was Brian that said a while back that there should never be a SHOULD in
> a doc without an accompanied "unless ..." that spells out when the SHOULD
> can safely not be followed. It's not hard to imagine a similar guideline
> for "RECOMMENDED, because ..." that explains why something is recommended,
> and ideally also spells out the consequences if it is not done.
>
> The idea being that 10 years from now a document can stand on its own as
> the repository of information about the topic it describes without having
> to fall back on WG discussions, anecdotes, etc. Another way to look at it
> is to ask the question, "Does this document have everything necessary for
> someone to create an interoperable implementation from scratch?"
>
> thoughts?
>
> Doug
>



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

--e89a8f3bb04f8ca16a04e018aaf6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">+1<div><br></div><div style>I think SHOULD and RECOMMENDED=
 should both be used when there is a strong suggestion that implementations=
 comply with the following statement unless there are reasons not to.</div>
<div style><br></div><div style>Where I think it is time to go beyond 2119 =
is that we can distinguish two circumstances:</div><div style><br></div><di=
v style>SHOULD is the preferred term when the reasons are objective, e.g. c=
ertain platforms don&#39;t support green flidgets.</div>
<div style><br></div><div style>RECOMMENDED is the preferred term when the =
reasons are subjective or subject to change. I can recommend AES but only o=
n the basis of current knowledge.</div><div style><br></div><div style>
<br></div><div style>I really don&#39;t see hotlinks from other institution=
s to RFC 2119 as any problem at all. RFC 2119 will not change even if the I=
ETF updates it. A document that references 2119 for normative language will=
 continue to do so unless reissued with a new RFC number.</div>
<div style><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Wed, Jun 26, 2013 at 8:26 PM, Doug Barton <span dir=3D"ltr=
">&lt;<a href=3D"mailto:dougb@dougbarton.us" target=3D"_blank">dougb@dougba=
rton.us</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">In English as it is commonly spoken &quot;re=
commended,&quot; and &quot;should&quot; do indeed mean different things. Ar=
guably it&#39;s unfortunate that 2119 conflated them, but that&#39;s the la=
ndscape we&#39;re living in.<br>

<br>
So if the question is, &quot;How do we improve the normative language in RF=
Cs?&quot; we should probably be thinking along the lines of giving more det=
ails about the conditions related to the things should/recommended apply to=
. I think it was Brian that said a while back that there should never be a =
SHOULD in a doc without an accompanied &quot;unless ...&quot; that spells o=
ut when the SHOULD can safely not be followed. It&#39;s not hard to imagine=
 a similar guideline for &quot;RECOMMENDED, because ...&quot; that explains=
 why something is recommended, and ideally also spells out the consequences=
 if it is not done.<br>

<br>
The idea being that 10 years from now a document can stand on its own as th=
e repository of information about the topic it describes without having to =
fall back on WG discussions, anecdotes, etc. Another way to look at it is t=
o ask the question, &quot;Does this document have everything necessary for =
someone to create an interoperable implementation from scratch?&quot;<br>

<br>
thoughts?<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Doug<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><=
br>
</div>

--e89a8f3bb04f8ca16a04e018aaf6--

From sm@elandsys.com  Thu Jun 27 02:51:23 2013
Return-Path: <sm@elandsys.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 5FCD021F9A81 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 02:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 FhNJZHWhjTLO for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 02:51:22 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DDEE721F9799 for <ietf@ietf.org>; Thu, 27 Jun 2013 02:51:22 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.150.5]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5R9pAQ9028084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 27 Jun 2013 02:51:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372326682; bh=r/NIwy+fnEXDjNXpcJ8v/CLxTzBvCcZscyzev4J4mYc=; h=Date:To:From:Subject; b=O+X0uds3h+aJxPoUYgKA3fm0DULODfXBWG08m+KEV1ozENWfiyVj6iYjONT/kzEU7 z9DkIvgqXsO1+EJkmts/py8ztFL/SdowRV//rDKZwQWw1xAho5mYExSeJ0bE666g/l 4PmdvqNXGJEJ9Yn9MIR/uBSu9hCrlokmvuJVUiNk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372326682; i=@elandsys.com; bh=r/NIwy+fnEXDjNXpcJ8v/CLxTzBvCcZscyzev4J4mYc=; h=Date:To:From:Subject; b=VTe9jgPXaSqJ5a58XBqya6YqFy9vUmoMNF7N0ag7O66tTAI02VsHlL02I8GdoGJBy Ky9GFz6k2BemgeaORh0Sn1syr2k4sRUuFv+bPr5TWeS4G2mG1XG9qYoFc7pgDmwh5+ AUEpQWRBylfUj9cO+xy87FEDn8XecM2+5odR3boM=
Message-Id: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jun 2013 02:50:56 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: The Nominating Committee Process: Eligibility
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Thu, 27 Jun 2013 09:51:23 -0000

Hello,

RFC 3777 specifies the process by which members of the Internet 
Architecture Board, Internet Engineering Steering Group and IETF 
Administrative Oversight Committee are selected, confirmed, and recalled.

draft-moonesamy-nomcom-eligibility proposes an update RFC 3777 to 
allow remote contributors to the IETF Standards Process to be 
eligible to serve on NomCom and sign a Recall petition ( 
http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-00 ).

Could you please read the draft and comment?

Regards,
S. Moonesamy


From arturo.servin@gmail.com  Thu Jun 27 03:00:52 2013
Return-Path: <arturo.servin@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 CC83321F9CBB for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 03:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 l0mb9Xo3S9Qx for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 03:00:52 -0700 (PDT)
Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com [IPv6:2a00:1450:4013:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E897621F9CB6 for <ietf@ietf.org>; Thu, 27 Jun 2013 03:00:51 -0700 (PDT)
Received: by mail-ea0-f170.google.com with SMTP id h10so286778eaj.1 for <ietf@ietf.org>; Thu, 27 Jun 2013 03:00:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=7YymCRdaHQOkcPxg3buryR6t25MYyJEq7je/VUvoDK0=; b=zPiR/8sUyFGE1NDtN01LXtmYA1mpFJTajB4M+hcCLqnSLY3ETYnA6viYTZibBwUkt/ H2QUjHGxLj+FYC0wgEgWuihLj89SU4OvjUVoPLl2s527YFeWuN3RN5sLKeglsYb79e3Q eCXWNn0bkh59+ZdHsj5nqVikBKMuEHU6E/4C2y/pPFsSuUnCn5Hezg/FIpe1quMfYg1x IR8ogfLvAwS5vrnRDcSYY+Q78YEPNXvBvQk9gdc7zVBSn+xtNclqZM/DkY7jBKP+/kZR uGACAMmU79brOdOUjOG+x38vQ/ud9Qxuo4tVj+sXICS1wWauULZNIMbkvrGyp8CLKvQy 8nog==
X-Received: by 10.15.53.4 with SMTP id q4mr8207435eew.134.1372327250546; Thu, 27 Jun 2013 03:00:50 -0700 (PDT)
Received: from [192.168.0.5] ([90.214.33.42]) by mx.google.com with ESMTPSA id b7sm2729965eef.16.2013.06.27.03.00.49 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 03:00:49 -0700 (PDT)
Message-ID: <51CC0D50.8080708@gmail.com>
Date: Thu, 27 Jun 2013 11:00:48 +0100
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Thu, 27 Jun 2013 10:00:52 -0000

SM,

    I read the draft and although I like the idea I have some concerns.

    Today it is possible to verify that somebody attended to an IETF
meeting. You have to register, pay and collect your badge. However, in
remote participation we do not have mechanisms to verify that somebody
attended to a session.

    Even, if we had a registration similar to the face to face meetings,
it would be difficult to verify that the people attended to a session
remotely (even if you correlated registry vs. jabber/webex logs it would
be difficult to know if it is really the person registred, somebody else
or even a bot). I guess that there would be many ways to game the system.

    As I said I like the idea and I think that we should try to make it
work. I do not know if all the locks and tools to protect the system
against some sort of abuse should be in the draft or not, but we should
address those (before or in parallel with adopting/working on the draft.)

Regards,
as

   


On 6/27/13 10:50 AM, S Moonesamy wrote:
> Hello,
>
> RFC 3777 specifies the process by which members of the Internet
> Architecture Board, Internet Engineering Steering Group and IETF
> Administrative Oversight Committee are selected, confirmed, and recalled.
>
> draft-moonesamy-nomcom-eligibility proposes an update RFC 3777 to
> allow remote contributors to the IETF Standards Process to be eligible
> to serve on NomCom and sign a Recall petition (
> http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-00 ).
>
> Could you please read the draft and comment?
>
> Regards,
> S. Moonesamy


From lars@netapp.com  Thu Jun 27 03:04:08 2013
Return-Path: <lars@netapp.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 911A221F9CC4 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 03:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.199
X-Spam-Level: 
X-Spam-Status: No, score=-8.199 tagged_above=-999 required=5 tests=[AWL=2.400,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 GjZQQKva+NW6 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 03:04:03 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 7CEFE21F9CC2 for <ietf@ietf.org>; Thu, 27 Jun 2013 03:04:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,951,1363158000"; d="scan'208";a="31832682"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx2-out.netapp.com with ESMTP; 27 Jun 2013 03:03:58 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Thu, 27 Jun 2013 03:03:58 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
Thread-Topic: The Nominating Committee Process: Eligibility
Thread-Index: AQHOcxvvKlstUrItYkuAdBa8NnJK15lJymeA
Date: Thu, 27 Jun 2013 10:03:57 +0000
Message-ID: <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8A550D4F0DB1B24BAFD1734C273D3F5C@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <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: Thu, 27 Jun 2013 10:04:08 -0000

Hi,

Section 2 says:
   RFC 3777 [RFC3777], Section 5, "Nominating Committee Operation",
   Paragraph 1 of Rule 14, is replaced as follows:

      Members of the IETF community must have attended at least 3 of
      last 5 IETF meetings remotely or in person including at least 1 of
      the 5 last IETF meetings in person in order to volunteer.

A few questions:

(1) How do you define "remote attendance"?

(2) How does the secretariat determine whether someone has remotely attende=
d? (Based on whatever definition of remote attendance you have in mind.)

Thanks,
Lars=

From ynir@checkpoint.com  Thu Jun 27 03:33:59 2013
Return-Path: <ynir@checkpoint.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 9EA7321F9BDC for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 03:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level: 
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 lmrxvt6ZDf0q for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 03:33:52 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id ABDF021F9BBD for <ietf@ietf.org>; Thu, 27 Jun 2013 03:33:51 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r5RAXUlc010288; Thu, 27 Jun 2013 13:33:31 +0300
X-CheckPoint: {51CC14FA-21-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.180]) with mapi id 14.02.0342.003; Thu, 27 Jun 2013 13:33:30 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: The Nominating Committee Process: Eligibility
Thread-Topic: The Nominating Committee Process: Eligibility
Thread-Index: AQHOcxv6j7EPYIJH/EmbKEwv1RSrN5lJIsOAgAAIQ4A=
Date: Thu, 27 Jun 2013 10:33:31 +0000
Message-ID: <CEA6010B-BAB8-4533-A582-8A4F95BEA3E9@checkpoint.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com>
In-Reply-To: <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [194.29.34.101]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 11d7dbc9e3ddd0700811709dc1c6bb566573d70621
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4A84C4D851041B45B07D3AE95FCB6D36@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: S Moonesamy <sm+ietf@elandsys.com>, "<ietf@ietf.org>" <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: Thu, 27 Jun 2013 10:33:59 -0000

On Jun 27, 2013, at 1:03 PM, "Eggert, Lars" <lars@netapp.com> wrote:

> Hi,
>=20
> Section 2 says:
>   RFC 3777 [RFC3777], Section 5, "Nominating Committee Operation",
>   Paragraph 1 of Rule 14, is replaced as follows:
>=20
>      Members of the IETF community must have attended at least 3 of
>      last 5 IETF meetings remotely or in person including at least 1 of
>      the 5 last IETF meetings in person in order to volunteer.
>=20
> A few questions:
>=20
> (1) How do you define "remote attendance"?
>=20
> (2) How does the secretariat determine whether someone has remotely atten=
ded? (Based on whatever definition of remote attendance you have in mind.)

When we started having one day passes, the question was raised about whethe=
r attending on a one day pass "counts" for NomCom eligibility. If I remembe=
r correctly the answer was no. So we couldn't let listening in on one sessi=
on count, right? =20

I guess you can prove attendance by Jabber log, but that's not really helpf=
ul IMO.

Yoav=

From randy@psg.com  Thu Jun 27 03:38:59 2013
Return-Path: <randy@psg.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 5E96D21F9BB7 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 03:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 MtNyyqhvSZ7M for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 03:38:59 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id EABB921F9C1B for <ietf@ietf.org>; Thu, 27 Jun 2013 03:38:51 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Us9bG-000Ojv-E2; Thu, 27 Jun 2013 10:38:50 +0000
Date: Thu, 27 Jun 2013 19:38:49 +0900
Message-ID: <m2obardeiu.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <CEA6010B-BAB8-4533-A582-8A4F95BEA3E9@checkpoint.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com> <CEA6010B-BAB8-4533-A582-8A4F95BEA3E9@checkpoint.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <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: Thu, 27 Jun 2013 10:38:59 -0000

> I guess you can prove attendance by Jabber log

as much of the acculturation happens outside of wgs, we can have the nsa
install jabber spies in the hallway.  and they log everything!

randy

From stephen.farrell@cs.tcd.ie  Thu Jun 27 03:52:06 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
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 D44A321F9CAB for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 03:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 by-OOZeEMWtl for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 03:52:02 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 4604221F9CD7 for <ietf@ietf.org>; Thu, 27 Jun 2013 03:50:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 0C32CBE53; Thu, 27 Jun 2013 11:50:36 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oGhtHczvne51; Thu, 27 Jun 2013 11:50:35 +0100 (IST)
Received: from [IPv6:2001:770:10:203:24df:5689:4b1e:394b] (unknown [IPv6:2001:770:10:203:24df:5689:4b1e:394b]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D9E9CBDDC; Thu, 27 Jun 2013 11:50:35 +0100 (IST)
Message-ID: <51CC18FB.1030409@cs.tcd.ie>
Date: Thu, 27 Jun 2013 11:50:35 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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: Thu, 27 Jun 2013 10:52:07 -0000

On 06/27/2013 10:50 AM, S Moonesamy wrote:
> Hello,
> 
> RFC 3777 specifies the process by which members of the Internet
> Architecture Board, Internet Engineering Steering Group and IETF
> Administrative Oversight Committee are selected, confirmed, and recalled.
> 
> draft-moonesamy-nomcom-eligibility proposes an update RFC 3777 to allow
> remote contributors to the IETF Standards Process to be eligible to
> serve on NomCom and sign a Recall petition (
> http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-00 ).
> 
> Could you please read the draft and comment?

I think physically attending 1 meeting might not be enough
esp. if a nomcom were selected that had a lot of folks on
who'd only ever been to one meeting. But I'm sympathetic
to the goal and am sure some qualification rule (*) could
be worked out. (Probably after about 1000 messages;-)

However, before getting into that I'd like to hear from
folks who've been on or chaired nomcoms. I know a lot of
it is done remotely, but how important is the f2f part
that happens during meetings? Would it really be ok if
say 5 voting members could never come to a meeting
whilst serving? (And I think that'd not be an unlikely
outcome.)

S.

(*) Like I said, too early to get into it, but the nomcom
selection process could also require that the voting
members collectively have been to N meetings, with each
voting member able to contribute at most M to that total.
Say with N=30 and M=4 or something, and keep running the
random selection until you get 10 voting members that
satisfy that. And if we went there, we could also require
that nomcom as a group have written a number of RFCs
perhaps or even have some folks with Jari's h-index>3
or something. We could have lots of fun with all that:-)


> 
> Regards,
> S. Moonesamy
> 
> 

From ogud@ogud.com  Thu Jun 27 04:06:40 2013
Return-Path: <ogud@ogud.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 C6EFF21F9605 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 04:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 7MtZokyaKVDb for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 04:06:36 -0700 (PDT)
Received: from smtp86.ord1c.emailsrvr.com (smtp86.ord1c.emailsrvr.com [108.166.43.86]) by ietfa.amsl.com (Postfix) with ESMTP id 38E5F21F962D for <ietf@ietf.org>; Thu, 27 Jun 2013 04:06:35 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id B13AE500F9; Thu, 27 Jun 2013 07:06:34 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 7ACED500B4;  Thu, 27 Jun 2013 07:06:34 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: The Nominating Committee Process: Eligibility
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
Date: Thu, 27 Jun 2013 07:06:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <549BEFE0-8E23-4351-A2DB-CF138AC24FBD@ogud.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: Internet Whining TF <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: Thu, 27 Jun 2013 11:06:40 -0000

On Jun 27, 2013, at 5:50 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hello,
>=20
> RFC 3777 specifies the process by which members of the Internet =
Architecture Board, Internet Engineering Steering Group and IETF =
Administrative Oversight Committee are selected, confirmed, and =
recalled.
>=20
> draft-moonesamy-nomcom-eligibility proposes an update RFC 3777 to =
allow remote contributors to the IETF Standards Process to be eligible =
to serve on NomCom and sign a Recall petition ( =
http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-00 ).
>=20
> Could you please read the draft and comment?
>=20
> Regards,
> S. Moonesamy
>=20


SM,=20
I read the draft, I think there might be some merit to this proposal but =
I think the threshold issue should be clarified.=20
What does "one of the last five mean" during an IETF meeting?=20

I think the threshold of having attended one meeting is too low, I would =
relax the rule to say something like this:
"must have attended at least 5 meetings of the last 15 and including one =
of the last 5".=20
15 meetings is 5 years, I know that is a long time, t this will allow =
people that that have been involved for a long time but have limited=20
resources to attend to participate in Nomcom/recall processes.=20

Q: do you want to limit how many "infrequent" attendees can be on Nomcom =
just like the number of people from a single organization can sign a
recall ?=20


	Olafur


From sm@elandsys.com  Thu Jun 27 04:30:27 2013
Return-Path: <sm@elandsys.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 5EB8521F9D0A for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 04:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 EplqWKlOkS8L for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 04:30:26 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A631721F9D08 for <ietf@ietf.org>; Thu, 27 Jun 2013 04:30:26 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.150.5]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5RBU87r008780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 04:30:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372332620; bh=4eTHpKU8/118IjQB5Of70S491wWnEzE5ZSAZeNi1t6g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=s4PY+yS4cVSw1WRMY/djzyiGv80HQGMGXIHQm43b81x/xc26TORPltPnlwOI+74yo ZqT5fsFwHkQWwQgLf/eQfhzVkaMw3RdpVgftQaTw7fejhz/MQ/vZnfGiwotsme2sT+ X/QqBGaPIqUEn0xt9ch4i5ZbCShIWMhZhbMeEuIM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372332620; i=@elandsys.com; bh=4eTHpKU8/118IjQB5Of70S491wWnEzE5ZSAZeNi1t6g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JHzmYNESNVMQloWXgHYxDExSw1SynoMjJ8vBQjdlB2+rXjE9i2U1IxjHvR0qINAeP xQ8kCWhsF5+hi7vv//95c0ff8TSKlpAuLKKz7HyZ3SF+24p/z5EobUupo+Ai3z7MZI NhzZ3DCVUFUoY8a3gmGn7JQgV0tt14AKGXfjF3QY=
Message-Id: <6.2.5.6.2.20130627033519.0d474338@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jun 2013 04:29:53 -0700
To: Arturo Servin <arturo.servin@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <51CC0D50.8080708@gmail.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC0D50.8080708@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Thu, 27 Jun 2013 11:30:27 -0000

Hi Arturo,
At 03:00 27-06-2013, Arturo Servin wrote:
>     I read the draft and although I like the idea I have some concerns.

Thanks for taking the time to read the draft.  I'll comment below.

>     Today it is possible to verify that somebody attended to an IETF
>meeting. You have to register, pay and collect your badge. However, in
>remote participation we do not have mechanisms to verify that somebody
>attended to a session.

I am aware of a case where the person attending the IETF meeting is 
not the one who's name is on the badge.  I don't think that there was 
any malice or that it is a problem as that person will not game the system.

>     Even, if we had a registration similar to the face to face meetings,
>it would be difficult to verify that the people attended to a session
>remotely (even if you correlated registry vs. jabber/webex logs it would
>be difficult to know if it is really the person registred, somebody else
>or even a bot). I guess that there would be many ways to game the system.

I do not wish to suggest having registration.  The IETF does not 
require registration to participate in working group discussions.  I 
agree that there can be many ways to game the system.

I will quote the second paragraph of the Introduction section of the draft:

   "The IETF Trust considers any submission to the IETF intended by the
    Contributor for publication as all or part of an Internet-Draft or
    RFC and any statement made within the context of an IETF activity
    [RFC5378].  Such statements include oral statements in IETF sessions
    as well as written and electronic communications, made through a
    Jabber room."

It would be a serious issue, in my opinion, if the IETF cannot 
identify its contributors.  There are people who currently contribute 
through Jabber.  It has never been considered as a problem.

>     As I said I like the idea and I think that we should try to make it
>work. I do not know if all the locks and tools to protect the system
>against some sort of abuse should be in the draft or not, but we should
>address those (before or in parallel with adopting/working on the draft.)

I agree that you and I should try to make it work.  One of the 
problems of putting all the details in a document is that we lose the 
flexibility to, for example, address some sort of abuse that we did 
not specify clearly at the time the document was written.  I would 
not look for locks and tools to protect the system; I would look for 
something else.

Regards,
S. Moonesamy 


From arturo.servin@gmail.com  Thu Jun 27 04:44:28 2013
Return-Path: <arturo.servin@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 B01E621F9BBE for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 04:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Gk9f2KDPTfdf for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 04:44:28 -0700 (PDT)
Received: from mail-ee0-x231.google.com (mail-ee0-x231.google.com [IPv6:2a00:1450:4013:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id DCA0521F979E for <ietf@ietf.org>; Thu, 27 Jun 2013 04:44:27 -0700 (PDT)
Received: by mail-ee0-f49.google.com with SMTP id b57so332315eek.8 for <ietf@ietf.org>; Thu, 27 Jun 2013 04:44:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=XsAjdXSPgS9W+sBgBizWjQd/r1QltJwx6JOfwYA505Q=; b=cQ8CGqGt8dtoJJup8N7sBFTbyn4Vqx9cHCZphKq1mXAV1f3EJQmvmw9cfC88XBLe2s axb+YOpi1Mkb+krL5Si+nyFKRIfJRXmkz4y6VvtNntXG2qYUkUl5ZYnfBMSMcuIGMl0y HQijlSYsqANWvndSwRbD5Ah7T4CKzm9T6oVqgMVa309I/WBQAPuqnLBpn+P6AfhQ+XIh vn3hvqyx60dKeSwhuVoLZWqNFCYq4Xo+8AJHFctivFunIFjslLoeyBNg42M81zcASpu5 w6aQFEbsqaAMqSQpLIVNtGs2hRXDaPex5RSJcFM18RzJNlk7ZroVblkvEZ5pC44pfjyp 5WwQ==
X-Received: by 10.15.98.203 with SMTP id bj51mr8776129eeb.22.1372333467044; Thu, 27 Jun 2013 04:44:27 -0700 (PDT)
Received: from [192.168.0.5] ([90.214.33.42]) by mx.google.com with ESMTPSA id b7sm3277754eef.16.2013.06.27.04.44.25 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 04:44:26 -0700 (PDT)
Message-ID: <51CC2598.3010002@gmail.com>
Date: Thu, 27 Jun 2013 12:44:24 +0100
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Thu, 27 Jun 2013 11:44:28 -0000

    I have a general question.

    What is the rationale of the requirement to attend psychically to
meetings?

    - That nomcom participants know the IETF
    - That nomcom participant know in person people appointed to IESG,
IAB, etc
    - To avoid game/abuse the system by an organization?

    etc.

    I think that something that the draft need to say is why we need to
change the requirement, is it obsolete? why?

Regards,
as

   
On 6/27/13 10:50 AM, S Moonesamy wrote:
> Hello,
>
> RFC 3777 specifies the process by which members of the Internet
> Architecture Board, Internet Engineering Steering Group and IETF
> Administrative Oversight Committee are selected, confirmed, and recalled.
>
> draft-moonesamy-nomcom-eligibility proposes an update RFC 3777 to
> allow remote contributors to the IETF Standards Process to be eligible
> to serve on NomCom and sign a Recall petition (
> http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-00 ).
>
> Could you please read the draft and comment?
>
> Regards,
> S. Moonesamy


From Ted.Lemon@nominum.com  Thu Jun 27 04:59:51 2013
Return-Path: <Ted.Lemon@nominum.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 274EB21F9CD8 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 04:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.508
X-Spam-Level: 
X-Spam-Status: No, score=-106.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 g+a82cUPsL1n for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 04:59:44 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id 6A20621F9BF3 for <ietf@ietf.org>; Thu, 27 Jun 2013 04:59:44 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKUcwpL3jWLIHy1DIT1VQfxNbDucii6fcX@postini.com; Thu, 27 Jun 2013 04:59:44 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9E9FB1B81B0 for <ietf@ietf.org>; Thu, 27 Jun 2013 04:59:43 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 54B9919005D; Thu, 27 Jun 2013 04:59:42 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 27 Jun 2013 04:59:42 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
Thread-Topic: The Nominating Committee Process: Eligibility
Thread-Index: AQHOcxvyxXO9Q4sQjkCMj5JqOh7SBJlJ5ngAgAAERYA=
Date: Thu, 27 Jun 2013 11:59:41 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751EE1AD@mbx-01.win.nominum.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC2598.3010002@gmail.com>
In-Reply-To: <51CC2598.3010002@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <68CD69B0C6594949B45234F10BF06957@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <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: Thu, 27 Jun 2013 11:59:51 -0000

On Jun 27, 2013, at 7:44 AM, Arturo Servin <arturo.servin@gmail.com> wrote:
>    What is the rationale of the requirement to attend psychically to
> meetings?

Acculturation: the opportunity over time to absorb the IETF culture and bec=
ome a part of it.  The other points you raised are valid, but this is the m=
ain thing.

I think acculturation is possible for remote attendees in theory, but not w=
ith the current level of support for off-site participation=97while what we=
 have is great for helping people to participate in selected working group =
meetings, it doesn't provide anything like the experience of an on-site par=
ticipant.


From arturo.servin@gmail.com  Thu Jun 27 05:06:34 2013
Return-Path: <arturo.servin@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 9388721F9A50 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 05:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 LYZ-xK2wmWeV for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 05:06:34 -0700 (PDT)
Received: from mail-ee0-x233.google.com (mail-ee0-x233.google.com [IPv6:2a00:1450:4013:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id DA46221F99AA for <ietf@ietf.org>; Thu, 27 Jun 2013 05:06:33 -0700 (PDT)
Received: by mail-ee0-f51.google.com with SMTP id e52so348457eek.24 for <ietf@ietf.org>; Thu, 27 Jun 2013 05:06:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=pahIn1ol0V9DbTfRoxVNVkbZpeFk8cjYSTtq7Eftu7c=; b=ErZTFXWKP34I3oRXfZubCeSa0I31iisQQpP0YGXsgYhwv33u6PFKUZ5CHtNBbJmv7a 9Lvrk6nY+8glnI9ZsJSozmMHu8MOml8Uuv07kLl5vfD8ty7uVK+WnsUZ1A7B9nD8miZV X6sf0O+4jyjwO7G3JjirJbZK5wQauvu3pKqDkNQPvIEWakY5Q+nq31E9CX4Xgb4YRW4d aUM4Ky283XvkYfqaHXylEh/TmNPWmRKscAibd/sP6u79zcZgZkM9f9ppvtL8QvttAOKJ eac68ckIrh0ro8pPOedzZDMOrCIIg8jyF9iTys50DuI+XYa2WglZg4jUa5Bkm6vwTM6P mbog==
X-Received: by 10.14.38.198 with SMTP id a46mr8601604eeb.42.1372334785001; Thu, 27 Jun 2013 05:06:25 -0700 (PDT)
Received: from [192.168.0.5] ([90.214.33.42]) by mx.google.com with ESMTPSA id w43sm3465840eez.6.2013.06.27.05.06.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 05:06:23 -0700 (PDT)
Message-ID: <51CC2ABE.9090101@gmail.com>
Date: Thu, 27 Jun 2013 13:06:22 +0100
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC2598.3010002@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751EE1AD@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751EE1AD@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: "<ietf@ietf.org>" <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: Thu, 27 Jun 2013 12:06:34 -0000

Ted,

    Thanks.

    Perhaps then Olafur recommendation:

"must have attended at least 5 meetings of the last 15 and including one of the last 5". 

	may be a good compromise. Also, I would suggest "one of the last 6" (instead of 5). I guess in two years the IETF does not change too much.

Regards,
as

On 6/27/13 12:59 PM, Ted Lemon wrote:
> On Jun 27, 2013, at 7:44 AM, Arturo Servin <arturo.servin@gmail.com> wrote:
>>    What is the rationale of the requirement to attend psychically to
>> meetings?
> Acculturation: the opportunity over time to absorb the IETF culture and become a part of it.  The other points you raised are valid, but this is the main thing.
>
> I think acculturation is possible for remote attendees in theory, but not with the current level of support for off-site participation—while what we have is great for helping people to participate in selected working group meetings, it doesn't provide anything like the experience of an on-site participant.


From Ted.Lemon@nominum.com  Thu Jun 27 05:11:21 2013
Return-Path: <Ted.Lemon@nominum.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 E7B7621F918F for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 05:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.518
X-Spam-Level: 
X-Spam-Status: No, score=-106.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 T6SHM5FvMKEd for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 05:11:15 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id 3C11B21F8FC4 for <ietf@ietf.org>; Thu, 27 Jun 2013 05:11:15 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUcwr4w+DtDVrBKrL0jM+qkTm0IpGxJFU@postini.com; Thu, 27 Jun 2013 05:11:15 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id DCB171B81B0 for <ietf@ietf.org>; Thu, 27 Jun 2013 05:11:14 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D398019005D; Thu, 27 Jun 2013 05:11:14 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 27 Jun 2013 05:11:08 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
Thread-Topic: The Nominating Committee Process: Eligibility
Thread-Index: AQHOcxvyxXO9Q4sQjkCMj5JqOh7SBJlJ5ngAgAAERYCAAAHeAIAAAVUA
Date: Thu, 27 Jun 2013 12:11:08 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751EE243@mbx-01.win.nominum.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC2598.3010002@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751EE1AD@mbx-01.win.nominum.com> <51CC2ABE.9090101@gmail.com>
In-Reply-To: <51CC2ABE.9090101@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <C904106D7121F84CAEFB574B1FD6D2AD@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <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: Thu, 27 Jun 2013 12:11:22 -0000

On Jun 27, 2013, at 8:06 AM, Arturo Servin <arturo.servin@gmail.com> wrote:
> "must have attended at least 5 meetings of the last 15 and including one =
of the last 5".=20
>=20
> 	may be a good compromise. Also, I would suggest "one of the last 6" (ins=
tead of 5). I guess in two years the IETF does not change too much.

I think Olafur's suggestion is a good one, and I tend to support it, but be=
ar in mind that the problem is not the IETF changing: it's the former atten=
dee changing.   We want them to return to the well from time to time to tak=
e another deep draught, so that they do not lose the unique flavor that the=
 waters bear.


From jari.arkko@piuha.net  Thu Jun 27 05:20:56 2013
Return-Path: <jari.arkko@piuha.net>
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 6FA6521F9CDF; Thu, 27 Jun 2013 05:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 rMH5KhDofpzk; Thu, 27 Jun 2013 05:20:51 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 3E17421F9CDC; Thu, 27 Jun 2013 05:20:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 61B802CC48; Thu, 27 Jun 2013 15:20:32 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HesJlnkmX_R7; Thu, 27 Jun 2013 15:20:31 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 127E82CC3C; Thu, 27 Jun 2013 15:20:30 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC74398261AAE61@nambx08.corp.adobe.com>
Date: Thu, 27 Jun 2013 08:20:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <23465268-C5EB-42E7-BC98-0B300BBCCDCC@piuha.net>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com> <D9D602D39A98E34D9C43E965BEC74398261AAE1D@nambx08.corp.adobe.com> <3F184F54-61DA-44D3-A705-A12F224E716A@nostrum.com> <D9D602D39A98E34D9C43E965BEC74398261AAE61@nambx08.corp.adobe.com>
To: Michael Thornburgh <mthornbu@adobe.com>
X-Mailer: Apple Mail (2.1508)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion 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: Thu, 27 Jun 2013 12:20:56 -0000

Ben, thank you very much for the review, and Michael, thank you for =
answering and addressing the issues.=20

I am still concerned about the crypto profile question, however. I'd =
like to understand what the lack of a profile specification means for =
interoperability and the ability of others to use this spec.

Jari


From jcurran@istaff.org  Thu Jun 27 05:36:40 2013
Return-Path: <jcurran@istaff.org>
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 55F6A21F9929 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 05:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 4dAH5iepvyaT for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 05:36:30 -0700 (PDT)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by ietfa.amsl.com (Postfix) with ESMTP id 8827521F979E for <ietf@ietf.org>; Thu, 27 Jun 2013 05:36:29 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1UsBR6-000L8i-Vx; Thu, 27 Jun 2013 12:36:29 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/ZIcKiCAJovSDRLkuSDWb0
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: The Nominating Committee Process: Eligibility
From: John Curran <jcurran@istaff.org>
In-Reply-To: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
Date: Thu, 27 Jun 2013 08:36:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA275766-42C8-4C70-B0A1-17DE2C6DD7BA@istaff.org>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: 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: Thu, 27 Jun 2013 12:36:40 -0000

On Jun 27, 2013, at 5:50 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hello,
>=20
> RFC 3777 specifies the process by which members of the Internet =
Architecture Board, Internet Engineering Steering Group and IETF =
Administrative Oversight Committee are selected, confirmed, and =
recalled.
>=20
> draft-moonesamy-nomcom-eligibility proposes an update RFC 3777 to =
allow remote contributors to the IETF Standards Process to be eligible =
to serve on NomCom and sign a Recall petition ( =
http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-00 ).
>=20
> Could you please read the draft and comment?

SM -=20

I have read the draft, and believe that it moves the qualification to=20
serve on the NomCom in the right direction.  Long-term, it would be =
ideal=20
if remote IETF participation was equivalent (both as an experience and =
as=20
a NomCom qualification) to in-person IETF participation.

Noting agreement in the direction, the reality of remote participation=20=

today is somewhat different.  In recent years, I have been a frequent=20
remote participant and occasional on-site participant, and while it is
possible to effectively contribute to working group efforts remotely,=20
such success is predicated on knowing quite a bit about IETF processes=20=

and workflow, and it not clear to me that a remote participant picks=20
up the necessary background at anywhere near the same rate as on-site=20
participants.  As a result, I am concerned that the proposed language=20
in draft wouldn't necessarily provide for experienced IETF participants=20=

in the NomCom, and/or those who have well-informed insight into what=20
makes for good IAB/IESG/IAOC members.

Note also that the proposed language also increases the possibility of=20=

"capture" (i.e. the ability of an single organization to inappropriately
skew the outcome of the process) in that a relatively large pool of=20
remote participants could quickly be made NomCom-eligible by having them=20=

attend the very next IETF meeting, and then all volunteered to serve on=20=

the NomCom.  While this is not a particularly likely course for a party
not happy with the IETF, it is an aspect to be considered in the NomCom
processes.

With an view towards finding a middle ground, would it be possible to
change your proposed text from:

      "Members of the IETF community must have attended at least 3 of
      last 5 IETF meetings remotely or in person including at least 1=20
      of the 5 last IETF meetings in person in order to volunteer."

to this:

      "Members of the IETF community must have attended at least 3 of
      last 5 IETF meetings remotely or in person including at least _2_=20=

      of the 5 last IETF meetings in person in order to volunteer."

The change from 1 to 2 meetings being in-person significantly reduces =
the
potential risk of capture while also increasing the exposure level of
NomCom volunteers to dynamics that occur in the hallways and between the
formal IETF working group sessions.  The net result recognizes the value
of remote participation, moves in the right direction, but does so at a
more moderate pace than you originally propose.

Thoughts?
/John

Disclaimers:  My views alone.  NomCom '95 Chair (back before any NomCom
              procedures existed... :-)


From alejandroacostaalamo@gmail.com  Thu Jun 27 05:42:54 2013
Return-Path: <alejandroacostaalamo@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 838F521F9AAF; Thu, 27 Jun 2013 05:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.846
X-Spam-Level: 
X-Spam-Status: No, score=-0.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753]
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 vEjh5pcgHHCY; Thu, 27 Jun 2013 05:42:54 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id A3DD321F9A84; Thu, 27 Jun 2013 05:42:49 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id x12so1448336ief.12 for <multiple recipients>; Thu, 27 Jun 2013 05:42:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-rim-org-msg-ref-id:message-id:content-transfer-encoding:reply-to :x-priority:references:in-reply-to:sensitivity:importance:subject:to :cc:from:date:content-type:mime-version; bh=mOXKFeCbZd99eWmtDuNuAwDyRG2YmZ1BTIyiLoOrUg8=; b=Qai1VfLQK9+oT6CdbW7G2hS7iK1siMnCKOVk3yuN20XyP8xQkYkq+1ZNnJxwprqPTg R0Lgp35bAeFIGE80KemVrBIMHV1Jt9DswSs2pqP17HVr+46/JgeogtvGaMnB6oQRzwzL nrzX4hruJGq3XQm+q3Ouekw9ioaciOY4q6x0PRtDnFIhf41+s4VTKwS93o6CI6lmHsWs MtpKEr0G6RTI5NWGb81EMs6RZ0loPkFiYoMRZskz1hBvP4aR2YUBODq7gE4cq4M4+a0l gSQpR7Mq9Vxkg2Zn4/I2Rn/G3ELVL6pkVrzMiNzKOZYZh2ZI16Z4c2uGMmRZ5zvuZHA/ QADw==
X-Received: by 10.50.3.37 with SMTP id 5mr6474742igz.0.1372336969220; Thu, 27 Jun 2013 05:42:49 -0700 (PDT)
Received: from 172.29.196.190 (bda-74-82-80-161.bis6.us.blackberry.com. [74.82.80.161]) by mx.google.com with ESMTPSA id nt6sm12722648igb.10.2013.06.27.05.42.48 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 27 Jun 2013 05:42:48 -0700 (PDT)
X-rim-org-msg-ref-id: 698352922
Message-ID: <698352922-1372336945-cardhu_decombobulator_blackberry.rim.net-675039072-@b17.c3.bise6.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <549BEFE0-8E23-4351-A2DB-CF138AC24FBD@ogud.com>
In-Reply-To: <549BEFE0-8E23-4351-A2DB-CF138AC24FBD@ogud.com>
Sensitivity: Normal
Importance: Normal
Subject: Re: The Nominating Committee Process: Eligibility
To: "Olafur Gudmundsson" <ogud@ogud.com>, ietf-bounces@ietf.org, "S Moonesamy" <sm+ietf@elandsys.com>
From: alejandroacostaalamo@gmail.com
Date: Thu, 27 Jun 2013 12:42:27 +0000
Content-Type: text/plain
MIME-Version: 1.0
Cc: Internet Whining TF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: alejandroacostaalamo@gmail.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: Thu, 27 Jun 2013 12:42:54 -0000

SGksDQogIEZpcnN0LCBhcyBhIGNvbW1lbnQsIEkgZ3Vlc3MgdGhlcmUgaXMgcGVvcGxlIHdobyBm
b2xsb3cgbW9yZSBJRVRGIHJlbW90ZWx5IHRoYW4gb3RoZXIgaW4gcGxhY2UuDQogIFNlY29uZCwg
SSBsaWtlIHRoaXMgaWRlYSBvZiBjaGFuZ2luZyB0aGUgdGhyZXNob2xkLg0KICBUaGlyZCwgSW4g
dGhlIG90aGVyIGhhbmQsIHNpbmNlIHRoZXJlIGFyZSBzZXZlcmFsIHBvc2l0aW9ucyB0aGF0IGFy
ZSBmaWxsIHVzaW5nIHRoaXMgUkZDIG1heWJlIHdlIGNhbiBwbGFjZSBhIHRlc3RiZWQuIDUwJSBj
YW4gYmUgZmlsbCB1c2luZyB0aGUgY3VycmVudCB3YXkgYW5kIDUwJSB1c2luZyB0aGUgcHJvcG9z
ZWQgd2F5LCBzb3VuZHMgY3JhenkgYnV0IGl0IG1pZ2h0IGJlIGEgZ29vZCBiZWdpbm5pbmcuDQoN
ClRoYW5rcywNCg0KQWxlamFuZHJvLA0KDQoNCkVzdGUgbWVuc2FqZSBoYSBzaWRvIGVudmlhZG8g
Z3JhY2lhcyBhbCBzZXJ2aWNpbyBCbGFja0JlcnJ5IGRlIE1vdmlsbmV0DQoNCi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBPbGFmdXIgR3VkbXVuZHNzb24gPG9ndWRAb2d1ZC5jb20+
DQpTZW5kZXI6IGlldGYtYm91bmNlc0BpZXRmLm9yZw0KRGF0ZTogVGh1LCAyNyBKdW4gMjAxMyAw
NzowNjozNiANClRvOiBTIE1vb25lc2FteTxzbStpZXRmQGVsYW5kc3lzLmNvbT4NCkNjOiBJbnRl
cm5ldCBXaGluaW5nIFRGPGlldGZAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogVGhlIE5vbWluYXRp
bmcgQ29tbWl0dGVlIFByb2Nlc3M6IEVsaWdpYmlsaXR5DQoNCg0KT24gSnVuIDI3LCAyMDEzLCBh
dCA1OjUwIEFNLCBTIE1vb25lc2FteSA8c20raWV0ZkBlbGFuZHN5cy5jb20+IHdyb3RlOg0KDQo+
IEhlbGxvLA0KPiANCj4gUkZDIDM3Nzcgc3BlY2lmaWVzIHRoZSBwcm9jZXNzIGJ5IHdoaWNoIG1l
bWJlcnMgb2YgdGhlIEludGVybmV0IEFyY2hpdGVjdHVyZSBCb2FyZCwgSW50ZXJuZXQgRW5naW5l
ZXJpbmcgU3RlZXJpbmcgR3JvdXAgYW5kIElFVEYgQWRtaW5pc3RyYXRpdmUgT3ZlcnNpZ2h0IENv
bW1pdHRlZSBhcmUgc2VsZWN0ZWQsIGNvbmZpcm1lZCwgYW5kIHJlY2FsbGVkLg0KPiANCj4gZHJh
ZnQtbW9vbmVzYW15LW5vbWNvbS1lbGlnaWJpbGl0eSBwcm9wb3NlcyBhbiB1cGRhdGUgUkZDIDM3
NzcgdG8gYWxsb3cgcmVtb3RlIGNvbnRyaWJ1dG9ycyB0byB0aGUgSUVURiBTdGFuZGFyZHMgUHJv
Y2VzcyB0byBiZSBlbGlnaWJsZSB0byBzZXJ2ZSBvbiBOb21Db20gYW5kIHNpZ24gYSBSZWNhbGwg
cGV0aXRpb24gKCBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1tb29uZXNhbXktbm9t
Y29tLWVsaWdpYmlsaXR5LTAwICkuDQo+IA0KPiBDb3VsZCB5b3UgcGxlYXNlIHJlYWQgdGhlIGRy
YWZ0IGFuZCBjb21tZW50Pw0KPiANCj4gUmVnYXJkcywNCj4gUy4gTW9vbmVzYW15DQo+IA0KDQoN
ClNNLCANCkkgcmVhZCB0aGUgZHJhZnQsIEkgdGhpbmsgdGhlcmUgbWlnaHQgYmUgc29tZSBtZXJp
dCB0byB0aGlzIHByb3Bvc2FsIGJ1dCBJIHRoaW5rIHRoZSB0aHJlc2hvbGQgaXNzdWUgc2hvdWxk
IGJlIGNsYXJpZmllZC4gDQpXaGF0IGRvZXMgIm9uZSBvZiB0aGUgbGFzdCBmaXZlIG1lYW4iIGR1
cmluZyBhbiBJRVRGIG1lZXRpbmc/IA0KDQpJIHRoaW5rIHRoZSB0aHJlc2hvbGQgb2YgaGF2aW5n
IGF0dGVuZGVkIG9uZSBtZWV0aW5nIGlzIHRvbyBsb3csIEkgd291bGQgcmVsYXggdGhlIHJ1bGUg
dG8gc2F5IHNvbWV0aGluZyBsaWtlIHRoaXM6DQoibXVzdCBoYXZlIGF0dGVuZGVkIGF0IGxlYXN0
IDUgbWVldGluZ3Mgb2YgdGhlIGxhc3QgMTUgYW5kIGluY2x1ZGluZyBvbmUgb2YgdGhlIGxhc3Qg
NSIuIA0KMTUgbWVldGluZ3MgaXMgNSB5ZWFycywgSSBrbm93IHRoYXQgaXMgYSBsb25nIHRpbWUs
IHQgdGhpcyB3aWxsIGFsbG93IHBlb3BsZSB0aGF0IHRoYXQgaGF2ZSBiZWVuIGludm9sdmVkIGZv
ciBhIGxvbmcgdGltZSBidXQgaGF2ZSBsaW1pdGVkIA0KcmVzb3VyY2VzIHRvIGF0dGVuZCB0byBw
YXJ0aWNpcGF0ZSBpbiBOb21jb20vcmVjYWxsIHByb2Nlc3Nlcy4gDQoNClE6IGRvIHlvdSB3YW50
IHRvIGxpbWl0IGhvdyBtYW55ICJpbmZyZXF1ZW50IiBhdHRlbmRlZXMgY2FuIGJlIG9uIE5vbWNv
bSBqdXN0IGxpa2UgdGhlIG51bWJlciBvZiBwZW9wbGUgZnJvbSBhIHNpbmdsZSBvcmdhbml6YXRp
b24gY2FuIHNpZ24gYQ0KcmVjYWxsID8gDQoNCg0KCU9sYWZ1cg0KDQo=


From lear@cisco.com  Thu Jun 27 05:48:36 2013
Return-Path: <lear@cisco.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 593DD21F9C41 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 05:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.864
X-Spam-Level: 
X-Spam-Status: No, score=-109.864 tagged_above=-999 required=5 tests=[AWL=0.735, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 GiqSHMxuZbFZ for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 05:48:31 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 5B1DD21F9C3A for <ietf@ietf.org>; Thu, 27 Jun 2013 05:48:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4005; q=dns/txt; s=iport; t=1372337311; x=1373546911; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=P2J/p50aMI3en5D2Bros2fKlHj00u72r7ILkRdwAu/I=; b=iUAWNSJ6LvslgcNfl/i+tud2haYmCYpHNlHuA1evdxiwYe/YI4gPR9zr EJMI5rQy6Z8WciCB04cpPi+muECybYkhuwACv0EOfT/FKDDIG1kZX7fFt 0KMHbk+vrOrfQVAgEWMY0FI9A3IzwVe+N8EakucWA7NqzAlwVRLQMnlyi M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0FAAQ0zFGQ/khN/2dsb2JhbABbgwkxg1C8AXwWdIIjAQEBAQMOFUIJCgEQCw4EBgICBRYLAgIJAwIBAgErDA4GDQEFAgEBEId6DKkOkTeBJo4vB4JPgRYDk3ODUoEpkByDEzo
X-IronPort-AV: E=Sophos;i="4.87,952,1363132800"; d="scan'208";a="14564550"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 27 Jun 2013 12:48:26 +0000
Received: from mctiny.local ([10.61.223.240]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r5RCmOA2025466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 12:48:24 GMT
Message-ID: <51CC3498.8060904@cisco.com>
Date: Thu, 27 Jun 2013 14:48:24 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: John Curran <jcurran@istaff.org>
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <FA275766-42C8-4C70-B0A1-17DE2C6DD7BA@istaff.org>
In-Reply-To: <FA275766-42C8-4C70-B0A1-17DE2C6DD7BA@istaff.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: S Moonesamy <sm+ietf@elandsys.com>, 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: Thu, 27 Jun 2013 12:48:36 -0000

John,

I agree with everything you wrote.  I especially applaud SM for getting
out there with new ideas, and I like the idea of opening up eligibility
a bit more.  John's proposed change would reduce risk of capture.  I do
think that risk is also mitigated through other mechanisms (like
limiting the number of people with the same affiliation from joining the
NOMCOM), but Ted's point is also important, that people have some feel
for how the IETF operates, both in person and on mailing list.  John's
proposal seems to strike a good balance.

Eliot

On 6/27/13 2:36 PM, John Curran wrote:
> On Jun 27, 2013, at 5:50 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
>
>> Hello,
>>
>> RFC 3777 specifies the process by which members of the Internet Architecture Board, Internet Engineering Steering Group and IETF Administrative Oversight Committee are selected, confirmed, and recalled.
>>
>> draft-moonesamy-nomcom-eligibility proposes an update RFC 3777 to allow remote contributors to the IETF Standards Process to be eligible to serve on NomCom and sign a Recall petition ( http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-00 ).
>>
>> Could you please read the draft and comment?
> SM - 
>
> I have read the draft, and believe that it moves the qualification to 
> serve on the NomCom in the right direction.  Long-term, it would be ideal 
> if remote IETF participation was equivalent (both as an experience and as 
> a NomCom qualification) to in-person IETF participation.
>
> Noting agreement in the direction, the reality of remote participation 
> today is somewhat different.  In recent years, I have been a frequent 
> remote participant and occasional on-site participant, and while it is
> possible to effectively contribute to working group efforts remotely, 
> such success is predicated on knowing quite a bit about IETF processes 
> and workflow, and it not clear to me that a remote participant picks 
> up the necessary background at anywhere near the same rate as on-site 
> participants.  As a result, I am concerned that the proposed language 
> in draft wouldn't necessarily provide for experienced IETF participants 
> in the NomCom, and/or those who have well-informed insight into what 
> makes for good IAB/IESG/IAOC members.
>
> Note also that the proposed language also increases the possibility of 
> "capture" (i.e. the ability of an single organization to inappropriately
> skew the outcome of the process) in that a relatively large pool of 
> remote participants could quickly be made NomCom-eligible by having them 
> attend the very next IETF meeting, and then all volunteered to serve on 
> the NomCom.  While this is not a particularly likely course for a party
> not happy with the IETF, it is an aspect to be considered in the NomCom
> processes.
>
> With an view towards finding a middle ground, would it be possible to
> change your proposed text from:
>
>       "Members of the IETF community must have attended at least 3 of
>       last 5 IETF meetings remotely or in person including at least 1 
>       of the 5 last IETF meetings in person in order to volunteer."
>
> to this:
>
>       "Members of the IETF community must have attended at least 3 of
>       last 5 IETF meetings remotely or in person including at least _2_ 
>       of the 5 last IETF meetings in person in order to volunteer."
>
> The change from 1 to 2 meetings being in-person significantly reduces the
> potential risk of capture while also increasing the exposure level of
> NomCom volunteers to dynamics that occur in the hallways and between the
> formal IETF working group sessions.  The net result recognizes the value
> of remote participation, moves in the right direction, but does so at a
> more moderate pace than you originally propose.
>
> Thoughts?
> /John
>
> Disclaimers:  My views alone.  NomCom '95 Chair (back before any NomCom
>               procedures existed... :-)
>
>
>


From fluffy@iii.ca  Thu Jun 27 06:09:00 2013
Return-Path: <fluffy@iii.ca>
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 7AE1221F9D5F for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 TXbFctIR2i1Z for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:08:46 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 5147321F93B9 for <ietf@ietf.org>; Thu, 27 Jun 2013 06:08:45 -0700 (PDT)
Received: from rtp-vpn4-658.cisco.com (unknown [64.102.254.33]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A9E5522E256 for <ietf@ietf.org>; Thu, 27 Jun 2013 09:08:35 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: The Nominating Committee Process: Eligibility
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
Date: Thu, 27 Jun 2013 09:08:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8880FC90-ECE0-405C-9750-9D0A0E6ABC72@iii.ca>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1508)
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: Thu, 27 Jun 2013 13:09:00 -0000

I have attended some IETF meetings remotely and I am not in favor of =
this change.


On Jun 27, 2013, at 5:50 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hello,
>=20
> RFC 3777 specifies the process by which members of the Internet =
Architecture Board, Internet Engineering Steering Group and IETF =
Administrative Oversight Committee are selected, confirmed, and =
recalled.
>=20
> draft-moonesamy-nomcom-eligibility proposes an update RFC 3777 to =
allow remote contributors to the IETF Standards Process to be eligible =
to serve on NomCom and sign a Recall petition ( =
http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-00 ).
>=20
> Could you please read the draft and comment?
>=20
> Regards,
> S. Moonesamy
>=20


From mcr@sandelman.ca  Thu Jun 27 06:19:47 2013
Return-Path: <mcr@sandelman.ca>
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 C3EEE21F9DB2 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 a+aBTVzAqg2V for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:19:43 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id A87FA21F9DB3 for <ietf@ietf.org>; Thu, 27 Jun 2013 06:19:39 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 913F92025C; Thu, 27 Jun 2013 10:23:39 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 8F41E63A7C; Thu, 27 Jun 2013 09:18:25 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 7CA4263A5E; Thu, 27 Jun 2013 09:18:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 27 Jun 2013 09:18:25 -0400
Message-ID: <8846.1372339105@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: 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: Thu, 27 Jun 2013 13:19:47 -0000

--=-=-=



I have not read the thread yet, on purpose.
As a person who has done significant remote participation myself, and has also
observed the difficulty new people have in understanding how things fit
together, I can not support your specific proposal, but I support the idea.

I would suggest:

2.  Updated Text from RFC 3777

   RFC 3777 [RFC3777], Section 5, "Nominating Committee Operation",
   Paragraph 1 of Rule 14, is replaced as follows:

      Members of the IETF community become eligible for the NomCom by
      having attended at least 3 of the last 7 IETF meetings in person.

      Once a person has become eligible for NomCom, they retain their
      elibility to NomCom by attending at least 1 of the last 4 IETF meetings
      in person, and at least 3 of the last 5 meetings in person or remotely.

      Should a person lose eligibility for NomCom, they return to not-eligible.

(We could, true to form, describe this as a state machine with three states,
or even a simpler to write in Verilog one with 7-8 states)
===

I have raised the bar slightly over your requirements in the form of still
requiring 3 meetings to be attended, but lengthening the time to 7 meetings,
such that a person who attends one meeting/year, if they do it right, can
become eligible easily.  I feel perhaps that in the becoming eligible
process, that some of the 4 meetings not-attended should be clearly attended
remotely, but I'm sure how to specify that.

I have lowered the bar to remain eligible such that a person who not travel
for 12 months (such as someone on maternity/paternity leave. Civilized
countries get at least 1 year..) could remain eligible.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [





--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUcw7noqHRg3pndX9AQJohAP/Vv3Gjfr0dv1Ezn91ksL6KtVjp6VGpOo/
u48sIW2hJfFr+fDLLe1IV3f7Ib9FFfXMX223YTs6ZIGKXg6vdgO+J+e5nqlENHUf
zX1KE88IjPC0rlsNZSO+FK7qQc4BGTamTOiN1zGg35f5SpgnCFYrzkDl0rD1ENvw
EUQOD/R6SOE=
=M7+3
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Thu Jun 27 06:22:16 2013
Return-Path: <mcr@sandelman.ca>
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 B156221F9A97 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:22:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 hzcF7+7AMchb for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:22:15 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 757BF21F9A9B for <ietf@ietf.org>; Thu, 27 Jun 2013 06:22:12 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5E1432025C; Thu, 27 Jun 2013 10:26:22 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 6164163A7C; Thu, 27 Jun 2013 09:21:08 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 508F663A5E; Thu, 27 Jun 2013 09:21:08 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <51CC0D50.8080708@gmail.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC0D50.8080708@gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 27 Jun 2013 09:21:08 -0400
Message-ID: <9673.1372339268@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: 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: Thu, 27 Jun 2013 13:22:16 -0000

--=-=-=


Arturo Servin <arturo.servin@gmail.com> wrote:
    > Today it is possible to verify that somebody attended to an IETF
    > meeting. You have to register, pay and collect your badge. However, in
    > remote participation we do not have mechanisms to verify that somebody
    > attended to a session.

We need to have registration for remote participation, even if we charge
zero.   I believe that perhaps we need to provide some magic token in jabber
or in the NoteWell slide, that needs to be used by remote participants to
check-in. They have to do that during the meeting itself.

I also ask whether remote participation on the plenary should be "mandatory"

We also need to permit judgement calls.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUcw8QYqHRg3pndX9AQK6eAP/ZowSWSoJ2rBFy23KsiOdHpAEXJ/hc55m
s8rkG172xUJyBO98OVgkgcIdwU+0x4QpyhrtUi/5n1IxY3pB95nwt0AK3SrbiUcz
mALLk2zRXzGmBBGOr5D4lXuJr145BnDE7FEEe9gHgJ1/7r5Yl+t8xqDeGEvvsbH/
3WkNlq8Hkck=
=rT6B
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Thu Jun 27 06:25:44 2013
Return-Path: <mcr@sandelman.ca>
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 D4F9921F9DCD for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 dt5+K0v6VLzU for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:25:33 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 6505621F9DCB for <ietf@ietf.org>; Thu, 27 Jun 2013 06:25:30 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4B91B2025C; Thu, 27 Jun 2013 10:29:40 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 4EB9363A7C; Thu, 27 Jun 2013 09:24:26 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3EDE963A5E; Thu, 27 Jun 2013 09:24:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <51CC18FB.1030409@cs.tcd.ie>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC18FB.1030409@cs.tcd.ie>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 27 Jun 2013 09:24:26 -0400
Message-ID: <10679.1372339466@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: S Moonesamy <sm+ietf@elandsys.com>, 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: Thu, 27 Jun 2013 13:25:44 -0000

--=-=-=


Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
    > However, before getting into that I'd like to hear from
    > folks who've been on or chaired nomcoms. I know a lot of
    > it is done remotely, but how important is the f2f part
    > that happens during meetings? Would it really be ok if
    > say 5 voting members could never come to a meeting
    > whilst serving? (And I think that'd not be an unlikely
    > outcome.)

Please note two things:
1) under the original proposal and my revised one, you have
   attend in person somewhat regularly.

2) for the November meeting, the nomcom *itself* must be present.
   I think it unrealistic to think that the nomcom itself could
   be remote for that meeting.  For the summer and march meeting,
   the nomcom could be anywhere.

so, even if you are eligible, don't volunteer for the nomcom if you can't
attend the november meeting.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUcw9B4qHRg3pndX9AQKbMwQAjBr/Cg5eXIsbfp2MW+yImG7Rg5Sr+3Q8
eSNWxwNRy2AvfjieP2w+ftcZ8Iv0h1QR7berevW7YAod5Hs7U7rCOhFfUCSX7aRj
5U4Yn1ZjOAsDml3aZGgup6/xJwIgasJlHzxHy43Sxu/hB2eyHNV7SIlG+sZnmsyU
o0OuulhTUj0=
=+Waa
-----END PGP SIGNATURE-----
--=-=-=--

From stephen.farrell@cs.tcd.ie  Thu Jun 27 06:32:15 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
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 C0D5321F9DBF for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 R9Osg-ty5oH1 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:32:08 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 712C121F9DA0 for <ietf@ietf.org>; Thu, 27 Jun 2013 06:32:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id EB54FBE61; Thu, 27 Jun 2013 14:31:39 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bVY2-MLEqxhS; Thu, 27 Jun 2013 14:31:39 +0100 (IST)
Received: from [IPv6:2001:770:10:203:24df:5689:4b1e:394b] (unknown [IPv6:2001:770:10:203:24df:5689:4b1e:394b]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id CAA38BE53; Thu, 27 Jun 2013 14:31:39 +0100 (IST)
Message-ID: <51CC3EBB.5040000@cs.tcd.ie>
Date: Thu, 27 Jun 2013 14:31:39 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC18FB.1030409@cs.tcd.ie> <10679.1372339466@sandelman.ca>
In-Reply-To: <10679.1372339466@sandelman.ca>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: S Moonesamy <sm+ietf@elandsys.com>, 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: Thu, 27 Jun 2013 13:32:16 -0000

On 06/27/2013 02:24 PM, Michael Richardson wrote:
> 
> Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>     > However, before getting into that I'd like to hear from
>     > folks who've been on or chaired nomcoms. I know a lot of
>     > it is done remotely, but how important is the f2f part
>     > that happens during meetings? Would it really be ok if
>     > say 5 voting members could never come to a meeting
>     > whilst serving? (And I think that'd not be an unlikely
>     > outcome.)
> 
> Please note two things:
> 1) under the original proposal and my revised one, you have
>    attend in person somewhat regularly.
> 
> 2) for the November meeting, the nomcom *itself* must be present.

Tend to agree.

>    I think it unrealistic to think that the nomcom itself could
>    be remote for that meeting.  For the summer and march meeting,
>    the nomcom could be anywhere.

Not this year:-)

> 
> so, even if you are eligible, don't volunteer for the nomcom if you can't
> attend the november meeting.

But doesn't that run counter to one aspect of SM's otherwise
reasonable goal? (And if getting randomly picked for nomcom
implied some I* thing has to pay your way to the Nov meeting,
then this is IMO a *much* larger change proposal.)

S.

> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> 
> 

From jnc@mercury.lcs.mit.edu  Thu Jun 27 06:34:53 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
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 83C2221F9E20 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 w-5yg6XrAhOe for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:34:48 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 728A021F9D3F for <ietf@ietf.org>; Thu, 27 Jun 2013 06:34:48 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id C27F018C0B9; Thu, 27 Jun 2013 09:34:47 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: The Nominating Committee Process: Eligibility
Message-Id: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu>
Date: Thu, 27 Jun 2013 09:34:47 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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: Thu, 27 Jun 2013 13:34:53 -0000

    > From: John Curran <jcurran@istaff.org>

    > the proposed language also increases the possibility of "capture" (i.e.
    > the ability of an single organization to inappropriately skew the
    > outcome of the process) 

Why not just say directly that 'to prevent "capture", no more than X% of
the NomCom may work for a single organization' (where X is 15% or so, so
that even if a couple collude, they still can't get control).

	Noel

From akatlas@gmail.com  Thu Jun 27 06:35:39 2013
Return-Path: <akatlas@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 116A321F9E2F for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  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 CGxLsXGcsL+j for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:35:38 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 1C28821F9E2B for <ietf@ietf.org>; Thu, 27 Jun 2013 06:35:38 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id 10so1582695ied.0 for <ietf@ietf.org>; Thu, 27 Jun 2013 06:35:37 -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=VqdQof2dtHg7ogLyW5uCbl5Oku7LYn2czu7Dal634l8=; b=rnKYPrG5oIbIdx9lbL3s9ZuL5S9xW+b9SzqafYrDvatg4GpydkFY0ZfW9X07yfzrws hlHVNo11ZhrIFp7R1S3NrDwPKS1Zt57sIB6YXoAFu88XvTfIAabgVi76PFMD4P0RxEkl MCI0a03ZSmtB20OmyTvNTTTC5bm9j86wFdbveHfhkAgg2s4xRE2LH/newWieMHME/8u2 yUn7wgxZso1P+JN4DSeU1LDqFnAIA6kv9KWvXCtKQuJxroMpKrUhNQqsRTtyUuzvcWG2 P8NQ355RxABTvjdGuqRW0RGA7i1ZBApUuspvQqE5ipc1+PS/ktTXnWH+xF92TrGMuE0V 9o9w==
MIME-Version: 1.0
X-Received: by 10.50.77.80 with SMTP id q16mr4242672igw.3.1372340137715; Thu, 27 Jun 2013 06:35:37 -0700 (PDT)
Received: by 10.64.47.168 with HTTP; Thu, 27 Jun 2013 06:35:37 -0700 (PDT)
In-Reply-To: <9673.1372339268@sandelman.ca>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC0D50.8080708@gmail.com> <9673.1372339268@sandelman.ca>
Date: Thu, 27 Jun 2013 09:35:37 -0400
Message-ID: <CAG4d1rdqiYTk9VZXmn4WGCAtQPxuSvUPGQ5XsFhStJMx84WhvA@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
From: Alia Atlas <akatlas@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=047d7bdc12386b6e1404e022d6af
Cc: Arturo Servin <arturo.servin@gmail.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: Thu, 27 Jun 2013 13:35:39 -0000

--047d7bdc12386b6e1404e022d6af
Content-Type: text/plain; charset=ISO-8859-1

Just a quick aside, but having run an interim WG meeting where we did not
charge a meeting fee and knowing how significantly attendance diverged, I
would strongly support at least some meeting fee for remote attendance.
 There's also the key fact that the IETF is funded by IETF meeting fees and
ISOC.   Maybe the remote fee is scaled by region of attendee or such if
there is concern that it is burdensome.

I have attended one meeting remotely - and the experience is nothing at all
like being at IETF.  I can see modifying NomCom eligibility constraints
slightly - but I really do not think that remote attendees will have the
necessary experience and acculturation unless they have attended a number
of IETFs in person.

Having served on a NomCom a long time ago, I'd say that an inexperienced
volunteer set gives substantially more strength and bias to the non-voting
members, who are definitionally very familiar with the IETF and the
candidates for office.

I am not convinced the trade-off is worth it - but I can see the benefit of
modifying eligibility constraints to keep people eligible for longer.  I'd
like to see a way to include active and experienced remote attendees, but
am quite cautious on that.

Alia


On Thu, Jun 27, 2013 at 9:21 AM, Michael Richardson
<mcr+ietf@sandelman.ca>wrote:

>
> Arturo Servin <arturo.servin@gmail.com> wrote:
>     > Today it is possible to verify that somebody attended to an IETF
>     > meeting. You have to register, pay and collect your badge. However,
> in
>     > remote participation we do not have mechanisms to verify that
> somebody
>     > attended to a session.
>
> We need to have registration for remote participation, even if we charge
> zero.   I believe that perhaps we need to provide some magic token in
> jabber
> or in the NoteWell slide, that needs to be used by remote participants to
> check-in. They have to do that during the meeting itself.
>
> I also ask whether remote participation on the plenary should be
> "mandatory"
>
> We also need to permit judgement calls.
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        | network
> architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails
>    [
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>
>
>

--047d7bdc12386b6e1404e022d6af
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Just a quick aside, but having run an interim WG meeting w=
here we did not charge a meeting fee and knowing how significantly attendan=
ce diverged, I would strongly support at least some meeting fee for remote =
attendance. =A0There&#39;s also the key fact that the IETF is funded by IET=
F meeting fees and ISOC. =A0 Maybe the remote fee is scaled by region of at=
tendee or such if there is concern that it is burdensome.<div>
<br></div><div>I have attended one meeting remotely - and the experience is=
 nothing at all like being at IETF. =A0I can see modifying NomCom eligibili=
ty constraints slightly - but I really do not think that remote attendees w=
ill have the necessary experience and acculturation unless they have attend=
ed a number of IETFs in person. =A0=A0</div>
<div><br></div><div>Having served on a NomCom a long time ago, I&#39;d say =
that an inexperienced volunteer set gives substantially more strength and b=
ias to the non-voting members, who are definitionally very familiar with th=
e IETF and the candidates for office.=A0</div>
<div><br></div><div>I am not convinced the trade-off is worth it - but I ca=
n see the benefit of modifying eligibility constraints to keep people eligi=
ble for longer. =A0I&#39;d like to see a way to include active and experien=
ced remote attendees, but am quite cautious on that.</div>
<div><br></div><div>Alia=A0</div></div><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">On Thu, Jun 27, 2013 at 9:21 AM, Michael Richards=
on <span dir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D=
"_blank">mcr+ietf@sandelman.ca</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
Arturo Servin &lt;<a href=3D"mailto:arturo.servin@gmail.com">arturo.servin@=
gmail.com</a>&gt; wrote:<br>
=A0 =A0 &gt; Today it is possible to verify that somebody attended to an IE=
TF<br>
=A0 =A0 &gt; meeting. You have to register, pay and collect your badge. How=
ever, in<br>
=A0 =A0 &gt; remote participation we do not have mechanisms to verify that =
somebody<br>
=A0 =A0 &gt; attended to a session.<br>
<br>
</div>We need to have registration for remote participation, even if we cha=
rge<br>
zero. =A0 I believe that perhaps we need to provide some magic token in jab=
ber<br>
or in the NoteWell slide, that needs to be used by remote participants to<b=
r>
check-in. They have to do that during the meeting itself.<br>
<br>
I also ask whether remote participation on the plenary should be &quot;mand=
atory&quot;<br>
<br>
We also need to permit judgement calls.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
] =A0 =A0 =A0 =A0 =A0 =A0 =A0 Never tell me the odds! =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 | ipv6 mesh networks [<br>
] =A0 Michael Richardson, Sandelman Software Works =A0 =A0 =A0 =A0| network=
 architect =A0[<br>
] =A0 =A0 <a href=3D"mailto:mcr@sandelman.ca">mcr@sandelman.ca</a> =A0<a hr=
ef=3D"http://www.sandelman.ca/" target=3D"_blank">http://www.sandelman.ca/<=
/a> =A0 =A0 =A0 =A0| =A0 ruby on rails =A0 =A0[<br>
<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
<br>
<br>
</div></div></blockquote></div><br></div>

--047d7bdc12386b6e1404e022d6af--

From dave@cridland.net  Thu Jun 27 06:36:09 2013
Return-Path: <dave@cridland.net>
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 34E3221F9E3B for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 j-ozZw9KnfMx for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:36:08 -0700 (PDT)
Received: from mail-oa0-x22e.google.com (mail-oa0-x22e.google.com [IPv6:2607:f8b0:4003:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 99FEA21F9E3A for <ietf@ietf.org>; Thu, 27 Jun 2013 06:36:08 -0700 (PDT)
Received: by mail-oa0-f46.google.com with SMTP id h1so838652oag.19 for <ietf@ietf.org>; Thu, 27 Jun 2013 06:36:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=j5JI8NlPT4Msx58Bxo/s8ea/t4+fwH1Vwm38H2pZurw=; b=DM2XBoTwXkAQIkEZZy+Y+9wnFjiye2+Zv7EaPnI6DyglgD3iKjy2+n6h9R7FImcx8h HqA/wd27kpkyFyD0O5NepfhvoshiD1Xdj/P2fngG20NRiS6AkEWjJDK4RzoN01FYBK4X SGflCkgkkumZy6v0N1r8Q0u9TPSQekClufuvs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=j5JI8NlPT4Msx58Bxo/s8ea/t4+fwH1Vwm38H2pZurw=; b=X4apFCCdJ+kyYzVdCqPlqzyVmIo+KLITpIf94B83TZvG7za9RDvH/0YloW5E2ArOyC GYPTp4uYM0qU2KkJHaSyFu5h9Fj/Oafsp7Z32sZcCBvHIOUiNEdo4XMgWg6fnSqrupRt T/jCorVVJWuw9BobyoC1myBy7X3DFujojC6vkaLFC3RSVh9Ut31GPyXDXXd6x690+bLl Tr9vhHIy8g/8D+LSlgCBuyt+ZbOV/0ejdd73o7QGVxNna3tW7quYaA66RUJgEFuEL9xX sw3TKB9IHA+Tl40S3bPIjCxxCz8c9L292Bri9ncSLvx24DMKkvnGUfsiqz3nDpjx/aNP A08Q==
MIME-Version: 1.0
X-Received: by 10.60.57.164 with SMTP id j4mr2795172oeq.10.1372340168152; Thu, 27 Jun 2013 06:36:08 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Thu, 27 Jun 2013 06:36:08 -0700 (PDT)
In-Reply-To: <9673.1372339268@sandelman.ca>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC0D50.8080708@gmail.com> <9673.1372339268@sandelman.ca>
Date: Thu, 27 Jun 2013 14:36:08 +0100
Message-ID: <CAKHUCzyCa4L_osvnVD6=QJ3EwzTRksD4PwBuAkT=n5cMDdAy0Q@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
From: Dave Cridland <dave@cridland.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=089e013d0ce83bec8604e022d8f5
X-Gm-Message-State: ALoCoQljc5Ip08/ggrdep/kPAEC9eAOBCr/wqFfHvSZqB8pyebE0tEjNLe5HfOKOrVbQBb1ZxiA/
Cc: Arturo Servin <arturo.servin@gmail.com>, "ietf@ietf.org Discussion" <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: Thu, 27 Jun 2013 13:36:09 -0000

--089e013d0ce83bec8604e022d8f5
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 27, 2013 at 2:21 PM, Michael Richardson
<mcr+ietf@sandelman.ca>wrote:

>
> Arturo Servin <arturo.servin@gmail.com> wrote:
>     > Today it is possible to verify that somebody attended to an IETF
>     > meeting. You have to register, pay and collect your badge. However,
> in
>     > remote participation we do not have mechanisms to verify that
> somebody
>     > attended to a session.
>
> We need to have registration for remote participation, even if we charge
> zero.   I believe that perhaps we need to provide some magic token in
> jabber
> or in the NoteWell slide, that needs to be used by remote participants to
> check-in. They have to do that during the meeting itself.
>

We could require room registration for the XMPP ("Jabber") chatrooms, and
have remote participants fill in an equivalent of the blue sheet in order
to join the room.

I'm not sure if the current XMPP implementation supports this, but it will
work in principle with a number of existing deployed implementations.

(And, note, we no longer have to care about Google Talk interop, which
makes things easier).

Dave.

--089e013d0ce83bec8604e022d8f5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Jun 27, 2013 at 2:21 PM, Michael Richardson <span =
dir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">=
mcr+ietf@sandelman.ca</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><=
div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
Arturo Servin &lt;<a href=3D"mailto:arturo.servin@gmail.com">arturo.servin@=
gmail.com</a>&gt; wrote:<br>
=A0 =A0 &gt; Today it is possible to verify that somebody attended to an IE=
TF<br>
=A0 =A0 &gt; meeting. You have to register, pay and collect your badge. How=
ever, in<br>
=A0 =A0 &gt; remote participation we do not have mechanisms to verify that =
somebody<br>
=A0 =A0 &gt; attended to a session.<br>
<br>
</div>We need to have registration for remote participation, even if we cha=
rge<br>
zero. =A0 I believe that perhaps we need to provide some magic token in jab=
ber<br>
or in the NoteWell slide, that needs to be used by remote participants to<b=
r>
check-in. They have to do that during the meeting itself.<br></blockquote><=
div><br></div><div style>We could require room registration for the XMPP (&=
quot;Jabber&quot;) chatrooms, and have remote participants fill in an equiv=
alent of the blue sheet in order to join the room.</div>
<div style><br></div><div style>I&#39;m not sure if the current XMPP implem=
entation supports this, but it will work in principle with a number of exis=
ting deployed implementations.</div><div style><br></div><div style>(And, n=
ote, we no longer have to care about Google Talk interop, which makes thing=
s easier).</div>
<div style><br></div><div style>Dave.</div></div></div></div>

--089e013d0ce83bec8604e022d8f5--

From lear@cisco.com  Thu Jun 27 06:42:38 2013
Return-Path: <lear@cisco.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 409E621F9CC5 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.962
X-Spam-Level: 
X-Spam-Status: No, score=-109.962 tagged_above=-999 required=5 tests=[AWL=0.637, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 HrEz2ZIEv82d for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:42:33 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id E7B2121F9C6A for <ietf@ietf.org>; Thu, 27 Jun 2013 06:42:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=324; q=dns/txt; s=iport; t=1372340553; x=1373550153; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=A1FiGwUbPzATu2g5Nf3RuFGibj+5yC2RFMJ+S0OzWVU=; b=lq16FK+72rrEAMq5jAxbr/re7gQmxKMMwpGl6N81OvwRJr9zFKKbxypV CuGOF8HuHbfRI3F7JA+0D+bd0qHpkzQa2DDUU/a/mbYEpt+wNJryU74jg NtkJYz2d4OGmW3HIDcwh2HbxZ8yFzhjdTjLqLhDY4pdvCVnTYnYS0wH4w w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsFAMpAzFGQ/khL/2dsb2JhbABbDoJ7hAG8AX4WdIIjAQEBAQMjVhALDgoCAgUhAgIPAiwaBg0BBwEBiAqpJJE0gSaOLweCT4EWA5dFkUWCU0A6
X-IronPort-AV: E=Sophos;i="4.87,952,1363132800"; d="scan'208";a="15036472"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 27 Jun 2013 13:42:31 +0000
Received: from mctiny.local ([10.61.223.240]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r5RDgTVg008092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 13:42:29 GMT
Message-ID: <51CC4144.70600@cisco.com>
Date: Thu, 27 Jun 2013 15:42:28 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: The Nominating Committee Process: Eligibility
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu>
In-Reply-To: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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: Thu, 27 Jun 2013 13:42:38 -0000

On 6/27/13 3:34 PM, Noel Chiappa wrote:
>
> Why not just say directly that 'to prevent "capture", no more than X% of
> the NomCom may work for a single organization' (where X is 15% or so, so
> that even if a couple collude, they still can't get control).
>

It's already in RFC 3777.  No more than 2 per company.

From sm@elandsys.com  Thu Jun 27 06:47:45 2013
Return-Path: <sm@elandsys.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 E680721F9DF7 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 cHOADhR7x2Z3 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:47:45 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D052E21F9E06 for <ietf@ietf.org>; Thu, 27 Jun 2013 06:47:42 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.132.118]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5RDlQJA026202 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 06:47:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372340858; bh=UcBBCaz4GGjlgD3qr2g9uYGZlFDg2QgzVEBnoonIxjU=; h=Date:To:From:Subject:Cc:References; b=rje+k1++xhbC+Vog98dvbcQ4F7m+uAUMeYmXf6VrOZim0qS8/s/kDpo/qeG9Vo/Wa 23zME29bH3wOO/5/c+jq1rYjZ4evc2OhgNXhK2JMHTcVF6H6k5N7RB/ikHEx12MVWw 4/okAULU1bj4oMxUbmj7sIwBcBPaREAAy1qrirA4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372340858; i=@elandsys.com; bh=UcBBCaz4GGjlgD3qr2g9uYGZlFDg2QgzVEBnoonIxjU=; h=Date:To:From:Subject:Cc:References; b=4+TtBazmK0XTDFdA6NX1aWq6Aqj1QgZ77+pLXanc5gAmZwKoD/CaBylL8bZw+2AtO xP/Y9g1vY+gF9xBFg/WNiIML2xRSjDRLKMLd0Dubx5hxtvrMKPCkrkEF0HZCZA4AE8 hINBxKh2oRWWZLVrCWIt1Tohjglr1Zz6zYu1SMZ0=
Message-Id: <6.2.5.6.2.20130627061517.0d46aff8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jun 2013 06:38:13 -0700
To: alejandroacostaalamo@gmail.com
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <549BEFE0-8E23-4351-A2DB-CF138AC24FBD@ogud.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Thu, 27 Jun 2013 13:47:46 -0000

Hi Alejandro,
At 05:42 27-06-2013, alejandroacostaalamo@gmail.com wrote:
>   First, as a comment, I guess there is people who follow more IETF 
> remotely than other in place.

Yes.

Here's is an extract from a Jabber log:

   "I don't think I've seen a WG chatroom this full before
    Well the future of the free world is at stake here :-)"

>   Second, I like this idea of changing the threshold.

Thanks for reading the draft and providing feedback.

>   Third, In the other hand, since there are several positions that 
> are fill using this RFC maybe we can place a testbed. 50% can be 
> fill using the current way and 50% using the proposed way, sounds 
> crazy but it might be a good beginning.

I don't think that it sounds crazy.  A good beginning is when people 
make suggestions like you did.  I don't know yet whether I will say 
okay to the idea.  I would like to read all the suggestions, 
including yours, and then decide.

Regards,
S. Moonesamy 


From john-ietf@jck.com  Thu Jun 27 06:49:05 2013
Return-Path: <john-ietf@jck.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 937DA21F9E1F for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 gbD42larSs-q for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:48:59 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id AF3A321F9DF7 for <ietf@ietf.org>; Thu, 27 Jun 2013 06:48:59 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UsCZB-000BlP-Ur; Thu, 27 Jun 2013 09:48:53 -0400
Date: Thu, 27 Jun 2013 09:48:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
Message-ID: <458616F3563062FB2CC6EBFC@JcK-HP8200.jck.com>
In-Reply-To: <51CC18FB.1030409@cs.tcd.ie>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC18FB.1030409@cs.tcd.ie>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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: Thu, 27 Jun 2013 13:49:05 -0000

--On Thursday, June 27, 2013 11:50 +0100 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>...
> (*) Like I said, too early to get into it, but the nomcom
> selection process could also require that the voting
> members collectively have been to N meetings, with each
> voting member able to contribute at most M to that total.
> Say with N=30 and M=4 or something, and keep running the
> random selection until you get 10 voting members that
> satisfy that. And if we went there, we could also require
> that nomcom as a group have written a number of RFCs
> perhaps or even have some folks with Jari's h-index>3
> or something. We could have lots of fun with all that:-)

While it risks taking us into a statistical rathole, I think
that notions like the above may be the sort of thing we should
look at.  

More broadly, I think we may need to try to figure out what we
really want and need on or from the Nomcom in this decade
(remembering that the system was designed for the rather
different times and IETF composition of the early 1990s and has
been tuned in minor ways but not carefully and openly reviewed
since) and then try to devise criteria to match.   It seems to
me that may require looking at separate aspects of things rather
than trying to come up with a single surrogate for everything.  

For example, as the above suggests, there are some purposes for
which we probably need to look at overall Nomcom composition
rather that just individual qualifications.  Measures to avoid
capture fall into that category.  Whether the existing rules are
adequate in that regard or not, they represent on case where we
do look at total composition already.

We might want to look at whether some collections of
participants should be guaranteed representation or weighted
more heavily in the selection calculations (whether voting or
otherwise).  That raises the risk that SM identifies of pushing
us toward a Nomcom as a representative body of constituencies
demanding slots, but the advantages seem very strong for Dave
Crocker's proposal to guarantee a certain level of expertise and
some ideas to be sure that the perspective of remote
participants or other underrepresented populations are heard.
The question is how to find the right balance and then reach
sufficient consensus around the justification that we can hold
the line.   Not easy, but, at least IMO, probably worth the
investment it would take.

Similarly, I'm pretty sure that "groks the IETF" [1] is an
important and useful criterion.  I don't think "3 of last 5" is
a valid exclusive surrogate.  Perhaps what is needed is a list
of alternatives, any of which could demonstrate sufficient
familiarity with the culture.

If we separated the "IETF culture" requirement, I still think
that some level of participation, even face to face
participation is important.  I don't think that 3 face to face
meetings in 5 is needed for people who already understand the
culture; maybe some combination of remote participation and less
frequent attendance should be equally acceptable. 

"Participation" is similar.  If we think it is important, then
someone who is actively contributing to mailing lists and
document reviews and who is showing up in meeting Jabber logs
with useful comments is, IMO, a more appropriate Nomcom member
than someone whose company pays registration fees and travel
expenses and who then shows up at meetings and either goes to
the beach or sits in a few WG meetings reading email.  I don't
know how to eliminate the second (perhaps others have ideas) but
I can think of ways to identify the former as long as they are
not the exclusive "minimum participation" admission criteria.  

I would just hope that we don't fall into the trap of focusing
on what is easy to measure and quantify rather than what is
important and a good measure of what we are looking for.   It is
always tempting but, at least IMO, this issue is important
enough to the community in the long term that we ought to be
willing to invest some resources in it.   "3 of 5" may represent
an instance of that trap however well-intentioned it was when it
was instituted.

    john


[1] I wonder, its introduction into the OED notwithstanding, if
the use of that term marks some of us as being either from a
particular, increasingly-ancient, generation or is more
culturally idiosyncratic than is appropriate.


From dmm@1-4-5.net  Thu Jun 27 06:51:25 2013
Return-Path: <dmm@1-4-5.net>
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 1690221F9997 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 K4PvHyUDXCQl for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 06:51:14 -0700 (PDT)
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) by ietfa.amsl.com (Postfix) with ESMTP id B716F21F99D9 for <ietf@ietf.org>; Thu, 27 Jun 2013 06:51:10 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wc20so738908obb.4 for <ietf@ietf.org>; Thu, 27 Jun 2013 06:51:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=xJfGnbEZ+qgcTXbqwBSPiwxM/WQOj+uKJ5kTmJyjnbk=; b=nHQB3RWaMISFBvpVVS/7L3TiJR1XPm5FGkSdPCfXcGFlh2hlccX8t9ajkIENrSE//E /einbWzNSBrFw7RBpKB7YJIghVRYbOzADodFNKnZ5OcQZPED93lDKaWU3WMOcua36tSq hh5b4VtnDs2jVEKUwPiYL3OHOQQ7BDjT7lj1xvhqER7tVGVyNNiq7cuK3yMnACqISLkA gnjkxQm3jtMgWi+VJCMSESjctTBlLla8BOptqkgKn0FZDpAZhKZ6NDPMKZWwMtw2n5Ae wuRfg/7vY3vGBUU+EwPfwzihGNefz200ATAKoxkqkG0B4lKO57HZuEcfX4lvR0e3k9oM PsoQ==
MIME-Version: 1.0
X-Received: by 10.60.62.238 with SMTP id b14mr2846047oes.90.1372341070291; Thu, 27 Jun 2013 06:51:10 -0700 (PDT)
Received: by 10.182.114.34 with HTTP; Thu, 27 Jun 2013 06:51:10 -0700 (PDT)
X-Originating-IP: [63.145.238.4]
In-Reply-To: <51CC4144.70600@cisco.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com>
Date: Thu, 27 Jun 2013 06:51:10 -0700
Message-ID: <CAHiKxWhB6T5EPmseadYixTZvWe_Frk5AmH7Ejty8DjDxVCGTPA@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
From: David Meyer <dmm@1-4-5.net>
To: Eliot Lear <lear@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkqW6+OI/TzUK96eopPhUqSVIXJfs2rqzhFcznH2wbqWG9Ug0dofSPej7o4xzLdwkboSqed
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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: Thu, 27 Jun 2013 13:51:25 -0000

On Thu, Jun 27, 2013 at 6:42 AM, Eliot Lear <lear@cisco.com> wrote:
>
> On 6/27/13 3:34 PM, Noel Chiappa wrote:
>>
>> Why not just say directly that 'to prevent "capture", no more than X% of
>> the NomCom may work for a single organization' (where X is 15% or so, so
>> that even if a couple collude, they still can't get control).
>>
>
> It's already in RFC 3777.  No more than 2 per company.

BTW, while I understand the spirit of 3777 on this point, I have
always found the restriction somewhat at odds with our belief (hope?)
that we represent ourselves and the best interest of the Internet at
the IETF. In addition, a central ethic (IMO anyway) of the IETF has
always been to honor individualism and independence, so I find it a
bit strange that in the NomCom context we're all just corporate (or
otherwise) drones. All of that said, evidently reality doesn't always
match our ideals, hence clauses like the one you cite from 3777. --dmm

From andy@yumaworks.com  Thu Jun 27 07:05:26 2013
Return-Path: <andy@yumaworks.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 1876E21F9E13 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 07:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level: 
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[AWL=1.083,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 h-c6az65g57a for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 07:05:20 -0700 (PDT)
Received: from mail-pb0-f42.google.com (mail-pb0-f42.google.com [209.85.160.42]) by ietfa.amsl.com (Postfix) with ESMTP id 8603321F9E12 for <ietf@ietf.org>; Thu, 27 Jun 2013 07:05:20 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so967218pbc.15 for <ietf@ietf.org>; Thu, 27 Jun 2013 07:05:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=EUqs4kf98bFSB9QUQ1PSjX5L5IYK8of1Kp49JsorHx8=; b=RgApxwpNoIxWahHA6jNl7SzcgQ9qHBOU29Ube0pAwUyNuMNizibiQ3kw1Jp+uBE8N3 d1eZXxN9I4OqIpkzSebX0YhrWC2tmVG2IltdqPJFOD/aEnfM07YQT11+qAU4M+InUSxY j8pr8BtLODSVYKAQGdJ1JEf8C0IO34vwHrszJuY6qW2gyAd1orr2bsUrAz2qrIwK8qp5 q2lR+t/D/HdSKABrLLfJm+c59+Wc5LjxiEUJ/OTkVfAcH1p+B/l25Le1zABmX40o6PXM XzN2i/O5h01Fy/JbxNdLtC7+lpdl1wxbLdYb6VI+oRwCyYOq90TTQg6STS27pLoedkVB eodg==
MIME-Version: 1.0
X-Received: by 10.68.111.228 with SMTP id il4mr6152396pbb.134.1372341920203; Thu, 27 Jun 2013 07:05:20 -0700 (PDT)
Received: by 10.70.48.233 with HTTP; Thu, 27 Jun 2013 07:05:20 -0700 (PDT)
In-Reply-To: <CAKHUCzyCa4L_osvnVD6=QJ3EwzTRksD4PwBuAkT=n5cMDdAy0Q@mail.gmail.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC0D50.8080708@gmail.com> <9673.1372339268@sandelman.ca> <CAKHUCzyCa4L_osvnVD6=QJ3EwzTRksD4PwBuAkT=n5cMDdAy0Q@mail.gmail.com>
Date: Thu, 27 Jun 2013 07:05:20 -0700
Message-ID: <CABCOCHT-pRAdhrNOF+PHrdP1Aq+KGpXtgf1VvULH+rMi2_9thg@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
From: Andy Bierman <andy@yumaworks.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=047d7b67201aaa239d04e0234033
X-Gm-Message-State: ALoCoQlAXtZ8SXIxlNGkwwYw0mN8w9Gx+UIaqwAGUdMdhCpYHOV3kZQJPZ/5EqZmWayl8g7nS6Rt
Cc: Arturo Servin <arturo.servin@gmail.com>, "ietf@ietf.org Discussion" <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: Thu, 27 Jun 2013 14:05:26 -0000

--047d7b67201aaa239d04e0234033
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I am strongly opposed to a remote meeting registration process and remote
meeting fees.
This increases the financial bias towards large corporate control of IETF
standards.
I like the IETF because anybody can comment on a draft or write a draft
without
paying fees.

I think there could be several ways to prove one has been recently involved
in the
IETF.  IMO I-D or RFC authorship shows more involvement than just showing up
at an IETF.  People who never read, write or comment on any drafts can be
more nomcom-qualified (by attendance metrics) than somebody who worked on
10 drafts
over the same time span.

Andy


On Thu, Jun 27, 2013 at 6:36 AM, Dave Cridland <dave@cridland.net> wrote:

> On Thu, Jun 27, 2013 at 2:21 PM, Michael Richardson <mcr+ietf@sandelman.ca
> > wrote:
>
>>
>> Arturo Servin <arturo.servin@gmail.com> wrote:
>>     > Today it is possible to verify that somebody attended to an IETF
>>     > meeting. You have to register, pay and collect your badge. However,
>> in
>>     > remote participation we do not have mechanisms to verify that
>> somebody
>>     > attended to a session.
>>
>> We need to have registration for remote participation, even if we charge
>> zero.   I believe that perhaps we need to provide some magic token in
>> jabber
>> or in the NoteWell slide, that needs to be used by remote participants to
>> check-in. They have to do that during the meeting itself.
>>
>
> We could require room registration for the XMPP ("Jabber") chatrooms, and
> have remote participants fill in an equivalent of the blue sheet in order
> to join the room.
>
> I'm not sure if the current XMPP implementation supports this, but it will
> work in principle with a number of existing deployed implementations.
>
> (And, note, we no longer have to care about Google Talk interop, which
> makes things easier).
>
> Dave.
>

--047d7b67201aaa239d04e0234033
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>I am strongly opposed to a remote meeting registrati=
on process and remote meeting fees.</div><div>This increases the financial =
bias towards large corporate control of IETF standards.</div><div>I like th=
e IETF because anybody can comment on a draft or write a draft without</div=
>
<div>paying fees.</div><div><br></div><div>I think there could be several w=
ays to prove one has been recently involved in the</div><div>IETF. =A0IMO I=
-D or RFC authorship shows more involvement than just showing up</div><div>
at an IETF. =A0People who never read, write or comment on any drafts can be=
</div><div>more nomcom-qualified (by attendance metrics) than somebody who =
worked on 10 drafts</div><div>over the same time span.</div><div><br></div>
<div>Andy</div><div><br></div><div><br><div class=3D"gmail_quote">On Thu, J=
un 27, 2013 at 6:36 AM, Dave Cridland <span dir=3D"ltr">&lt;<a href=3D"mail=
to:dave@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt;</span> wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">On Thu, Jun 27, 2013 at 2:2=
1 PM, Michael Richardson <span dir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@s=
andelman.ca" target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;</span> wrote:<=
br>
<div class=3D"gmail_extra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><br>
Arturo Servin &lt;<a href=3D"mailto:arturo.servin@gmail.com" target=3D"_bla=
nk">arturo.servin@gmail.com</a>&gt; wrote:<br>
=A0 =A0 &gt; Today it is possible to verify that somebody attended to an IE=
TF<br>
=A0 =A0 &gt; meeting. You have to register, pay and collect your badge. How=
ever, in<br>
=A0 =A0 &gt; remote participation we do not have mechanisms to verify that =
somebody<br>
=A0 =A0 &gt; attended to a session.<br>
<br>
</div>We need to have registration for remote participation, even if we cha=
rge<br>
zero. =A0 I believe that perhaps we need to provide some magic token in jab=
ber<br>
or in the NoteWell slide, that needs to be used by remote participants to<b=
r>
check-in. They have to do that during the meeting itself.<br></blockquote><=
div><br></div><div>We could require room registration for the XMPP (&quot;J=
abber&quot;) chatrooms, and have remote participants fill in an equivalent =
of the blue sheet in order to join the room.</div>

<div><br></div><div>I&#39;m not sure if the current XMPP implementation sup=
ports this, but it will work in principle with a number of existing deploye=
d implementations.</div><div><br></div><div>(And, note, we no longer have t=
o care about Google Talk interop, which makes things easier).</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div><div>Dave.</div></font></span></div></div></div>
</blockquote></div><br></div>

--047d7b67201aaa239d04e0234033--

From jcurran@istaff.org  Thu Jun 27 07:12:28 2013
Return-Path: <jcurran@istaff.org>
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 4A1D021F9C6C for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 07:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 1tfZmq7fNKWA for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 07:12:22 -0700 (PDT)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by ietfa.amsl.com (Postfix) with ESMTP id 6306D21F9B60 for <ietf@ietf.org>; Thu, 27 Jun 2013 07:12:22 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1UsCvt-0006Ad-Ti; Thu, 27 Jun 2013 14:12:21 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19aEb6WICc5prACgQwLDCHw
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: The Nominating Committee Process: Eligibility
From: John Curran <jcurran@istaff.org>
In-Reply-To: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu>
Date: Thu, 27 Jun 2013 10:12:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4FEF8934-CE7F-4666-808C-7D9C37D2381B@istaff.org>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.1508)
Cc: 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: Thu, 27 Jun 2013 14:12:28 -0000

On Jun 27, 2013, at 9:34 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu> =
wrote:

> Why not just say directly that 'to prevent "capture", no more than X% =
of
> the NomCom may work for a single organization' (where X is 15% or so, =
so
> that even if a couple collude, they still can't get control).

There are already controls for that, but folks who engage in games such =
as
this generally make use of consultants/proxies/etc. which are not at all
apparent.  I'm not citing this as a huge risk, but one which could occur
if the in-person requirement drops to a single meeting. (i.e. due to the=20=

large pool of remote participants that one could enlist and fund a =
single
on-site attendance if the goal was to seat an particular IAB or IESG =
member.)

FYI,
/John

Disclaimers: My views alone (& not part of any group seeking NomCom =
capture... :-)



From john-ietf@jck.com  Thu Jun 27 07:14:23 2013
Return-Path: <john-ietf@jck.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 5CDC121F9D4D for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 07:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 OaglCpi-qBXN for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 07:14:12 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 524C221F9D49 for <ietf@ietf.org>; Thu, 27 Jun 2013 07:14:12 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UsCxf-000Bo1-I8; Thu, 27 Jun 2013 10:14:11 -0400
Date: Thu, 27 Jun 2013 10:14:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alia Atlas <akatlas@gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
Message-ID: <672FB2487DB4CC35B9C45286@JcK-HP8200.jck.com>
In-Reply-To: <CAG4d1rdqiYTk9VZXmn4WGCAtQPxuSvUPGQ5XsFhStJMx84WhvA@mail.gmail.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC0D50.8080708@gmail.com> <9673.1372339268@sandelman.ca> <CAG4d1rdqiYTk9VZXmn4WGCAtQPxuSvUPGQ5XsFhStJMx84WhvA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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: Thu, 27 Jun 2013 14:14:23 -0000

--On Thursday, June 27, 2013 09:35 -0400 Alia Atlas
<akatlas@gmail.com> wrote:

> Just a quick aside, but having run an interim WG meeting where
> we did not charge a meeting fee and knowing how significantly
> attendance diverged, I would strongly support at least some
> meeting fee for remote attendance.  There's also the key fact
> that the IETF is funded by IETF meeting fees and ISOC.

FWIW, so would I, if only because a large fraction of where that
fee goes (at least given some assumptions about disposition of
registration fee and ISOC money) is to support activities that
have little or nothing to do with actual meeting costs.   That
makes a fee for remote participates a matter of fairness, even
though I would hope that we could keep it low enough to avoid
discouraging participation (and maybe differentiate between a
lurker fee and an active remote participant fee).   Again,
creative thinking is called for, IMO.

>   Maybe
> the remote fee is scaled by region of attendee or such if
> there is concern that it is burdensome.

We already have a fee waiver mechanism.  It may need to be more
widely publicized and/or modified to reduce the load on the IETF
Chair if the number of requests rises, but I'd hope we could
avoid region-based formulae (if the reasons aren't clear, I can
elaborate).

> I have attended one meeting remotely - and the experience is
> nothing at all like being at IETF.  I can see modifying NomCom
> eligibility constraints slightly - but I really do not think
> that remote attendees will have the necessary experience and
> acculturation unless they have attended a number of IETFs in
> person.

See several previous notes on this list and the Nomcom one about
acculturation.  But, as to the difference in experience, I fully
agree that it is very different.   There is, however, a bit of a
chicken-and-egg problem: while I think the IESG and other
leadership bodies have good intentions toward remote (including
mailing-list-only) participants, having those bodies be more
accountable to remote folks is probably key to making that
experience better.  I have doubts as to whether it will every be
good enough that the average remote-only participant will every
fully understand the culture and actors, but maybe we don't need
that as a criterion for success.

    john

> 
> Having served on a NomCom a long time ago, I'd say that an
> inexperienced volunteer set gives substantially more strength
> and bias to the non-voting members, who are definitionally
> very familiar with the IETF and the candidates for office.
> 
> I am not convinced the trade-off is worth it - but I can see
> the benefit of modifying eligibility constraints to keep
> people eligible for longer.  I'd like to see a way to include
> active and experienced remote attendees, but am quite cautious
> on that.
> 
> Alia
> 
> 
> On Thu, Jun 27, 2013 at 9:21 AM, Michael Richardson
> <mcr+ietf@sandelman.ca>wrote:
> 
>> 
>> Arturo Servin <arturo.servin@gmail.com> wrote:
>>     > Today it is possible to verify that somebody attended
>>     > to an IETF meeting. You have to register, pay and
>>     > collect your badge. However,
>> in
>>     > remote participation we do not have mechanisms to
>>     > verify that
>> somebody
>>     > attended to a session.
>> 
>> We need to have registration for remote participation, even
>> if we charge zero.   I believe that perhaps we need to
>> provide some magic token in jabber
>> or in the NoteWell slide, that needs to be used by remote
>> participants to check-in. They have to do that during the
>> meeting itself.
>> 
>> I also ask whether remote participation on the plenary should
>> be "mandatory"
>> 
>> We also need to permit judgement calls.
>> 
>> --
>> ]               Never tell me the odds!                 |
>> ipv6 mesh networks [
>> ]   Michael Richardson, Sandelman Software Works        |
>> network architect  [
>> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |
>> ruby on rails [
>> 
>> 
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman
>> Software Works
>> 
>> 
>> 





From lear@cisco.com  Thu Jun 27 07:17:13 2013
Return-Path: <lear@cisco.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 806E921F9B8C for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 07:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.002
X-Spam-Level: 
X-Spam-Status: No, score=-110.002 tagged_above=-999 required=5 tests=[AWL=0.596, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 L9Mj71h7DB9l for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 07:17:08 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 258C821F9DE1 for <ietf@ietf.org>; Thu, 27 Jun 2013 07:17:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3504; q=dns/txt; s=iport; t=1372342628; x=1373552228; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=SLDGJeSvw4t2Up4ikxxOhcrwFjO6LPKKYvK7faoq7E4=; b=PGNMFrlQZjrlOFw5OtpbJyjPIxQddvv6zp7adQcFhxuy9nldw6rADqCY NYNH7kUbc71crFvU/EyZ+AutJgFbqEtV6a3YNPXgi8CmDfn2Rtpz8JewD W8LfP4HSfpUZUZMj3yUq8KYY1jxEp/mzpMA1YDLjZmjHRdLMO7ZD/5OnJ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0FAPtIzFGQ/khN/2dsb2JhbABbgwkxg1CFXbYlfhZ0giQBAQQjVQEQCwQdFgsCAgkDAgECASsaBg0BBwEBiAqpKZE1j1UHgk+BFgOXRZFFgxM6
X-IronPort-AV: E=Sophos;i="4.87,952,1363132800";  d="scan'208,217";a="155830789"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 27 Jun 2013 14:17:05 +0000
Received: from mctiny.local ([10.61.223.240]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r5REH3cp018585 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 14:17:03 GMT
Message-ID: <51CC495F.4010808@cisco.com>
Date: Thu, 27 Jun 2013 16:17:03 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC0D50.8080708@gmail.com> <9673.1372339268@sandelman.ca>
In-Reply-To: <9673.1372339268@sandelman.ca>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative; boundary="------------050201000708020509060006"
Cc: Arturo Servin <arturo.servin@gmail.com>, 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: Thu, 27 Jun 2013 14:17:13 -0000

This is a multi-part message in MIME format.
--------------050201000708020509060006
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Michael,

I think what you're getting at is that there are different types of
remote participation.  If one wants to listen in, that should only
require the appropriate software and a network connection.  If one
actually wants to participate, then one either has to get onto a WeBex
or Meetecho system.  The point of this is that there has should be some
demonstration that someone substantially participated in an IETF event.

Speaking of which, let me also raise another issue.  As those of you who
will be there in person will see in Berlin, we have a *vast* number of
BoFs planned, and this could lead to a vast number of additional new
working groups.  We won't have room for them all.  In addition, I myself
am co-chair of a working group who is not intended to meet â€“ *ever*. 
Linked to the issue of NOMCOM is the idea that working groups actually
meet at IETFs.  Some certainly will continue to do so.  Others, on the
other hand, require more bandwidth.  Case and point: the httpbis working
group has held two interim meetings and two more are planned.  All off
site.  Should these people be counted?  If so, how?

And yes, it is possible to make this so complex that nobody would be
able to figure out who is eligible.

And so, as I said, I'm fine with SM's idea, modulo John's suggested
edit.  But I also think it would be useful to look beyond that change as
well.

Eliot

--------------050201000708020509060006
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Michael,<br>
    <br>
    I think what you're getting at is that there are different types of
    remote participation.Â  If one wants to listen in, that should only
    require the appropriate software and a network connection.Â  If one
    actually wants to participate, then one either has to get onto a
    WeBex or Meetecho system.Â  The point of this is that there has
    should be some demonstration that someone substantially participated
    in an IETF event.<br>
    <br>
    Speaking of which, let me also raise another issue.Â  As those of you
    who will be there in person will see in Berlin, we have a <b>vast</b>
    number of BoFs planned, and this could lead to a vast number of
    additional new working groups.Â  We won't have room for them all.Â  In
    addition, I myself am co-chair of a working group who is not
    intended to meet â€“ <b>ever</b>.Â  Linked to the issue of NOMCOM is
    the idea that working groups actually meet at IETFs.Â  Some certainly
    will continue to do so.Â  Others, on the other hand, require more
    bandwidth.Â  Case and point: the httpbis working group has held two
    interim meetings and two more are planned.Â  All off site.Â  Should
    these people be counted?Â  If so, how?<br>
    <br>
    And yes, it is possible to make this so complex that nobody would be
    able to figure out who is eligible.<br>
    <br>
    And so, as I said, I'm fine with SM's idea, modulo John's suggested
    edit.Â  But I also think it would be useful to look beyond that
    change as well.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------050201000708020509060006--

From mcr@sandelman.ca  Thu Jun 27 07:55:53 2013
Return-Path: <mcr@sandelman.ca>
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 C7B7D21F9D57 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 07:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 E88UCaYtm8jF for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 07:55:52 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id F0C4A21F9D72 for <ietf@ietf.org>; Thu, 27 Jun 2013 07:55:48 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 3E59A20170; Thu, 27 Jun 2013 11:59:50 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 0630963A7C; Thu, 27 Jun 2013 10:54:35 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id EBF3163A5E; Thu, 27 Jun 2013 10:54:35 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alia Atlas <akatlas@gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <CAG4d1rdqiYTk9VZXmn4WGCAtQPxuSvUPGQ5XsFhStJMx84WhvA@mail.gmail.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC0D50.8080708@gmail.com> <9673.1372339268@sandelman.ca> <CAG4d1rdqiYTk9VZXmn4WGCAtQPxuSvUPGQ5XsFhStJMx84WhvA@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 27 Jun 2013 10:54:35 -0400
Message-ID: <5831.1372344875@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Arturo Servin <arturo.servin@gmail.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: Thu, 27 Jun 2013 14:55:53 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Alia Atlas <akatlas@gmail.com> wrote:
    > I have attended one meeting remotely - and the experience is nothing =
at all
    > like being at IETF. =C2=A0I can see modifying NomCom eligibility cons=
traints
    > slightly - but I really do not think that remote attendees will have =
the
    > necessary experience and acculturation unless they have attended a nu=
mber of
    > IETFs in person.

That's why, I am not in favour of significantly changing the criteria to
*become* nomcom eligible.  I really don't think anyone thinks that one can
become clueful about IETF culture without being there in person a few times.

=2D-
]               Never tell me the odds!                 | ipv6 mesh network=
s [
]   Michael Richardson, Sandelman Software Works        | network architect=
  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [


=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUcxSKYqHRg3pndX9AQJyuAP/alrPf6MEwmjeKdbAOkHaAP0TJcA2EntV
b09ZjN4fRnFF9Rsv07UjHl87G/zAUdRFi+ot9yTwDo9YP+KoDi1FCV5hhFzHjfQu
V/EXF9VznBf7i/q1FH4V//L2x08XVISaZ4gCbVxeU4qG247p9m7HKUFnzGSwU6Cq
XkOtNZCOT1o=
=TcEa
-----END PGP SIGNATURE-----
--=-=-=--

From mstjohns@comcast.net  Thu Jun 27 08:07:55 2013
Return-Path: <mstjohns@comcast.net>
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 8CA6121F9A50 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
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 D8E0BiqKhBka for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:07:49 -0700 (PDT)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by ietfa.amsl.com (Postfix) with ESMTP id 8C3B821F9D9B for <ietf@ietf.org>; Thu, 27 Jun 2013 08:07:45 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta08.westchester.pa.mail.comcast.net with comcast id tPlv1l00417dt5G58T7kZA; Thu, 27 Jun 2013 15:07:44 +0000
Received: from Mike-T530.comcast.net ([63.68.157.173]) by omta13.westchester.pa.mail.comcast.net with comcast id tT7X1l01F3kl1PB3ZT7agA; Thu, 27 Jun 2013 15:07:42 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 27 Jun 2013 11:07:35 -0400
To: Eliot Lear <lear@cisco.com>,Noel Chiappa <jnc@mercury.lcs.mit.edu>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <51CC4144.70600@cisco.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1372345664; bh=nnNEBoD43uHcbcXcNBTrh5UKT2ACIFNXYOkB2+I4kes=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=hJpCI4t4aZgm6mUe2KETCKb9zQYUKMIsNl6wAhzYlpqJnoKgUgoXhsOkIXISQ8rHq x2/jmPgmKYmIEQWjxQPOB9qlrFB5hlAf7zh9ILftEy4aQlKXVS9WrleGsGfEF4lyVF gIJg0JYHONXENSrtvK6+mRBm6yO5j5orm0oS/iVA55w9cmAlaHNUbiAFUIMT23eOdK SF0BuzfrIhUCXSO3AgEdP0bh1Ug4UmsB9j9WNYtqDMpEW5ODNvNC+4pZlUk6H7MWtl lk5Sx2nCk4IBjDbI2WuxeMTaRpbRMkyAwN9iDhz7oUP8Dz88IuKN0Q0LWx1kUOcKc4 NCzmbf+pNY5SQ==
Message-Id: <20130627150745.8C3B821F9D9B@ietfa.amsl.com>
Cc: 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: Thu, 27 Jun 2013 15:07:55 -0000

At 09:42 AM 6/27/2013, Eliot Lear wrote:

>On 6/27/13 3:34 PM, Noel Chiappa wrote:
>>
>> Why not just say directly that 'to prevent "capture", no more than X% of
>> the NomCom may work for a single organization' (where X is 15% or so, so
>> that even if a couple collude, they still can't get control).
>>
>
>It's already in RFC 3777.  No more than 2 per company.


But that's still problematic.  The current rules basically give any company who provides >= 30% of the Nomcom volunteer pool an ~85.1% chance of having 2 members (sum of all percentages from 2-10 members), a 12.1% chance of having 1 and a 2.8% chance of having 0.  


I believe the proposal as stated would further exacerbate that problem - not for a given company, but for pretty much locking small companies and individuals out of the Nomcom.  Once scenario for this - both benign intentions and non-benign - is that a company instead of sending one person to all the meetings starts rotating the opportunity to attend the IETF among a number of people - say 5.  So instead of the potential of say 30 volunteers from one company, we now suddenly have 150.  And me with my single person consultancy - still only has 1 slot to volunteer.



While it would be good to have more people involved, it would be bad in the ways in which larger companies could game the system.

So - I'm not a big fan of the proposal without a lot more analysis of the unintended consequences - and there WILL be unintended consequences.

Mike









From mcr@sandelman.ca  Thu Jun 27 08:12:26 2013
Return-Path: <mcr@sandelman.ca>
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 5300121F924A for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
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 9Zh+MdOtyUXC for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:12:25 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id A7A8F21F918F for <ietf@ietf.org>; Thu, 27 Jun 2013 08:12:22 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id CA53820170; Thu, 27 Jun 2013 12:16:32 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 81D0463A7C; Thu, 27 Jun 2013 11:11:18 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 7477463A5E; Thu, 27 Jun 2013 11:11:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@cisco.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <51CC495F.4010808@cisco.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC0D50.8080708@gmail.com> <9673.1372339268@sandelman.ca> <51CC495F.4010808@cisco.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 27 Jun 2013 11:11:18 -0400
Message-ID: <10884.1372345878@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Arturo Servin <arturo.servin@gmail.com>, 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: Thu, 27 Jun 2013 15:12:26 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Eliot Lear <lear@cisco.com> wrote:
    > I think what you're getting at is that there are different types of r=
emote
    > participation.=C2=A0 If one wants to listen in, that should only requ=
ire the
    > appropriate software and a network connection.=C2=A0 If one actually =
wants to
    > participate, then one either has to get onto a WeBex or Meetecho syst=
em.=C2=A0 The
    > point of this is that there has should be some demonstration that som=
eone
    > substantially participated in an IETF event.

I find that jabber+streamed mp3 is sufficient for a lot of things.
I do not think that one has to actively contribute as much as be available =
to
object to bad ideas.  So, we mostly need to register for that remotely
controlled hum generator.

    > to do so.=C2=A0 Others, on the other hand, require more bandwidth.=C2=
=A0 Case and point:
    > the httpbis working group has held two interim meetings and two more =
are
    > planned.=C2=A0 All off site.=C2=A0 Should these people be counted?=C2=
=A0 If so, how?

I think that once we have a mechanism to count remote participation, we will
use it.  I think that an interim meeting is just part of the in-person
meeting that follows it.  That makes it simple and direct.

An in-person interim meeting may provide substantially more "indoctrination"
to a new person than a full blown meeting.

    > And so, as I said, I'm fine with SM's idea, modulo John's suggested e=
dit.=C2=A0 But
    > I also think it would be useful to look beyond that change as well.

+1


=2D-
]               Never tell me the odds!                 | ipv6 mesh network=
s [
]   Michael Richardson, Sandelman Software Works        | network architect=
  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUcxWFIqHRg3pndX9AQIFuAP/Qu+re3GJByWtYEaUyhWGcAcnWeSovbDl
Bo2/OG3ZUzYig+sbhWpRNiBSRe1AZKKe9T5BLJHD7LP5negCdB6gedl8CErhfwTr
8EKwDsNytT4/UY8/4skurBm5v6AUBzBJGK1D6/4sdd7Kf8r08J8G/qIISSIRblQO
NmWA8+vdFFc=
=c80S
-----END PGP SIGNATURE-----
--=-=-=--

From scott.brim@gmail.com  Thu Jun 27 08:28:13 2013
Return-Path: <scott.brim@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 5C65D21F924A for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 6Bqg+eHqdmt4 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:28:12 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 9E8C821F9E3A for <ietf@ietf.org>; Thu, 27 Jun 2013 08:13:40 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wc20so843480obb.4 for <ietf@ietf.org>; Thu, 27 Jun 2013 08:13:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=bV3werKc0aBmVPyRXspyW76mDyPZJPLJQZCEIjaMrTE=; b=JdBi28s9Rh1cCHVYdDzPUvZaCvAyDVQLMS0qIIzaZm1KVt250oJx59euzfTtKVp/YJ /trwzZ2uIh56ag4iQHFaNnQFfkZT9VQj65mmtPhRCFkcFQXL/aeU1NX09EF1gQQgoAI5 f7I3Os6pWS2Ex08XQjOBgOECAHpfBCehzE5cP5gsMc8Rv7GuJnA9qY9ZK0tbDDafko5n A7qVAsKnenN+UYimdBczbACn60iO8ulda/JqrvycHeIJwKlyyKM1Xb/BOOxqr0Ww0j01 HgFXFc+fKp/t7LJouLqvU7RJAT3pVJ/OyY6n94bgDXAMilO3BzfWhQ1kcJ328OdbDrPc SpEg==
X-Received: by 10.182.214.39 with SMTP id nx7mr4389917obc.20.1372346020024; Thu, 27 Jun 2013 08:13:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.97.37 with HTTP; Thu, 27 Jun 2013 08:13:19 -0700 (PDT)
In-Reply-To: <20130627150745.8C3B821F9D9B@ietfa.amsl.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <20130627150745.8C3B821F9D9B@ietfa.amsl.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 27 Jun 2013 11:13:19 -0400
Message-ID: <CAPv4CP9LauDGChbZ5cCnvy_Vp0KdmiL7fg2m1q6u2QxYZRS1Gw@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
To: Michael StJohns <mstjohns@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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: Thu, 27 Jun 2013 15:28:13 -0000

On Thu, Jun 27, 2013 at 11:07 AM, Michael StJohns <mstjohns@comcast.net> wrote:
> Once scenario for this - both benign intentions and non-benign - is that a company instead of sending one person to all the meetings starts rotating the opportunity to attend the IETF among a number of people - say 5.

Some already do.

From mstjohns@comcast.net  Thu Jun 27 08:31:52 2013
Return-Path: <mstjohns@comcast.net>
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 21DF121F9DB8 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.162
X-Spam-Level: **
X-Spam-Status: No, score=2.162 tagged_above=-999 required=5 tests=[FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 3z+VO-EZx9Kr for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:31:45 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 3B47021F91C4 for <ietf@ietf.org>; Thu, 27 Jun 2013 08:30:36 -0700 (PDT)
Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta03.westchester.pa.mail.comcast.net with comcast id tPtT1l00116LCl053TWawL; Thu, 27 Jun 2013 15:30:34 +0000
Received: from Mike-T530.comcast.net ([63.68.157.173]) by omta06.westchester.pa.mail.comcast.net with comcast id tTWB1l00x3kl1PB3STWKWw; Thu, 27 Jun 2013 15:30:32 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 27 Jun 2013 11:30:14 -0400
To: Scott Brim <scott.brim@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <CAPv4CP9LauDGChbZ5cCnvy_Vp0KdmiL7fg2m1q6u2QxYZRS1Gw@mail.g mail.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <20130627150745.8C3B821F9D9B@ietfa.amsl.com> <CAPv4CP9LauDGChbZ5cCnvy_Vp0KdmiL7fg2m1q6u2QxYZRS1Gw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1372347034; bh=XHB9B/S9m5cGmM59R6b+3lom14DPFRtvLYVK09fTDXQ=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=KFpUz0weJ7CXEaHxUcMPE9Bns1is8CNBlWW7XL7cSVESIBe01wRjb3kXcyyzZt0tl vhTeAJMnlak5KiOZJDla5Pf4/XHnPceaNX1WKahJgKUt702vaC1pc/yeIWx5fg5EJS 1hHDL2VfhGoONa4wGj1z0IX6jVWmmriP/tPQOgqhtRBQpwCE0mO7P2uV1IXC+tWSPM LjysuaKj4fYm6HpKizNqLVFDkWX7igy4ZR+Kx5bvX1KD08TwCc2XEoTnhKe4D9rkQF kyWopkGNPwT8rtltGxMnlrnt6UfNx/ZLvoI8loTGinf+q9B8qXRZYww2llv35vVmOW I+H4NmDPjLWFA==
Message-Id: <20130627153036.3B47021F91C4@ietfa.amsl.com>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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: Thu, 27 Jun 2013 15:31:52 -0000

At 11:13 AM 6/27/2013, Scott Brim wrote:
>On Thu, Jun 27, 2013 at 11:07 AM, Michael StJohns <mstjohns@comcast.net> wrote:
>> Once scenario for this - both benign intentions and non-benign - is that a company instead of sending one person to all the meetings starts rotating the opportunity to attend the IETF among a number of people - say 5.
>
>Some already do.

But those 5 are not Nomcom eligible at this time.  (And that was the "benign" intention I mentioned before...)

Mike



From mstjohns@comcast.net  Thu Jun 27 08:39:24 2013
Return-Path: <mstjohns@comcast.net>
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 C3F4B21F9D56 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.227
X-Spam-Level: **
X-Spam-Status: No, score=2.227 tagged_above=-999 required=5 tests=[AWL=-0.065,  FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_RMML_Stock10=0.13]
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 MfEAWux--OqX for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:39:19 -0700 (PDT)
Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:24]) by ietfa.amsl.com (Postfix) with ESMTP id 0848E21F9D5C for <ietf@ietf.org>; Thu, 27 Jun 2013 08:39:18 -0700 (PDT)
Received: from omta13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by qmta02.emeryville.ca.mail.comcast.net with comcast id tT9D1l00417UAYkA2TfJJP; Thu, 27 Jun 2013 15:39:18 +0000
Received: from Mike-T530.comcast.net ([63.68.157.173]) by omta13.emeryville.ca.mail.comcast.net with comcast id tTev1l00o3kl1PB8ZTf2Xw; Thu, 27 Jun 2013 15:39:16 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 27 Jun 2013 11:38:57 -0400
To: David Meyer <dmm@1-4-5.net>,Eliot Lear <lear@cisco.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <CAHiKxWhB6T5EPmseadYixTZvWe_Frk5AmH7Ejty8DjDxVCGTPA@mail.g mail.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <CAHiKxWhB6T5EPmseadYixTZvWe_Frk5AmH7Ejty8DjDxVCGTPA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1372347558; bh=PsNUlHtdScR2ze4uLu0efTmEsizLihhA0AjvNNaGG30=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=hRqtvcU57wU6s9chE3MlmqozPtisNyCiYHczGW9DV5T4ZJMsWdsQHFvbVr8TM7wHv RNM12kidMZ5+D09hkjC/eru36KUFUnqrXrP8dfNbkWvJZaTNw6YffMa++OP4d61jii DMKM74X0vtBbwf5PWCs9R0YSikGvTpfdznMCenwe2cdiCNLCB5WV39qDHMJaDPK3NJ uk/tDPQRVOdwMASxyzqSI+YqPXr95ZIYrQ+QV5I2A8ZA6xjyhszvgkeIzl4xo2nSDR QTdSU3C9PSuDfgZyYWldxSVIQpu6AkVo2VTUKAAqpy49XgCGfdOmBkjdMzbWKhdsD2 4MTY/4lgiopJA==
Message-Id: <20130627153919.0848E21F9D5C@ietfa.amsl.com>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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: Thu, 27 Jun 2013 15:39:24 -0000

At 09:51 AM 6/27/2013, David Meyer wrote:
>On Thu, Jun 27, 2013 at 6:42 AM, Eliot Lear <lear@cisco.com> wrote:
>>
>> On 6/27/13 3:34 PM, Noel Chiappa wrote:
>>>
>>> Why not just say directly that 'to prevent "capture", no more than X% of
>>> the NomCom may work for a single organization' (where X is 15% or so, so
>>> that even if a couple collude, they still can't get control).
>>>
>>
>> It's already in RFC 3777.  No more than 2 per company.
>
>BTW, while I understand the spirit of 3777 on this point, I have
>always found the restriction somewhat at odds with our belief (hope?)
>that we represent ourselves and the best interest of the Internet at
>the IETF. 

This is where acculturation comes in.  You and I are old hands - we've been doing this almost too long to remember.  This is built into our personal perception of the IETF.  Sadly - I think this attitude has become less and less prevalent, both in the newer companies that have sent people and in the newer people.  Part of this appears to be a belief that the IETF is exactly like all the other standards bodies and can be managed/manipulated by throwing people at it.   Given the current buy-in for the nomcom is about $6K per year per person (based on about a $4K per person direct cost - I don't know how to reasonably estimate the indirect costs of lost production because of travel if any), that provides at least a small barrier to entry to that type of manipulation, as does the acculturation that actually happens if they attend 3/5 meetings.

I really wish the IETF were a group of individuals, but I don't think that's ever been completely true, and I have then impression its getting to the point where its not even mostly true.

Mike



>In addition, a central ethic (IMO anyway) of the IETF has
>always been to honor individualism and independence, so I find it a
>bit strange that in the NomCom context we're all just corporate (or
>otherwise) drones. All of that said, evidently reality doesn't always
>match our ideals, hence clauses like the one you cite from 3777. --dmm



From dmm@1-4-5.net  Thu Jun 27 08:44:26 2013
Return-Path: <dmm@1-4-5.net>
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 4EF1D21F9AF1 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:44:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.248
X-Spam-Level: 
X-Spam-Status: No, score=-0.248 tagged_above=-999 required=5 tests=[FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_RMML_Stock10=0.13]
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 iyEif6bKqa4x for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:44:20 -0700 (PDT)
Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6B37221F9DC7 for <ietf@ietf.org>; Thu, 27 Jun 2013 08:44:20 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id j1so1043965oag.32 for <ietf@ietf.org>; Thu, 27 Jun 2013 08:44:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=BqjpVr452tPnAx3qkW9TbgjqT6YZ38C/hJqTgNnsZdc=; b=YhogjeWij6KF+Mj2lLsJCpZ0Z6G2RS4SRLQcMd2xmEXxkROxafNA85qjXUtYuSbMbA IL/cFwIvbDVd1fG3n51O7vKaAHyWVjq37sGHv4QL+jUeGhnwXnfd/3ctJU6/DV41Tj1y Ry6am9/nCzPR5OCeq4mzIw25O/iQKiduq16Z43SI1FNk6grQqcaICLfx//Y4wkiydD7z w+FlgOgMR2fqInKnTTCCWgyYCTavaPQM7+5SgzyieuHtf0PspJ03LD38jOusVV254EUl 01vlX4JtqJaNbxnFs7P2H/2o0nfzy2nqa4Hk2ZpWvajGu7SADTfRRW4VDs/dl2hPNtVy gz3Q==
MIME-Version: 1.0
X-Received: by 10.60.62.238 with SMTP id b14mr3095373oes.90.1372347859850; Thu, 27 Jun 2013 08:44:19 -0700 (PDT)
Received: by 10.182.114.34 with HTTP; Thu, 27 Jun 2013 08:44:19 -0700 (PDT)
X-Originating-IP: [144.49.132.3]
In-Reply-To: <51cc5ca7.c190420a.1a10.7a3eSMTPIN_ADDED_MISSING@mx.google.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <CAHiKxWhB6T5EPmseadYixTZvWe_Frk5AmH7Ejty8DjDxVCGTPA@mail.gmail.com> <51cc5ca7.c190420a.1a10.7a3eSMTPIN_ADDED_MISSING@mx.google.com>
Date: Thu, 27 Jun 2013 08:44:19 -0700
Message-ID: <CAHiKxWh69ptpNGDATmt-mCORoHcBFFYUPzjmrKtbNYa044guVQ@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
From: David Meyer <dmm@1-4-5.net>
To: Michael StJohns <mstjohns@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlk1CPpmpBPtXF2r5c97R+bbXLHaN+KvkBl8Q3ly1oH2QybLrBjxw8I+IHRwWD0yToCpkve
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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: Thu, 27 Jun 2013 15:44:26 -0000

On Thu, Jun 27, 2013 at 8:38 AM, Michael StJohns <mstjohns@comcast.net> wro=
te:
> At 09:51 AM 6/27/2013, David Meyer wrote:
>>On Thu, Jun 27, 2013 at 6:42 AM, Eliot Lear <lear@cisco.com> wrote:
>>>
>>> On 6/27/13 3:34 PM, Noel Chiappa wrote:
>>>>
>>>> Why not just say directly that 'to prevent "capture", no more than X% =
of
>>>> the NomCom may work for a single organization' (where X is 15% or so, =
so
>>>> that even if a couple collude, they still can't get control).
>>>>
>>>
>>> It's already in RFC 3777.  No more than 2 per company.
>>
>>BTW, while I understand the spirit of 3777 on this point, I have
>>always found the restriction somewhat at odds with our belief (hope?)
>>that we represent ourselves and the best interest of the Internet at
>>the IETF.
>
> This is where acculturation comes in.  You and I are old hands - we've be=
en doing this almost too long to remember.  This is built into our personal=
 perception of the IETF.  Sadly - I think this attitude has become less and=
 less prevalent, both in the newer companies that have sent people and in t=
he newer people.  Part of this appears to be a belief that the IETF is exac=
tly like all the other standards bodies and can be managed/manipulated by t=
hrowing people at it.   Given the current buy-in for the nomcom is about $6=
K per year per person (based on about a $4K per person direct cost - I don'=
t know how to reasonably estimate the indirect costs of lost production bec=
ause of travel if any), that provides at least a small barrier to entry to =
that type of manipulation, as does the acculturation that actually happens =
if they attend 3/5 meetings.
>
> I really wish the IETF were a group of individuals, but I don't think tha=
t's ever been completely true, and I have then impression its getting to th=
e point where its not even mostly true.

Agree with all of your points Mike. --dmm
>
> Mike
>
>
>
>>In addition, a central ethic (IMO anyway) of the IETF has
>>always been to honor individualism and independence, so I find it a
>>bit strange that in the NomCom context we're all just corporate (or
>>otherwise) drones. All of that said, evidently reality doesn't always
>>match our ideals, hence clauses like the one you cite from 3777. --dmm
>
>

From chris.dearlove@baesystems.com  Thu Jun 27 08:49:54 2013
Return-Path: <chris.dearlove@baesystems.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 289D321F9DFD for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level: 
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8]
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 b7MzrTM4u3Ti for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 08:49:49 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 94A6121F9DEE for <ietf@ietf.org>; Thu, 27 Jun 2013 08:49:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,953,1363132800"; d="scan'208";a="296156352"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 27 Jun 2013 16:49:48 +0100
X-IronPort-AV: E=Sophos;i="4.87,953,1363132800"; d="scan'208";a="20395616"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasodc005.greenlnk.net with ESMTP; 27 Jun 2013 16:49:48 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.180]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.02.0328.009; Thu, 27 Jun 2013 16:49:48 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RFC 6234 code
Thread-Topic: RFC 6234 code
Thread-Index: Ac5zTU86ivBUhTyDT4awcyYFLYCBkw==
Date: Thu, 27 Jun 2013 15:49:47 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
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: Thu, 27 Jun 2013 15:49:54 -0000

RFC 6234 contains, embedded in it, code to implement various functions, inc=
luding SHA-2.

Extracting that code from the RFC is not a clean process. In addition the c=
ode must have existed unembedded before being embedded.

Is that code available from the IETF or elsewhere?

(I have tried some approaches to finding such code before posting here, but=
 none successful.)

-- =

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From varun@comnet.tkk.fi  Wed Jun 26 10:43:34 2013
Return-Path: <varun@comnet.tkk.fi>
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 9406C11E80F5; Wed, 26 Jun 2013 10:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 MwpketrAEoBo; Wed, 26 Jun 2013 10:43:28 -0700 (PDT)
Received: from smtp-out-02.aalto.fi (smtp-out-02.aalto.fi [130.233.228.121]) by ietfa.amsl.com (Postfix) with ESMTP id 2D78D21F9DBB; Wed, 26 Jun 2013 10:43:27 -0700 (PDT)
Received: from smtp-out-02.aalto.fi (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 6D6BA271515_1CB283EB; Wed, 26 Jun 2013 17:43:26 +0000 (GMT)
Received: from smtp.netlab.hut.fi (sx2.tct.hut.fi [130.233.154.177]) by smtp-out-02.aalto.fi (Sophos Email Appliance) with ESMTP id 4DC7D27106F_1CB283EF; Wed, 26 Jun 2013 17:43:26 +0000 (GMT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.netlab.hut.fi (Postfix) with ESMTP id 453FE1E142; Wed, 26 Jun 2013 20:43:26 +0300 (EEST)
X-Virus-Scanned: by amavisd-new at luuri.netlab.hut.fi
Received: from smtp.netlab.hut.fi ([127.0.0.1]) by localhost (luuri.netlab.hut.fi [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LeTBDjw9eSWZ; Wed, 26 Jun 2013 20:43:21 +0300 (EEST)
Received: from [192.168.0.10] (cs181253247.pp.htv.fi [82.181.253.247]) by smtp.netlab.hut.fi (Postfix) with ESMTPSA id 8A3E41E13D; Wed, 26 Jun 2013 20:43:21 +0300 (EEST)
Subject: Re: Secdir review of draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Varun Singh <varun@comnet.tkk.fi>
In-Reply-To: <tslhagny6he.fsf@mit.edu>
Date: Wed, 26 Jun 2013 20:43:20 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <90938DE2-4AE6-4C45-B918-6C94CEB12D69@comnet.tkk.fi>
References: <tslhagny6he.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Thu, 27 Jun 2013 08:57:00 -0700
Cc: draft-ietf-xrblock-rtcp-xr-discard-rle-metrics.all@tools.ietf.org, ietf@ietf.org, secdir@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, 26 Jun 2013 17:43:34 -0000

Hi,

Thanks for the comments, comments inline.

On Jun 24, 2013, at 4:37 PM, Sam Hartman wrote:

>=20
>=20
> Please treat these comments as normal last-call comments.
>=20
> I've been asigned as a security directorate reviewer for this draft.
>=20
> This draft specifies a mechanism to indicate which packets were
> discarded in a RTP stream.  for the most part, this doesn't seem to =
have
> any security implications, and the text is clear.  I do have one
> concern.
>=20
> Has the WG analyzed implications of providing feedback to an attacker =
on
> what specific SRTP packets are discarded?  In the past we've run into
> trouble with security systems that were too verbose in error =
reporting.
> As an example, in certain public-key crypto constructions knowing
> whether a packet produced a decoding error vs a signature error after
> decryption can provide an attacker generating forged packets valuable
> information to attack the system.
>=20

In the draft, discarded packets are defined as: packets that were =
received but
dropped from the jitter buffer because they were either too early (for =
buffering)=20
or too late (for playout).=20

Since the timestamp field in the RTP header is not encrypted,=20
the endpoint can discard the packet before decrypting or authenticating =
it.
Forged packets that are discarded are not reported by this metric block.


> It's quite possible that SRTP doesn't have problems in this regard.  I
> just want to confirm that the analysis has been done.=20

Cheers,
Varun=

From hsantos@isdg.net  Thu Jun 27 09:29:51 2013
Return-Path: <hsantos@isdg.net>
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 BB78A21F9DC3 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
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 NWcgMqJmpeTe for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:29:46 -0700 (PDT)
Received: from mail.santronics.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7505921F9DC2 for <ietf@ietf.org>; Thu, 27 Jun 2013 09:29:45 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=595; t=1372350578; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=xN2qScK exEGW1tW3uykue6xBHAw=; b=SfjyNXVo3C+A/fjwHQV3Ic/wCyTDAHWLdVjkNKE +SZwKoeb0hwXjjF/y6E3B8DuHj0gklWTZ9R0NFQUrnSaH9wU/TcUZMtvnU54gxhK gExA7PAnVtwDe+efwnfQh4cFWwrJhKAOG9lErDWrUO8NCfo05qpae3Ilorx4x9Yg 3Wso=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 27 Jun 2013 12:29:38 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3108115918.4136.2800; Thu, 27 Jun 2013 12:29:37 -0400
Message-ID: <51CC67D0.8050600@isdg.net>
Date: Thu, 27 Jun 2013 12:26:56 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: Re: RFC 6234 code
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <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: Thu, 27 Jun 2013 16:29:51 -0000

What language, OS? There are plenty of rich hashing/encrypting C/C++ 
libraries out there. Windows has CAPI, even OPENSSL has these libraries.


On 6/27/2013 11:49 AM, Dearlove, Christopher (UK) wrote:
> RFC 6234 contains, embedded in it, code to implement various functions, including SHA-2.
>
> Extracting that code from the RFC is not a clean process. In addition the code must have existed unembedded before being embedded.
>
> Is that code available from the IETF or elsewhere?
>
> (I have tried some approaches to finding such code before posting here, but none successful.)
>


From sm@elandsys.com  Thu Jun 27 09:30:03 2013
Return-Path: <sm@elandsys.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 535E021F9DEE for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:30:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.76
X-Spam-Level: 
X-Spam-Status: No, score=-98.76 tagged_above=-999 required=5 tests=[SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
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 iacKP-aaaXmT for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:30:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D0C321F9DED for <ietf@ietf.org>; Thu, 27 Jun 2013 09:30:01 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.132.118]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5RGSDCh028031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 09:28:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372350513; bh=4s/KXjVOQ6+swaL+7NLO8mi7C/qfgk86Ft+lAJHH+GU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dIdzknmTzi4SiSoOovpuLVCjko115M0pU+ugAyjiXKdGN02R5d4mt6tr1Ng5ArmZT /5XI2osWxqKZB//rO/F0lJ04mpn+3HygpEgIYCeHrGIZjapPXrcDLNqy3nXRldoCQz TZwgC+0DDgmA4XnVhKVytcCIvapcWORONsCtl93Y=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372350513; i=@elandsys.com; bh=4s/KXjVOQ6+swaL+7NLO8mi7C/qfgk86Ft+lAJHH+GU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MewBFNabGMi3u0E9JnEUCA3SunkpLQPvHlh7Of88rTpXtCZDGW/KOqjdv/IwJajTF 9mGtX4AM26t3XhoaoIC+4tMvOCmSZXlJYddtgxiFwsIcUJBw5G7U+KMKYCBvCtl3x8 bQjfwdr1M6cC5Vhp89tyZ06GeVehb1RFanDwJ4KI=
Message-Id: <6.2.5.6.2.20130627070235.0be04120@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jun 2013 09:26:13 -0700
To: "Eggert, Lars" <lars@netapp.com>, Yoav Nir <ynir@checkpoint.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Olafur Gudmundsson <ogud@ogud.com>, John Curran <jcurran@istaff.org>, Michael Richardson <mcr+ietf@sandelman.ca>, John C Klensin <john-ietf@jck.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Thu, 27 Jun 2013 16:30:03 -0000

Hello,

I'll reply to several messages below to reduce ietf@ mail traffic.

At 03:03 27-06-2013, Eggert, Lars wrote:
>Section 2 says:
>    RFC 3777 [RFC3777], Section 5, "Nominating Committee Operation",
>    Paragraph 1 of Rule 14, is replaced as follows:
>
>       Members of the IETF community must have attended at least 3 of
>       last 5 IETF meetings remotely or in person including at least 1 of
>       the 5 last IETF meetings in person in order to volunteer.
>
>A few questions:
>
>(1) How do you define "remote attendance"?
>
>(2) How does the secretariat determine whether someone has remotely 
>attended? (Based on whatever definition of remote attendance you have in mind.)

I prefer not to get into a definition of "remote attendance" for 
now.  For what it is worth the current system only tells us that a 
person has paid the registration fee.  That person could have gone 
shopping, fallen asleep during the WG sessions, or sitting in a 
corner as he or she does not have a dot and is not considered as important.

Question (2) is based on the assumption that the IETF Secretariat has 
to make that determination.  I am leaving question (1) open as I 
would like to listen to what you and everyone else has to say 
first.  Question (2) could be addressed after that.

At 03:33 27-06-2013, Yoav Nir wrote:
>When we started having one day passes, the question was raised about 
>whether attending on a one day pass "counts" for NomCom eligibility. 
>If I remember correctly the answer was no. So we couldn't let 
>listening in on one session count, right?

Yes.

>I guess you can prove attendance by Jabber log, but that's not 
>really helpful IMO.

Agreed.

At 03:50 27-06-2013, Stephen Farrell wrote:
>I think physically attending 1 meeting might not be enough
>esp. if a nomcom were selected that had a lot of folks on
>who'd only ever been to one meeting. But I'm sympathetic
>to the goal and am sure some qualification rule (*) could
>be worked out. (Probably after about 1000 messages;-)

The MySQL field reserved only has two characters for the message 
count.  As such the limit is 99 messages. :-)

Please note that I am not ignoring the view expressed above.

>However, before getting into that I'd like to hear from
>folks who've been on or chaired nomcoms. I know a lot of
>it is done remotely, but how important is the f2f part
>that happens during meetings? Would it really be ok if
>say 5 voting members could never come to a meeting
>whilst serving? (And I think that'd not be an unlikely
>outcome.)

I'll leave to folks who have been on NomCom to comment.

>(*) Like I said, too early to get into it, but the nomcom
>selection process could also require that the voting
>members collectively have been to N meetings, with each
>voting member able to contribute at most M to that total.
>Say with N=30 and M=4 or something, and keep running the
>random selection until you get 10 voting members that
>satisfy that. And if we went there, we could also require
>that nomcom as a group have written a number of RFCs
>perhaps or even have some folks with Jari's h-index>3
>or something. We could have lots of fun with all that:-)

My first response to the above would be no.  However, there is 
something in the above which is interesting.  Once I get a sense of 
the high level picture I may get back to it.

At 04:06 27-06-2013, Olafur Gudmundsson wrote:
>I read the draft, I think there might be some merit to this proposal 
>but I think the threshold issue should be clarified.

Ok.

>What does "one of the last five mean" during an IETF meeting?

   "The 5 meetings are the five most recent meetings that ended prior
    to the date on which the solicitation for nominating committee
    volunteers was submitted for distribution to the IETF community."

It's any one meeting out of that.


>I think the threshold of having attended one meeting is too low, I 
>would relax the rule to say something like this:
>"must have attended at least 5 meetings of the last 15 and including 
>one of the last 5".
>15 meetings is 5 years, I know that is a long time, t this will 
>allow people that that have been involved for a long time but have limited
>resources to attend to participate in Nomcom/recall processes.

I tried that in another draft.  I dropped the proposal because of 
other NomCom-related issues.

>Q: do you want to limit how many "infrequent" attendees can be on 
>Nomcom just like the number of people from a single organization can sign a
>recall ?

The quick answer is yes.  One of the issues is the assumption behind 
"attended meetings".  There is also the question of fairness.  I will 
have to reconsider my answer based on the views that are expressed.

At 05:36 27-06-2013, John Curran wrote:
>I have read the draft, and believe that it moves the qualification to
>serve on the NomCom in the right direction.  Long-term, it would be ideal
>if remote IETF participation was equivalent (both as an experience and as
>a NomCom qualification) to in-person IETF participation.

My preference is to look for both short term and long term results.

>Noting agreement in the direction, the reality of remote participation
>today is somewhat different.  In recent years, I have been a frequent
>remote participant and occasional on-site participant, and while it is
>possible to effectively contribute to working group efforts remotely,
>such success is predicated on knowing quite a bit about IETF processes
>and workflow, and it not clear to me that a remote participant picks
>up the necessary background at anywhere near the same rate as on-site
>participants.  As a result, I am concerned that the proposed language
>in draft wouldn't necessarily provide for experienced IETF participants
>in the NomCom, and/or those who have well-informed insight into what
>makes for good IAB/IESG/IAOC members.

Reality is a dream that comes true when there is agreement and 
commitment.  I have participated remotely.  In my opinion, it is not 
possible to contribute effectively unless one has read the draft 
being discussed.  Being on-site does not mean that a person has done that.

The reality is that some working groups are not working and it has 
been like that since several meetings.  The reality is that one or 
more directorates have not been working since several years and 
nothing was done about that.

What, among other things, make a good IAOC member is someone who 
reads the contracts before approving them.  I leave it to experienced 
IETF participants to state whether they consider that as well-informed or not.

There are three IAB members from Europe and one from China. There are 
two IESG members from Europe.  There is one IAOC member from 
Europe.  Everyone else is from the United States.  It has always been 
that way and that's how it will be.

I chatted with a student from Greece.  It was the middle of the night 
at his location.  He has never attended the IETF.  He writes code and 
participates in a working group.  He offered to explain to me the 
work being done in that working group.  In my opinion he has an 
understanding of the IETF.  My opinion is based on something he told me.

>Note also that the proposed language also increases the possibility of
>"capture" (i.e. the ability of an single organization to inappropriately
>skew the outcome of the process) in that a relatively large pool of
>remote participants could quickly be made NomCom-eligible by having them
>attend the very next IETF meeting, and then all volunteered to serve on
>the NomCom.  While this is not a particularly likely course for a party
>not happy with the IETF, it is an aspect to be considered in the NomCom
>processes.

There is a limit on affiliation.  Any attempt to "capture" will be visible.

>With an view towards finding a middle ground, would it be possible to
>change your proposed text from:
>
>       "Members of the IETF community must have attended at least 3 of
>       last 5 IETF meetings remotely or in person including at least 1
>       of the 5 last IETF meetings in person in order to volunteer."
>
>to this:
>
>       "Members of the IETF community must have attended at least 3 of
>       last 5 IETF meetings remotely or in person including at least _2_
>       of the 5 last IETF meetings in person in order to volunteer."

Please do not read this as antagonistic.  I will say no.  I am 
actually saying no to the interpretation of "attended".

>The change from 1 to 2 meetings being in-person significantly reduces the
>potential risk of capture while also increasing the exposure level of
>NomCom volunteers to dynamics that occur in the hallways and between the
>formal IETF working group sessions.  The net result recognizes the value
>of remote participation, moves in the right direction, but does so at a
>more moderate pace than you originally propose.

There is a potential risk of doing nothing.  Bernard explained 
something to me.  I think I understood what he wrote.  I would be 
lacking empathy if I blamed him.

I have one word for the proposal, fairness.  I would like to read the 
explanation of the IETF Chair if the potential risk of capture means 
that the IETF cannot be fair.

>Disclaimers:  My views alone.  NomCom '95 Chair (back before any NomCom
>               procedures existed... :-)

Was that during the clergy days? :-)

At 06:18 27-06-2013, Michael Richardson wrote:
>I have not read the thread yet, on purpose.

Ok.

I would like to thank you for going out of your way to do something I asked.

>As a person who has done significant remote participation myself, and has also
>observed the difficulty new people have in understanding how things fit
>together, I can not support your specific proposal, but I support the idea.
>
>I would suggest:
>
>2.  Updated Text from RFC 3777
>
>    RFC 3777 [RFC3777], Section 5, "Nominating Committee Operation",
>    Paragraph 1 of Rule 14, is replaced as follows:
>
>       Members of the IETF community become eligible for the NomCom by
>       having attended at least 3 of the last 7 IETF meetings in person.
>
>       Once a person has become eligible for NomCom, they retain their
>       elibility to NomCom by attending at least 1 of the last 4 IETF meetings
>       in person, and at least 3 of the last 5 meetings in person or remotely.
>
>       Should a person lose eligibility for NomCom, they return to 
> not-eligible.
>
>(We could, true to form, describe this as a state machine with three states,
>or even a simpler to write in Verilog one with 7-8 states)

I agree that new people can have difficulty understanding how things 
fit together.

My quick response to the suggestion is no.  The reason is because of 
the way "attended" is being interpreted and because I don't think 
that it is good to have a high barrier of entry.

>I have lowered the bar to remain eligible such that a person who not travel
>for 12 months (such as someone on maternity/paternity leave. Civilized
>countries get at least 1 year..) could remain eligible.

Thanks for the explanation.  There was an unrelated discussion about 
parents finding it difficult to attend IETF meetings.

At 06:24 27-06-2013, Michael Richardson wrote:
>2) for the November meeting, the nomcom *itself* must be present.
>    I think it unrealistic to think that the nomcom itself could
>    be remote for that meeting.  For the summer and march meeting,
>    the nomcom could be anywhere.

When is it summer? :-)

At 06:48 27-06-2013, John C Klensin wrote:
>While it risks taking us into a statistical rathole, I think
>that notions like the above may be the sort of thing we should
>look at.

I left the door open for that.

>More broadly, I think we may need to try to figure out what we
>really want and need on or from the Nomcom in this decade
>(remembering that the system was designed for the rather
>different times and IETF composition of the early 1990s and has
>been tuned in minor ways but not carefully and openly reviewed
>since) and then try to devise criteria to match.   It seems to
>me that may require looking at separate aspects of things rather
>than trying to come up with a single surrogate for everything.

Yes.

>We might want to look at whether some collections of
>participants should be guaranteed representation or weighted
>more heavily in the selection calculations (whether voting or
>otherwise).  That raises the risk that SM identifies of pushing
>us toward a Nomcom as a representative body of constituencies
>demanding slots, but the advantages seem very strong for Dave
>Crocker's proposal to guarantee a certain level of expertise and
>some ideas to be sure that the perspective of remote
>participants or other underrepresented populations are heard.
>The question is how to find the right balance and then reach
>sufficient consensus around the justification that we can hold
>the line.   Not easy, but, at least IMO, probably worth the
>investment it would take.

I need to get back to something Dave Crocker wrote.  There was a 
discussion (not on an IETF mailing list) which pointed to 
constituencies and representativity.  I don't think that excluding 
people is a good idea.  The last sentence, in a way, sums up what the 
proposal will have to achieve.

>Similarly, I'm pretty sure that "groks the IETF" [1] is an
>important and useful criterion.  I don't think "3 of last 5" is
>a valid exclusive surrogate.  Perhaps what is needed is a list

Yes.

>If we separated the "IETF culture" requirement, I still think
>that some level of participation, even face to face
>participation is important.  I don't think that 3 face to face
>meetings in 5 is needed for people who already understand the
>culture; maybe some combination of remote participation and less
>frequent attendance should be equally acceptable.

The "IETF culture" requirement is ambiguous.  Arturo asked a good 
question.  I would describe the side discussions as being about 
understanding why the IETF is doing X.

>"Participation" is similar.  If we think it is important, then
>someone who is actively contributing to mailing lists and
>document reviews and who is showing up in meeting Jabber logs
>with useful comments is, IMO, a more appropriate Nomcom member
>than someone whose company pays registration fees and travel
>expenses and who then shows up at meetings and either goes to
>the beach or sits in a few WG meetings reading email.  I don't
>know how to eliminate the second (perhaps others have ideas) but
>I can think of ways to identify the former as long as they are
>not the exclusive "minimum participation" admission criteria.

My focus is "participation".

>I would just hope that we don't fall into the trap of focusing
>on what is easy to measure and quantify rather than what is
>important and a good measure of what we are looking for.   It is

I'll add that the trap is also focusing on the details prematurely.

Regards,
S. Moonesamy 


From chris.dearlove@baesystems.com  Thu Jun 27 09:33:24 2013
Return-Path: <chris.dearlove@baesystems.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 B8D6021F997B for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:33:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level: 
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8]
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 O6cdK4q85Cnt for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:33:20 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 1D45B21F9D56 for <ietf@ietf.org>; Thu, 27 Jun 2013 09:33:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,953,1363132800"; d="scan'208";a="296169680"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 27 Jun 2013 17:33:15 +0100
X-IronPort-AV: E=Sophos;i="4.87,953,1363132800"; d="scan'208";a="20402256"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasodc005.greenlnk.net with ESMTP; 27 Jun 2013 17:33:16 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.180]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.02.0328.009; Thu, 27 Jun 2013 17:33:16 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Hector Santos <hsantos@isdg.net>
Subject: RE: RFC 6234 code
Thread-Topic: RFC 6234 code
Thread-Index: Ac5zTU86ivBUhTyDT4awcyYFLYCBk///+uUA///t6lA=
Date: Thu, 27 Jun 2013 16:33:16 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net>
In-Reply-To: <51CC67D0.8050600@isdg.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <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: Thu, 27 Jun 2013 16:33:24 -0000

I want the specific code that is in the RFC (which happens to be in C) rath=
er than some other implementation.

-- =

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Hector Santos [mailto:hsantos@isdg.net] =

Sent: 27 June 2013 17:27
To: Dearlove, Christopher (UK)
Cc: ietf@ietf.org
Subject: Re: RFC 6234 code

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

What language, OS? There are plenty of rich hashing/encrypting C/C++ =

libraries out there. Windows has CAPI, even OPENSSL has these libraries.


On 6/27/2013 11:49 AM, Dearlove, Christopher (UK) wrote:
> RFC 6234 contains, embedded in it, code to implement various functions, i=
ncluding SHA-2.
>
> Extracting that code from the RFC is not a clean process. In addition the=
 code must have existed unembedded before being embedded.
>
> Is that code available from the IETF or elsewhere?
>
> (I have tried some approaches to finding such code before posting here, b=
ut none successful.)
>


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From dave@cridland.net  Thu Jun 27 09:41:52 2013
Return-Path: <dave@cridland.net>
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 B153721F9E4A for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.622
X-Spam-Level: 
X-Spam-Status: No, score=0.622 tagged_above=-999 required=5 tests=[FM_FORGED_GMAIL=0.622, 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 CdxT8MGdvNaP for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:41:52 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id E644F21F9E31 for <ietf@ietf.org>; Thu, 27 Jun 2013 09:41:51 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id v19so943435obq.7 for <ietf@ietf.org>; Thu, 27 Jun 2013 09:41:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TVNYHRcFKSOj0mRtZ/4anfCuMHJu7yF+OH+63lhlmVI=; b=JSubRpzqcV9T371vmrlOuAl0VhCcKNMiN6jGBdU1di/76BlBbieJQstgxcq4HQ3jJ4 agAp+FIzoh9+eJSfMYH5SmB97FBwm+a5DgAT0UTzNZS8cbyLdbcvKW/lPXKtZmsiupe9 kb3W5aSylHMpQAaABVZFjC7n3u8AIRwyOekDk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=TVNYHRcFKSOj0mRtZ/4anfCuMHJu7yF+OH+63lhlmVI=; b=h3n3+5ddAYOsNiTzzeBs2Ps2V/LuQRMNnkAqQ/l+zHyuZ8P7Ogw0TUvIAfnQhNxwLa n2om4TvWfeaC4DljKBwKJ2wgx0XQ4hKj0ZDRlt05+ntUeniXiD2v0hguSmB8ZeU6Tw6B LWdkWdxLy4BuJq721Vndy8PEBpTgAV9jUWW1Mztf/cYR2lpqDPqAHbx3EfEUqPBmaD75 t8U7Q2DGXjRpr6trGHHT0veIY82w2p0UOSZkCTac7joty71o5lB4jgbihXwMxt0eeGQK MCnHF7Od5gEg3xA5GBMePE4QJ9zd9M6NQF6OSY36ZL53P2489LesUQr1g0o6f1Mn96jN LE2w==
MIME-Version: 1.0
X-Received: by 10.60.50.106 with SMTP id b10mr3264483oeo.16.1372351311408; Thu, 27 Jun 2013 09:41:51 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Thu, 27 Jun 2013 09:41:51 -0700 (PDT)
In-Reply-To: <5831.1372344875@sandelman.ca>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC0D50.8080708@gmail.com> <9673.1372339268@sandelman.ca> <CAG4d1rdqiYTk9VZXmn4WGCAtQPxuSvUPGQ5XsFhStJMx84WhvA@mail.gmail.com> <5831.1372344875@sandelman.ca>
Date: Thu, 27 Jun 2013 17:41:51 +0100
Message-ID: <CAKHUCzzhji-UGCQ+FAFf=adB5qLAsBQSsvgcNPrRLa7R62cKiw@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
From: Dave Cridland <dave@cridland.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a11c1cbc06c819904e025707f
X-Gm-Message-State: ALoCoQlVsv8AwHao4XLtQF8B1Annusefa/WYS6yyuxQTTV+CtbU3RmxVvIuyIKLXp6B7cSd8tIaM
Cc: Arturo Servin <arturo.servin@gmail.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: Thu, 27 Jun 2013 16:41:52 -0000

--001a11c1cbc06c819904e025707f
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 27, 2013 at 3:54 PM, Michael Richardson
<mcr+ietf@sandelman.ca>wrote:

>
> Alia Atlas <akatlas@gmail.com> wrote:
>     > I have attended one meeting remotely - and the experience is nothing
> at all
>     > like being at IETF.  I can see modifying NomCom eligibility
> constraints
>     > slightly - but I really do not think that remote attendees will have
> the
>     > necessary experience and acculturation unless they have attended a
> number of
>     > IETFs in person.
>
> That's why, I am not in favour of significantly changing the criteria to
> *become* nomcom eligible.  I really don't think anyone thinks that one can
> become clueful about IETF culture without being there in person a few
> times.
>
>
That's possibly true.

That said, I have been to two meetings, none in the past five, and I
certainly don't think I'm automatically less clueful than all those who've
attended three of the past five.

In my favour, I've a few RFCs, including working group output, and I'm
co-chairing a working group.

Perhaps the volunteer selection process ought to be that working groups
provide a smallish set of volunteers each, and get rid of artificial
eligibility criteria which attempt to obliquely address real - and
important - criteria. I'd perhaps suggest that working group chairs cannot
be "volunteered" by their own working groups.

I suspect that doing things that way would both reflect participation
better, and produce a lot more engagement into the nomination process.

Dave.

--001a11c1cbc06c819904e025707f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Jun 27, 2013 at 3:54 PM, Michael Richardson <span =
dir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">=
mcr+ietf@sandelman.ca</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><=
div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
Alia Atlas &lt;<a href=3D"mailto:akatlas@gmail.com">akatlas@gmail.com</a>&g=
t; wrote:<br>
=A0 =A0 &gt; I have attended one meeting remotely - and the experience is n=
othing at all<br>
=A0 =A0 &gt; like being at IETF. =A0I can see modifying NomCom eligibility =
constraints<br>
=A0 =A0 &gt; slightly - but I really do not think that remote attendees wil=
l have the<br>
=A0 =A0 &gt; necessary experience and acculturation unless they have attend=
ed a number of<br>
=A0 =A0 &gt; IETFs in person.<br>
<br>
</div>That&#39;s why, I am not in favour of significantly changing the crit=
eria to<br>
*become* nomcom eligible. =A0I really don&#39;t think anyone thinks that on=
e can<br>
become clueful about IETF culture without being there in person a few times=
.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br></div></div></blockquote><div><=
br></div><div style>That&#39;s possibly true.</div><div style><br></div><di=
v style>That said, I have been to two meetings, none in the past five, and =
I certainly don&#39;t think I&#39;m automatically less clueful than all tho=
se who&#39;ve attended three of the past five.</div>
<div style><br></div><div style>In my favour, I&#39;ve a few RFCs, includin=
g working group output, and I&#39;m co-chairing a working group.</div><div =
style><br></div><div style>Perhaps the volunteer selection process ought to=
 be that working groups provide a smallish set of volunteers each, and get =
rid of artificial eligibility criteria which attempt to obliquely address r=
eal - and important - criteria. I&#39;d perhaps suggest that working group =
chairs cannot be &quot;volunteered&quot; by their own working groups.</div>
<div style><br></div><div style>I suspect that doing things that way would =
both reflect participation better, and produce a lot more engagement into t=
he nomination process.</div><div style><br></div><div style>Dave.</div>
</div></div></div>

--001a11c1cbc06c819904e025707f--

From lars@netapp.com  Thu Jun 27 09:44:57 2013
Return-Path: <lars@netapp.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 2193521F99FE for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
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 XJntlFhCqWaC for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:44:51 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 341D721F9E02 for <ietf@ietf.org>; Thu, 27 Jun 2013 09:44:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,953,1363158000"; d="scan'208";a="30113777"
Received: from vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) by mx11-out.netapp.com with ESMTP; 27 Jun 2013 09:44:40 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.03.0123.003; Thu, 27 Jun 2013 09:44:40 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
Thread-Topic: The Nominating Committee Process: Eligibility
Thread-Index: AQHOcxvvKlstUrItYkuAdBa8NnJK15lJymeAgABqzoCAAAUlAA==
Date: Thu, 27 Jun 2013 16:44:38 +0000
Message-ID: <509140AF-4C15-44A7-8916-737FD09CFF99@netapp.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com> <6.2.5.6.2.20130627070235.0be04120@resistor.net>
In-Reply-To: <6.2.5.6.2.20130627070235.0be04120@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <294E1D53926E6E45B6D1E0D3833E9459@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, John C Klensin <john-ietf@jck.com>, Olafur Gudmundsson <ogud@ogud.com>
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: Thu, 27 Jun 2013 16:44:57 -0000

Hi,

On Jun 27, 2013, at 18:26, S Moonesamy <sm+ietf@elandsys.com>
 wrote:
>> (1) How do you define "remote attendance"?
>>=20
>> (2) How does the secretariat determine whether someone has remotely atte=
nded? (Based on whatever definition of remote attendance you have in mind.)
>=20
> I prefer not to get into a definition of "remote attendance" for now.

sorry, but it's silly to attempt to propose that remote attendees be permit=
ted to volunteer for NomCom without defining what defines a remote attendee=
.

>  For what it is worth the current system only tells us that a person has =
paid the registration fee.  That person could have gone shopping, fallen as=
leep during the WG sessions, or sitting in a corner as he or she does not h=
ave a dot and is not considered as important.

The issue you are raising - that limiting the NomCom pool to recent attende=
es of physical IETF meetings may have downsides - is valid. But at least th=
e requirements the current policy sets are clearly defined.

Until you nail down what exactly defines a remote attendee, I can't really =
form an opinion on whether allowing them into the NomCom pool is a good ide=
a or not.

Lars


From lars@netapp.com  Thu Jun 27 09:47:19 2013
Return-Path: <lars@netapp.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 97A7A21F9E60 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level: 
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[AWL=4.000, RCVD_IN_DNSWL_HI=-8]
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 AZIeRpgxR0zI for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 09:47:15 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 7321121F9E52 for <ietf@ietf.org>; Thu, 27 Jun 2013 09:47:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,953,1363158000"; d="scan'208";a="69588387"
Received: from vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) by mx12-out.netapp.com with ESMTP; 27 Jun 2013 09:47:15 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.03.0123.003; Thu, 27 Jun 2013 09:47:14 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Subject: Re: RFC 6234 code
Thread-Topic: RFC 6234 code
Thread-Index: Ac5zTU86ivBUhTyDT4awcyYFLYCBkwAQ1bkA
Date: Thu, 27 Jun 2013 16:47:14 +0000
Message-ID: <1113B6A7-1C9D-41D2-B380-82A8013EFEE8@netapp.com>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <77B0EE987838484F814C0E4F3ED3C71A@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <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: Thu, 27 Jun 2013 16:47:19 -0000

Hi,

On Jun 27, 2013, at 17:49, "Dearlove, Christopher (UK)" <Chris.Dearlove@bae=
systems.com> wrote:
> RFC 6234 contains, embedded in it, code to implement various functions, i=
ncluding SHA-2.
>=20
> Extracting that code from the RFC is not a clean process.=20

https://tools.ietf.org/tools/rfcstrip/ can take the headers/footers out. Ex=
tracting the code from its output should be relatively easy.

Lars=

From paul.hoffman@vpnc.org  Thu Jun 27 10:00:41 2013
Return-Path: <paul.hoffman@vpnc.org>
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 2B97E21F9E4E for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 sYkhMyrgya4Z for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:00:40 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id A8E8421F9E4C for <ietf@ietf.org>; Thu, 27 Jun 2013 10:00:40 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5RH0Hwa031145 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 27 Jun 2013 10:00:18 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: The Nominating Committee Process: Eligibility
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <6.2.5.6.2.20130627070235.0be04120@resistor.net>
Date: Thu, 27 Jun 2013 10:00:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <77C69A59-6AFB-4254-BE6B-6224B787C610@vpnc.org>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com> <6.2.5.6.2.20130627070235.0be04120@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: 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: Thu, 27 Jun 2013 17:00:41 -0000

On Jun 27, 2013, at 9:26 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> I prefer not to get into a definition of "remote attendance" for now. =20=


Then maybe we should wait for you to do so. This discussion is kind of =
pointless if we don't have shared definitions.

--Paul Hoffman=

From melinda.shore@gmail.com  Thu Jun 27 10:02:43 2013
Return-Path: <melinda.shore@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 EDC3221F99B4 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 YxMwtUC8W3MM for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:02:43 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 5E76121F99AF for <ietf@ietf.org>; Thu, 27 Jun 2013 10:02:43 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id lf11so1310470pab.24 for <ietf@ietf.org>; Thu, 27 Jun 2013 10:02:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=YhGRmW257WhufiX+Fy/jXBcWS/B4qpd+Oapcei1G6hg=; b=OCYaoUa8hyNb3pem81T6rCDOTbo1hANuN0vTysbT0ze0VOQGIyVFDXb1mfPrN2Whf3 3H9PbQa4PMelf0BTL8CS+1KLk4ieqLoaujtCIgsEgK8xFe3335CqwgF+Y75TPOq4yTNV lOT3I+T+7rgxfBFGeXVZ5nFnzO8GLe8GRZgmJe2xP3jPetgVtBElkFTguHMvLlE7ikqj 8XfjAvfGDlBh8BCzkGvgeNtY6/BeqrlZTDzr1UVmwnZyhlYurXP6ly3GwZBv9nYDU22u q8n44oVUz7sMoEvhc96Cs47AiAw/GWZ2PKbzm6ihLQHmCHMjMuiMpJU/MEc0NqfBFHpM aJwQ==
X-Received: by 10.68.179.35 with SMTP id dd3mr7067827pbc.199.1372352562451; Thu, 27 Jun 2013 10:02:42 -0700 (PDT)
Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id z5sm3980710pbk.0.2013.06.27.10.02.40 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 10:02:41 -0700 (PDT)
Message-ID: <51CC702F.5090603@gmail.com>
Date: Thu, 27 Jun 2013 09:02:39 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <8880FC90-ECE0-405C-9750-9D0A0E6ABC72@iii.ca>
In-Reply-To: <8880FC90-ECE0-405C-9750-9D0A0E6ABC72@iii.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Thu, 27 Jun 2013 17:02:44 -0000

On 6/27/13 5:08 AM, Cullen Jennings wrote:
> I have attended some IETF meetings remotely and I am not in favor of this change.

To be honest, I'm skeptical, myself.  I have attended a lot of
meetings remotely and I don't think that it provides enough
context to be able to provide the background for critical
decisions about leadership.  I'm also not sure what problem
it's trying to solve.

Melinda


From jabley@hopcount.ca  Thu Jun 27 10:22:06 2013
Return-Path: <jabley@hopcount.ca>
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 5F17521F9E69 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 hkT5rx+Husit for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:22:05 -0700 (PDT)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 4A00821F9D3C for <ietf@ietf.org>; Thu, 27 Jun 2013 10:22:05 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id n10so1189336oag.28 for <ietf@ietf.org>; Thu, 27 Jun 2013 10:22:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=E53O/X+p6xOmhyJO3z7t8HOqD3XYszXSXmT5luDwHBI=; b=dYyhYlQ+t77gNJ59DDkHCF1BHh9OmC9FKLljQVBCdpZtfdpNNAGxuTj20iVRNxDDCw +XewzBFLZ7HGmJT5iFRkNpo94ZGWuwQIfg578byaE0vXiyYAjj6uBPjcJ/H2CuWJWREa 6D1HX88obhIQXTqH5VxP/nkS0LbjFiF1mJZBA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=E53O/X+p6xOmhyJO3z7t8HOqD3XYszXSXmT5luDwHBI=; b=oX0u1vIKJQqWDGeUw5iLzmpM+RZe5z2zsBfANldQdOAZSuLyyUq3p34dRYxYHqkWkn n1zvhafA4I+UUvyHY3ctDpADNW9UxsCI2aBOqahT7+z8WM+TvUuXgVeq/5AdYxWFF5J7 EVoYtYjLQdoYp8ZSBnlpGeXhrdZdSGMtTDYH96O5GvWePI9gUh2AFjgOpf+z1ByuEJEU w44zhFPuMdMRFxQh0vHVpW973HB8br2ZSrdGx62AKtdlrV0VLXx60u+HTrq5gdClNNz9 VJxD38oY/ndmEYLdDYR4W6fG7yyUTmS+9RxVd8XDVEACuZLcvX8tHN08hdE+8XzZ2j7K wkAA==
X-Received: by 10.60.115.199 with SMTP id jq7mr3326211oeb.19.1372353724785; Thu, 27 Jun 2013 10:22:04 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:b976:fd77:7f66:3880? ([2001:4900:1042:100:b976:fd77:7f66:3880]) by mx.google.com with ESMTPSA id cp7sm151502obb.0.2013.06.27.10.22.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 10:22:04 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: RFC 6234 code
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net>
Date: Thu, 27 Jun 2013 13:22:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8FC6A38B-7170-480D-9B0D-CD37308A5A82@hopcount.ca>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQkUG9XlXQ8PWZ4nIJhu+1tWK569L9v9OftQVGmWLgLm4fEnJgy+sV1A7eWKqrhd7xpr3ErJ
Cc: "ietf@ietf.org" <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: Thu, 27 Jun 2013 17:22:06 -0000

On 2013-06-27, at 11:49, "Dearlove, Christopher (UK)" =
<chris.dearlove@baesystems.com> wrote:

> RFC 6234 contains, embedded in it, code to implement various =
functions, including SHA-2.
>=20
> Extracting that code from the RFC is not a clean process. In addition =
the code must have existed unembedded before being embedded.
>=20
> Is that code available from the IETF or elsewhere?
>=20
> (I have tried some approaches to finding such code before posting =
here, but none successful.)

Turns out that extracting the code from the RFC is only twenty minutes' =
work. Probably faster just to do it than to talk about it. If you'd like =
a copy of the files I extracted from the RFC text, I can easily send you =
a tarball.

In general I think that maintaining code repositories is non-trivial, =
and also has been known (especially with respect to crypto/hash =
algorithms) to run into export licensing issues. Maintaining an archives =
of RFCs is already a core competency for the IETF, and (at least in some =
cases) exporting text is less problematic than exporting code.


Joe

[krill:~]% mkdir 6234
[krill:~]% cd 6234
[krill:~/6234]% curl -O 'http://tools.ietf.org/rfc/rfc6234.txt'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  =
Current
                                 Dload  Upload   Total   Spent    Left  =
Speed
100  231k  100  231k    0     0   190k      0  0:00:01  0:00:01 --:--:-- =
 190k
[krill:~/6234]% vi rfc6234.txt=20
[krill:~/6234]% ls
hkdf.c			sha.h			stdint-example.h
hmac.c			sha1.c			test-driver.c
rfc6234.txt		sha224-256.c		usha.c
sha-private.h		sha384-512.c
[krill:~/6234]% vi *.h *.c
10 files to edit
[krill:~/6234]% date
Thu 27 Jun 2013 13:14:53 EDT
[krill:~/6234]%=20
[krill:~/6234]% cc -c hmac.c
[krill:~/6234]% cc -c sha1.c
[krill:~/6234]% cc -c sha224-256.c
[krill:~/6234]% cc -c sha384-512.c=20
[krill:~/6234]% cc -c usha.c
[krill:~/6234]% cc -c test-driver.c
[krill:~/6234]% ls
hkdf.c			sha.h			sha384-512.o
hkdf.o			sha1.c			stdint-example.h
hmac.c			sha1.o			test-driver.c
hmac.o			sha224-256.c		test-driver.o
rfc6234.txt		sha224-256.o		usha.c
sha-private.h		sha384-512.c		usha.o
[krill:~/6234]% cc -o test-driver *.o
[krill:~/6234]% ./test-driver| egrep '(PASS|FAIL)'
SHA1 sha standard test 1: PASSED
SHA1 sha standard test 2: PASSED
SHA1 sha standard test 3: PASSED
SHA1 sha standard test 4: PASSED
SHA1 sha standard test 5: PASSED
SHA1 sha standard test 6: PASSED
SHA1 sha standard test 7: PASSED
SHA1 sha standard test 8: PASSED
SHA1 sha standard test 9: PASSED
SHA1 sha standard test 10: PASSED
SHA1 random test 0: PASSED
SHA1 random test 1: PASSED
SHA1 random test 2: PASSED
SHA1 random test 3: PASSED
SHA224 sha standard test 1: PASSED
SHA224 sha standard test 2: PASSED
SHA224 sha standard test 3: PASSED
SHA224 sha standard test 4: PASSED
SHA224 sha standard test 5: PASSED
SHA224 sha standard test 6: PASSED
SHA224 sha standard test 7: PASSED
SHA224 sha standard test 8: PASSED
SHA224 sha standard test 9: PASSED
SHA224 sha standard test 10: PASSED
SHA224 random test 0: PASSED
SHA224 random test 1: PASSED
SHA224 random test 2: PASSED
SHA224 random test 3: PASSED
SHA256 sha standard test 1: PASSED
SHA256 sha standard test 2: PASSED
SHA256 sha standard test 3: PASSED
SHA256 sha standard test 4: PASSED
SHA256 sha standard test 5: PASSED
SHA256 sha standard test 6: PASSED
SHA256 sha standard test 7: PASSED
SHA256 sha standard test 8: PASSED
SHA256 sha standard test 9: PASSED
SHA256 sha standard test 10: PASSED
SHA256 random test 0: PASSED
SHA256 random test 1: PASSED
SHA256 random test 2: PASSED
SHA256 random test 3: PASSED
SHA384 sha standard test 1: PASSED
SHA384 sha standard test 2: PASSED
SHA384 sha standard test 3: PASSED
SHA384 sha standard test 4: PASSED
SHA384 sha standard test 5: PASSED
SHA384 sha standard test 6: PASSED
SHA384 sha standard test 7: PASSED
SHA384 sha standard test 8: PASSED
SHA384 sha standard test 9: PASSED
SHA384 sha standard test 10: PASSED
SHA384 random test 0: PASSED
SHA384 random test 1: PASSED
SHA384 random test 2: PASSED
SHA384 random test 3: PASSED
SHA512 sha standard test 1: PASSED
SHA512 sha standard test 2: PASSED
SHA512 sha standard test 3: PASSED
SHA512 sha standard test 4: PASSED
SHA512 sha standard test 5: PASSED
SHA512 sha standard test 6: PASSED
SHA512 sha standard test 7: PASSED
SHA512 sha standard test 8: PASSED
SHA512 sha standard test 9: PASSED
SHA512 sha standard test 10: PASSED
SHA512 random test 0: PASSED
SHA512 random test 1: PASSED
SHA512 random test 2: PASSED
SHA512 random test 3: PASSED
[krill:~/6234]%=20


From john-ietf@jck.com  Thu Jun 27 10:23:28 2013
Return-Path: <john-ietf@jck.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 AED9721F9BB3 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 libx1VPW4YjD for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:23:22 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C6C9521F9BA0 for <ietf@ietf.org>; Thu, 27 Jun 2013 10:23:22 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UsFuk-000C1t-4r; Thu, 27 Jun 2013 13:23:22 -0400
Date: Thu, 27 Jun 2013 13:23:17 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: The Nominating Committee Process: Eligibility
Message-ID: <95CDE5247D5AF1F1B0B89A9D@JcK-HP8200.jck.com>
In-Reply-To: <20130627150745.8C3B821F9D9B@ietfa.amsl.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <20130627150745.8C3B821F9D9B@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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: Thu, 27 Jun 2013 17:23:28 -0000

--On Thursday, June 27, 2013 11:07 -0400 Michael StJohns
<mstjohns@comcast.net> wrote:

>...
> But that's still problematic.  The current rules basically
> give any company who provides >= 30% of the Nomcom volunteer
> pool an ~85.1% chance of having 2 members (sum of all
> percentages from 2-10 members), a 12.1% chance of having 1 and
> a 2.8% chance of having 0.  

And, of course, a few related companies or one with subsidiaries
that it claims are independent and a desire to game the system
can easily do so today to produce a highly-likely larger number
of members, perhaps even a majority.   We are clearly vunerable
in that area but, perhaps inevitably, have gone down multiple
ratholes as soon as we try to tighten the specifically
anti-capture rules further.  In particular, trying to
second-guess a company's assertions about what entities are
independent of it is just fraught with problems even thought
such assertions can be used to subvert any, or almost any, "no
more than X from one company/interest" rule.

> I believe the proposal as stated would further exacerbate that
> problem - not for a given company, but for pretty much locking
> small companies and individuals out of the Nomcom.  Once
> scenario for this - both benign intentions and non-benign - is
> that a company instead of sending one person to all the
> meetings starts rotating the opportunity to attend the IETF
> among a number of people - say 5.  So instead of the potential
> of say 30 volunteers from one company, we now suddenly have
> 150.  And me with my single person consultancy - still only
> has 1 slot to volunteer.

Yes, but...

(i) Some reasonable set of "demonstrate clue" provisions, if
adopted along with the "demonstrate participation" ones, would
tend to counter that, and might even reduce the available 30 (or
whatever number one picks).

(ii) A notion of "some remote participation is ok if you can
demonstrate clue/ groking the IETF in some other way" actually
helps to protect your ability to volunteer if you suddenly
missed a few consecutive meetings and that of other one-person
consultancies (including, in the interest of full disclosure,
me) and academics like Brian) who have discovered that, as
in-person attendance rises, they need to be selective about face
to face attendance.  If one (and, equivalently, one's one-person
consultancy) can't volunteer, the likelihood of being selected
are zero (and really easy to calculate).

(iii) Unless all of those 150 people were actually participating
actively and contributing to IETF work, the company's actual
ability to influence the standards process would go down.  

> While it would be good to have more people involved, it would
> be bad in the ways in which larger companies could game the
> system.

While I agree, I think it would be really unfortunate if we
discarded opportunities to get a broader spectrum of people
involved because of fears that come company or companies might
misbehave.  I think at least two things work in our favor in the
latter regard.  We can try to educate participants and their
organizations about how little marginal commercial advantage
they would gain by, e.g., getting an extra person on the IETF
and be sure that our other procedures and safeguards reinforce
that.  For example, the reputational harm a company, to say
nothing of the individuals involved, would suffer from a few
recalls based on collusion in support of company positions would
far exceed any possible advantages from having more people in
leadership positions.   I think there is also evidence of courts
and competitiveness/ antitrust authorities being _very_
unsympathetic to organizations who try to subvert open standards
processes.  They, of course, also have the resources and
authority to untangle relationships that we do not.

best,
   john



From arturo.servin@gmail.com  Thu Jun 27 10:24:15 2013
Return-Path: <arturo.servin@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 91A6D21F9D28 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 CpccOKqxewg5 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:24:15 -0700 (PDT)
Received: from mail-ee0-x232.google.com (mail-ee0-x232.google.com [IPv6:2a00:1450:4013:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id DB4D321F9E8F for <ietf@ietf.org>; Thu, 27 Jun 2013 10:24:08 -0700 (PDT)
Received: by mail-ee0-f50.google.com with SMTP id d49so533648eek.23 for <ietf@ietf.org>; Thu, 27 Jun 2013 10:24:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=qxKNxaYJKBf7h2X78H/+VvoCi4XnVTqhN3mZzamLNGo=; b=ycWbns1HuQbyExyyQ4aUFpUBQbOszFh217mNnMW3cUqlXd0Hi/EGyFpNlO6uLro445 Oj60QY5kB5XepGrZNAn8MuHzgaI5KQT/95DL/Zp4vm1iL5NBvedQ2WcqtUug9GAqFcFs Fe1q8Vh5Q3Em94i8HLrGhgvvoOx7hRWXqwCtEnC1e7kz5Io7yjt2AbbhBdhdjgBzrRmk fLfEsBtSgk96km92ClwrcfBXUjsdvhDA9bMfKLUKd3KeZpY8wA++C5hSI2ilFze7o7np jlks0rgCACNStn0XDqyiFCwHjBbs+asiZGi1xBToqvTglHxkxysS1slk4WkjeeiBq9YI aypw==
X-Received: by 10.14.106.195 with SMTP id m43mr10051170eeg.60.1372353847992; Thu, 27 Jun 2013 10:24:07 -0700 (PDT)
Received: from [192.168.0.5] ([90.214.33.42]) by mx.google.com with ESMTPSA id cg12sm5119379eeb.7.2013.06.27.10.24.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 10:24:07 -0700 (PDT)
Message-ID: <51CC7536.1030102@gmail.com>
Date: Thu, 27 Jun 2013 18:24:06 +0100
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: The Nominating Committee Process: Eligibility
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <20130627150745.8C3B821F9D9B@ietfa.amsl.com>
In-Reply-To: <20130627150745.8C3B821F9D9B@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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: Thu, 27 Jun 2013 17:24:15 -0000

    Yes, but instead of 150 volunteers from other organizations we could
have 500. So the probabilities are back to the same.

/as

On 6/27/13 4:07 PM, Michael StJohns wrote:
> I believe the proposal as stated would further exacerbate that problem - not for a given company, but for pretty much locking small companies and individuals out of the Nomcom.  Once scenario for this - both benign intentions and non-benign - is that a company instead of sending one person to all the meetings starts rotating the opportunity to attend the IETF among a number of people - say 5.  So instead of the potential of say 30 volunteers from one company, we now suddenly have 150.  And me with my single person consultancy - still only has 1 slot to volunteer.


From jabley@hopcount.ca  Thu Jun 27 10:24:33 2013
Return-Path: <jabley@hopcount.ca>
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 521DA21F9E8F for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:24:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 9tzZon4764U5 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:24:31 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6C46E21F9E9B for <ietf@ietf.org>; Thu, 27 Jun 2013 10:24:27 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id fb19so997570obc.23 for <ietf@ietf.org>; Thu, 27 Jun 2013 10:24:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=tY3iMlJafzJQchDwCxlls+b9pUAJmykiUi+vV1BUbFM=; b=BWAtwI9FiUiEv98v7rxYXwPKlLxsomfadeu1rFmJNWmM2zkiQxMKK/dEOsnv+jquUV /N0lJnp6w76mC7LkxKG5S/GQtfsvl/k03Q9jnl6fz97g3YJ3aTZHpYeNa0ThuMxXRWrr /NUTWuT4+kWOpMWxduISFJJS030akEYlWY93U=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=tY3iMlJafzJQchDwCxlls+b9pUAJmykiUi+vV1BUbFM=; b=F4+y6YCFJUvUDbtHPA6mAGfzdvshLQ+Sj2c2Cgpu3nH2aEvu8vJ4RCW3R0hqkAnTMQ mXJL7cUidBpiEcGIqcbTwNWDH70Y9N+yRn10yayghKlQ+LJ/vN0csptqrUYH95pEzpNV 8i9Rrq1byeHcp1k6mGKjYy9pJepn7yCgPFhVwJzQyViNmppeJNIZbc/rwwvsw67zmxEi Sot2ETXyMEA5S7LeiJ5CWQVv15+mM+WUel1exvjfq+PHiSJJ+1fbtx1XCuenYn7pq5vA zbC7xevvCcEuWqithCEpYf1yL86WugSG2i6hiAgw29HryWBp2da33i/TJwupJBnr1YLW R7KQ==
X-Received: by 10.60.39.193 with SMTP id r1mr3382877oek.40.1372353866922; Thu, 27 Jun 2013 10:24:26 -0700 (PDT)
Received: from [199.212.90.42] (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id ps5sm759508oeb.8.2013.06.27.10.24.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 10:24:26 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: RFC 6234 code
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <8FC6A38B-7170-480D-9B0D-CD37308A5A82@hopcount.ca>
Date: Thu, 27 Jun 2013 13:24:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D81B10B4-30A7-47D9-B97B-80FB8BF4A278@hopcount.ca>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <8FC6A38B-7170-480D-9B0D-CD37308A5A82@hopcount.ca>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQlFV45TsR08XtIHh6NIfMyG+C6az19p6Z6QFnIuBYr7HUROLmGv9s16PEiGraa3qD26zZID
Cc: "ietf@ietf.org" <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: Thu, 27 Jun 2013 17:24:33 -0000

Oh, I missed the first "date" line in my paste, which makes the second =
one a bit mysterious. Here it is :-)

[krill:~]% date
Thu 27 Jun 2013 12:56:35 EDT
[krill:~]% mkdir 6234
[krill:~]% cd 6234

...

On 2013-06-27, at 13:22, Joe Abley <jabley@hopcount.ca> wrote:

> [krill:~]% mkdir 6234
> [krill:~]% cd 6234
> [krill:~/6234]% curl -O 'http://tools.ietf.org/rfc/rfc6234.txt'
>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  =
Current
>                                 Dload  Upload   Total   Spent    Left  =
Speed
> 100  231k  100  231k    0     0   190k      0  0:00:01  0:00:01 =
--:--:--  190k
> [krill:~/6234]% vi rfc6234.txt=20
> [krill:~/6234]% ls
> hkdf.c			sha.h			stdint-example.h
> hmac.c			sha1.c			test-driver.c
> rfc6234.txt		sha224-256.c		usha.c
> sha-private.h		sha384-512.c
> [krill:~/6234]% vi *.h *.c
> 10 files to edit
> [krill:~/6234]% date
> Thu 27 Jun 2013 13:14:53 EDT
> [krill:~/6234]%=20
> [krill:~/6234]% cc -c hmac.c
> [krill:~/6234]% cc -c sha1.c
> [krill:~/6234]% cc -c sha224-256.c
> [krill:~/6234]% cc -c sha384-512.c=20
> [krill:~/6234]% cc -c usha.c
> [krill:~/6234]% cc -c test-driver.c
> [krill:~/6234]% ls
> hkdf.c			sha.h			sha384-512.o
> hkdf.o			sha1.c			stdint-example.h
> hmac.c			sha1.o			test-driver.c
> hmac.o			sha224-256.c		test-driver.o
> rfc6234.txt		sha224-256.o		usha.c
> sha-private.h		sha384-512.c		usha.o
> [krill:~/6234]% cc -o test-driver *.o
> [krill:~/6234]% ./test-driver| egrep '(PASS|FAIL)'
> SHA1 sha standard test 1: PASSED
> SHA1 sha standard test 2: PASSED
> SHA1 sha standard test 3: PASSED
> SHA1 sha standard test 4: PASSED
> SHA1 sha standard test 5: PASSED

[etc]



From sm@elandsys.com  Thu Jun 27 10:31:59 2013
Return-Path: <sm@elandsys.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 3C18821F9EB5 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:31:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.68
X-Spam-Level: 
X-Spam-Status: No, score=-100.68 tagged_above=-999 required=5 tests=[AWL=1.920, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Cb43Ae6doxll for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:31:58 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D09D21F9EB4 for <ietf@ietf.org>; Thu, 27 Jun 2013 10:31:57 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.132.118]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5RHUIQW024027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 10:30:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372354236; bh=V5L5NsGGYmin+NBTwFbgN441AgAjsVHlp2a+0rS3ATM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fP4uliWA7XYnUVqeYtr0ZfsUktnj2n8v2SFYILl32pHaKpmUyV4LK9swsweQWlBxE 0gx0wdEMdy3isQHYYBW2AJwRqerQto3EgELRHegX8S0Y4UrCJ1nKRgxnL6va1K01x0 LIav8JcGkitG/yy2M/gWCq1uvy76xF185ML9E0po=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372354236; i=@elandsys.com; bh=V5L5NsGGYmin+NBTwFbgN441AgAjsVHlp2a+0rS3ATM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=XrJt/jv/IGKprWYqoj2YbUfiUs3VbFQzVylsds+Vsje5waarV/LNcF44VWpfDdqwr lTrV134Pik3jjMrep274Anz9Ew4FDQMETxKd8YcdVMabCHVfCMMJU6lGKAfxdKKT2U aE0IfjojC3TZG/t93oVS9L6PRws/zk6njqFUYIm4=
Message-Id: <6.2.5.6.2.20130627095214.10ad6408@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jun 2013 10:29:36 -0700
To: "Eggert, Lars" <lars@netapp.com>, Paul Hoffman <paul.hoffman@vpnc.org>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <509140AF-4C15-44A7-8916-737FD09CFF99@netapp.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com> <6.2.5.6.2.20130627070235.0be04120@resistor.net> <509140AF-4C15-44A7-8916-737FD09CFF99@netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, John C Klensin <john-ietf@jck.com>, Olafur Gudmundsson <ogud@ogud.com>
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: Thu, 27 Jun 2013 17:31:59 -0000

At 09:44 27-06-2013, Eggert, Lars wrote:
>sorry, but it's silly to attempt to propose that remote attendees be 
>permitted to volunteer for NomCom without defining what defines a 
>remote attendee.

Agreed.

>The issue you are raising - that limiting the NomCom pool to recent 
>attendees of physical IETF meetings may have downsides - is valid. 
>But at least the requirements the current policy sets are clearly defined.
>
>Until you nail down what exactly defines a remote attendee, I can't 
>really form an opinion on whether allowing them into the NomCom pool 
>is a good idea or not.

What I did in the initial draft is to work from the text already in 
RFC 3777.  It has been mentioned by several people that participation 
is a way for somebody to get IETF experience.   The question is how 
that participation can be defined.

At 10:00 27-06-2013, Paul Hoffman wrote:
>Then maybe we should wait for you to do so. This discussion is kind 
>of pointless if we don't have shared definitions.

I think that the NomCom eligibility criteria should not discriminate 
between any contributor to the IETF Standard Process.  The view I got 
from a previous discussion of the draft is that "people from emerging 
regions are disenfranchised; that's how IETF culture works".

Regards,
S. Moonesamy 


From dhc@dcrocker.net  Thu Jun 27 10:43:34 2013
Return-Path: <dhc@dcrocker.net>
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 F182D21F9E30 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 BRiGHbfBTX7I for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:43:29 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CA58321F9CAD for <ietf@ietf.org>; Thu, 27 Jun 2013 10:43:23 -0700 (PDT)
Received: from [10.58.166.202] (72-254-41-211.client.stsn.net [72.254.41.211]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5RHgwuM017544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 27 Jun 2013 10:43:02 -0700
Message-ID: <51CC799C.9050306@dcrocker.net>
Date: Thu, 27 Jun 2013 10:42:52 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC18FB.1030409@cs.tcd.ie>
In-Reply-To: <51CC18FB.1030409@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 27 Jun 2013 10:43:02 -0700 (PDT)
Cc: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Thu, 27 Jun 2013 17:43:34 -0000

On 6/27/2013 3:50 AM, Stephen Farrell wrote:
> However, before getting into that I'd like to hear from
> folks who've been on or chaired nomcoms. I know a lot of
> it is done remotely, but how important is the f2f part
> that happens during meetings? Would it really be ok if
> say 5 voting members could never come to a meeting
> whilst serving? (And I think that'd not be an unlikely
> outcome.)


I've been a voting member on 3 and liaison on 1.  I can't imagine a 
nomcom process succeeding without a significant amount of face-to-face time.

There are two reasons.  One is creating basic working relationships for 
this type of personnel selection topic -- especially when few of the 
members have much experience with such an exercise.  Much of nomcom is 
about haggling.  Trade-offs about and among candidates.  Debating what's 
true.  Debating what matters.  Debating combinatorials for slates.

All of that is made fundamentally easier -- and easier does not mean 
easy -- when each member has a sense of knowing the other members.  (As 
I recall, there are /many/ research studies about this sort of thing.)

The second reason is interviewing nomination candidates.  There is a 
'feel' for a candidate that one can get from f2f that is much harder to 
obtain with only a voice call.  That said, recent nomcoms seem to have 
de-valued f2f interviews.

So, yes, much of nomcom is thru voice conferencing.  But I believe the 
nature of the decision-making nomcom does requires the group to have had 
significant face-time.

d/



-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From scott.brim@gmail.com  Thu Jun 27 10:50:33 2013
Return-Path: <scott.brim@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 A0A5821F9E84 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.301
X-Spam-Level: 
X-Spam-Status: No, score=-101.301 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 gUpP8AdZx0Ln for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 10:50:32 -0700 (PDT)
Received: from mail-oa0-x22e.google.com (mail-oa0-x22e.google.com [IPv6:2607:f8b0:4003:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 343DE21F9E47 for <ietf@ietf.org>; Thu, 27 Jun 2013 10:50:32 -0700 (PDT)
Received: by mail-oa0-f46.google.com with SMTP id h1so1210078oag.19 for <ietf@ietf.org>; Thu, 27 Jun 2013 10:50:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=oAR6Yas0WJTaF6Son3AZKQMf28zhyq8YDVurkgGN7ME=; b=BxoJVEYCoi4vBGzazeUMpgNvxNYi+tSfAGVsv3ntGCahKsOkQq1Kgy9QXkwvufh0/7 DkM2qX1OIMw3OxJ1LmNyIxpgOOf7lyfTANLT3sSRc2Dy+bNxoUpadJ36uUrgKGdUROdm ILSgsOl8242KcTVC3xvla1LFHLBPEwXIKsEc1v7knCC5JIPgVa8AL8jWpLhD8jEjI3X+ VG4h6iEW2nSzAZXyIPARVfBY2BeZ1AFrK/KvB19K22jzGPIlX2AJFUBZ1cC0msvn3AB5 J2a3d1RNZM9hTmNtq6e7M4OgW6JZOF6KRjN2NT4dQI7262Tx/3UAYQIyOlUP/74SrcoO Q5Rw==
X-Received: by 10.60.97.34 with SMTP id dx2mr3431665oeb.54.1372355431771; Thu, 27 Jun 2013 10:50:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.97.37 with HTTP; Thu, 27 Jun 2013 10:50:11 -0700 (PDT)
In-Reply-To: <51CC7536.1030102@gmail.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <20130627150745.8C3B821F9D9B@ietfa.amsl.com> <51CC7536.1030102@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 27 Jun 2013 13:50:11 -0400
Message-ID: <CAPv4CP8HYn6EGLOj_+PVhkSTprUK+eM_jmfyAZy9vrLjew7wEQ@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
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: Thu, 27 Jun 2013 17:50:33 -0000

These days I don't contribute much to the IETF, so I hesitate to say
much, but I care about it a lot and may contribute again someday.
IMHO ...

Once I lived in Japan for a year and got to think I understood
Japanese culture, but finally realized I had hardly scratched the
surface.  Once, in Germany, I thought Germans were a lot like
Americans, but finally realized I had no idea how different they were.
 And so on.  Likewise, people may think they understand how the IETF
"works", and deduce from that what IETF culture means, when they have
just begun to grasp it.

The IETF mission is already vulnerable.  Most of the time we can hold
the culture together, although it takes a lot of work as unanimity has
already begun falling apart.  If we want to change the mission and
culture, that's okay but we should do so consciously and explicitly.
The NomCom is pivotal for the IETF being able to do its work, to
fulfill its mission, in the future.  People who "know" how the IETF
works but do not have enough experience in the culture will not know
how to express it well, in difficult and subtle situations.  I'm not
talking about knowledge of information, I'm talking about mastery of a
trade -- something that comes with a lot of experience practicing it.

Because of that, weakening requirements for NomCom participation
greatly increases the probability that our culture will fracture, and
our mission statement lose meaning, before we have a chance to agree
on what they should become.  I supported the proposal to require a few
old-timers on every NomCom a few years ago.  I'm quite against the
idea of lowering requirements now.  I would only entrust the future of
the IETF to those who have enough experience and hard-earned wisdom to
make the difficult decisions that are required.  Those who participate
in the process but are not really deep in the culture are already
well-represented through the vehicles for contributing to the NomCom
process.

Scott

From mcr@sandelman.ca  Thu Jun 27 11:47:58 2013
Return-Path: <mcr@sandelman.ca>
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 D066A21F9E21 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 11:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 z8Cy4WBflW2p for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 11:47:58 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id F02AE21F9E15 for <ietf@ietf.org>; Thu, 27 Jun 2013 11:47:57 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 77D042025C; Thu, 27 Jun 2013 15:52:06 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 87CAD63A7C; Thu, 27 Jun 2013 14:46:51 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 75F6163732; Thu, 27 Jun 2013 14:46:51 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <CAPv4CP8HYn6EGLOj_+PVhkSTprUK+eM_jmfyAZy9vrLjew7wEQ@mail.gmail.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <20130627150745.8C3B821F9D9B@ietfa.amsl.com> <51CC7536.1030102@gmail.com> <CAPv4CP8HYn6EGLOj_+PVhkSTprUK+eM_jmfyAZy9vrLjew7wEQ@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Thu, 27 Jun 2013 14:46:51 -0400
Message-ID: <11086.1372358811@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: 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: Thu, 27 Jun 2013 18:47:59 -0000

Scott Brim <scott.brim@gmail.com> wrote:
    > Because of that, weakening requirements for NomCom participation
    > greatly increases the probability that our culture will fracture, and
    > our mission statement lose meaning, before we have a chance to agree
    > on what they should become.  I supported the proposal to require a few
    > old-timers on every NomCom a few years ago.  I'm quite against the
    > idea of lowering requirements now.  I would only entrust the future of
    > the IETF to those who have enough experience and hard-earned wisdom to
    > make the difficult decisions that are required.  Those who participate
    > in the process but are not really deep in the culture are already
    > well-represented through the vehicles for contributing to the NomCom
    > process.

Just as long as you understand that you are influencing the diversity of the nomcom itself.

The people involved will be older, work for bigger companies, and have a
tendancy to be white, north american, male, and not have small
children (or rather, not have made the choice to stay home with child).

Since people tend to pick people who look like them, that means that nomcom
will pick people who are less diverse.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [




From iad@ietf.org  Thu Jun 27 12:06:38 2013
Return-Path: <iad@ietf.org>
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 C501321F9F0F; Thu, 27 Jun 2013 12:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 tm0pTv5lASUX; Thu, 27 Jun 2013 12:06:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D911721F9EA6; Thu, 27 Jun 2013 12:06:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Accessibility of IETF Remote Participation Services
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130627190637.30843.75779.idtracker@ietfa.amsl.com>
Date: Thu, 27 Jun 2013 12:06:37 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org, iaoc-rps@ietf.org
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: Thu, 27 Jun 2013 19:06:39 -0000

From: iaoc-rps@ietf.org
Subject:  Accessibility of IETF Remote Participation Services

For more than a decade, the IETF has tried to make it easier for remote =

attendees to participate in regular and interim face-to-face  meetings.   T=
he =

current tools that the IETF has been using, as well as the state of remote =

participation services in the IETF was summarized by the IETF Chair in a =

message to the IETF-Announce list on 5 February 2013:
http://www.ietf.org/mail-archive/web/ietf/current/msg77020.html


Section 1 summarizes the current remote participation system: =


   The IETF's current remote participation system ("RPS") consists of a
   outbound real-time audio stream for each session carried to remote
   attendees over HTTP, textual multi-user chat carried over XMPP
   (commonly called Jabber), and posting of slides prior to the WG
   session so that they can be downloaded from the IETF web site.

   WebEx and Meetecho are experimentally supported, offering outbound
   real-time audio stream synchronized to the slides for the remote
   participant.  Meetecho displays the Jabber Room on the screen with
   slides, and it can also be used to replay the audio and slides from
   a recording.

As noted in Section 4 of the IETF Chair message, the IETF is currently soli=
citing =

suggestions for improvements in its RPS capabilities.   As part of that, th=
e IETF =

would like to solicit feedback on the accessibility and usability of remote=
 participation =

services by IETF participants with disabilities.  If you would like to comm=
ent on =

the accessibility and usability of IETF RPS services, please send email by =
July 26, 2013 to =

iaoc-rps at ietf.org, Subject: RPS Accessibility, and CC: ietf@ietf.org. =


Bernard Aboba
Chair, IETF Remote Participation Services Committee=20

From paul.hoffman@vpnc.org  Thu Jun 27 12:12:50 2013
Return-Path: <paul.hoffman@vpnc.org>
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 B2E4821F9DCE for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 qYoDWq74Z4Mm for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:12:50 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0E9FC21F9A7E for <ietf@ietf.org>; Thu, 27 Jun 2013 12:12:50 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5RJCShq034408 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 27 Jun 2013 12:12:29 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: The Nominating Committee Process: Eligibility
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <6.2.5.6.2.20130627095214.10ad6408@elandnews.com>
Date: Thu, 27 Jun 2013 12:12:27 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0BC0F734-C4EC-4C71-86FE-7942E3D718A0@vpnc.org>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com> <6.2.5.6.2.20130627070235.0be04120@resistor.net> <509140AF-4C15-44A7-8916-737FD09CFF99@netapp.com> <6.2.5.6.2.20130627095214.10ad6408@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org 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: Thu, 27 Jun 2013 19:12:50 -0000

On Jun 27, 2013, at 10:29 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> I think that the NomCom eligibility criteria should not discriminate =
between any contributor to the IETF Standard Process. =20

-1. Those choosing the leadership of an organization should understand =
more than the leadership of the one WG they have participated in.

> The view I got from a previous discussion of the draft is that "people =
from emerging regions are disenfranchised; that's how IETF culture =
works".

That's one view; another is "we need to be more creative on how to =
increase diversity". "Creative" doesn't mean "ignoring all obvious =
security and stability issues".

--Paul Hoffman=

From abdussalambaryun@gmail.com  Thu Jun 27 12:16:44 2013
Return-Path: <abdussalambaryun@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 9286721F9F21 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 BYOzqD113EzI for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:16:44 -0700 (PDT)
Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 15C4621F9F1D for <ietf@ietf.org>; Thu, 27 Jun 2013 12:16:44 -0700 (PDT)
Received: by mail-pb0-f43.google.com with SMTP id md12so1312004pbc.16 for <ietf@ietf.org>; Thu, 27 Jun 2013 12:16:43 -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=psJEu5HKbwIWp2gnbcwSGpKXMStfUzp75fpZyGrGxUo=; b=y2zErnQeDO1ajU9g1sX58yNx3Q+KlXfGAlHG7BpR1Swu74fBEvAHao2S7Z2V4+iM8A UWnXL0JZIPRwfGIG3sEg3kwIm4Qosqort6Ev0tNYbT7ImnA7KpuxH2K+D9mTIxyvJ9gt 38dxvNlbF0mTe5ZGcRjqcVNYOnJOEXgIFwQAQjw5Qm1nW4lJ4xImPv+Aq8f15Fyz8cyb 9pVI1EckZntSn/7b/Qgdekcs7VBa/2F+vPvr2MbHxKJPMtXsa5eb7tn/Ml08sPLwS3tP xAF0gsz8BOQmdZvQ5XOiq5NsE1+hTveHUGNEsVj4ANyAf1zEeHubPPjZOqoTLqjt24GA UAeg==
MIME-Version: 1.0
X-Received: by 10.68.110.131 with SMTP id ia3mr7701901pbb.181.1372360603743; Thu, 27 Jun 2013 12:16:43 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Thu, 27 Jun 2013 12:16:43 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
Date: Thu, 27 Jun 2013 20:16:43 +0100
Message-ID: <CADnDZ8_Nw9TvfgWhKh5HYWu45s-an9BinHN7_i_wKbA2BR3x=g@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=047d7b673f164a3cd104e0279a71
Cc: ietf <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: Thu, 27 Jun 2013 19:16:44 -0000

--047d7b673f164a3cd104e0279a71
Content-Type: text/plain; charset=ISO-8859-1

Thanks Moonesamy,

I support the draft, it will give all participants from all the world equal
opputunity. I made input related to this on the list because I found that I
am remote participant and there was limits and conditions which I don't
want. However, there may be some reasons that IETF done it that way which
the draft may need to clarify and solve,

AB


On Thu, Jun 27, 2013 at 10:50 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hello,
>
> RFC 3777 specifies the process by which members of the Internet
> Architecture Board, Internet Engineering Steering Group and IETF
> Administrative Oversight Committee are selected, confirmed, and recalled.
>
> draft-moonesamy-nomcom-**eligibility proposes an update RFC 3777 to allow
> remote contributors to the IETF Standards Process to be eligible to serve
> on NomCom and sign a Recall petition ( http://tools.ietf.org/html/**
> draft-moonesamy-nomcom-**eligibility-00<http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-00>).
>
> Could you please read the draft and comment?
>
> Regards,
> S. Moonesamy
>
>

--047d7b673f164a3cd104e0279a71
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks Moonesamy,</div><div>=A0</div><div>I support t=
he draft, it will give all participants from all the world equal opputunity=
. I made input related to this on the list because I found that I am remote=
 participant and there was limits and conditions which I don&#39;t want. Ho=
wever, there may be some reasons that IETF done it that way which the draft=
 may need to clarify and solve,</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Thu, Jun 27, 2013 at 10:50 AM, S Moonesamy <span dir=
=3D"ltr">&lt;<a href=3D"mailto:sm+ietf@elandsys.com" target=3D"_blank">sm+i=
etf@elandsys.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hello,<br>
<br>
RFC 3777 specifies the process by which members of the Internet Architectur=
e Board, Internet Engineering Steering Group and IETF Administrative Oversi=
ght Committee are selected, confirmed, and recalled.<br>
<br>
draft-moonesamy-nomcom-<u></u>eligibility proposes an update RFC 3777 to al=
low remote contributors to the IETF Standards Process to be eligible to ser=
ve on NomCom and sign a Recall petition ( <a href=3D"http://tools.ietf.org/=
html/draft-moonesamy-nomcom-eligibility-00" target=3D"_blank">http://tools.=
ietf.org/html/<u></u>draft-moonesamy-nomcom-<u></u>eligibility-00</a> ).<br=
>

<br>
Could you please read the draft and comment?<br>
<br>
Regards,<br>
S. Moonesamy<br>
<br>
</blockquote></div><br></div>

--047d7b673f164a3cd104e0279a71--

From scott.brim@gmail.com  Thu Jun 27 12:17:38 2013
Return-Path: <scott.brim@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 3BE2E21F859B for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.95
X-Spam-Level: 
X-Spam-Status: No, score=-101.95 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 sOsr1-aGLojQ for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:17:37 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id B3EBD21F859A for <ietf@ietf.org>; Thu, 27 Jun 2013 12:17:37 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wc20so1123473obb.18 for <ietf@ietf.org>; Thu, 27 Jun 2013 12:17:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=NzD8ga10tNaYORZnDDKq9vRei+mG5tpoD/hM3ZCgwj4=; b=snAQXE/x/bJmDSZS5ZTQaSH1xgpujX0ygWeznQiRoIlpdRP9Pt3KSckNi1WmaPzqiD gUXqbUOpvye3E0Ai4Tg00Iwldp/icyf4h8P0ja126/Qx37q7/EzhTJvUdAL1DimQ8dg7 IRGQuRspMuVa98dIujceZfm4P+xGOj0MEf+khpgvfYJPZMEhEL3GHq8nZpfFjajCTArk ROutMNiY2lCPf0p/il9DG0hPFs5f2JEBI+7NOfh6znnfdjO2Q3pKC6Uw6rSBWtK/c9oY 3JH9JGnha8HpluiZKLpxoS/CcHOmvb/VDJWjmWNnVwh1GmuVMVCc//8nY+rvxj0CxzIE rK6A==
X-Received: by 10.60.92.165 with SMTP id cn5mr3650210oeb.53.1372360657305; Thu, 27 Jun 2013 12:17:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.97.37 with HTTP; Thu, 27 Jun 2013 12:17:17 -0700 (PDT)
In-Reply-To: <11086.1372358811@sandelman.ca>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <20130627150745.8C3B821F9D9B@ietfa.amsl.com> <51CC7536.1030102@gmail.com> <CAPv4CP8HYn6EGLOj_+PVhkSTprUK+eM_jmfyAZy9vrLjew7wEQ@mail.gmail.com> <11086.1372358811@sandelman.ca>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 27 Jun 2013 15:17:17 -0400
Message-ID: <CAPv4CP84_YDve9OeY_y=9ACJdO7vhVuBuYkEFY67W0NigXPPzQ@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
To: Michael Richardson <mcr@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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: Thu, 27 Jun 2013 19:17:38 -0000

On Thu, Jun 27, 2013 at 2:46 PM, Michael Richardson <mcr@sandelman.ca> wrote:
> Just as long as you understand that you are influencing the diversity of the nomcom itself.

Yes, we need to cultivate more talent and more viewpoints while
simultaneously using hard-earned wisdom and encouraging growth of that
wisdom in the less experienced.  I'm looking for the proposal from a
few years ago for a balance like that in the NomCom, but haven't found
it yet.

From john-ietf@jck.com  Thu Jun 27 12:34:14 2013
Return-Path: <john-ietf@jck.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 96B9D21F9EC5 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 xZ7599ihPbrc for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:34:08 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B470421F9E8A for <ietf@ietf.org>; Thu, 27 Jun 2013 12:34:08 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UsHxA-000CB1-D0; Thu, 27 Jun 2013 15:34:00 -0400
Date: Thu, 27 Jun 2013 15:33:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>, "Eggert, Lars" <lars@netapp.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: The Nominating Committee Process: Eligibility
Message-ID: <FD9026F66E249FEBE90BCA3D@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20130627095214.10ad6408@elandnews.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com> <6.2.5.6.2.20130627070235.0be04120@resistor.net> <509140AF-4C15-44A7-8916-737FD09CFF99@netapp.com> <6.2.5.6.2.20130627095214.10ad6408@elandnews.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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: Thu, 27 Jun 2013 19:34:14 -0000

--On Thursday, June 27, 2013 10:29 -0700 S Moonesamy
<sm+ietf@elandsys.com> wrote:

> At 09:44 27-06-2013, Eggert, Lars wrote:
>> sorry, but it's silly to attempt to propose that remote
>> attendees be  permitted to volunteer for NomCom without
>> defining what defines a  remote attendee.
> 
> Agreed.

I'm not sure I agree and want to come back to an earlier point
-- we should figure out what we really need and want and then
see if we can work out the details to make it work.  If we
conclude --as I think some have suggested-- that we don't want
often-remote volunteers on the Nomcom no matter what, or that we
don't want people who cannot just about guarantee physical
attendance at all relevant meetings to serve on the Nomcom, or
that we are unwilling to consider relaxing the current 3 of 5
rule for other reasons, then I'd argue that putting energy into
defining appropriate criteria for being a remote attendee is
pretty much a waste of time.  If we do decide we want to open
the door to remote attendees on the Nomcom and later discover
that we can't agree on criteria, that is just how it goes.

In principle, one could consider the "do we want this" and "what
would the criteria be" questions in either order.  In practice,
I think the former question is the more important and should be
considered first because it informs how we really feel about
diversity and the role of participants who don't attend a lot of
f2f meetings.   I also believe that, while I might be very
difficult to come up with a perfect definition of remote
participation on which we could all agree, coming up with a
definite that would be at least as good at discriminating
between actual remote participants and contributors and other
sorts of folks as the current 3 of 5 rule is at discriminating
between those who understand the IETF culture and those who
don't.

>...


--On Thursday, June 27, 2013 13:50 -0400 Scott Brim
<scott.brim@gmail.com> wrote:

> Because of that, weakening requirements for NomCom
> participation greatly increases the probability that our
> culture will fracture, and our mission statement lose meaning,
> before we have a chance to agree on what they should become.
> I supported the proposal to require a few old-timers on every
> NomCom a few years ago.  I'm quite against the idea of
> lowering requirements now.  I would only entrust the future of
> the IETF to those who have enough experience and hard-earned
> wisdom to make the difficult decisions that are required.
> Those who participate in the process but are not really deep
> in the culture are already well-represented through the
> vehicles for contributing to the NomCom process.

Well, I agree with all of that in principle.  In practice, I
don't think the combination of a heavy Nomcom workload and long
period of commitment with the 3 of 5 rule has served us very
well in recent years, especially in terms of guaranteeing that
the criteria you think are important are met.   I think we would
be better off with requirements that made it more feasible for
people like you to volunteer to serve on the Nomcom on the basis
of long-term understanding of the culture, a history of
participating in a diverse collection of WGs, a few less f2f
meetings, and some remote participation.  Instead, the 3 of 5
rule and those other factors have brought us Nomcoms with a
large fraction of the volunteer pool being folks with far less
experience and perspective and a need to rely almost completely
on questionnaires and interviews rather than knowledge.  I don't
think those relative newcomers should be excluded either, but
I'm concerned when they appear to be dominating the volunteer
pool because they are the ones with company support, time on
their hands, and no expectations about getting selected for the
IESG, IAN, or IAOC if they don't volunteer for the Nomcom.

It is certainly possible that considering and making some
changes could make things worse.  But they could also make
things better.  And, IMO, merely having a serious conversation
about what we would like our criteria to be and what we are
trying to optimize is useful.   If nothing else, some relative
newcomers might learn something useful about the culture from
the conversation and how we carry it out.

  best,
   john





From adrian@olddog.co.uk  Thu Jun 27 12:38:46 2013
Return-Path: <adrian@olddog.co.uk>
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 7D52421F9E1A for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.733
X-Spam-Level: 
X-Spam-Status: No, score=-1.733 tagged_above=-999 required=5 tests=[AWL=0.866,  BAYES_00=-2.599]
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 YLtpG5rkan-U for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:38:40 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 6A06C21F9E19 for <ietf@ietf.org>; Thu, 27 Jun 2013 12:38:39 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5RJcbTW008422;  Thu, 27 Jun 2013 20:38:37 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5RJcYSr008414 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 27 Jun 2013 20:38:35 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Michael Richardson'" <mcr@sandelman.ca>, "'Scott Brim'" <scott.brim@gmail.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu>	<51CC4144.70600@cisco.com>	<20130627150745.8C3B821F9D9B@ietfa.amsl.com>	<51CC7536.1030102@gmail.com>	<CAPv4CP8HYn6EGLOj_+PVhkSTprUK+eM_jmfyAZy9vrLjew7wEQ@mail.gmail.com> <11086.1372358811@sandelman.ca>
In-Reply-To: <11086.1372358811@sandelman.ca>
Subject: RE: The Nominating Committee Process: Eligibility
Date: Thu, 27 Jun 2013 20:38:30 +0100
Message-ID: <001d01ce736d$e8e89830$bab9c890$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIjFUpQDvlALVO/0PbZlYSBiyChwQHujvE2AZjPLuQCIJIDPgImDuuSAg+TvF6YUcKBEA==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Thu, 27 Jun 2013 19:38:46 -0000

>     > Because of that, weakening requirements for NomCom participation
>     > greatly increases the probability that our culture will fracture, and
>     > our mission statement lose meaning, before we have a chance to agree
>     > on what they should become.  I supported the proposal to require a few
>     > old-timers on every NomCom a few years ago.  I'm quite against the
>     > idea of lowering requirements now.  I would only entrust the future of
>     > the IETF to those who have enough experience and hard-earned wisdom to
>     > make the difficult decisions that are required.  Those who participate
>     > in the process but are not really deep in the culture are already
>     > well-represented through the vehicles for contributing to the NomCom
>     > process.
> 
> Just as long as you understand that you are influencing the diversity of the
> nomcom itself.
> 
> The people involved will be older, work for bigger companies, and have a
> tendancy to be white, north american, male, and not have small
> children (or rather, not have made the choice to stay home with child).

I can support what Scott says if (and only if) we divide up the composition of
NomCom.  Taken to its extreme, what Scott says might return a NomCom made up
only of people over 65 who have previously served on the IAB/IESG.

But the same applies to SM's draft. Taken to its extreme, SM's draft might
return a NomCom made up only of people who have absolutely no idea how the IETF
functions today, and (more importantly) why.

I think you can rely on each person actually on NomCom to speak their mind and
deliver from their experience (and we can rely on the NomCom chair to tease that
out). So surely we can say something like:
2 old-timers chosen randomly from a list of old-timers
4 people who have been around the IETF a lot (e.g. 3 out of last 5 meetings)
3 people who have worked in the IETF quite a bit (e.g.  front page of > 2 RFCs)
3 people who have evidence of participation in technical work on mailing lists.
Each person is only allowed to be placed in one pool before selection.

I would like to see SM reconsider his Section 2 along these lines (although not
with these precise definitions).

Adrian


From hsantos@isdg.net  Thu Jun 27 12:41:24 2013
Return-Path: <hsantos@isdg.net>
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 27E7821F9F15 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ZNk6dWvHFZcj for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 12:41:19 -0700 (PDT)
Received: from ntbbs.winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2186D21F9EBE for <ietf@ietf.org>; Thu, 27 Jun 2013 12:41:18 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=488; t=1372362068; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=S7ib1On 6DoE+8/daE6xW0VBW/gA=; b=EqtIo7v/YsApUjJwH8icmDI0e0pToh5jSaraLtU m0hntqFLfEg+KIQDjyPnWuwvUhTOPoQ77vghK/pFR+RO8QVIzqZ9+lu7bmT5tTV6 nngs0HAWfnUZTkb8NhQZFgxfbcyPHMjSH6MSYnwTwqC+MY2gE6bBDAbfEZO5aTCZ tx2M=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 27 Jun 2013 15:41:08 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3119605797.4136.4616; Thu, 27 Jun 2013 15:41:07 -0400
Message-ID: <51CC94B2.2060507@isdg.net>
Date: Thu, 27 Jun 2013 15:38:26 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: Re: RFC 6234 code
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <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: Thu, 27 Jun 2013 19:41:24 -0000

Ok, other than time, it should be easy to extract, clean up and cross 
your fingers that it compiles with your favorite C compiler.  But I 
would write to the authors to get the original source. Or google:

     C source crypto libraries API hashing functions

among the first hit:

http://www.cryptopp.com/


On 6/27/2013 12:33 PM, Dearlove, Christopher (UK) wrote:
> I want the specific code that is in the RFC (which happens to be in C) rather than some other implementation.
>


From abdussalambaryun@gmail.com  Thu Jun 27 12:45:37 2013
Return-Path: <abdussalambaryun@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 A760821F9E8D; Thu, 27 Jun 2013 12:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 E91yGMxMig9p; Thu, 27 Jun 2013 12:45:36 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 9F74B21F9E98; Thu, 27 Jun 2013 12:45:36 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr13so1337930pbb.6 for <multiple recipients>; Thu, 27 Jun 2013 12:45:36 -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=2BOn+Tnm8KJIsWgwNAcL7cHFsFQncxvXlWGw1Tcw8Pw=; b=CHfZqR6AFBrAmlCRoddbLfVntCa5P40y4AVxn+7S7GKqsMqQpLD76vtHaJWAenOpZB cT1dNzgAWaiphf/eZqpePNVCk5fz9CpsWIbApQQ+SfxY/eQyyNSVrhFyGCLYXoplLwHf hWrr/Uwyoyp2zZk5BVunVJ3Gwxat+cvZRu9eIVxkkXaLWeUXzf1nHeQ0GXm3LvIS5O4w dMPeJ68WoVK0kOLbZRTQgUDVF02qYJN9zfUC1cKFpzLAGikl3BRTWJBewdUko8CQ3/CJ Y97ZZY8mClYJAk6lkAs/sLp+s372/IvOlXE4CTdcvQ6CUfx3y8AdxLgvcgezwtinB8le OYAg==
MIME-Version: 1.0
X-Received: by 10.68.230.40 with SMTP id sv8mr7723844pbc.30.1372362336354; Thu, 27 Jun 2013 12:45:36 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Thu, 27 Jun 2013 12:45:36 -0700 (PDT)
In-Reply-To: <20130627190637.30843.75779.idtracker@ietfa.amsl.com>
References: <20130627190637.30843.75779.idtracker@ietfa.amsl.com>
Date: Thu, 27 Jun 2013 20:45:36 +0100
Message-ID: <CADnDZ8-z4GXvv34VL+eN_sxmaxGwuj-0Z9_dh_YgEhuwV7FtNQ@mail.gmail.com>
Subject: Re: Accessibility of IETF Remote Participation Services
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: iaoc-rps@ietf.org
Content-Type: multipart/alternative; boundary=047d7b33946d8fc75f04e0280154
Cc: ietf <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: Thu, 27 Jun 2013 19:45:37 -0000

--047d7b33946d8fc75f04e0280154
Content-Type: text/plain; charset=ISO-8859-1

As per a request I received from you
============================

Dear Bernard,
Chair, IETF Remote Participation Services Committee

Thanks for your message. I am a remote participant that never ever came to
the IETF meetings and not sure if I would. I think my experience may help
your committee and it will help my investigation as well about the IETF
performance. I hope that your committee has some people that are remote to
IETF, so they have the feeling of our feelings.

My feedback (as you request it) can be as below:

< The below observation is owned by the sender to be used in future I-draft
>

1- I don't feel that some WG chairs give importance to remote participants,
maybe even presenters in IETF may not even know who is in remote. This
needs to be improved.

2- I rememebr that once while my participation, I asked about how many f2f
participants in the room agree or disagree, and I was noticed, but it will
be helpful if WG chairs are using Jabber while checking the consensus, and
say what is the situation, because I felt that the remote participants were
not checked if they agree or disagree only f2f participants.

3- I as remote participant when I enter a room I want to know how many
attending the room from both (f2f and remote), I only know how many are
remote, and I seen some f2f participants are also in remote so they can see
both sessions in the room.

4- We need more interaction from remote people than from f2f participants,
I have feeling that the attended f2f are driving the meeting, no equal
opportunity between participants

5- Some use the excuse of time limits, so remote people can easily be
excluded from time used because maybe not important in the room
discussions. Why do you get that feeling, IMHO all are equal and important,
otherwise the IETF should give all regions equal meeting times.

6- I got once an I-D and wanted to present it while I was remote, but the
IETF did not provide a way to enable me to present that I-D. I tried even
to find a person to present but no one done for me. I was excluded even
when I already done some efforts, does that mean that people who cannot
attend cannot get their I-D adopted?

7- I have many other points but would like to leave them to my future I-Ds
that when I get better time will share, but above are the main ones.

Best Regards
AB



On Thu, Jun 27, 2013 at 8:06 PM, IETF Administrative Director
<iad@ietf.org>wrote:

> From: iaoc-rps@ietf.org
> Subject:  Accessibility of IETF Remote Participation Services
>
> For more than a decade, the IETF has tried to make it easier for remote
> attendees to participate in regular and interim face-to-face  meetings.
> The
> current tools that the IETF has been using, as well as the state of remote
> participation services in the IETF was summarized by the IETF Chair in a
> message to the IETF-Announce list on 5 February 2013:
> http://www.ietf.org/mail-archive/web/ietf/current/msg77020.html
>
>
> Section 1 summarizes the current remote participation system:
>
>    The IETF's current remote participation system ("RPS") consists of a
>    outbound real-time audio stream for each session carried to remote
>    attendees over HTTP, textual multi-user chat carried over XMPP
>    (commonly called Jabber), and posting of slides prior to the WG
>    session so that they can be downloaded from the IETF web site.
>
>    WebEx and Meetecho are experimentally supported, offering outbound
>    real-time audio stream synchronized to the slides for the remote
>    participant.  Meetecho displays the Jabber Room on the screen with
>    slides, and it can also be used to replay the audio and slides from
>    a recording.
>
> As noted in Section 4 of the IETF Chair message, the IETF is currently
> soliciting
> suggestions for improvements in its RPS capabilities.   As part of that,
> the IETF
> would like to solicit feedback on the accessibility and usability of
> remote participation
> services by IETF participants with disabilities.  If you would like to
> comment on
> the accessibility and usability of IETF RPS services, please send email by
> July 26, 2013 to
> iaoc-rps at ietf.org, Subject: RPS Accessibility, and CC: ietf@ietf.org.
>
> Bernard Aboba
> Chair, IETF Remote Participation Services Committee
>

--047d7b33946d8fc75f04e0280154
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>As per a request I received from you</div><div>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D</div><div>=A0</div><div>Dear Bernard,</div><div>Chair, IETF Remote Part=
icipation Services Committee</div><div>=A0</div><div>Thanks for your messag=
e. I am a remote participant that never ever came to the IETF meetings and =
not sure if I would. I think my experience may help your committee and it w=
ill help my investigation as well about the IETF performance. I hope that y=
our committee has some people that are remote to IETF, so they have the fee=
ling of our feelings.</div>
<div>=A0</div><div>My feedback (as you request it) can be as below:</div><d=
iv>=A0</div><div>&lt; The below observation is owned by the sender to be us=
ed in future I-draft &gt;</div><div>=A0</div><div>1- I don&#39;t feel that =
some WG chairs give importance to remote participants, maybe even presenter=
s in IETF may not even know who is in remote. This needs to be improved.</d=
iv>
<div>=A0</div><div>2- I rememebr that once while my participation, I asked =
about how many f2f participants in the room agree or disagree, and I was no=
ticed, but it will be helpful if WG chairs are using Jabber while checking =
the consensus, and say what is the situation, because I felt that the remot=
e participants were not checked if they agree or disagree only f2f particip=
ants.</div>
<div>=A0</div><div>3- I as remote participant when I enter a room I want to=
 know how many attending the room from both (f2f and remote), I only know h=
ow many are remote, and I seen some f2f participants are also in remote so =
they can see both sessions in the room.</div>
<div>=A0</div><div>4- We need more interaction from remote people=A0than fr=
om f2f participants, I have feeling that the attended f2f=A0are driving=A0t=
he meeting, no equal opportunity between participants</div><div>=A0</div><d=
iv>5- Some use the excuse of time limits, so remote people can easily be ex=
cluded from time used=A0because maybe not important in the room discussions=
. Why do you get that feeling, IMHO all are equal and important, otherwise =
the IETF should give all regions equal meeting times.</div>
<div>=A0</div><div>6- I got once an I-D and wanted to present it while I wa=
s remote, but the IETF did not provide a way to enable me to present that I=
-D. I tried even to find a person to present but no one done for me. I was =
excluded even when I already done some efforts, does that mean that people =
who cannot attend cannot get their I-D adopted?</div>
<div>=A0</div><div>7- I have many other points but would like to leave them=
 to my future I-Ds that when I get better time will share, but above are th=
e main ones.</div><div>=A0</div><div>Best Regards</div><div>AB</div><div>=
=A0</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
 Jun 27, 2013 at 8:06 PM, IETF Administrative Director <span dir=3D"ltr">&l=
t;<a href=3D"mailto:iad@ietf.org" target=3D"_blank">iad@ietf.org</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">From: <a href=3D"mailto:iaoc-rps@ietf.org">i=
aoc-rps@ietf.org</a><br>
Subject: =A0Accessibility of IETF Remote Participation Services<br>
<br>
For more than a decade, the IETF has tried to make it easier for remote<br>
attendees to participate in regular and interim face-to-face =A0meetings. =
=A0 The<br>
current tools that the IETF has been using, as well as the state of remote<=
br>
participation services in the IETF was summarized by the IETF Chair in a<br=
>
message to the IETF-Announce list on 5 February 2013:<br>
<a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg77020.html"=
 target=3D"_blank">http://www.ietf.org/mail-archive/web/ietf/current/msg770=
20.html</a><br>
<br>
<br>
Section 1 summarizes the current remote participation system:<br>
<br>
=A0 =A0The IETF&#39;s current remote participation system (&quot;RPS&quot;)=
 consists of a<br>
=A0 =A0outbound real-time audio stream for each session carried to remote<b=
r>
=A0 =A0attendees over HTTP, textual multi-user chat carried over XMPP<br>
=A0 =A0(commonly called Jabber), and posting of slides prior to the WG<br>
=A0 =A0session so that they can be downloaded from the IETF web site.<br>
<br>
=A0 =A0WebEx and Meetecho are experimentally supported, offering outbound<b=
r>
=A0 =A0real-time audio stream synchronized to the slides for the remote<br>
=A0 =A0participant. =A0Meetecho displays the Jabber Room on the screen with=
<br>
=A0 =A0slides, and it can also be used to replay the audio and slides from<=
br>
=A0 =A0a recording.<br>
<br>
As noted in Section 4 of the IETF Chair message, the IETF is currently soli=
citing<br>
suggestions for improvements in its RPS capabilities. =A0 As part of that, =
the IETF<br>
would like to solicit feedback on the accessibility and usability of remote=
 participation<br>
services by IETF participants with disabilities. =A0If you would like to co=
mment on<br>
the accessibility and usability of IETF RPS services, please send email by =
July 26, 2013 to<br>
iaoc-rps at <a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a>, Sub=
ject: RPS Accessibility, and CC: <a href=3D"mailto:ietf@ietf.org">ietf@ietf=
.org</a>.<br>
<br>
Bernard Aboba<br>
Chair, IETF Remote Participation Services Committee<br>
</blockquote></div><br></div>

--047d7b33946d8fc75f04e0280154--

From jabley@hopcount.ca  Thu Jun 27 13:06:39 2013
Return-Path: <jabley@hopcount.ca>
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 29A5911E80FD for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 13:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 zAaG-HTXr+Pp for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 13:06:38 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id A7DBA11E80F9 for <ietf@ietf.org>; Thu, 27 Jun 2013 13:06:38 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id v19so1181491obq.35 for <ietf@ietf.org>; Thu, 27 Jun 2013 13:06:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=cZ08Ck5vFL3+AS9WR7e4Tffren9pHQXSodYwRhtx8lg=; b=UP8cG6Wf8rwh3dX9rYJkPkQ58KI4LLj87OoNbgHXHw2CaeNZM4HPGyyL0/LBhakRjX GtkOCEl3iGn9XfiWHNhFHJD23cTi3CjdJh8UBw964AKuFbdacCyQkRilTzQYRrD1IhmV /3/COB1dCqCjysyUMj8BFazi6AlTReirrA888=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=cZ08Ck5vFL3+AS9WR7e4Tffren9pHQXSodYwRhtx8lg=; b=UkrSsHwDGWnnqOIV6w9bny+Y6kkDhZ7Rq2Drhj2hdsGoPmthetxcy93HjHTWXUKtcV EpsWKPx5m/NizpD8UXOJ2aI0uDGj+j79snhownJrJq/LWdgdbha3bX4zppgqgKzusme9 2JlmPi6PVOKxdZh1XN3b0zs0qKyUzs1haw9TGnr3YQ7JHy1IGH8GLALBifLlfNfbZuR8 tPT0jM+IrlK24rITHvTFs7OxtIKgyRda117FoNxuU2IWaAA2u/ZYxElj3BOwpCkkYXFo xHF/jLpEzuoKLEuYYvPX3bYCCS0c+m2qrQmda3iIThruiFGdDciflkR5RoEPrV9+ZWms VZMw==
X-Received: by 10.182.247.100 with SMTP id yd4mr5066037obc.46.1372363598144; Thu, 27 Jun 2013 13:06:38 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:b976:fd77:7f66:3880? ([2001:4900:1042:100:b976:fd77:7f66:3880]) by mx.google.com with ESMTPSA id df11sm965177oec.0.2013.06.27.13.06.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 13:06:37 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: RFC 6234 code
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <51CC94B2.2060507@isdg.net>
Date: Thu, 27 Jun 2013 16:06:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <56C73846-26CD-4B22-B5ED-383CD877CB09@hopcount.ca>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQkLaxoQNrcEcsiy0fT5Bbu64NJVGZwxtE85e5CfCsb3hhxhAn7V/vhlmq3ZgYM3ceDqU8pm
Cc: "ietf@ietf.org" <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: Thu, 27 Jun 2013 20:06:39 -0000

On 2013-06-27, at 15:38, Hector Santos <hsantos@isdg.net> wrote:

> Ok, other than time, it should be easy to extract, clean up and cross =
your fingers that it compiles with your favorite C compiler.

Having just done it, I'm happy to report that there was little =
finger-crossing involved. The fact that there's a fairly comprehensive =
test suite included in the source code in the RFC makes it quite easy to =
gain confidence that the non-test code was extracted intact, beyond the =
simple lack of compiler warnings.


Joe


From agenda@ietf.org  Thu Jun 27 14:58:51 2013
Return-Path: <agenda@ietf.org>
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 948D521F9DB0; Thu, 27 Jun 2013 14:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.844
X-Spam-Level: 
X-Spam-Status: No, score=-101.844 tagged_above=-999 required=5 tests=[AWL=0.756, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 rBpJR2yqWiWp; Thu, 27 Jun 2013 14:58:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 311FB21F9D69; Thu, 27 Jun 2013 14:58:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Agenda <agenda@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 87 Preliminary Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130627215851.18352.24360.idtracker@ietfa.amsl.com>
Date: Thu, 27 Jun 2013 14:58:51 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF Agenda <agenda@ietf.org>
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: Thu, 27 Jun 2013 21:58:51 -0000

The IETF 87 Preliminary Agenda has been posted.  The final agenda will be p=
ublished on Friday, July 5th.  =


https://datatracker.ietf.org/meeting/87/agenda.html
https://datatracker.ietf.org/meeting/87/agenda.txt

https://www.ietf.org/meeting/87/index.html

Thank you!

IETF Secretariat

From mcr@sandelman.ca  Thu Jun 27 15:13:22 2013
Return-Path: <mcr@sandelman.ca>
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 669AD21F9E81; Thu, 27 Jun 2013 15:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 oUCoMw9TIis4; Thu, 27 Jun 2013 15:13:18 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id D120021F9E7E; Thu, 27 Jun 2013 15:13:17 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id B241A2018C; Thu, 27 Jun 2013 19:17:20 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 4719563A7C; Thu, 27 Jun 2013 18:12:05 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3AA1263732; Thu, 27 Jun 2013 18:12:05 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: iaoc-rps@ietf.org
Subject: Re: Accessibility of IETF Remote Participation Services
In-Reply-To: <20130627190637.30843.75779.idtracker@ietfa.amsl.com>
References: <20130627190637.30843.75779.idtracker@ietfa.amsl.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 27 Jun 2013 18:12:05 -0400
Message-ID: <8612.1372371125@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: 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: Thu, 27 Jun 2013 22:13:22 -0000

--=-=-=


>>>>> "iaoc-rps" == iaoc-rps  <iaoc-rps@ietf.org> writes:
    iaoc-rps> As noted in Section 4 of the IETF Chair message, the IETF is
    iaoc-rps> currently soliciting suggestions for improvements in its RPS
    iaoc-rps> capabilities.   As part of that, the IETF would like to solicit
    iaoc-rps> feedback on the accessibility and usability of remote
    iaoc-rps> participation services by IETF participants with disabilities.
    iaoc-rps> If you would like to comment on

I am unclear about the question.  (I don't think AB read it through at all)

I believe that you are asking about people with disabilities such as physical
(eyes, hands, ears,) and mental (learning, dyslexia, etc.), but the subject
talks about accessibility.  They aren't exactly the same thing.

Sometimes a web site is "accessible" if it "works with any browser" rather
than IE5 in 1024x768.
Is not being willing to run unstable browser plugins a "disability"?
(or being unwilling to run an unstable operating system to run a less stable
browser...)

You have mentioned webex (which comes from a single vendor) and meetecho
(which unifies a number of IETF standards into one place) as well as the
underlying technologies.  Are you asking for *accessibility* issues with
webex (it breaks regularly for me, audio has never, ever, worked), or are you
asking about usability issues that people have with it?
I know two really smart people that never figured out how to find the
chat window on webex, or who muted themselves and were unable to unmute -- I
know that there is lots of undiagnostic austistic-spectrum people in our
community.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUcy4soqHRg3pndX9AQKabAP+Ic/5aoTCAJNmUsRy/EuAIhSbtxh4yYr7
7IVe/JccF/nfX6ZFuKUs8QjdgTjqk8J0LPnfJXnqOJWPwmuNcbOPyLpRxOJSsUcZ
NL8MO8xmq3OLByEggFLBAvlTphmN5+mYROQsXk++Ckv5Jgnc0AZjwkgX1D6hafx8
1RNzEqQGXio=
=nnAA
-----END PGP SIGNATURE-----
--=-=-=--

From dougb@dougbarton.us  Thu Jun 27 15:14:14 2013
Return-Path: <dougb@dougbarton.us>
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 1432C21F9947 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 15:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 tJRKGBsmaLAp for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 15:14:10 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE4B21F9E80 for <ietf@ietf.org>; Thu, 27 Jun 2013 15:14:10 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:48c1:e1bd:d924:315] (unknown [IPv6:2001:470:d:5e7:48c1:e1bd:d924:315]) by dougbarton.us (Postfix) with ESMTPSA id AE7AB22B13 for <ietf@ietf.org>; Thu, 27 Jun 2013 22:14:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1372371249; bh=Z8UhgzhB7bRqASmGx9xOsE/bkotu8AqfgIubbWD3viQ=; h=Date:From:To:Subject:References:In-Reply-To; b=FokNv4yza5xWQ9r0zFSLBO4MQxHJkEtVFPJhd6K9vHQwcYpNoGZ/qxzGeVTmsTd+l qJQP9eKuJMOPakVRp5adQ8Ji/EIvAuBdHIhuJ3NS8pyK9vKVGKyjqwDpwIdjZvOVQK TFsmJuCV39vvUwhIZxzuaLcFEfCQjK1VP7FIt5qM=
Message-ID: <51CCB931.8010105@dougbarton.us>
Date: Thu, 27 Jun 2013 15:14:09 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The Nominating Committee Process: Eligibility
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 27 Jun 2013 22:14:14 -0000

On 06/27/2013 02:50 AM, S Moonesamy wrote:
> Hello,
>
> RFC 3777 specifies the process by which members of the Internet
> Architecture Board, Internet Engineering Steering Group and IETF
> Administrative Oversight Committee are selected, confirmed, and recalled.
>
> draft-moonesamy-nomcom-eligibility proposes an update RFC 3777 to allow
> remote contributors to the IETF Standards Process to be eligible to
> serve on NomCom and sign a Recall petition (
> http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-00 ).
>
> Could you please read the draft and comment?

FWIW, all opinions my own, etc. :)

I have attended several meetings in person, and several remotely. 
Unfortunately I do not support the concept of allowing remote attendance 
to qualify a person for Nomcom.

As others have pointed out, the acculturation that happens during in 
person attendance is a significant part of this issue. Included in that 
is the chance to have at least some exposure to potential candidates as 
people outside of what is seen in e-mail and on line during meetings. 
Those who participate remotely don't have that opportunity, and IMO the 
Nomcom would be the poorer because of that.

I am definitely sympathetic to the argument that meeting attendance 
places a high burden on the participants, and being able to attend 
enough meetings to become Nomcom eligible is a substantial investment. 
However I don't see a practical way to change that without a significant 
changes in IETF structure. (Arguably such changes may be desirable, but 
it would have to come wholesale, not piecemeal.)

Doug


From dhc@dcrocker.net  Thu Jun 27 15:33:44 2013
Return-Path: <dhc@dcrocker.net>
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 24E7511E80DC; Thu, 27 Jun 2013 15:33:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ILaElwp+4lI1; Thu, 27 Jun 2013 15:33:39 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 23DC811E80D2; Thu, 27 Jun 2013 15:33:39 -0700 (PDT)
Received: from [192.168.1.116] (99-150-245-122.lightspeed.sndgca.sbcglobal.net [99.150.245.122]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5RMXQfQ026753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 27 Jun 2013 15:33:34 -0700
Message-ID: <51CCBDAE.8000201@dcrocker.net>
Date: Thu, 27 Jun 2013 15:33:18 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org, iaoc-rps@ietf.org
Subject: Re: Accessibility of IETF Remote Participation Services
References: <20130627190637.30843.75779.idtracker@ietfa.amsl.com>
In-Reply-To: <20130627190637.30843.75779.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 27 Jun 2013 15:33:38 -0700 (PDT)
Cc: wgchairs@ietf.org, iaoc@ietf.org, iab@iab.org, iesg@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Thu, 27 Jun 2013 22:33:44 -0000

On 6/27/2013 12:06 PM, IETF Administrative Director wrote:
>    As part of that, the IETF
> would like to solicit feedback on the accessibility and usability of remote participation
> services by IETF participants with disabilities.  If you would like to comment on
> the accessibility and usability of IETF RPS services,


To the extent that the intent is to formulate requirements, it would 
probably help to augment community comments by hiring an interaction and 
web usability and accessibility expert to review current and plausible 
capabilities.

Since the topic is a professional specialty that is not certain to be 
represented amongst IETF protocol engineers who choose to comment, it 
seems wise to ask for help from a professional.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From sm@elandsys.com  Thu Jun 27 15:56:02 2013
Return-Path: <sm@elandsys.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 DC6D211E8117 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 15:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.639
X-Spam-Level: 
X-Spam-Status: No, score=-101.639 tagged_above=-999 required=5 tests=[AWL=0.960, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 dCQpWdovg1U8 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 15:56:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2794A11E8114 for <ietf@ietf.org>; Thu, 27 Jun 2013 15:56:00 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.132.118]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5RMtiMg000135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 15:55:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372373757; bh=KESTyBZtDO+OEVnIl/E+42UJ7k9qbW8RI+ObWN9OlVY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pWRphtu3XpA6rBglRYv9vu5lWq+pRt7ydy4pT437sQvSqZ+IxQ16gPkBvnZirDc/Z Er2huGkK9rAEq6aoaQ3PbQhQ/OTygbLyClKUFVtDdcbA3JvU+pJSGVowxx8p6tvq6l CJAP7JpiWOn3R8hclfemJSU2orC7GeFc25Tf6aaE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372373757; i=@elandsys.com; bh=KESTyBZtDO+OEVnIl/E+42UJ7k9qbW8RI+ObWN9OlVY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dKWvaoaTZLIMtO9IypGyz37jlaGrF1Rp4HDH1+o5ZvozraPMxfCHUajqRsKVY1FIo SfJY3T+jolW6SXXljwyQfGhVpT2J4GEkpRbs//f8b0eRjBjaH78Ui78MD5Hx8iMuiz nxofEMf2sVjiz6Npouv9XYv48W4AXlxuQF4fEoQ0=
Message-Id: <6.2.5.6.2.20130627131527.10bff450@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jun 2013 15:54:14 -0700
To: John C Klensin <john-ietf@jck.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <FD9026F66E249FEBE90BCA3D@JcK-HP8200.jck.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com> <6.2.5.6.2.20130627070235.0be04120@resistor.net> <509140AF-4C15-44A7-8916-737FD09CFF99@netapp.com> <6.2.5.6.2.20130627095214.10ad6408@elandnews.com> <FD9026F66E249FEBE90BCA3D@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Thu, 27 Jun 2013 22:56:03 -0000

Hi John,
At 12:33 27-06-2013, John C Klensin wrote:
>I'm not sure I agree and want to come back to an earlier point
>-- we should figure out what we really need and want and then
>see if we can work out the details to make it work.  If we

The definition of "attend" is and has been people who pay the 
attendance fee for the three out of the last five meetings.

I'll quote a part of Paul Hoffman's message:

   "-1. Those choosing the leadership of an organization should
    understand more than the leadership of the one WG they have
    participated in."

Currently, the people choosing IAB and IESG members do not even have 
to understand as much as the leadership of the working group they 
have participated in.  I'll quote an extract from Scott Brim's message:

   "I would only entrust the future of the IETF to those who have enough
    experience and hard-earned wisdom to make the difficult decisions that
    are required.  Those who participate in the process but are not really
    deep in the culture are already well-represented through the vehicles
    for contributing to the NomCom process."

And part of a reply from Michael Richardson:

   "The people involved will be older, work for bigger companies, and have a
    tendancy to be white, north american, male, and not have small
    children (or rather, not have made the choice to stay home with child).

    Since people tend to pick people who look like them, that means that nomcom
    will pick people who are less diverse."

I'll go back to what is said to be oral tradition:

   "The strength of the IAB is found in part in the balance of the demographics
    of its members (e.g., national distribution, years of experience, gender,
    etc.), the combined skill set of its members, and the combined sectors
    (e.g., industry, academia, etc.) represented by its members."

In my opinion the IETF has solved the problem on paper.  If I take, 
for example, gender, there is only one woman on the IAB.  Had the IAB 
been able to address the gender problem over the last 10 years?  I 
would say no (I am using "no" as it is easier for people for which 
English is not their native language to easily understand my response).

Is there balance in the national distribution of IAB members?  I 
would say no (see above for explanation of the "no").   Is there 
balance in industry and academia affiliations?  I would say no.

Those issues have been discussed during the diversity debate and even 
before that.  I am reluctant to make a suggestion that makes the IETF 
an oligarchy.  I took at quick look at this thread.  Most of the 
participants are from North America.  There are two women who have 
commented.  If Adrian Farrel asks me why we do not see participation 
from South America and Africa, my answer is:

  If you entrust the future of the IETF to those who have enough experience and
  hard-earned wisdom the end result is that the rest of the world 
will not believe
  that it is worthwhile to participate unless they have money to gain from that
  participation.

I'll quote an extract from Michael StJohns:

   "Sadly - I think this attitude has become less and less prevalent,
    both in the newer companies that have sent people and in the newer
    people.  Part of this appears to be a belief that the IETF is exactly
    like all the other standards bodies and can be managed/manipulated by
    throwing people at it."

The fact is that there has been NomCom lobbying.  That fact was 
reported a few years ago.  Is there a link between that and what 
Michael StJohns said?  I don't know.

The "open list" approach was adopted a few years back.  Two NomComs 
had different interpretations of the RFC.  I don't think that it 
matters much.  The point here is that definitions are subject to 
interpretation.  For example, there was a previous NomCom discussion 
about the affiliation of an IETF participant.

This is a side note, I'll use Ted Lemon as an example.  I see that he 
is affiliated with nominum.com.  It is easy for anyone to determine 
that.  I'll compare him with Olafur Gudmundsson.  I see that he is 
ogud.com.  Let's say that they are both chairs of a DNS-related 
working group.  Would the average working group participant be 
comfortable to ask about affiliation if he or she is not happy with a 
decision these working group chairs have taken?  Would NomCom members 
be aware of a questionable decision they have taken and how they 
handled the situation?   Would people who do not have the opportunity 
to be physically present at a meeting be comfortable providing 
negative feedback about them if the person does not personally know 
one of the NomCom members?

The IETF had to wait until Olafur stepped forward with a Recall 
petition before doing anything about an ex-IETF Trust Chair who 
likely understood IETF culture.

I agree that it would be good to figure out what is really needed and 
desired and then work out the details.

>conclude --as I think some have suggested-- that we don't want
>often-remote volunteers on the Nomcom no matter what, or that we
>don't want people who cannot just about guarantee physical
>attendance at all relevant meetings to serve on the Nomcom, or
>that we are unwilling to consider relaxing the current 3 of 5
>rule for other reasons, then I'd argue that putting energy into
>defining appropriate criteria for being a remote attendee is
>pretty much a waste of time.  If we do decide we want to open
>the door to remote attendees on the Nomcom and later discover
>that we can't agree on criteria, that is just how it goes.

Yes.

>In principle, one could consider the "do we want this" and "what
>would the criteria be" questions in either order.  In practice,
>I think the former question is the more important and should be
>considered first because it informs how we really feel about
>diversity and the role of participants who don't attend a lot of
>f2f meetings.   I also believe that, while I might be very
>difficult to come up with a perfect definition of remote
>participation on which we could all agree, coming up with a
>definite that would be at least as good at discriminating
>between actual remote participants and contributors and other
>sorts of folks as the current 3 of 5 rule is at discriminating
>between those who understand the IETF culture and those who
>don't.

In my opinion the easier path is to focus on contributors.  The IETF 
culture angle is  controversial because it is like saying that the 
person has to adopt North America culture.

>Well, I agree with all of that in principle.  In practice, I
>don't think the combination of a heavy Nomcom workload and long
>period of commitment with the 3 of 5 rule has served us very
>well in recent years, especially in terms of guaranteeing that
>the criteria you think are important are met.   I think we would
>be better off with requirements that made it more feasible for
>people like you to volunteer to serve on the Nomcom on the basis
>of long-term understanding of the culture, a history of
>participating in a diverse collection of WGs, a few less f2f
>meetings, and some remote participation.  Instead, the 3 of 5

The above does not require any process changes.

>rule and those other factors have brought us Nomcoms with a
>large fraction of the volunteer pool being folks with far less
>experience and perspective and a need to rely almost completely
>on questionnaires and interviews rather than knowledge.  I don't

Yes.

>It is certainly possible that considering and making some
>changes could make things worse.  But they could also make
>things better.  And, IMO, merely having a serious conversation
>about what we would like our criteria to be and what we are
>trying to optimize is useful.   If nothing else, some relative
>newcomers might learn something useful about the culture from
>the conversation and how we carry it out.

A side-effect of the discussion could be about enabling new people to 
learn something useful.  If the only way to learn something useful 
about the culture is to have a meeting near your home or to have 
extensive travel resources to get to a meeting the IETF is 
restricting itself to people who work for large vendors.  I leave it 
to the reader to determine whether it leads to large corporate 
control of IETF standards.

I'll quote an extract of a message from the IETF Chair (presently IAB 
Chair) and IAOC Chair:

   "The IETF has always used the Internet to do its work, and remote
    participation is no exception."

Is that correct or is the definition of the IETF everything except 
the IAB, IESG, IAOC, IETF Trust and NomCom?

The IETF mentioned that:

   "Currently, the IETF meets in North America, Europe, and Asia. The intention
    is to meet once a year in each region, although due to scheduling issues
    there are often more meetings in North America and fewer in Asia 
and Europe."

The intention is commendable.  In my opinion it is what happens in 
practice that matters.  I'll quote Olaf (I forgot the actual words): 
the IAB publishes its minutes so that anybody who cares can see what 
the IAB is doing.  If there is a scheduling issue people might 
understand it.  If there are two or three of four scheduling issues 
some people might still be understand it.  If there are systematic 
scheduling issues people will no longer believe what Olaf is saying.

Regards,
S. Moonesamy 


From brian.e.carpenter@gmail.com  Thu Jun 27 16:24:28 2013
Return-Path: <brian.e.carpenter@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 1D3D021F9DEA for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 16:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 vjSbCmAEhUlm for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 16:24:27 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 35C3621F9DE3 for <ietf@ietf.org>; Thu, 27 Jun 2013 16:24:27 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id rl6so1691456pac.1 for <ietf@ietf.org>; Thu, 27 Jun 2013 16:24:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=2l8xf262FpSpVDRPdnRn8NPx/YlRsT8NK5qQN6WL44Y=; b=tOuI6NoT3cMHEV+TkAMtlq6y9b9I7pBaX19WVIt55PHuljR/1lQmvinsPiKkprPMfU 5sbvhz9Bs5xq5g6mumQmblvtiPNDzPtlQXNbU7rW1PtWlzS9KJ1G6LrK+PCmU3Z5Opxe KazKJdxl5VbhDfyQLASf4NgtagbpReOeCxhuyM1FBUzZc5ZnVgGtt+H9WJKVPcTeq94L NGdKfGxcftfham57P+xajeZ8kt8I2GxcOL+b8xFydOWkDFmfwIq3u9CnY8EUE9A3jixe XMoj1GR3wH2aHAPayVwTUjO3uhtlnuDmDyoTxHgUdtDQkd9W62jK09nvJtV5YJIIkwqC /8EA==
X-Received: by 10.68.219.194 with SMTP id pq2mr8542291pbc.151.1372375467006; Thu, 27 Jun 2013 16:24:27 -0700 (PDT)
Received: from [192.168.178.22] (133.198.69.111.dynamic.snap.net.nz. [111.69.198.133]) by mx.google.com with ESMTPSA id yj2sm5042239pbb.40.2013.06.27.16.24.25 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 16:24:26 -0700 (PDT)
Message-ID: <51CCC9B3.70606@gmail.com>
Date: Fri, 28 Jun 2013 11:24:35 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Evi Nemeth
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Thu, 27 Jun 2013 23:24:28 -0000

Evi used to be an IETF regular. There is rather ominous news - she is
lost at sea between New Zealand and Australia:

http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=10893482

http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=10893503

Regards
   Brian Carpenter



From john-ietf@jck.com  Thu Jun 27 16:30:13 2013
Return-Path: <john-ietf@jck.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 D149711E810C for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 16:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 5LtmE2Sz0QZG for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 16:30:08 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C9D6A21F99A8 for <ietf@ietf.org>; Thu, 27 Jun 2013 16:30:08 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UsLdg-000CPP-Db; Thu, 27 Jun 2013 19:30:08 -0400
Date: Thu, 27 Jun 2013 19:30:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: Evi Nemeth
Message-ID: <4A4D208E6E2940BDEF5945A4@JcK-HP8200.jck.com>
In-Reply-To: <51CCC9B3.70606@gmail.com>
References: <51CCC9B3.70606@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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: Thu, 27 Jun 2013 23:30:13 -0000

--On Friday, June 28, 2013 11:24 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> Evi used to be an IETF regular. There is rather ominous news -
> she is lost at sea between New Zealand and Australia:
> 
> http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=
> 10893482
> 
> http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=
> 10893503

Brian,

Thanks for posting this.  Truly scary... she and her colleagues
should be in all of our thoughts and prayers.

  john


From akatlas@gmail.com  Thu Jun 27 16:33:12 2013
Return-Path: <akatlas@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 A4E8421F9A5F for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 16:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 kszudjtFbMRN for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 16:33:12 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3695921F88EA for <ietf@ietf.org>; Thu, 27 Jun 2013 16:32:53 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id x12so2571573ief.26 for <ietf@ietf.org>; Thu, 27 Jun 2013 16:32:52 -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=l41M9CyyDeeoM8h8U2Ib4x9wr8UUtK2eqIsbUMwG83s=; b=EmCVwnNJRPOMVYehildDcXFnXU1dSN+ZLVj8bWAtS4oSQUvEoB5N7kHajfH2ofBOhN BIXid3IaZPmBlVeJ5QnKas1HG8CEQwZQf/+EXmx39435dILhBWONhxJIiB5+L14ip0jh FUUYCtg2sP+68gw81q9gCrbJrelYh8rEL+7TMStxU8shkSZiL/KOvPRCBX8/NdHOwauC yy4XAO5kk32PzJgfK0ZtaAdRNTRP036tX6QOZK29kJomD5hDoKOxV6pSsPoV/lieQd7f 9Nk2e8af9lNbeYFVCjTdWT9LCY/ZYmid4pZTmDEpphqME8sh12wON41geWGdp7QZpsK1 mzmA==
MIME-Version: 1.0
X-Received: by 10.50.1.70 with SMTP id 6mr926519igk.54.1372375972770; Thu, 27 Jun 2013 16:32:52 -0700 (PDT)
Received: by 10.64.47.168 with HTTP; Thu, 27 Jun 2013 16:32:52 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130627131527.10bff450@elandnews.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <2B6C3EBE-3A54-483D-B352-0B9768B88EC8@netapp.com> <6.2.5.6.2.20130627070235.0be04120@resistor.net> <509140AF-4C15-44A7-8916-737FD09CFF99@netapp.com> <6.2.5.6.2.20130627095214.10ad6408@elandnews.com> <FD9026F66E249FEBE90BCA3D@JcK-HP8200.jck.com> <6.2.5.6.2.20130627131527.10bff450@elandnews.com>
Date: Thu, 27 Jun 2013 19:32:52 -0400
Message-ID: <CAG4d1rdyHZ8+sTJYx51cjepUSjx+u1iUZbazqxDHwqfHR5vRJw@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
From: Alia Atlas <akatlas@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=047d7bd6c7305afcef04e02b2ede
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: Thu, 27 Jun 2013 23:33:12 -0000

--047d7bd6c7305afcef04e02b2ede
Content-Type: text/plain; charset=ISO-8859-1

[I have significantly cut down the thread to respond to a couple points.]

On Thu, Jun 27, 2013 at 6:54 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
>
>
>  In principle, one could consider the "do we want this" and "what
>> would the criteria be" questions in either order.  In practice,
>> I think the former question is the more important and should be
>> considered first because it informs how we really feel about
>> diversity and the role of participants who don't attend a lot of
>> f2f meetings.   I also believe that, while I might be very
>> difficult to come up with a perfect definition of remote
>> participation on which we could all agree, coming up with a
>> definite that would be at least as good at discriminating
>> between actual remote participants and contributors and other
>> sorts of folks as the current 3 of 5 rule is at discriminating
>> between those who understand the IETF culture and those who
>> don't.
>>
>
> In my opinion the easier path is to focus on contributors.  The IETF
> culture angle is  controversial because it is like saying that the person
> has to adopt North America culture.


The IETF is the protector of what I'd describe as a "public good".  When I
talk about IETF culture, part of what I mean is having people understand
this and have the desire to protect, preserve, and grow it - rather than
loot it for their (or their company's) profit.  It might be viewed as
helping the "pie get larger" instead of thinking of it as zero-sum game.
 Knowing what is important to preserve and protect is also important, but
can be learned.

Alia

--047d7bd6c7305afcef04e02b2ede
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style>[I have significantly cut down the thread to re=
spond to a couple points.]</div><br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">On Thu, Jun 27, 2013 at 6:54 PM, S Moonesamy <span dir=3D"=
ltr">&lt;<a href=3D"mailto:sm+ietf@elandsys.com" target=3D"_blank">sm+ietf@=
elandsys.com</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
In principle, one could consider the &quot;do we want this&quot; and &quot;=
what<br>
would the criteria be&quot; questions in either order. =A0In practice,<br>
I think the former question is the more important and should be<br>
considered first because it informs how we really feel about<br>
diversity and the role of participants who don&#39;t attend a lot of<br>
f2f meetings. =A0 I also believe that, while I might be very<br>
difficult to come up with a perfect definition of remote<br>
participation on which we could all agree, coming up with a<br>
definite that would be at least as good at discriminating<br>
between actual remote participants and contributors and other<br>
sorts of folks as the current 3 of 5 rule is at discriminating<br>
between those who understand the IETF culture and those who<br>
don&#39;t.<br>
</blockquote>
<br></div>
In my opinion the easier path is to focus on contributors. =A0The IETF cult=
ure angle is =A0controversial because it is like saying that the person has=
 to adopt North America culture.</blockquote><div><br></div><div style>The =
IETF is the protector of what I&#39;d describe as a &quot;public good&quot;=
. =A0When I talk about IETF culture, part of what I mean is having people u=
nderstand this and have the desire to protect, preserve, and grow it - rath=
er than loot it for their (or their company&#39;s) profit. =A0It might be v=
iewed as helping the &quot;pie get larger&quot; instead of thinking of it a=
s zero-sum game. =A0Knowing what is important to preserve and protect is al=
so important, but can be learned.</div>
<div style><br></div><div style>Alia</div><div>=A0</div></div></div></div>

--047d7bd6c7305afcef04e02b2ede--

From dhc@dcrocker.net  Thu Jun 27 16:39:31 2013
Return-Path: <dhc@dcrocker.net>
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 8246A21F9CD9 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 16:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 UqPNHe7THd+q for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 16:39:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 070AD21F9CB6 for <ietf@ietf.org>; Thu, 27 Jun 2013 16:39:27 -0700 (PDT)
Received: from [192.168.1.116] (99-150-245-122.lightspeed.sndgca.sbcglobal.net [99.150.245.122]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5RNdN62028036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 27 Jun 2013 16:39:26 -0700
Message-ID: <51CCCD24.2080601@dcrocker.net>
Date: Thu, 27 Jun 2013 16:39:16 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Evi Nemeth
References: <51CCC9B3.70606@gmail.com>
In-Reply-To: <51CCC9B3.70606@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 27 Jun 2013 16:39:26 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Thu, 27 Jun 2013 23:39:31 -0000

On 6/27/2013 4:24 PM, Brian E Carpenter wrote:
> Evi used to be an IETF regular. There is rather ominous news - she is
> lost at sea between New Zealand and Australia:



    http://en.wikipedia.org/wiki/Evi_Nemeth

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From sm@elandsys.com  Thu Jun 27 16:56:43 2013
Return-Path: <sm@elandsys.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 CE7F311E813A for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 16:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.959
X-Spam-Level: 
X-Spam-Status: No, score=-101.959 tagged_above=-999 required=5 tests=[AWL=0.640, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 PfGL4R0gWJUa for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 16:56:43 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CF4FA11E812E for <ietf@ietf.org>; Thu, 27 Jun 2013 16:56:42 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.132.118]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5RNuFQK021225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 16:56:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372377388; bh=0kVLHNdjMUx6urPBXFIkLiLvEahPCtJQG+MpTLPQ1y4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WdlsA9pZ3ufsvxAWQyAa6/ifpfCDHFN3+7OVyOALZeYzgvhk9n5BHElVhGPrp+ba0 Py52DHPuqbcoFGguyL8ZmkX0baq+8yeDuPZbmuwM9n3aHNsy2fNVSCcFMCyF3O8mm4 6STIafZE8Mi+VW7PSy35SUxr1LslfXYIydVC4PNE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372377388; i=@elandsys.com; bh=0kVLHNdjMUx6urPBXFIkLiLvEahPCtJQG+MpTLPQ1y4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3f+eIkDaWhoeshtGXKKQMZe6BMq8dugQhl2JW3FqcSinsciO89x5MW5yB4TRx/01l kAo6cpPOi/SDGlUr+LkLV9ExMIAlI0XKZNkmurJ39KsYOVqKrYpYe5Lk8dYJA8nMxT vicZ+eK0swj4ZhOzksqf+4e8KDGWu5DEwRwQ0KCs=
Message-Id: <6.2.5.6.2.20130627162513.10447070@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jun 2013 16:38:25 -0700
To: adrian@olddog.co.uk
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: The Nominating Committee Process: Eligibility
In-Reply-To: <001d01ce736d$e8e89830$bab9c890$@olddog.co.uk>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <20130627150745.8C3B821F9D9B@ietfa.amsl.com> <51CC7536.1030102@gmail.com> <CAPv4CP8HYn6EGLOj_+PVhkSTprUK+eM_jmfyAZy9vrLjew7wEQ@mail.gmail.com> <11086.1372358811@sandelman.ca> <001d01ce736d$e8e89830$bab9c890$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, Michael Richardson <mcr@sandelman.ca>
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: Thu, 27 Jun 2013 23:56:44 -0000

At 12:38 27-06-2013, Adrian Farrel wrote:
>I think you can rely on each person actually on NomCom to speak their mind and
>deliver from their experience (and we can rely on the NomCom chair 
>to tease that
>out). So surely we can say something like:
>2 old-timers chosen randomly from a list of old-timers
>4 people who have been around the IETF a lot (e.g. 3 out of last 5 meetings)
>3 people who have worked in the IETF quite a bit (e.g.  front page 
>of > 2 RFCs)
>3 people who have evidence of participation in technical work on 
>mailing lists.
>Each person is only allowed to be placed in one pool before selection.

I'll comment on the above.  I have seen the request about 
reconsidering Section 2 of the draft and I am not ignoring it.

Someone would have to create a list of old-timers.

I think I understand what you mean by "around the IETF a lot".  I'll 
skip that for now.

The front page of more than two RFCs can create an incentive to:

  (a) generate more RFCs

  (b) add more names to the author list

There are a few ideas (including the above quoted text) which could 
be combined to figure out one or more workable alternatives.

Regards,
S. Moonesamy 


From sm@elandsys.com  Thu Jun 27 17:56:38 2013
Return-Path: <sm@elandsys.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 BF2A411E80F9 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 17:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.119
X-Spam-Level: 
X-Spam-Status: No, score=-102.119 tagged_above=-999 required=5 tests=[AWL=0.480, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 baGBndc-ZP3n for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 17:56:38 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 293B721F9CB8 for <ietf@ietf.org>; Thu, 27 Jun 2013 17:56:37 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.132.118]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5S0uLpq018906 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 17:56:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372380993; bh=vm4jq9DH+3sKQpNpvEnvmx4XsjtEfd6h2s0+lsZLnfg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Aej9ODIi/iiivkvyVTfxzFzyZN1FDkc+P8CWM6TnM1L8sR1cm9eSeHlLTMY00F8dR hGvp4JOYifSDXRiSYBw27w/xtfTV5TVDI+33oBRlSEZ3dTMomrnGXBPyKVvaKwWMUc RRMeYnErVFEdgYjG6b5fTVrvHJUKIHFFzsCoQgcQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372380993; i=@elandsys.com; bh=vm4jq9DH+3sKQpNpvEnvmx4XsjtEfd6h2s0+lsZLnfg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tqcV3Y5iFaaRM8KzUpredLVfj3F9Splte+bEnnyDaC8MM0U/NGzj6P5XcwKh+8yaX NNZM1O0qDnTR2vSR9woeaEBocqaF9Kn8BhXWOvuJ1r0UJ+NyZhg9j+p5AZgx24UkTG eRPwoDcv9xvztUnizfVpTwJ2OiA7B3rLSVI/GhjE=
Message-Id: <6.2.5.6.2.20130627172330.10adf4d0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jun 2013 17:50:17 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Nominating Committee Process: Eligibility
In-Reply-To: <CADnDZ8_Nw9TvfgWhKh5HYWu45s-an9BinHN7_i_wKbA2BR3x=g@mail.g mail.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <CADnDZ8_Nw9TvfgWhKh5HYWu45s-an9BinHN7_i_wKbA2BR3x=g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Fri, 28 Jun 2013 00:56:38 -0000

Hi Abdussalam,
At 12:16 27-06-2013, Abdussalam Baryun wrote:
>I support the draft, it will give all participants from all the 
>world equal opputunity. I made input related to this on the list 
>because I found that I am remote participant and there was limits 
>and conditions which I don't want. However, there may be some 
>reasons that IETF done it that way which the draft may need to 
>clarify and solve,

Thanks for explaining why you support the draft.  I am going to list 
some questions.  Please read them as points to consider.  There isn't 
any obligation to provide comments.

  - What is your opinion about helping the "pie get larger"?

  - What would be an acceptable way of determining whether someone
    has been contributing to the IETF over a period of five meetings?

  - Dave Cridland suggested that working groups provide a smallish set of
    volunteers each for the selection process.  Is it okay to leave it
    to the working group chair to make the decision?

Regards,
S. Moonesamy 


From scott.brim@gmail.com  Thu Jun 27 18:15:37 2013
Return-Path: <scott.brim@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 0688A21F9DBE for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 18:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 IRc3YwsrOgOi for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 18:15:36 -0700 (PDT)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 38D2321F9DB8 for <ietf@ietf.org>; Thu, 27 Jun 2013 18:15:36 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id n10so1679597oag.0 for <ietf@ietf.org>; Thu, 27 Jun 2013 18:15:34 -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 :content-type; bh=IRnR+uAFukYsSkiQ/lE+4YVMz0pJHn1f4jbwf0HJhG0=; b=bN/HYBVyQcB3rEfXxbq6KrapgoPInEUnmCprQWp2gVofAYHk4cEvKMzcLm5SudKdcZ RZDb1vwqJ5b++R9kKEYDR7CjVFzT0bM4S5hI37ykI6vk7pRZ8isu6dNmJayAxf0FPBKj FRy5rhsp/gLkvexxANtfrd/7cMeM8A+JU1TMFmcle4pw5kxRsMSL6WlVZTcrbAYoYKTh C2COm8YGeWFsl9VTmoXzXLYROhVJr6oeZ8qnUlir9itUkZPWURIWDWTt6TyafpSzD1YE RSh3mAcfsYwx7bUF+hLaGN09SceqFqs5N9wRARRAE+5pLFeMcNYxXW98Wd/8NnKUx1eC zVxg==
MIME-Version: 1.0
X-Received: by 10.182.39.168 with SMTP id q8mr5397020obk.72.1372382134648; Thu, 27 Jun 2013 18:15:34 -0700 (PDT)
Received: by 10.182.97.37 with HTTP; Thu, 27 Jun 2013 18:15:34 -0700 (PDT)
In-Reply-To: <CAPv4CP84_YDve9OeY_y=9ACJdO7vhVuBuYkEFY67W0NigXPPzQ@mail.gmail.com>
References: <20130627133447.C27F018C0B9@mercury.lcs.mit.edu> <51CC4144.70600@cisco.com> <20130627150745.8C3B821F9D9B@ietfa.amsl.com> <51CC7536.1030102@gmail.com> <CAPv4CP8HYn6EGLOj_+PVhkSTprUK+eM_jmfyAZy9vrLjew7wEQ@mail.gmail.com> <11086.1372358811@sandelman.ca> <CAPv4CP84_YDve9OeY_y=9ACJdO7vhVuBuYkEFY67W0NigXPPzQ@mail.gmail.com>
Date: Thu, 27 Jun 2013 21:15:34 -0400
Message-ID: <CAPv4CP9FeObGDjKTZHQpY+Zr9SNw7nwa1YcQm-_LH6=-CL8GZg@mail.gmail.com>
Subject: Re: The Nominating Committee Process: Eligibility
From: Scott Brim <scott.brim@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3059ea1ca6604e02c9dff
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: Fri, 28 Jun 2013 01:15:37 -0000

--001a11c3059ea1ca6604e02c9dff
Content-Type: text/plain; charset=ISO-8859-1

On Thursday, June 27, 2013, Scott Brim wrote:

> On Thu, Jun 27, 2013 at 2:46 PM, Michael Richardson <mcr@sandelman.ca<javascript:;>>
> wrote:
> > Just as long as you understand that you are influencing the diversity of
> the nomcom itself.
>
> Yes, we need to cultivate more talent and more viewpoints while
> simultaneously using hard-earned wisdom and encouraging growth of that
> wisdom in the less experienced.  I'm looking for the proposal from a
> few years ago for a balance like that in the NomCom, but haven't found
> it yet.
>

Here it is: http://tools.ietf.org/id/draft-crocker-nomcom-process-00.txt

I was particularly thinking of section 3, but reading it all might be worth
your while.

Yes we need to cultivate new leadership but that must not override the more
important need for experience and wisdom in the vital functions of the
IETF.  Finding that balance is not a new concern, anywhere in the IETF --
25 years ago I was told that the best working groups have "six young turks
and six old farts".

John Klensin pointed out that there are other problems with the current
NomCom selection rules.  True.  I'm not defending the current rules, just
the principle of what the NomCom should be able to represent.  I have no
issues with changes to the NomCom process as long as they make the NomCom
better at what it is supposed to do.

Cheers ... Scott

--001a11c3059ea1ca6604e02c9dff
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thursday, June 27, 2013, Scott Brim  wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">On Thu, Jun 27, 2013 at 2:46 PM, Michael Richardson &lt;<a href=3D"ja=
vascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;mcr@sandelman.ca&#39;=
)">mcr@sandelman.ca</a>&gt; wrote:<br>

&gt; Just as long as you understand that you are influencing the diversity =
of the nomcom itself.<br>
<br>
Yes, we need to cultivate more talent and more viewpoints while<br>
simultaneously using hard-earned wisdom and encouraging growth of that<br>
wisdom in the less experienced. =A0I&#39;m looking for the proposal from a<=
br>
few years ago for a balance like that in the NomCom, but haven&#39;t found<=
br>
it yet.<br></blockquote><div><br></div><div>Here it is: <a href=3D"http://t=
ools.ietf.org/id/draft-crocker-nomcom-process-00.txt">http://tools.ietf.org=
/id/draft-crocker-nomcom-process-00.txt</a></div><div><br></div><div>I was =
particularly thinking of section 3, but reading it all might be worth your =
while.=A0</div>
<div><br></div><div>Yes we need to cultivate new leadership but that must n=
ot override the more important need for experience and wisdom in the vital =
functions of the IETF. =A0Finding that balance is not a new concern, anywhe=
re in the IETF -- 25 years ago I was told that the best working groups have=
 &quot;six young turks and six old farts&quot;. =A0</div>
<div><br></div><div>John Klensin pointed out that there are other problems =
with the current NomCom selection rules. =A0True. =A0I&#39;m not defending =
the current rules, just the principle of what the NomCom should be able to =
represent. =A0I have no issues with changes to the NomCom process as long a=
s they make the NomCom better at what it is supposed to do.</div>
<div><br></div><div>Cheers ... Scott</div>

--001a11c3059ea1ca6604e02c9dff--

From dmm@1-4-5.net  Thu Jun 27 18:24:43 2013
Return-Path: <dmm@1-4-5.net>
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 4A39D21F9DB8 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 18:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 Sx0qtVnubArB for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 18:24:29 -0700 (PDT)
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) by ietfa.amsl.com (Postfix) with ESMTP id CEEC921F9C63 for <ietf@ietf.org>; Thu, 27 Jun 2013 18:24:29 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wc20so1414092obb.18 for <ietf@ietf.org>; Thu, 27 Jun 2013 18:24:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=f3xOF5QDces3s4Rl70M5s3qQgAQWrit9QyFd1ZH+w/o=; b=Ilud9XEhTDPge37tIdLjP2qI3sZsHGcSJyfGfW+X8Jgyhob8P1CfK4vpgRCKi0KXHg QvlzQjK2x4uMvt/HVu0ZT5piiUVoLazye4O+QLfikrb3U1r/FxEpKFDAK+W6TejSsTWv IgArK0Fmv+EsbUkh0w9lBI5Nll1DFCb2rEz6qspVzQHlUu3YzoSF9FI5YokmJ4SRVN/1 GiAE86rvO29albhZ4HBtdypuUX4NxCSx3IbB/dDpD10sI7Fvo6QlCBnsVlPW+raHLZbN ZfcyPhHIXtPirz8VxT8bnJm9oLswmvht1CqQuBXu8wdqC7BbNmnlFnZUIa6NYMDLvRP6 U9EQ==
MIME-Version: 1.0
X-Received: by 10.182.16.137 with SMTP id g9mr5395851obd.17.1372382669419; Thu, 27 Jun 2013 18:24:29 -0700 (PDT)
Received: by 10.182.114.34 with HTTP; Thu, 27 Jun 2013 18:24:29 -0700 (PDT)
X-Originating-IP: [50.200.68.226]
In-Reply-To: <4A4D208E6E2940BDEF5945A4@JcK-HP8200.jck.com>
References: <51CCC9B3.70606@gmail.com> <4A4D208E6E2940BDEF5945A4@JcK-HP8200.jck.com>
Date: Thu, 27 Jun 2013 18:24:29 -0700
Message-ID: <CAHiKxWj-NdSOoxQz8RWN92LJiJ+7wnfWQhadDV14jc1ZbfyYtQ@mail.gmail.com>
Subject: Re: Evi Nemeth
From: David Meyer <dmm@1-4-5.net>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmkyI6u42f5RdareY2CUmgjcatNbmzdQacvRNulmSshC2a3Yyjv/Eq2tHAo9TvGQUH5gLHo
Cc: IETF discussion 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: Fri, 28 Jun 2013 01:24:43 -0000

On Thu, Jun 27, 2013 at 4:30 PM, John C Klensin <john-ietf@jck.com> wrote:
>
>
> --On Friday, June 28, 2013 11:24 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>
>> Evi used to be an IETF regular. There is rather ominous news -
>> she is lost at sea between New Zealand and Australia:
>>
>> http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=
>> 10893482
>>
>> http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=
>> 10893503
>
> Brian,
>
> Thanks for posting this.  Truly scary... she and her colleagues
> should be in all of our thoughts and prayers.

Definitely. I spent a lot of time with Evi over the years.

--dmm

>
>   john


>

From faizzeya@yahoo.com  Thu Jun 27 19:11:23 2013
Return-Path: <faizzeya@yahoo.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 1C01511E8145 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 19:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=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 4FvnoV0DjEUP for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 19:11:17 -0700 (PDT)
Received: from nm36-vm6.bullet.mail.bf1.yahoo.com (nm36-vm6.bullet.mail.bf1.yahoo.com [72.30.238.142]) by ietfa.amsl.com (Postfix) with ESMTP id 22B0111E814E for <ietf@ietf.org>; Thu, 27 Jun 2013 19:11:17 -0700 (PDT)
Received: from [98.139.212.148] by nm36.bullet.mail.bf1.yahoo.com with NNFMP; 28 Jun 2013 02:11:15 -0000
Received: from [98.139.212.219] by tm5.bullet.mail.bf1.yahoo.com with NNFMP; 28 Jun 2013 02:11:15 -0000
Received: from [127.0.0.1] by omp1028.mail.bf1.yahoo.com with NNFMP; 28 Jun 2013 02:11:15 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 903235.17225.bm@omp1028.mail.bf1.yahoo.com
Received: (qmail 32088 invoked by uid 60001); 28 Jun 2013 02:11:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1372385475; bh=LtP4GckaomvyHEZJEqAQVL259pb2Bs3IKJ23bYGwseg=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=4TpKzAx4KqyzdEkJm7rvw6Arx4uxeb0piJnKWBCrFLJ/bG8eNa2OG8oCjKEF+KTQjSJEJvOU7okxKMrbebcwlwICYJJi+siz7C+wFRZeKGxfD5b/hCLwUo+dmeZlQpFdx1OxMb5i6AicrUDuL08MMb3F2is5GOvyigJ3rgtI1Ls=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=Mrt9+1uMPzAa+nmDPDhb2bL0UjoVRF1nPOoNRooysCRubu2o1PMyvzEdcIwvYMaY9qnkTFv+iFln3ic3eO4x4Pf4R8XrCgHCoAzCou0U+uBuZOC/h+XbD9Xq9Z1qBhcbWvqqk475v9IucMcbjiqkM4nrpqSU96z+NfN8YGbna3w=;
X-YMail-OSG: PcIOllsVM1nhPOCDPElNvLEWbfDdDpQLMDYXPwLSJ0oaek. RkTunkq3E2jGnadhbw9NpUQPSG6HwDbHJAaUOBg4xMJmdIE57ciLsHtj3_VG EG_SIMcPUqZPV.gzDghgll6I7PXL0dDMHAPRUn0GNnFkq_vov0Efk3r3E3xz Nl_GQktg4Usb8lwt5GVI01qqQaJBI3S2za.bnnWprn4BTI0KjcIrsa0jz_Yg 1p2AICJku3GKfO5mOSpV_PePxmuBQhEA1mb3fr1rHlS9CZgUkMNtHgam5WD5 fziEFEVCCP2mZWtdnjAohAGIYO9OcqS5YGEBn2B3uG_Ujd_AA2fMG6V02s2Z uRqH0AKhI6V7fkvDCqKV0_DL7ztQDR4mNk7MXPXUasPTgaFs39.tXRh3Ewhc m270KpHwgEEt0eT9s2_NFcxZUu0Wu7cbR1xYE0BIB.vBuP0UTjay7gHla5ll hedhrKsSKLEG7zh1tbGas7xGG97yWGL7eYPizM0WxhJU87f1AKmNqvMBUiRa jdGqd.uyv2w7sGHpQWHkT4VpEoaRV4PVv35RYT7EFuWkRmQ--
Received: from [39.48.228.250] by web162401.mail.bf1.yahoo.com via HTTP; Thu, 27 Jun 2013 19:11:15 PDT
X-Rocket-MIMEInfo: 002.001, SGkgYWxsLArCoEkgaGF2ZSBhbiBpZGVhIGFuZCB3YW50IHRvIHNoYXJlLkl0IGlzIGFib3V0IGFkYXB0aXZlIGh0dHAuIFRoZSBwcm90b2NvbCByZXF1ZXN0cyB0aGUgaW50ZXJlc3RzIGFuZCBvdGhlciBwYXJhbWV0ZXJzIGZyb20gdGhlIGNsaWVudCBhbmQgc2VuZCB0aGUgd2ViIHBhZ2UgZHluYW1pY2FsbHkgZGlmZmVyZW50IHRvIGRpZmZlcmVudCB1c2VycyBiYXNlZCBvbiB0aGUgaW50ZXJlc3RzLiBUaGUgaW50ZXJzdHMgY2FuIGJlIHNoYXJlZCB2aWEgWE1MLiBUaGlzIGlzIGluIGNvbnRyYXN0IHRvIGMBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.148.557
Message-ID: <1372385475.31973.YahooMailNeo@web162401.mail.bf1.yahoo.com>
Date: Thu, 27 Jun 2013 19:11:15 -0700 (PDT)
From: Faiz ul haque Zeya <faizzeya@yahoo.com>
Subject: adaptive http
To: "ietf@ietf.org" <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-1911863903-1846245163-1372385475=:31973"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Faiz ul haque Zeya <faizzeya@yahoo.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: Fri, 28 Jun 2013 02:15:16 -0000

---1911863903-1846245163-1372385475=:31973
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,=0A=A0I have an idea and want to share.It is about adaptive http. Th=
e protocol requests the interests and other parameters from the client and =
send the web page dynamically different to different users based on the int=
erests. The intersts can be shared via XML. This is in contrast to configur=
ed html pages a different mechanism,=0Aregards=0Afaiz=0A
---1911863903-1846245163-1372385475=:31973
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:12pt"><div>Hi all,</div><di=
v>&nbsp;I have an idea and want to share.It is about adaptive http. The pro=
tocol requests the interests and other parameters from the client and send =
the web page dynamically different to different users based on the interest=
s. The intersts can be shared via XML. This is in contrast to configured ht=
ml pages a different mechanism,</div><div>regards</div><div>faiz</div><div>=
<br></div></div></body></html>
---1911863903-1846245163-1372385475=:31973--

From iab-chair@iab.org  Thu Jun 27 19:36:19 2013
Return-Path: <iab-chair@iab.org>
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 4E87621F9BF0; Thu, 27 Jun 2013 19:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_53=0.6, USER_IN_WHITELIST=-100]
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 zUUTFlZiWZE8; Thu, 27 Jun 2013 19:36:14 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id EF67B21F9B9E; Thu, 27 Jun 2013 19:36:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 6FC99A8AB1; Thu, 27 Jun 2013 19:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P4ZJFleVJg5T; Thu, 27 Jun 2013 19:35:49 -0700 (PDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) by c9a.amsl.com (Postfix) with ESMTPSA id D13F1A8AB0; Thu, 27 Jun 2013 19:35:48 -0700 (PDT)
From: IAB Chair <iab-chair@iab.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Call for Volunteers to Serve on the ICANN Nominating Committee
Date: Thu, 27 Jun 2013 22:36:12 -0400
Message-Id: <5607FF5A-75CB-4A4B-9B3C-2798D6DF9BFB@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <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: Fri, 28 Jun 2013 02:36:19 -0000

Please forward to all interested parties.

Dear Colleagues,

The IAB (on behalf of the IETF) has been asked to supply a member to the =
2014 ICANN Nominating Committee (NomCom) by 15 August 2013. We would =
therefore like to ask the community for volunteers to serve on the ICANN =
NomCom. If you are interested, please send a short e-mail to iab-chair =
at iab.org with a copy to execd at iab.org with your motivation and =
information concerning your familiarity with the IETF and ICANN.  The =
deadline for volunteering is 19 July 2013.

The IAB will select from the available candidates, taking into account =
the familiarity with ICANN and the IETF, their roles, and their =
processes. The selected candidate will serve on the ICANN NomCom on =
personal title; however, we will be looking for a candidate who has an =
understanding of the interests of the technical community.

The ICANN NomCom process itself is governed by the ICANN bylaws; an =
abstract of the relevant articles can be found at =
http://nomcom.icann.org/bylaws.htm.  In addition, each NomCom determines =
a number of its own operational procedures, including the role of the =
NomCom in recruiting and selecting candidates.

The ICANN Nominating Committee typically meets in person at or around =
three consecutive ICANN meetings. The first of these meetings, when the=20=

committee is formally established, will be held  22-23 November 2013 =
following the Buenos Aires ICANN meeting on 17-21 November. The =
committee will next attend the "Spring" ICANN meeting, which in 2014 =
will be in Singapore on 23-27 March 2014. Finally, the committee will =
meet during and after the "Summer" ICANN meeting in London on 22-26 June =
2014 where the final slate of candidates for the ICANN Board, the GNSO, =
ccNSO,and ALAC will be agreed upon.

Candidates should be able to join monthly teleconferences (typically at =
UTC 14:00), with the expectation that these teleconferences will held =
weekly during the candidate assessment process in May-June.

NOTE: ICANN does cover travel and hotel costs for a pre-determined =
number of days at each of the 3 consecutive ICANN meetings.

For more information about the ICANN NomCom see: =
http://nomcom.icann.org/.  If you are willing to be considered or would =
like to nominate someone for the position, please send an email to =
iab-chair at iab.org and execd at iab.org.

On behalf of the IAB,
  Russ Housley
  IAB Chair=

From narten@us.ibm.com  Thu Jun 27 21:53:14 2013
Return-Path: <narten@us.ibm.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 7C3F021F9B2D for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 21:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.144
X-Spam-Level: 
X-Spam-Status: No, score=-108.144 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 WIiLhCYR4Ejp for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 21:53:07 -0700 (PDT)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by ietfa.amsl.com (Postfix) with ESMTP id 7502721F8F87 for <ietf@ietf.org>; Thu, 27 Jun 2013 21:53:07 -0700 (PDT)
Received: from /spool/local by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 27 Jun 2013 22:53:06 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 27 Jun 2013 22:53:05 -0600
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 7A7851FF001D for <ietf@ietf.org>; Thu, 27 Jun 2013 22:47:48 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r5S4r4NB318002 for <ietf@ietf.org>; Thu, 27 Jun 2013 22:53:04 -0600
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r5S4tXdc012651 for <ietf@ietf.org>; Thu, 27 Jun 2013 22:55:33 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r5S4tWeP012621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 27 Jun 2013 22:55:33 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r5S4r2gY023994 for <ietf@ietf.org>; Fri, 28 Jun 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r5S4r2Fx023959 for ietf@ietf.org; Fri, 28 Jun 2013 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201306280453.r5S4r2Fx023959@rotala.raleigh.ibm.com>
Date: Fri, 28 Jun 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13062804-7282-0000-0000-000018BED6FF
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: Fri, 28 Jun 2013 04:53:14 -0000

Total of 177 messages in the last 7 days.
 
script run at: Fri Jun 28 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.65% |   10 |  8.11% |   110934 | hallam@gmail.com
  5.65% |   10 |  5.57% |    76202 | john-ietf@jck.com
  4.52% |    8 |  5.47% |    74837 | sm+ietf@elandsys.com
  4.52% |    8 |  4.48% |    61298 | hsantos@isdg.net
  2.82% |    5 |  4.83% |    66157 | mthornbu@adobe.com
  3.95% |    7 |  3.37% |    46083 | arturo.servin@gmail.com
  3.95% |    7 |  3.06% |    41900 | dhc@dcrocker.net
  3.39% |    6 |  2.96% |    40545 | scott.brim@gmail.com
  3.39% |    6 |  2.94% |    40172 | mcr+ietf@sandelman.ca
  2.82% |    5 |  3.22% |    44133 | abdussalambaryun@gmail.com
  2.26% |    4 |  3.15% |    43058 | dave@cridland.net
  2.82% |    5 |  2.50% |    34215 | brian.e.carpenter@gmail.com
  2.82% |    5 |  2.07% |    28370 | lars@netapp.com
  2.26% |    4 |  2.16% |    29572 | jcurran@istaff.org
  2.26% |    4 |  1.91% |    26171 | sm@resistor.net
  1.69% |    3 |  2.15% |    29469 | akatlas@gmail.com
  1.69% |    3 |  1.85% |    25314 | jabley@hopcount.ca
  1.13% |    2 |  2.38% |    32597 | ben@nostrum.com
  1.69% |    3 |  1.76% |    24108 | lear@cisco.com
  1.69% |    3 |  1.67% |    22799 | ynir@checkpoint.com
  1.69% |    3 |  1.47% |    20134 | mstjohns@comcast.net
  1.69% |    3 |  1.47% |    20119 | dmm@1-4-5.net
  1.69% |    3 |  1.26% |    17180 | stpeter@stpeter.im
  1.69% |    3 |  1.07% |    14713 | randy@psg.com
  1.13% |    2 |  1.36% |    18554 | daedulus@btconnect.com
  1.13% |    2 |  1.22% |    16695 | barryleiba@computer.org
  1.13% |    2 |  1.19% |    16317 | dharkins@lounge.org
  1.13% |    2 |  1.00% |    13656 | fred@cisco.com
  1.13% |    2 |  0.99% |    13588 | chris.dearlove@baesystems.com
  1.13% |    2 |  0.98% |    13415 | dougb@dougbarton.us
  1.13% |    2 |  0.95% |    13022 | ted.lemon@nominum.com
  1.13% |    2 |  0.95% |    12989 | stephen.farrell@cs.tcd.ie
  1.13% |    2 |  0.94% |    12845 | iab-chair@iab.org
  1.13% |    2 |  0.90% |    12257 | melinda.shore@gmail.com
  1.13% |    2 |  0.81% |    11043 | jari.arkko@piuha.net
  1.13% |    2 |  0.78% |    10724 | paul.hoffman@vpnc.org
  1.13% |    2 |  0.64% |     8778 | jnc@mercury.lcs.mit.edu
  0.56% |    1 |  0.96% |    13129 | ron.even.tlv@gmail.com
  0.56% |    1 |  0.77% |    10514 | andy@yumaworks.com
  0.56% |    1 |  0.73% |     9993 | narten@us.ibm.com
  0.56% |    1 |  0.71% |     9769 | jdrake@juniper.net
  0.56% |    1 |  0.63% |     8650 | richard@shockey.us
  0.56% |    1 |  0.61% |     8295 | presnick@qti.qualcomm.com
  0.56% |    1 |  0.60% |     8144 | sob@harvard.edu
  0.56% |    1 |  0.59% |     8111 | farmer@umn.edu
  0.56% |    1 |  0.58% |     7976 | alexey.melnikov@isode.com
  0.56% |    1 |  0.58% |     7902 | alejandroacostaalamo@gmail.com
  0.56% |    1 |  0.57% |     7844 | faizzeya@yahoo.com
  0.56% |    1 |  0.54% |     7453 | hannes.tschofenig@gmx.net
  0.56% |    1 |  0.53% |     7290 | adrian@olddog.co.uk
  0.56% |    1 |  0.52% |     7155 | tony@att.com
  0.56% |    1 |  0.52% |     7120 | bob.hinden@gmail.com
  0.56% |    1 |  0.50% |     6843 | varun@comnet.tkk.fi
  0.56% |    1 |  0.49% |     6770 | elwynd@dial.pipex.com
  0.56% |    1 |  0.48% |     6621 | housley@vigilsec.com
  0.56% |    1 |  0.48% |     6621 | dwm@xpasc.com
  0.56% |    1 |  0.47% |     6391 | stbryant@cisco.com
  0.56% |    1 |  0.47% |     6368 | mcr@sandelman.ca
  0.56% |    1 |  0.45% |     6142 | ogud@ogud.com
  0.56% |    1 |  0.44% |     6072 | rpelletier@isoc.org
  0.56% |    1 |  0.44% |     6067 | iad@ietf.org
  0.56% |    1 |  0.43% |     5848 | jmamodio@gmail.com
  0.56% |    1 |  0.42% |     5781 | hartmans-ietf@mit.edu
  0.56% |    1 |  0.41% |     5638 | loa@pi.nu
  0.56% |    1 |  0.40% |     5449 | doug@ewellic.org
  0.56% |    1 |  0.39% |     5293 | fluffy@iii.ca
  0.56% |    1 |  0.37% |     5025 | mrex@sap.com
  0.56% |    1 |  0.33% |     4458 | agenda@ietf.org
--------+------+--------+----------+------------------------
100.00% |  177 |100.00% |  1368695 | Total


From chris.dearlove@baesystems.com  Fri Jun 28 01:53:52 2013
Return-Path: <chris.dearlove@baesystems.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 0FC5E21F9DB0 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 01:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 7faWUY0Pi9ZG for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 01:53:40 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 9B09621F9C39 for <ietf@ietf.org>; Fri, 28 Jun 2013 01:53:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,957,1363132800"; d="scan'208";a="296282464"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 28 Jun 2013 09:53:10 +0100
X-IronPort-AV: E=Sophos;i="4.87,957,1363132800"; d="scan'208";a="20454064"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasodc005.greenlnk.net with ESMTP; 28 Jun 2013 09:53:10 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.180]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.02.0328.009; Fri, 28 Jun 2013 09:53:10 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Hector Santos <hsantos@isdg.net>
Subject: RE: RFC 6234 code
Thread-Topic: RFC 6234 code
Thread-Index: Ac5zTU86ivBUhTyDT4awcyYFLYCBk///+uUA///t6lCAAEeXAP//E5XA
Date: Fri, 28 Jun 2013 08:53:09 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net>
In-Reply-To: <51CC94B2.2060507@isdg.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <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: Fri, 28 Jun 2013 08:53:52 -0000

I'd actually tried the authors, but no reply yet (only a few days). I also =
tried the RFC Editor thinking they might have e.g. XML from which extractio=
n might have been easier, but also no response yet. And I had found several=
 libraries, but not the RFC code. I can't see any suggestion that the libra=
ry you indicate includes that code, it also bills itself as a C++ library, =
which the RFC code is not (and also not what I want, but that's not a subje=
ct for this list).

But the broader point is that if it's worth the IETF publishing the code as=
 an RFC, it's worth making the code available straightforwardly.

For me, a thanks to Tony Hansen, who did the extraction for me. (That makes=
 me feel a little guilty, why should he do my work I could have done?) But =
the point of posting on this list was to say that the code should be availa=
ble so that each person wanting that code doesn't have to do that again.

Christopher

-- =

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: Hector Santos [mailto:hsantos@isdg.net] =

Sent: 27 June 2013 20:38
To: Dearlove, Christopher (UK)
Cc: ietf@ietf.org
Subject: Re: RFC 6234 code

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

Ok, other than time, it should be easy to extract, clean up and cross =

your fingers that it compiles with your favorite C compiler.  But I =

would write to the authors to get the original source. Or google:

     C source crypto libraries API hashing functions

among the first hit:

http://www.cryptopp.com/


On 6/27/2013 12:33 PM, Dearlove, Christopher (UK) wrote:
> I want the specific code that is in the RFC (which happens to be in C) ra=
ther than some other implementation.
>


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From lars@netapp.com  Fri Jun 28 01:57:26 2013
Return-Path: <lars@netapp.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 B578D21F9E54 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 01:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.3
X-Spam-Level: 
X-Spam-Status: No, score=-5.3 tagged_above=-999 required=5 tests=[AWL=-2.700,  BAYES_00=-2.599]
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 XsXGaHSCWF2W for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 01:57:15 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 2CA4C21F9E27 for <ietf@ietf.org>; Fri, 28 Jun 2013 01:57:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,957,1363158000"; d="scan'208";a="30369422"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx11-out.netapp.com with ESMTP; 28 Jun 2013 01:57:07 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Fri, 28 Jun 2013 01:57:07 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: Re: RFC 6234 code
Thread-Topic: RFC 6234 code
Thread-Index: Ac5zTU86ivBUhTyDT4awcyYFLYCBkwAQIDoAAAA4oAAABneFAAAbwVKAAAAjUQA=
Date: Fri, 28 Jun 2013 08:57:06 +0000
Message-ID: <93DE6BA0-4677-40E6-9257-4AFECF04EC25@netapp.com>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B5B6377778205E46A4076F9C44829782@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <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: Fri, 28 Jun 2013 08:57:26 -0000

Hi,

On Jun 28, 2013, at 10:53, "Dearlove, Christopher (UK)" <chris.dearlove@bae=
systems.com>
 wrote:
> But the broader point is that if it's worth the IETF publishing the code =
as an RFC, it's worth making the code available straightforwardly.

some WGs are good at this. RFC5662 for example includes the shell commands =
to extract the sources it contains.

It would certainly be nice if other WGs did this, too, but I'm not sure we =
need to make it a requirement.

Lars=

From chris.dearlove@baesystems.com  Fri Jun 28 01:59:39 2013
Return-Path: <chris.dearlove@baesystems.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 1DB0B21F9D88 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 01:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 QIxSQKv3KJ5U for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 01:59:29 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 0576221F844E for <ietf@ietf.org>; Fri, 28 Jun 2013 01:59:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,957,1363132800"; d="scan'208";a="296284648"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 28 Jun 2013 09:59:25 +0100
X-IronPort-AV: E=Sophos;i="4.87,957,1363132800"; d="scan'208";a="20455154"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasodc005.greenlnk.net with ESMTP; 28 Jun 2013 09:59:24 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.180]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.02.0328.009; Fri, 28 Jun 2013 09:59:23 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Joe Abley <jabley@hopcount.ca>
Subject: RE: RFC 6234 code
Thread-Topic: RFC 6234 code
Thread-Index: Ac5zTU86ivBUhTyDT4awcyYFLYCBkwABSaAAACK7XkA=
Date: Fri, 28 Jun 2013 08:59:23 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CEA@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <8FC6A38B-7170-480D-9B0D-CD37308A5A82@hopcount.ca>
In-Reply-To: <8FC6A38B-7170-480D-9B0D-CD37308A5A82@hopcount.ca>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <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: Fri, 28 Jun 2013 08:59:39 -0000

I think we must agree to differ on whether the IETF should do this. If it t=
akes twenty minutes work for everyone who has to do it, either that stacks =
up, or no one is actually interested, so is the RFC worth it?

As for maintaining the code, I'm just suggesting the same snapshot as the R=
FC is maintained. It could even be another link off the tools page: here's =
the text, here's the XML, here's any code.

-- =

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Joe Abley [mailto:jabley@hopcount.ca] =

Sent: 27 June 2013 18:22
To: Dearlove, Christopher (UK)
Cc: ietf@ietf.org
Subject: Re: RFC 6234 code

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

On 2013-06-27, at 11:49, "Dearlove, Christopher (UK)" <chris.dearlove@baesy=
stems.com> wrote:

> RFC 6234 contains, embedded in it, code to implement various functions, i=
ncluding SHA-2.
> =

> Extracting that code from the RFC is not a clean process. In addition the=
 code must have existed unembedded before being embedded.
> =

> Is that code available from the IETF or elsewhere?
> =

> (I have tried some approaches to finding such code before posting here, b=
ut none successful.)

Turns out that extracting the code from the RFC is only twenty minutes' wor=
k. Probably faster just to do it than to talk about it. If you'd like a cop=
y of the files I extracted from the RFC text, I can easily send you a tarba=
ll.

In general I think that maintaining code repositories is non-trivial, and a=
lso has been known (especially with respect to crypto/hash algorithms) to r=
un into export licensing issues. Maintaining an archives of RFCs is already=
 a core competency for the IETF, and (at least in some cases) exporting tex=
t is less problematic than exporting code.


Joe

[krill:~]% mkdir 6234
[krill:~]% cd 6234
[krill:~/6234]% curl -O 'http://tools.ietf.org/rfc/rfc6234.txt'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Cur=
rent
                                 Dload  Upload   Total   Spent    Left  Spe=
ed
100  231k  100  231k    0     0   190k      0  0:00:01  0:00:01 --:--:--  1=
90k
[krill:~/6234]% vi rfc6234.txt =

[krill:~/6234]% ls
hkdf.c			sha.h			stdint-example.h
hmac.c			sha1.c			test-driver.c
rfc6234.txt		sha224-256.c		usha.c
sha-private.h		sha384-512.c
[krill:~/6234]% vi *.h *.c
10 files to edit
[krill:~/6234]% date
Thu 27 Jun 2013 13:14:53 EDT
[krill:~/6234]% =

[krill:~/6234]% cc -c hmac.c
[krill:~/6234]% cc -c sha1.c
[krill:~/6234]% cc -c sha224-256.c
[krill:~/6234]% cc -c sha384-512.c =

[krill:~/6234]% cc -c usha.c
[krill:~/6234]% cc -c test-driver.c
[krill:~/6234]% ls
hkdf.c			sha.h			sha384-512.o
hkdf.o			sha1.c			stdint-example.h
hmac.c			sha1.o			test-driver.c
hmac.o			sha224-256.c		test-driver.o
rfc6234.txt		sha224-256.o		usha.c
sha-private.h		sha384-512.c		usha.o
[krill:~/6234]% cc -o test-driver *.o
[krill:~/6234]% ./test-driver| egrep '(PASS|FAIL)'
SHA1 sha standard test 1: PASSED
SHA1 sha standard test 2: PASSED
SHA1 sha standard test 3: PASSED
SHA1 sha standard test 4: PASSED
SHA1 sha standard test 5: PASSED
SHA1 sha standard test 6: PASSED
SHA1 sha standard test 7: PASSED
SHA1 sha standard test 8: PASSED
SHA1 sha standard test 9: PASSED
SHA1 sha standard test 10: PASSED
SHA1 random test 0: PASSED
SHA1 random test 1: PASSED
SHA1 random test 2: PASSED
SHA1 random test 3: PASSED
SHA224 sha standard test 1: PASSED
SHA224 sha standard test 2: PASSED
SHA224 sha standard test 3: PASSED
SHA224 sha standard test 4: PASSED
SHA224 sha standard test 5: PASSED
SHA224 sha standard test 6: PASSED
SHA224 sha standard test 7: PASSED
SHA224 sha standard test 8: PASSED
SHA224 sha standard test 9: PASSED
SHA224 sha standard test 10: PASSED
SHA224 random test 0: PASSED
SHA224 random test 1: PASSED
SHA224 random test 2: PASSED
SHA224 random test 3: PASSED
SHA256 sha standard test 1: PASSED
SHA256 sha standard test 2: PASSED
SHA256 sha standard test 3: PASSED
SHA256 sha standard test 4: PASSED
SHA256 sha standard test 5: PASSED
SHA256 sha standard test 6: PASSED
SHA256 sha standard test 7: PASSED
SHA256 sha standard test 8: PASSED
SHA256 sha standard test 9: PASSED
SHA256 sha standard test 10: PASSED
SHA256 random test 0: PASSED
SHA256 random test 1: PASSED
SHA256 random test 2: PASSED
SHA256 random test 3: PASSED
SHA384 sha standard test 1: PASSED
SHA384 sha standard test 2: PASSED
SHA384 sha standard test 3: PASSED
SHA384 sha standard test 4: PASSED
SHA384 sha standard test 5: PASSED
SHA384 sha standard test 6: PASSED
SHA384 sha standard test 7: PASSED
SHA384 sha standard test 8: PASSED
SHA384 sha standard test 9: PASSED
SHA384 sha standard test 10: PASSED
SHA384 random test 0: PASSED
SHA384 random test 1: PASSED
SHA384 random test 2: PASSED
SHA384 random test 3: PASSED
SHA512 sha standard test 1: PASSED
SHA512 sha standard test 2: PASSED
SHA512 sha standard test 3: PASSED
SHA512 sha standard test 4: PASSED
SHA512 sha standard test 5: PASSED
SHA512 sha standard test 6: PASSED
SHA512 sha standard test 7: PASSED
SHA512 sha standard test 8: PASSED
SHA512 sha standard test 9: PASSED
SHA512 sha standard test 10: PASSED
SHA512 random test 0: PASSED
SHA512 random test 1: PASSED
SHA512 random test 2: PASSED
SHA512 random test 3: PASSED
[krill:~/6234]% =



********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From elwynd@dial.pipex.com  Fri Jun 28 04:55:10 2013
Return-Path: <elwynd@dial.pipex.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 CEF9821F93E1 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 04:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8vlAHVJ4GEog for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 04:55:05 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 1112D21F9A15 for <ietf@ietf.org>; Fri, 28 Jun 2013 04:55:00 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1UsXGM-00076t-RH; Fri, 28 Jun 2013 12:54:56 +0100
Subject: New form of remote attendance [was Re: The Nominating Committee Process: Eligibility]
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Arturo Servin <arturo.servin@gmail.com>
In-Reply-To: <51CC2598.3010002@gmail.com>
References: <6.2.5.6.2.20130627024747.0cfe3030@elandnews.com> <51CC2598.3010002@gmail.com>
Content-Type: text/plain
Date: Fri, 28 Jun 2013 12:52:43 +0100
Message-Id: <1372420363.4524.18237.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: 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: Fri, 28 Jun 2013 11:55:10 -0000

On Thu, 2013-06-27 at 12:44 +0100, Arturo Servin (probably did not
intend to) wrote:

>     What is the rationale of the requirement to attend psychically to
> meetings?

I attend all meetings psychically.... so spriritual!

Sorry.. couldn't resist.
E.


From shimshamshimmy@gmail.com  Fri Jun 28 05:31:16 2013
Return-Path: <shimshamshimmy@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 B189921F9AAC for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 05:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.376
X-Spam-Level: **
X-Spam-Status: No, score=2.376 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, 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 cAEnltP8qbiQ for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 05:31:08 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 93E9621F847A for <ietf@ietf.org>; Fri, 28 Jun 2013 05:31:08 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id l18so1495270wgh.2 for <ietf@ietf.org>; Fri, 28 Jun 2013 05:31:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=nsot/R1pAGPFuP0OEPCUfcpHGjXjtXvSgv5owR9dCqE=; b=uIBGNHZI8Y97fhs6aFgHJfGORWSqxBUcsi9szlvd0AqbtjR9DxfzTP5lVEf1sB8piZ /pyr5U6IAMlGHPjdqJq1ejF5An7lOpV1OLos3p9dF34tLf2DAQ8BdU6MJeHJlV946vIa vGy0s4UFla4YovYfGK5jlKrbrXebqbKaC/OliEJGV5PAy3Ndshj49dNMKhzZlUrpjCNG W9a6pRXoMFptdhGMCzU/GiQeah0RgZBp0A3XkNToeeiJCJq4SimLUwhyL4GDeAbnlBYX Xh+R87atCbDlsC6+SNMxUC6ah8MvdmcIfSXo56KXSbkoSE7YnyKG+Q/QaaTBOdjNGR0b UB8w==
MIME-Version: 1.0
X-Received: by 10.181.12.80 with SMTP id eo16mr2243001wid.44.1372422667711; Fri, 28 Jun 2013 05:31:07 -0700 (PDT)
Sender: shimshamshimmy@gmail.com
Received: by 10.194.26.193 with HTTP; Fri, 28 Jun 2013 05:31:07 -0700 (PDT)
In-Reply-To: <51CCC9B3.70606@gmail.com>
References: <51CCC9B3.70606@gmail.com>
Date: Fri, 28 Jun 2013 21:31:07 +0900
X-Google-Sender-Auth: ErSqoZ7el0NEzaSVwonALW0RpG4
Message-ID: <CA+k18nWmSM0Pp_4EQxJn8RDK-it+yXSR40JB7CUFzFj6sLegmA@mail.gmail.com>
Subject: Re: Evi Nemeth
From: Jun Murai <jun@wide.ad.jp>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0438ede5973a4304e0360d20
Cc: IETF discussion 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: Fri, 28 Jun 2013 12:31:16 -0000

--f46d0438ede5973a4304e0360d20
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

As we have been working together as IETF community as well as univ.
community with us, I would share thiss loss of Evi with us and all the
students working with her at IETF.
Jun Murai


2013$BG/(B6$B7n(B28$BF|6bMKF|(B Brian E Carpenter brian.e.carpenter@gmail.com:

> Evi used to be an IETF regular. There is rather ominous news - she is
> lost at sea between New Zealand and Australia:
>
> http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=10893482
>
> http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=10893503
>
> Regards
>    Brian Carpenter
>
>
>

--f46d0438ede5973a4304e0360d20
Content-Type: text/html; charset=ISO-2022-JP
Content-Transfer-Encoding: base64

QXMgd2UgaGF2ZSBiZWVuIHdvcmtpbmcgdG9nZXRoZXIgYXMgSUVURiBjb21tdW5pdHkgYXMgd2Vs
bCBhcyZuYnNwO3VuaXYuIGNvbW11bml0eSB3aXRoIHVzLCBJIHdvdWxkIHNoYXJlIHRoaXNzJm5i
c3A7bG9zcyBvZiBFdmkgd2l0aCB1cyBhbmQgYWxsIHRoZSBzdHVkZW50cyB3b3JraW5nIHdpdGgg
aGVyIGF0IElFVEYuPGRpdj5KdW4gTXVyYWk8c3Bhbj48L3NwYW4+PGJyPjxkaXY+PGJyPjxicj4y
MDEzGyRCRy8bKEI2GyRCN24bKEIyOBskQkZ8NmJNS0Z8GyhCIEJyaWFuIEUgQ2FycGVudGVyIDxh
IGhyZWY9Im1haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb20iPmJyaWFuLmUuY2FycGVu
dGVyQGdtYWlsLmNvbTwvYT46PGJyPg0KPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBz
dHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGlu
Zy1sZWZ0OjFleCI+RXZpIHVzZWQgdG8gYmUgYW4gSUVURiByZWd1bGFyLiBUaGVyZSBpcyByYXRo
ZXIgb21pbm91cyBuZXdzIC0gc2hlIGlzPGJyPg0KbG9zdCBhdCBzZWEgYmV0d2VlbiBOZXcgWmVh
bGFuZCBhbmQgQXVzdHJhbGlhOjxicj4NCjxicj4NCjxhIGhyZWY9Imh0dHA6Ly93d3cubnpoZXJh
bGQuY28ubnovbnovbmV3cy9hcnRpY2xlLmNmbT9jX2lkPTEmYW1wO29iamVjdGlkPTEwODkzNDgy
IiB0YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3dy5uemhlcmFsZC5jby5uei9uei9uZXdzL2FydGlj
bGUuY2ZtP2NfaWQ9MSZhbXA7b2JqZWN0aWQ9MTA4OTM0ODI8L2E+PGJyPg0KPGJyPg0KPGEgaHJl
Zj0iaHR0cDovL3d3dy5uemhlcmFsZC5jby5uei9uei9uZXdzL2FydGljbGUuY2ZtP2NfaWQ9MSZh
bXA7b2JqZWN0aWQ9MTA4OTM1MDMiIHRhcmdldD0iX2JsYW5rIj5odHRwOi8vd3d3Lm56aGVyYWxk
LmNvLm56L256L25ld3MvYXJ0aWNsZS5jZm0/Y19pZD0xJmFtcDtvYmplY3RpZD0xMDg5MzUwMzwv
YT48YnI+DQo8YnI+DQpSZWdhcmRzPGJyPg0KJm5ic3A7ICZuYnNwO0JyaWFuIENhcnBlbnRlcjxi
cj4NCjxicj4NCjxicj4NCjwvYmxvY2txdW90ZT48L2Rpdj48L2Rpdj4NCg==
--f46d0438ede5973a4304e0360d20--

From tony@att.com  Fri Jun 28 07:11:56 2013
Return-Path: <tony@att.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 EF4D921F9B64 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 07:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level: 
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_73=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 CpRZ+9aGr8AL for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 07:11:49 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id 5E61321F91B4 for <ietf@ietf.org>; Fri, 28 Jun 2013 07:11:49 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 4a99dc15.0.988771.00-330.2765394.nbfkord-smmo07.seg.att.com (envelope-from <tony@att.com>);  Fri, 28 Jun 2013 14:11:49 +0000 (UTC)
X-MXL-Hash: 51cd99a54e4b9b72-7e632808ee910c76b488babc09b370c1f0234826
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r5SEBm8W027495 for <ietf@ietf.org>; Fri, 28 Jun 2013 10:11:48 -0400
Received: from alpi131.aldc.att.com (alpi131.aldc.att.com [130.8.218.69]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r5SEBdQY027381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 28 Jun 2013 10:11:41 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi131.aldc.att.com (RSA Interceptor) for <ietf@ietf.org>; Fri, 28 Jun 2013 14:11:22 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r5SEBLu1010568 for <ietf@ietf.org>; Fri, 28 Jun 2013 10:11:22 -0400
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r5SEBDO4010263 for <ietf@ietf.org>; Fri, 28 Jun 2013 10:11:15 -0400
Received: from [135.70.75.53] (vpn-135-70-75-53.vpn.swst.att.com[135.70.75.53]) by maillennium.att.com (mailgw1) with ESMTP id <20130628141111gw100bhhdbe> (Authid: tony); Fri, 28 Jun 2013 14:11:13 +0000
X-Originating-IP: [135.70.75.53]
Message-ID: <51CD9987.8010401@att.com>
Date: Fri, 28 Jun 2013 10:11:19 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: Re: RFC 6234 code
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=2.0 cv=A+LbydqG c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=OuLO4SLYqAsA:10 a=3ukmKKXcZEAA:10 a=ofMgfj31e3cA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=zQP7CpKOAAAA:8 a=qgx6ZmRx]
X-AnalysisOut: [DrOvFdJENTAA:9 a=wPNLvfGTeEIA:10]
Cc: RFC Interest <rfc-interest@rfc-editor.org>, "ietf@ietf.org" <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: Fri, 28 Jun 2013 14:11:57 -0000

On 6/28/2013 4:53 AM, Dearlove, Christopher (UK) wrote:
> I'd actually tried the authors, but no reply yet (only a few days). ....
>
> For me, a thanks to Tony Hansen, who did the extraction for me. (That makes me feel a little guilty, why should he do my work I could have done?) But the point of posting on this list was to say that the code should be available so that each person wanting that code doesn't have to do that again.

Hmmm, as one of the authors of RFC6234, I'm not sure how to respond to
that, other than to say, You're welcome. :-) (And no, you didn't get the
files extracted from the RFC, but instead got the files as used to
generate the RFC.)

> I also tried the RFC Editor thinking they might have e.g. XML from which extraction might have been easier, but also no response yet. And I had found several libraries, but not the RFC code. ...
> But the broader point is that if it's worth the IETF publishing the
> code as an RFC, it's worth making the code available straightforwardly. 

I've suggested on a couple occasions to the RFC Editor that, when an RFC
provides source code, they should allow rfcXXXX.tar or rfcXXXX.tgz to be
provided as well.

There's only a handful of RFCs that do provide source code, for whatever
reason, so this should not be an onerous additional feature.

I've CC'd the RFC Interest mailing list, where this would be more
properly discussed.

    Tony Hansen





From framefritti@gmail.com  Fri Jun 28 07:35:10 2013
Return-Path: <framefritti@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 6046621F9AB8 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 07:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_73=0.6, 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 5lUwo4U1HYwj for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 07:35:09 -0700 (PDT)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) by ietfa.amsl.com (Postfix) with ESMTP id DA51E21F9A70 for <ietf@ietf.org>; Fri, 28 Jun 2013 07:35:06 -0700 (PDT)
Received: by mail-lb0-f171.google.com with SMTP id 13so1075194lba.16 for <ietf@ietf.org>; Fri, 28 Jun 2013 07:34:57 -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 :content-type:content-transfer-encoding; bh=CDiZDwm7Ohg3X6ugKCh+v6Rhlntp4qu0DMehNzP+UwQ=; b=alGvAWe49580tK2/723GMB5g0Hq9mIBxP3dZ/opvQnE6hfb8Vxh5gl+zPJ0EKluG96 9xuy/uudMvmxEqtluWZb0aRD++1HVI2xgODAjeyIs5Fhnr+6F3U+V8asNy6occM9xMe+ h3VuFaWj9TXA7j6oQR1OCeV41q28uCjgTCGKwktQbbksl7fRPLzFUThbWleytWBN9Qcc 9f975c1GTFJTBTzLO1JTBt0LdnsTQuACZ6Lry+fMPzvTvDvoLES0UwuR6foYFSn+JnBW +CnTGZIbtsS2UPuFIXq//l34r3QUqjbHzlZM7I8isdGVDDqKAzWHqmpSZ4b2YAg+Rw9r U52g==
MIME-Version: 1.0
X-Received: by 10.152.19.131 with SMTP id f3mr6842190lae.9.1372430097658; Fri, 28 Jun 2013 07:34:57 -0700 (PDT)
Received: by 10.112.63.42 with HTTP; Fri, 28 Jun 2013 07:34:57 -0700 (PDT)
In-Reply-To: <51CD9987.8010401@att.com>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net> <51CD9987.8010401@att.com>
Date: Fri, 28 Jun 2013 16:34:57 +0200
Message-ID: <CABSMSPXBAAXjyt4EHck4f0haHfXtwnnouDTEwyzv-zoLbnLJPA@mail.gmail.com>
Subject: Re: RFC 6234 code
From: Riccardo Bernardini <framefritti@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: Fri, 28 Jun 2013 14:35:10 -0000

On Fri, Jun 28, 2013 at 4:11 PM, Tony Hansen <tony@att.com> wrote:
> On 6/28/2013 4:53 AM, Dearlove, Christopher (UK) wrote:
>> I'd actually tried the authors, but no reply yet (only a few days). ....
>>
>> For me, a thanks to Tony Hansen, who did the extraction for me. (That ma=
kes me feel a little guilty, why should he do my work I could have done?) B=
ut the point of posting on this list was to say that the code should be ava=
ilable so that each person wanting that code doesn't have to do that again.
>
> Hmmm, as one of the authors of RFC6234, I'm not sure how to respond to
> that, other than to say, You're welcome. :-) (And no, you didn't get the
> files extracted from the RFC, but instead got the files as used to
> generate the RFC.)
>
>> I also tried the RFC Editor thinking they might have e.g. XML from which=
 extraction might have been easier, but also no response yet. And I had fou=
nd several libraries, but not the RFC code. ...
>> But the broader point is that if it's worth the IETF publishing the
>> code as an RFC, it's worth making the code available straightforwardly.
>
> I've suggested on a couple occasions to the RFC Editor that, when an RFC
> provides source code, they should allow rfcXXXX.tar or rfcXXXX.tgz to be
> provided as well.
>
> There's only a handful of RFCs that do provide source code, for whatever
> reason, so this should not be an onerous additional feature.
>
> I've CC'd the RFC Interest mailing list, where this would be more
> properly discussed.

This came to my mind while reading: why not embedding the archive in
the text with some special "line header" that makes automatic
extraction possible?  For example, this could be a first rough draft
of the procedure

  1.  Create an archive of the source files with ar.  This command has
the characteristic that if the files are text files, also the archive
is pure text
  2.  Embed the archive in the RFC by adding at the beginning of each
line a '!' (or another marker).  Lines too long for an RFC can be
split and the marker changed to (say) '?'

In order to extract the archive should suffice to process it with an
awk script, piped to ar to extract the files (and if you have Windows,
you install cygwin :-).  With this approach the source code would also
remain human-readable in the RFC text.  The only drawback is the
length of the resulting RFC if the embedded code is very large.

Riccardo Bernardini

>
>     Tony Hansen
>
>
>
>

From rlb@ipv.sx  Fri Jun 28 07:40:39 2013
Return-Path: <rlb@ipv.sx>
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 040BF21F9B26 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 07:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 0V4+Axb54LkZ for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 07:40:34 -0700 (PDT)
Received: from mail-oa0-f47.google.com (mail-oa0-f47.google.com [209.85.219.47]) by ietfa.amsl.com (Postfix) with ESMTP id 89F8A21F8574 for <ietf@ietf.org>; Fri, 28 Jun 2013 07:40:34 -0700 (PDT)
Received: by mail-oa0-f47.google.com with SMTP id m1so2426072oag.34 for <ietf@ietf.org>; Fri, 28 Jun 2013 07:40:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=ujL9Ga5jd+qlr9aRsiFW+49TfqcACOsxM95HKG0habU=; b=gPuSphj0bo037pybJBj3X3hOIFJZD5wSMX9YtMGs65QyS1sAJ1R+BCQqv/JNfNErSo M6wuxPrxwpwuwnv0iaJE3cgE2GcMEpohRDtCmyx2Jbdvnheq9rB+KbGQHGdotLluJIXw sSL1RyJO2M9vRbQKCoZRiA6zX98Av0nRQwb6JvEXy2IVTzo1AJ3GrazUMsUdFbigbJia RW8kFnnIodHvUGO5h1sJPpMohXRxX+pYcZOBpxN+j+KYhJvqbItRenCy80EsYmz4jdpJ niEHpsOKFPpc0hqx+X8iEj6s2w0ukth2S08jxDaBPhhOqKSGTHJ9x5u69cXRaO6tugJM RJmw==
MIME-Version: 1.0
X-Received: by 10.60.115.199 with SMTP id jq7mr5218422oeb.19.1372430434064; Fri, 28 Jun 2013 07:40:34 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Fri, 28 Jun 2013 07:40:33 -0700 (PDT)
X-Originating-IP: [174.255.18.209]
In-Reply-To: <1372385475.31973.YahooMailNeo@web162401.mail.bf1.yahoo.com>
References: <1372385475.31973.YahooMailNeo@web162401.mail.bf1.yahoo.com>
Date: Fri, 28 Jun 2013 10:40:33 -0400
Message-ID: <CAL02cgQpPDm40n_m2_JcqKt=sMrj0QqRz-uHRxsmSH64i9uh9w@mail.gmail.com>
Subject: Re: adaptive http
From: Richard Barnes <rlb@ipv.sx>
To: Faiz ul haque Zeya <faizzeya@yahoo.com>
Content-Type: multipart/alternative; boundary=089e0115e8e8806b0604e037dcbc
X-Gm-Message-State: ALoCoQn8U1HNpn+HrxGeZxeJctUHkhJZiu9h+Oi+EmwIjhyy+9n+UuuqgZTEWaRuB8NW6PicV36T
Cc: "ietf@ietf.org" <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: Fri, 28 Jun 2013 14:40:39 -0000

--089e0115e8e8806b0604e037dcbc
Content-Type: text/plain; charset=ISO-8859-1

Hi Faiz,

Thanks for bringing your idea to the IETF.  The best way to propose your
idea is to write down the details in an "Internet-draft".  That helps make
sure that everyone understands how your system works.  There are some tools
for writing drafts here:
http://tools.ietf.org/

Once you've written your draft, submit it here:
http://datatracker.ietf.org/submit/

--Richard



On Thursday, June 27, 2013, Fail ul haque Zeya wrote:

> Hi all,
>  I have an idea and want to share.It is about adaptive http. The protocol
> requests the interests and other parameters from the client and send the
> web page dynamically different to different users based on the interests.
> The intersts can be shared via XML. This is in contrast to configured html
> pages a different mechanism,
> regards
> faiz
>
>

--089e0115e8e8806b0604e037dcbc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Faiz,<div><br></div><div>Thanks for bringing your idea to the IETF. =A0T=
he best way to propose your idea is to write down the details=A0in=A0an &qu=
ot;Internet-draft&quot;. =A0That helps make sure that everyone understands =
how your system works. =A0There are some tools for writing drafts here:</di=
v>
<div><a href=3D"http://tools.ietf.org/">http://tools.ietf.org/</a></div><di=
v><br></div><div>Once you&#39;ve written your draft, submit it here:</div><=
div><a href=3D"http://datatracker.ietf.org/submit/">http://datatracker.ietf=
.org/submit/</a></div>
<div><br></div><div>--Richard</div><div><br></div><div><span></span><br><br=
>On Thursday, June 27, 2013, Fail ul haque Zeya  wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<div><div style=3D"font-size:12pt;font-family:times new roman,new york,time=
s,serif"><div>Hi all,</div><div>=A0I have an idea and want to share.It is a=
bout adaptive http. The protocol requests the interests and other parameter=
s from the client and send the web page dynamically different to different =
users based on the interests. The intersts can be shared via XML. This is i=
n contrast to configured html pages a different mechanism,</div>
<div>regards</div><div>faiz</div><div><br></div></div></div></blockquote></=
div>

--089e0115e8e8806b0604e037dcbc--

From paul.hoffman@vpnc.org  Fri Jun 28 07:53:09 2013
Return-Path: <paul.hoffman@vpnc.org>
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 59EE121F9B81 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 07:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 78EWLK6zlxU6 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 07:53:09 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1315821F9B41 for <ietf@ietf.org>; Fri, 28 Jun 2013 07:53:08 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5SEr3uX062900 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 28 Jun 2013 07:53:04 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: RFC 6234 code
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <93DE6BA0-4677-40E6-9257-4AFECF04EC25@netapp.com>
Date: Fri, 28 Jun 2013 07:53:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <592193B1-FC60-4EE2-B304-CE1B7B131614@vpnc.org>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net> <93DE6BA0-4677-40E6-9257-4AFECF04EC25@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org" <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: Fri, 28 Jun 2013 14:53:09 -0000

On Jun 28, 2013, at 1:57 AM, "Eggert, Lars" <lars@netapp.com> wrote:

> some WGs are good at this. RFC5662 for example includes the shell =
commands to extract the sources it contains.

Earlier example: RFC 4134.

> It would certainly be nice if other WGs did this, too, but I'm not =
sure we need to make it a requirement.

Fully agree. This is a service that the RFC Editor should provide to the =
community.

--Paul Hoffman=

From hsantos@isdg.net  Fri Jun 28 08:59:14 2013
Return-Path: <hsantos@isdg.net>
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 8B28321F848E for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 08:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.735
X-Spam-Level: 
X-Spam-Status: No, score=-101.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
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 y79xuKZ4TuPI for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 08:59:03 -0700 (PDT)
Received: from dkim.winserver.com (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id BF2E121F9ADC for <ietf@ietf.org>; Fri, 28 Jun 2013 08:59:02 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2346; t=1372435140; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=BFqfgk5 GDwkzWSCiIrau/L21OLo=; b=XisvfHdp+UK4IlIuLJbtGEZEt+PAU7zhONSmyRa gZuz3sXZ/QwNFlYbZbYYcpmMVJUez3QxSW2aJIiV2qdlIvEhT1ohaU2ekULprf75 tPYWBNbK/i4vP01+uutYWrOOnxqyXnfl9omAxBzQffdclol9Mz8OoANnQZFd82/T Tnvw=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 28 Jun 2013 11:59:00 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3192676837.5276.4012; Fri, 28 Jun 2013 11:58:59 -0400
Message-ID: <51CDB221.4060906@isdg.net>
Date: Fri, 28 Jun 2013 11:56:17 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: Part of Improving IETF Electronic Diversity [was: RFC 6234 code]
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <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: Fri, 28 Jun 2013 15:59:14 -0000

I believe this is all part of improving the IETF Electronic Diversity 
picture. Just like we have to deal with greater people personal 
globalization diversity issues, there is also greater technology and 
legal diversity issues to deal with. So many tools, so many languages, 
so many OSes, so many devices and communications API platforms, where 
are the proposals for better, new "IETF Global Commons?"  Guidelines for 
technical writing for the new world engineers to use, etc.

For me, when I saw this RFC, the things crossed my mind:

- I have trouble with the licensing statement. The RFC describes public 
domain technology.  It requires passing this thru your lawyer(s) to see 
if it can used in our commercial product lines.

- Far too big to distribute via a RFC.  Provide a link to some RFC site. 
Note, I'm just saying in general. I did not read in detail if
the RFC already included links to the official source code.

- Because it was too big, it requires a stripper/parser, although a good 
power programmer can quickly macro-clean it up.  The RFCSTRIP tool, 
well, what language is that? I'm not an *nix person. So this adds to the 
complexity for the Windows shops to get at these hashing functions.  Of 
course, its a piece of cake for a sharp programmer, but even the 
sharpest knives eventually get dull.

--
HLS


On 6/28/2013 4:53 AM, Dearlove, Christopher (UK) wrote:
> I'd actually tried the authors, but no reply yet (only a few days). I also tried the RFC Editor thinking they might have e.g. XML from which extraction might have been easier, but also no response yet. And I had found several libraries, but not the RFC code. I can't see any suggestion that the library you indicate includes that code, it also bills itself as a C++ library, which the RFC code is not (and also not what I want, but that's not a subject for this list).
>
> But the broader point is that if it's worth the IETF publishing the code as an RFC, it's worth making the code available straightforwardly.
>
> For me, a thanks to Tony Hansen, who did the extraction for me. (That makes me feel a little guilty, why should he do my work I could have done?) But the point of posting on this list was to say that the code should be available so that each person wanting that code doesn't have to do that again.
>
> Christopher
>


From d3e3e3@gmail.com  Thu Jun 27 11:24:45 2013
Return-Path: <d3e3e3@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 6DD4F21F9E92 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 11:24:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 fl7Nj-W2e378 for <ietf@ietfa.amsl.com>; Thu, 27 Jun 2013 11:24:45 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id F398421F9E90 for <ietf@ietf.org>; Thu, 27 Jun 2013 11:24:44 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id fb19so1061743obc.23 for <ietf@ietf.org>; Thu, 27 Jun 2013 11:24:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=6Qzc4beQL5qpvc0Cd0lv081BZz0tfAmOGVO0ix9GpBc=; b=PSiHpruJIj6hVbg+pRekSgYDKKlV/bFOWb9SIlSAyiuANo+VVhHxAlcGdLDelMgJA4 fo2ox7It681nkuwERiAqB7LPWM5PFquQLa2Un70heZYR8TKITin4pqiGcbfaZuaX+eV6 t/qqJInClZxj0a18Y1p75doIBrB8v69BhHu7Q/uBazSyNzksqQ8Q3CeL0xO/VdFoKDTg OmZbj/joQl7x6CT0mLxdTSziwRLkpsBoKqQhSjovExanYfFPZcRoHCOC/axPTRgivMho bFEAC6XPrYec72No64h3zWkjT5zjWzQDWiogIquDYQhpRw7kUGLeS1/pU4BZwIzS4CK4 NDPA==
X-Received: by 10.182.148.100 with SMTP id tr4mr4720677obb.53.1372357484056; Thu, 27 Jun 2013 11:24:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.12.65 with HTTP; Thu, 27 Jun 2013 11:24:23 -0700 (PDT)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 27 Jun 2013 14:24:23 -0400
Message-ID: <CAF4+nEG_rnXXNjebywpPVyA4mfXGGs7=Fj8m8QgM1QpXjo+rDw@mail.gmail.com>
Subject: draft-eastlake-trill-rfc6327bis-00 was replaced by draft-ietf-trill-rfc6327bis-00
To: internet-drafts@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Fri, 28 Jun 2013 08:59:23 -0700
Cc: Erik Nordmark <nordmark@acm.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: Thu, 27 Jun 2013 18:24:45 -0000

Hi,

Please note that draft-eastlake-trill-rfc6327bis-00 was replaced by
draft-ietf-trill-rfc6327bis-00.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

From hannes.tschofenig@gmx.net  Fri Jun 28 09:54:54 2013
Return-Path: <hannes.tschofenig@gmx.net>
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 146FA21F9A24 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 09:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 sgeEG7zycD3x for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 09:54:49 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id D02AC21F965B for <ietf@ietf.org>; Fri, 28 Jun 2013 09:54:11 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.16]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0Mdp4t-1UbsIZ1ulZ-00PanU for <ietf@ietf.org>; Fri, 28 Jun 2013 18:54:10 +0200
Received: (qmail invoked by alias); 28 Jun 2013 16:54:10 -0000
Received: from host-94-101-1-228.igua.fi (EHLO [192.168.4.115]) [94.101.1.228] by mail.gmx.net (mp016) with SMTP; 28 Jun 2013 18:54:10 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18t0PQquWgtMHq0I4cxPxbqmygq9supjPI3eLIZYo DUsbJQNBAgjGup
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Experience with Online Protocol Testing
Date: Fri, 28 Jun 2013 19:54:06 +0300
Message-Id: <5B3DFCA9-D8CB-4FD2-A6E6-CD2337DBA54E@gmx.net>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Pgp-Agent: GPGMail 1.4.1
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 0
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: Fri, 28 Jun 2013 16:54:54 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

[I posted this question a little while ago to the WG chairs mailing list =
and got no response.
Maybe my question is too trivial but I thought I should try it on the =
ietf@ietf.org list as well to=20
get some feedback.]

Hi all,

when concerns about the lack of interoperability surfaced mid last year=20=

in the OAuth working group we (Derek, and myself) tried to figure out=20
whether we should schedule a face-to-face interop and/or to develop an=20=

online test suite. We got in touch with Lucy Lynch (ISOC) and she helped=20=

us to find developers to work with us on the test software.

Roland Hedberg, one of the guys working on the project for OAuth=20
testing, presented his ongoing work in the OAuth working group, see
http://www.ietf.org/proceedings/86/slides/slides-86-oauth-2.pdf

OAuth is a bit more complex since it involves more than two parties and=20=

we were looking for a test framework that could be re-used to develop=20
the desired results more quickly. To our surprise we couldn't find=20
a test framework that we could easily re-use since most test frameworks=20=

really focus on different types of tests. Of course, we might=20
have looked in the wrong direction.

Here is how it works at the moment:
* Imagine you have developed an OAuth-based identity management server=20=

(that contains an OAuth 2.0 authorization server) and it runs somewhere=20=

on the Internet (or in your lab). You don't need to have access to the=20=

source code to execute the tests.
* You download the scripts that Roland & Co had developed and configure=20=

them. Of course you will have to create an account at your IdP as well.
* You run the test scripts against the authorization server and the=20
script plays the other OAuth 2.0 parties in the exchange. The script =
contains a number=20
of test cases (around 60+ at the moment) and determines whether the IdP=20=

responds correctly in the exchanges.

I know that these ideas have come up in other working groups in the past=20=

already (such as in SCIM, which also has a test server up and=20
running).

It would be interesting to hear what others have been doing and what=20
worked for you or what didn't.

Ciao
Hannes



-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJRzb+vAAoJEGhJURNOOiAtZBwIAISKHjD7gv8irkL4yaBR31K8
KLZCr/1n0n1OcXl3rE9MFOyA85hYNplZFd1giJLLgEX3UyofYXg/L2QOOLqtP0lT
JgnW2CvR0WWKfIT1iKjAwAodCVLsHF8MdPE4tl0LBlCeqhA1waj/oCLkBzZrrhhq
oWnZzP0I9nFdlSxV9EAHQ62RAxLUVQmBEqgMxl7A+iC9fGD8IhWSNSqqsaF0WOaB
6bHdwCFLYYAyqKhiuJAo/f6YFGEzIbPgpHPGjwBZzBIjwP/EGiFnAliyF8WATHzF
RM+OWg6QASh1cNwzc0dbMcrcr1L1ve7amATMc4uPN7sRjhv0s62iguWfGRhQhHw=3D
=3DYT5M
-----END PGP SIGNATURE-----

From Michael.Tuexen@lurchi.franken.de  Fri Jun 28 10:05:55 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 9458721F9BB9 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 10:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 9Hb1QuRTG6FY for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 10:05:55 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 74CAB21F9BB4 for <ietf@ietf.org>; Fri, 28 Jun 2013 10:05:54 -0700 (PDT)
Received: from [192.168.1.200] (p508F1AC4.dip0.t-ipconnect.de [80.143.26.196]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 0E7FA1C0C0693; Fri, 28 Jun 2013 19:05:50 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Experience with Online Protocol Testing
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <5B3DFCA9-D8CB-4FD2-A6E6-CD2337DBA54E@gmx.net>
Date: Fri, 28 Jun 2013 19:05:50 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B991E86-BA03-4F31-888F-947BE568A5B6@lurchi.franken.de>
References: <5B3DFCA9-D8CB-4FD2-A6E6-CD2337DBA54E@gmx.net>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org Discussion" <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: Fri, 28 Jun 2013 17:05:55 -0000

On Jun 28, 2013, at 6:54 PM, Hannes Tschofenig =
<Hannes.Tschofenig@gmx.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>=20
> [I posted this question a little while ago to the WG chairs mailing =
list and got no response.
> Maybe my question is too trivial but I thought I should try it on the =
ietf@ietf.org list as well to=20
> get some feedback.]
>=20
> Hi all,
>=20
> when concerns about the lack of interoperability surfaced mid last =
year=20
> in the OAuth working group we (Derek, and myself) tried to figure out=20=

> whether we should schedule a face-to-face interop and/or to develop an=20=

> online test suite. We got in touch with Lucy Lynch (ISOC) and she =
helped=20
> us to find developers to work with us on the test software.
>=20
> Roland Hedberg, one of the guys working on the project for OAuth=20
> testing, presented his ongoing work in the OAuth working group, see
> http://www.ietf.org/proceedings/86/slides/slides-86-oauth-2.pdf
>=20
> OAuth is a bit more complex since it involves more than two parties =
and=20
> we were looking for a test framework that could be re-used to develop=20=

> the desired results more quickly. To our surprise we couldn't find=20
> a test framework that we could easily re-use since most test =
frameworks=20
> really focus on different types of tests. Of course, we might=20
> have looked in the wrong direction.
>=20
> Here is how it works at the moment:
> * Imagine you have developed an OAuth-based identity management server=20=

> (that contains an OAuth 2.0 authorization server) and it runs =
somewhere=20
> on the Internet (or in your lab). You don't need to have access to the=20=

> source code to execute the tests.
> * You download the scripts that Roland & Co had developed and =
configure=20
> them. Of course you will have to create an account at your IdP as =
well.
> * You run the test scripts against the authorization server and the=20
> script plays the other OAuth 2.0 parties in the exchange. The script =
contains a number=20
> of test cases (around 60+ at the moment) and determines whether the =
IdP=20
> responds correctly in the exchanges.
>=20
> I know that these ideas have come up in other working groups in the =
past=20
> already (such as in SCIM, which also has a test server up and=20
> running).
>=20
> It would be interesting to hear what others have been doing and what=20=

> worked for you or what didn't.
So it sounds like you are doing some sort of conformance testing...

For SCTP we did a number of interoperability tests, which were
face to face meetings and the people who were developing stacks
we there. This events were always very helpful not only for improving
the stacks but also for improving the IETF documents.
I also developed a test tool for conformance testing based on some
test descriptions provided by ETSI. However, it would have made sense to
specify also some tests within the IETF. That can also help to clarify
some protocol aspects and to focus on "common mistakes".
Providing tests is a very good thing in my experience. Unfortunately,
at the point we did this for SCTP, the IETF position was that testing
isn't an objective. Maybe it is time to change that...

Best regards
Michael
>=20
> Ciao
> Hannes
>=20
>=20
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
>=20
> iQEcBAEBCgAGBQJRzb+vAAoJEGhJURNOOiAtZBwIAISKHjD7gv8irkL4yaBR31K8
> KLZCr/1n0n1OcXl3rE9MFOyA85hYNplZFd1giJLLgEX3UyofYXg/L2QOOLqtP0lT
> JgnW2CvR0WWKfIT1iKjAwAodCVLsHF8MdPE4tl0LBlCeqhA1waj/oCLkBzZrrhhq
> oWnZzP0I9nFdlSxV9EAHQ62RAxLUVQmBEqgMxl7A+iC9fGD8IhWSNSqqsaF0WOaB
> 6bHdwCFLYYAyqKhiuJAo/f6YFGEzIbPgpHPGjwBZzBIjwP/EGiFnAliyF8WATHzF
> RM+OWg6QASh1cNwzc0dbMcrcr1L1ve7amATMc4uPN7sRjhv0s62iguWfGRhQhHw=3D
> =3DYT5M
> -----END PGP SIGNATURE-----
>=20


From hannes.tschofenig@gmx.net  Fri Jun 28 10:14:57 2013
Return-Path: <hannes.tschofenig@gmx.net>
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 58DCC21F9A90 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 10:14:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 9AwH-rU6GXcF for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 10:14:45 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id C7BBD21F9A79 for <ietf@ietf.org>; Fri, 28 Jun 2013 10:14:44 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.31]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0Lrp0S-1U7hgA0Z9q-013ebu for <ietf@ietf.org>; Fri, 28 Jun 2013 19:14:44 +0200
Received: (qmail invoked by alias); 28 Jun 2013 17:14:43 -0000
Received: from host-94-101-1-228.igua.fi (EHLO [192.168.4.115]) [94.101.1.228] by mail.gmx.net (mp031) with SMTP; 28 Jun 2013 19:14:43 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/HeelsfkzHDZv+HMsudzEwzzBYh1uxRtXXAIh0N+ zK8c/jOwm8N+LN
Subject: Re: Experience with Online Protocol Testing
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
In-Reply-To: <5B991E86-BA03-4F31-888F-947BE568A5B6@lurchi.franken.de>
Date: Fri, 28 Jun 2013 20:14:41 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7985DB9-2635-4D63-B5D8-5BEB82EFFE66@gmx.net>
References: <5B3DFCA9-D8CB-4FD2-A6E6-CD2337DBA54E@gmx.net> <5B991E86-BA03-4F31-888F-947BE568A5B6@lurchi.franken.de>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
X-Pgp-Agent: GPGMail 1.4.1
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 0
Cc: "ietf@ietf.org Discussion" <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: Fri, 28 Jun 2013 17:14:57 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> For SCTP we did a number of interoperability tests, which were
> face to face meetings and the people who were developing stacks
> we there. This events were always very helpful not only for improving
> the stacks but also for improving the IETF documents.
> I also developed a test tool for conformance testing based on some
> test descriptions provided by ETSI. However, it would have made sense =
to
> specify also some tests within the IETF. That can also help to clarify
> some protocol aspects and to focus on "common mistakes".
> Providing tests is a very good thing in my experience. Unfortunately,
> at the point we did this for SCTP, the IETF position was that testing
> isn't an objective. Maybe it is time to change that...
>=20
> Best regards
> Michael


I guess the code you wrote for your online test cases was your own work =
and you didn't re-use some else's test framework?=20
The SCTP case is also a bit simpler than the OAuth scenario since in =
SCTP might have only tested client-server interactions (right?)

Ciao
Hannes

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJRzcSCAAoJEGhJURNOOiAt064H/3iowM2lBBunk58jOq1/eAfK
Cy+y+dpEqJoXeqMI7RLtTsXXDbblxI83cxO6OXol7HU37elmomdiD7qGg2KPeeOJ
1GyEWnXXJ1oaC9AcWAkPiRan2EhdXGxu6yWG1iuHniOSkC3WvU9nhVU8PLUkSPwB
WSzh4hsj6tnTpR67oYoHkDwtQsFuvcvxiYkNV9rI3fy+FIXJ5ygf9UPmgVJpNqIx
azmc8W9iWUUeGGnaU+/2APRybe8PpCZf6y+QKVFA/6Zkai86/HfTaDFdAnL/eOXV
xhdXjHsn8Ci4CkCXJ7Pn2JRpIYX1y7ccMOvu8WHuvJnSQ2S091/EFHBY2w/Wydk=3D
=3DvU1M
-----END PGP SIGNATURE-----

From Michael.Tuexen@lurchi.franken.de  Fri Jun 28 10:58:41 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 1345921F8628 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 10:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 J0djgpjHK-6w for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 10:58:40 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id E1F4821F861F for <ietf@ietf.org>; Fri, 28 Jun 2013 10:58:39 -0700 (PDT)
Received: from [192.168.1.200] (p508F1AC4.dip0.t-ipconnect.de [80.143.26.196]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 7D3E01C0C0695; Fri, 28 Jun 2013 19:58:37 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Experience with Online Protocol Testing
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <E7985DB9-2635-4D63-B5D8-5BEB82EFFE66@gmx.net>
Date: Fri, 28 Jun 2013 19:58:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC6B97C1-E537-4572-88D9-B87720D7D01E@lurchi.franken.de>
References: <5B3DFCA9-D8CB-4FD2-A6E6-CD2337DBA54E@gmx.net> <5B991E86-BA03-4F31-888F-947BE568A5B6@lurchi.franken.de> <E7985DB9-2635-4D63-B5D8-5BEB82EFFE66@gmx.net>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org Discussion" <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: Fri, 28 Jun 2013 17:58:41 -0000

On Jun 28, 2013, at 7:14 PM, Hannes Tschofenig =
<Hannes.Tschofenig@gmx.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>=20
>> For SCTP we did a number of interoperability tests, which were
>> face to face meetings and the people who were developing stacks
>> we there. This events were always very helpful not only for improving
>> the stacks but also for improving the IETF documents.
>> I also developed a test tool for conformance testing based on some
>> test descriptions provided by ETSI. However, it would have made sense =
to
>> specify also some tests within the IETF. That can also help to =
clarify
>> some protocol aspects and to focus on "common mistakes".
>> Providing tests is a very good thing in my experience. Unfortunately,
>> at the point we did this for SCTP, the IETF position was that testing
>> isn't an objective. Maybe it is time to change that...
>>=20
>> Best regards
>> Michael
>=20
>=20
> I guess the code you wrote for your online test cases was your own =
work and you didn't re-use some else's test framework?=20
Not a test framework, but a scheme interpreter (guile) was extended with =
the
necessary stuff for sending/receiving packets, such that tests can be =
implemented
as simple scheme functions. Doing a test is calling a scheme function =
which
returns whether the corresponding test was passed or failed. Some shell =
scripts
allows you running a test suite.
> The SCTP case is also a bit simpler than the OAuth scenario since in =
SCTP might have only tested client-server interactions (right?)
Well, the testtool only deals with network layer events. Taking =
interactions
with the application (API) into account is a different story. We also =
have
an API tester, which is also self written. We currently don't have =
something
which takes network and API events into account.

Best regards
Michael
>=20
> Ciao
> Hannes
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
>=20
> iQEcBAEBCgAGBQJRzcSCAAoJEGhJURNOOiAt064H/3iowM2lBBunk58jOq1/eAfK
> Cy+y+dpEqJoXeqMI7RLtTsXXDbblxI83cxO6OXol7HU37elmomdiD7qGg2KPeeOJ
> 1GyEWnXXJ1oaC9AcWAkPiRan2EhdXGxu6yWG1iuHniOSkC3WvU9nhVU8PLUkSPwB
> WSzh4hsj6tnTpR67oYoHkDwtQsFuvcvxiYkNV9rI3fy+FIXJ5ygf9UPmgVJpNqIx
> azmc8W9iWUUeGGnaU+/2APRybe8PpCZf6y+QKVFA/6Zkai86/HfTaDFdAnL/eOXV
> xhdXjHsn8Ci4CkCXJ7Pn2JRpIYX1y7ccMOvu8WHuvJnSQ2S091/EFHBY2w/Wydk=3D
> =3DvU1M
> -----END PGP SIGNATURE-----
>=20


From john-ietf@jck.com  Fri Jun 28 12:10:50 2013
Return-Path: <john-ietf@jck.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 D0FF421F9CAE for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 12:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_73=0.6, USER_IN_WHITELIST=-100]
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 gJSnSezd5Ywf for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 12:10:45 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 06AA521F9CAD for <ietf@ietf.org>; Fri, 28 Jun 2013 12:10:45 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Use4A-000E2T-4A; Fri, 28 Jun 2013 15:10:42 -0400
Date: Fri, 28 Jun 2013 15:10:37 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tony Hansen <tony@att.com>, "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: Re: RFC 6234 code
Message-ID: <BEFC413A958E9B25913F2FE9@JcK-HP8200.jck.com>
In-Reply-To: <51CD9987.8010401@att.com>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net> <51CD9987.8010401@att.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: RFC Interest <rfc-interest@rfc-editor.org>, 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: Fri, 28 Jun 2013 19:10:51 -0000

--On Friday, June 28, 2013 10:11 -0400 Tony Hansen
<tony@att.com> wrote:

>> I also tried the RFC Editor thinking they might have e.g. XML
>> from which extraction might have been easier, but also no
>> response yet. And I had found several libraries, but not the
>> RFC code. ... But the broader point is that if it's worth the
>> IETF publishing the code as an RFC, it's worth making the
>> code available straightforwardly. 
> 
> I've suggested on a couple occasions to the RFC Editor that,
> when an RFC provides source code, they should allow
> rfcXXXX.tar or rfcXXXX.tgz to be provided as well.
> 
> There's only a handful of RFCs that do provide source code,
> for whatever reason, so this should not be an onerous
> additional feature.

Folks, IANAL, but please be _very_ careful about the comment Joe
made about the potential difference between publishing a paper
or article that contains code and exporting the code itself or
making it generally available for export.   I have no reason to
believe that this particular case is a problem given how widely
the details of SHA-2 has been published but, if we want the RFC
Editor to go into the code distribution business, we should be
very sure that an attorney with the right specialties has looked
at the situation and either cleared it generally or advised on
what needs to be examined case by case.

   john




From paul.hoffman@vpnc.org  Fri Jun 28 12:19:24 2013
Return-Path: <paul.hoffman@vpnc.org>
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 7A1A021F9C2B for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 12:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 rtLrUQi6c4TB for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 12:19:24 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0720721F9B22 for <ietf@ietf.org>; Fri, 28 Jun 2013 12:19:23 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5SJJLMq069438 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 28 Jun 2013 12:19:22 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: RFC 6234 code
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <BEFC413A958E9B25913F2FE9@JcK-HP8200.jck.com>
Date: Fri, 28 Jun 2013 12:19:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D3A3A63A-0CB1-4254-A087-655F9BDA6CEC@vpnc.org>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net> <51CD9987.8010401@att.com> <BEFC413A958E9B25913F2FE9@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Cc: RFC Interest <rfc-interest@rfc-editor.org>, "ietf@ietf.org 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: Fri, 28 Jun 2013 19:19:24 -0000

On Jun 28, 2013, at 12:10 PM, John C Klensin <john-ietf@jck.com> wrote:

> Folks, IANAL, but please be _very_ careful about the comment Joe
> made about the potential difference between publishing a paper
> or article that contains code and exporting the code itself or
> making it generally available for export.   I have no reason to
> believe that this particular case is a problem given how widely
> the details of SHA-2 has been published but, if we want the RFC
> Editor to go into the code distribution business, we should be
> very sure that an attorney with the right specialties has looked
> at the situation and either cleared it generally or advised on
> what needs to be examined case by case.

The RFC Editor is publishing code in a text file that is formatted like =
an RFC. The proposal is for the RFC Editor to publish *the exact same =
code* in a file without the RFC wrapping.

If you really think you see a legal difference in doing the second, =
fine; I propose that you are just searching for problems that do not =
exist.

--Paul Hoffman=

From jabley@hopcount.ca  Fri Jun 28 13:41:10 2013
Return-Path: <jabley@hopcount.ca>
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 35B3921F9C96 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 13:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 PnUJuzSQ5xSq for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 13:41:09 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 240FF21F9C8B for <ietf@ietf.org>; Fri, 28 Jun 2013 13:41:08 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id g12so2789002oah.25 for <ietf@ietf.org>; Fri, 28 Jun 2013 13:41:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=twrL+QqTRQik8/keiDTnR56Pnnw7MxguL0Vy3NAEzuE=; b=LV0ZJtZm3DxrqeBdffZd3wrcKvWc/oKPaid8JRkjQ4ZCE824Aawffd5kPD9YOTRtmE Woq5jUKjTl8gyQEIc+9DyCDfNMDLyFMyvRAuIHhlfMA0jzkl7sUH01zraOXSAu24UwAZ z6t0HpnuALuYrLjfdat5Nh+Z2CW/0c2pJUcdY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=twrL+QqTRQik8/keiDTnR56Pnnw7MxguL0Vy3NAEzuE=; b=OEoFJVXI6nbealrfWf8eug11pBvF7H4OFRbZZV8ctJXEnuviMukrtzXlXQJnDgqOXB nYFmFiF0Y1apu/IlR+z7TenWgE8qqy7BxIYoy9rvRMogdP895LzxuSt+ArxHlKoE1jRJ Tglo4AmDJUERm4rce3jIKWRTSJJ4yt3yP+x9Jz7//9EYk8ByI9wWweAgkEhUIragq4wx NpU3X5MHmYspkQ2pbzVVRuRFwsQQIPfy9OA/+C4hjibI5rxZjZWGwxYArxOEHxC6n4ER cE6pJHXjwPv+P7SC8D7YcL9ufUwl8R/UoBOW/QzLbRfX/z1xGfs7KoTQksqHAJXhRkAI 3KIA==
X-Received: by 10.60.70.4 with SMTP id i4mr5852930oeu.11.1372452066488; Fri, 28 Jun 2013 13:41:06 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:6d51:7949:c592:fc8c? ([2001:4900:1042:100:6d51:7949:c592:fc8c]) by mx.google.com with ESMTPSA id ps5sm2100313oeb.8.2013.06.28.13.41.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 28 Jun 2013 13:41:05 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: RFC 6234 code
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <D3A3A63A-0CB1-4254-A087-655F9BDA6CEC@vpnc.org>
Date: Fri, 28 Jun 2013 16:41:05 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB3A3E49-13C6-4CE3-87D5-8F86B37DFC57@hopcount.ca>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net> <51CD9987.8010401@att.com> <BEFC413A958E9B25913F2FE9@JcK-HP8200.jck.com> <D3A3A63A-0CB1-4254-A087-655F9BDA6CEC@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQkngzBosy+u532Y/Njt+wNtBvcY+xPuxAJEuh/OyyvFi71v5Ud27psEV9dtN8lgMW0AZN2n
Cc: John C Klensin <john-ietf@jck.com>, RFC Interest <rfc-interest@rfc-editor.org>, "ietf@ietf.org 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: Fri, 28 Jun 2013 20:41:10 -0000

On 2013-06-28, at 15:19, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> The RFC Editor is publishing code in a text file that is formatted =
like an RFC. The proposal is for the RFC Editor to publish *the exact =
same code* in a file without the RFC wrapping.
>=20
> If you really think you see a legal difference in doing the second, =
fine; I propose that you are just searching for problems that do not =
exist.

Quite possibly they don't, and I'm not presuming to talk for John. But =
the vague thoughts that crossed my mine were the issues that allowed =
Phil Zimmerman to publish PGP source code in book form and avoid =
conviction for munitions export without a licence.

Perhaps this is no longer an issue in the US following Bernstein vs. =
United States and Junger vs. Daley.

Just thinking aloud, really.

I will observe that far more than 20 minutes of combined person-minutes =
have been consumed by this thread already, and the approach of minimum =
collective effort is still "scrape the code from the RFC yourself and =
compile it".


Joe=

From d3e3e3@gmail.com  Fri Jun 28 14:19:53 2013
Return-Path: <d3e3e3@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 56C1B21F9D49 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 14:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 rd1ekyhEXK5I for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 14:19:52 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 437C421F9D47 for <ietf@ietf.org>; Fri, 28 Jun 2013 14:19:50 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id wo10so2461267obc.3 for <ietf@ietf.org>; Fri, 28 Jun 2013 14:19:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=rdA4hm6MaRVJoxvPbCRFj2hlad005FX4eosFr5iNBRQ=; b=TP9g7QHXdlnBGQZ33KkoXiRUonk4jtUhGAaDSqfQcK4DS7ikpIBWB155mMpYtzyjHX miM64FhkKCR3c6WEB/jLYTu01/2q8GazJ1molX+L8S+MaXcUyA9NOsxxZ6BR+IwOkd7g Gbh5ZvKPeubwhTO5B7bq4XCJv0Tw2OU/UJYQi1A5N3i39kAkSukzx00g6FjSBtGdSQ84 kbchK2u6Ijvdo2ppOEko+uU76CoJzovxCSCBuhVdAxEkuuepEgr6CEA6sX6l+UnXmyZM lK3xAkAX8gJbPhhiTl09bkcY69QXVdAdSoDS53dt7ny0WxqowY/xOINUF48ju1ayp9Dp 1czg==
X-Received: by 10.182.165.232 with SMTP id zb8mr7205633obb.101.1372454388072;  Fri, 28 Jun 2013 14:19:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.12.65 with HTTP; Fri, 28 Jun 2013 14:19:27 -0700 (PDT)
In-Reply-To: <51CDB221.4060906@isdg.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net> <51CDB221.4060906@isdg.net>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 28 Jun 2013 17:19:27 -0400
Message-ID: <CAF4+nEG8p9QttHNqCWm9BN4ss8hcwuqgjBv9S0uwsUAhmX-dEQ@mail.gmail.com>
Subject: Re: Part of Improving IETF Electronic Diversity [was: RFC 6234 code]
To: Hector Santos <hsantos@isdg.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org" <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: Fri, 28 Jun 2013 21:19:53 -0000

Hi Hector,

On Fri, Jun 28, 2013 at 11:56 AM, Hector Santos <hsantos@isdg.net> wrote:
> I believe this is all part of improving the IETF Electronic Diversity
> picture. Just like we have to deal with greater people personal
> globalization diversity issues, there is also greater technology and legal
> diversity issues to deal with. So many tools, so many languages, so many
> OSes, so many devices and communications API platforms, where are the
> proposals for better, new "IETF Global Commons?"  Guidelines for technical
> writing for the new world engineers to use, etc.

I think that computational code written in C, pretty much the lowest
common denominator, is just fine. I don't think there is any greater
diversity now that then was 10 or 20 years ago at that level. In fact,
I think there is less.

> For me, when I saw this RFC, the things crossed my mind:
>
> - I have trouble with the licensing statement. The RFC describes public
> domain technology.  It requires passing this thru your lawyer(s) to see if
> it can used in our commercial product lines.

Sorry, the standard simplified BSD license is required for code in
RFCs. The authors couldn't change it. But if you are doing a serious
commercial product and you don't have a lawyer checking such things
anyway, you are a fool.

> - Far too big to distribute via a RFC.  Provide a link to some RFC site.
> Note, I'm just saying in general. I did not read in detail if
> the RFC already included links to the official source code.

Nonsense. An RFC should be self contained and IO don't see what's "too
big" about this one. The code is in a relatively compact region of the
RFC, so you can read the text and skip the code, if you want, without
undue effort.

> - Because it was too big, it requires a stripper/parser, although a good
> power programmer can quickly macro-clean it up.  The RFCSTRIP tool, well,
> what language is that? I'm not an *nix person. So this adds to the
> complexity for the Windows shops to get at these hashing functions.  Of
> course, its a piece of cake for a sharp programmer, but even the sharpest
> knives eventually get dull.

This is just nonsense. If you are going to do anything serious with
code, you need a source code editor. With that, it is no big deal to
extract and test the code. Although I would agree that making the
RFCSTRIP tool available over the web, as many other tools are, would
be reasonable.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> --
> HLS
>
>
> On 6/28/2013 4:53 AM, Dearlove, Christopher (UK) wrote:
>>
>> I'd actually tried the authors, but no reply yet (only a few days). I also
>> tried the RFC Editor thinking they might have e.g. XML from which extraction
>> might have been easier, but also no response yet. And I had found several
>> libraries, but not the RFC code. I can't see any suggestion that the library
>> you indicate includes that code, it also bills itself as a C++ library,
>> which the RFC code is not (and also not what I want, but that's not a
>> subject for this list).
>>
>> But the broader point is that if it's worth the IETF publishing the code
>> as an RFC, it's worth making the code available straightforwardly.
>>
>> For me, a thanks to Tony Hansen, who did the extraction for me. (That
>> makes me feel a little guilty, why should he do my work I could have done?)
>> But the point of posting on this list was to say that the code should be
>> available so that each person wanting that code doesn't have to do that
>> again.
>>
>> Christopher
>>
>

From mrex@sap.com  Fri Jun 28 17:59:22 2013
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 913AE21F9DBB for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 17:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.649
X-Spam-Level: 
X-Spam-Status: No, score=-9.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_HI=-8]
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 U5t1lhzXE59v for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 17:59:18 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 2051921F9DBA for <ietf@ietf.org>; Fri, 28 Jun 2013 17:59:17 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r5T0xDqt012021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 29 Jun 2013 02:59:13 +0200 (MEST)
Subject: Re: RFC 6234 code
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Date: Sat, 29 Jun 2013 02:59:13 +0200 (CEST)
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: <20130629005913.81E691A868@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: "ietf@ietf.org" <ietf@ietf.org>
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: Sat, 29 Jun 2013 00:59:22 -0000

Dearlove, Christopher (UK) wrote:
>
> I'd actually tried the authors, but no reply yet (only a few days).
> I also tried the RFC Editor thinking they might have e.g. XML
> from which extraction might have been easier, but also no response yet.

Extracting code from text is pretty trivial.

Use copy&paste from the output of below simple perl script
(which removes the pagebreaks):


-Martin


#!/usr/bin/perl
#
$rfcnum="6234";
$footerpattern="^Eastlake";
$headerpattern="^RFC ${rfcnum}";

$url = "http://tools.ietf.org/rfc/rfc${rfcnum}.txt";

open(IN,"curl '${url}'|")
  || die("Download of \"$url\" failed: $!\n");
@doc  = ();
$show = 2;
while($line = <IN>) {
    $line =~ tr/\r\n//d;
    if ( $line =~ m/${footerpattern}/io ) {
        $show = 0;
        while ( $doc[$#doc] eq "" ) {
            pop(@doc);
        }
    }
    if ( $show>0 ) {
        if ( 2==$show || $line ne "" ) {
            push(@doc, $line);
            $show = 2;
        }
    }
    if ( 0==$show && $line =~ m/^${headerpattern}/ ) {
        $show = 1;
    }
}

close(IN);

print join("\n",@doc), "\n";



From mrex@sap.com  Fri Jun 28 18:46:40 2013
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 E6E6321F9E06 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 18:46:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.349
X-Spam-Level: 
X-Spam-Status: No, score=-9.349 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_HI=-8]
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 WrQWGsYdYdI7 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 18:46:36 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 8795321F9E04 for <ietf@ietf.org>; Fri, 28 Jun 2013 18:46:36 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r5T1kVhH016575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 29 Jun 2013 03:46:31 +0200 (MEST)
Subject: Re: RFC 6234 code
In-Reply-To: <20130629005913.81E691A868@ld9781.wdf.sap.corp>
To: mrex@sap.com
Date: Sat, 29 Jun 2013 03:46:31 +0200 (CEST)
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: <20130629014631.A20F81A869@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: rfc-interest@rfc-editor.org, "ietf@ietf.org" <ietf@ietf.org>
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: Sat, 29 Jun 2013 01:46:41 -0000

Martin Rex wrote:
> Dearlove, Christopher (UK) wrote:
> >
> > I'd actually tried the authors, but no reply yet (only a few days).
> > I also tried the RFC Editor thinking they might have e.g. XML
> > from which extraction might have been easier, but also no response yet.
> 
> Extracting code from text is pretty trivial.
> 
> Use copy&paste from the output of below simple perl script
> (which removes the pagebreaks):

Modified script which also does the extraction of the files
into the current directory as well (below).

  cc -c shatest.c sha1.c sha224-256.c sha384-512.c usha.c hmac.c hkdf.c
  cc -o shatest shatest.o sha1.o sha224-256.o sha384-512.o usha.o hmac.o hkdf.o
  ./shatest

it seems to work (for me on Linux, at least)

-Martin



#!/usr/bin/perl
#
$rfcnum="6234";
$footerpattern="^Eastlake";
$headerpattern="^RFC ${rfcnum}";

$url = "http://tools.ietf.org/rfc/rfc${rfcnum}.txt";

open(IN,"curl '${url}'|")
  || die("Download of \"$url\" failed: $!\n");
@origdoc = <IN>;
close(IN);

@doc  = ();
$show = 2;
$fname = "";
@file = ();

foreach $line ( @origdoc ) {

   $line =~ tr/\r\n//d;
   if ( $line =~ m/${footerpattern}/io ) {
      $show = 0;
      while ( $#doc >=0 && "" eq $doc[$#doc] ) {
         pop(@doc);
      }
      while ( $#file>=0 && "" eq $file[$#file] ) {
         pop(@file);
      }
   }
   if ( $show>0 ) {
      if ( 2==$show || $line ne "" ) {
         push(@doc, $line);
         $show = 2;
         if ( $fname eq "" && $line =~ m#^/\*\*.* (\w.+) \*\*#io ) {
            $fname = $1;
            $fname =~ tr/a-zA-Z0-9._-//cd;
            @file  = ();
         }
         if ( "" ne $fname ) {
            if ( $line =~ m/^\d/io ) {
               $filedata = join("\n",@file) . "\n";
               $filelen  = length($filedata);
               printf("Writing file \"$fname\" (len=${filelen})\n");
               open(OUT,">$fname")
                 || die("Could not write file \"$fname\": $!\n");
               print OUT $filedata;
               close(OUT);
               $fname = "";
            } else {
               push(@file, $line);
            }
         }
      }
   }
   if ( 0==$show && $line =~ m/${headerpattern}/io ) {
      $show = 1;
   }
}

# print join("\n",@doc), "\n";


From abdussalambaryun@gmail.com  Fri Jun 28 22:18:48 2013
Return-Path: <abdussalambaryun@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 79D7721F9E5A for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 22:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 VnBlIZ8TLmaD for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2013 22:18:47 -0700 (PDT)
Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id B280821F9E58 for <ietf@ietf.org>; Fri, 28 Jun 2013 22:18:47 -0700 (PDT)
Received: by mail-pb0-f43.google.com with SMTP id md12so2965654pbc.30 for <ietf@ietf.org>; Fri, 28 Jun 2013 22:18:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=1/XuxMV5BWUBnETP+m00TKy2VY7lI9W/tKTc+spNG1o=; b=hEyN+TajqGiP6s1d4bXEJ81JnF2UxwfRjeI9INmKz/0MeQm9cfHMaLzqec538jQ16A v3J/dNrKMzRycpB7R3wuaWBLUiIE5viQLqH+weBEjrBm+tSP0AXJ++hW744yAIMoYgjj 8SarOM1v3Udeq98emSCHDhvnlkmLRkhIXaYZ/+ErWCwDG5YOD5I5l85uZnvD4R2YIF9F ZO/MDzgFoQMZQH+N4Loo/HABYsVQaBG6LZLah9nXSbOv7UXWQwUy5SmBFUYei6ENUgC7 sP+hVC04Flb5q1RC8JOmm/FMQubtgSWV6UAWa+RW7jPg3dWvHa3Esqbt5iEr8eQlSx0v wPcg==
MIME-Version: 1.0
X-Received: by 10.66.221.101 with SMTP id qd5mr14402610pac.174.1372483127340;  Fri, 28 Jun 2013 22:18:47 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Fri, 28 Jun 2013 22:18:47 -0700 (PDT)
Date: Sat, 29 Jun 2013 07:18:47 +0200
Message-ID: <CADnDZ88zC8PCY9rLZA3btffhiKT7YdxjrE6QTKYbm1gxqDwTbA@mail.gmail.com>
Subject: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re: The Nominating Committee Process: Eligibility)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <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: Sat, 29 Jun 2013 05:18:48 -0000

This message is reply to an author of a new draft under ietf discussion.
If this list is not the correct place to discuss such matter, then the
list's responsible Chair is required to give details of where to
discuss such new work.
+++++++++++++++++++++++++++++++++++++++++++++++++

Hi Moonesamy,
(the Author of draft-moonesamy-nomcom-eligibility-00)

I think the draft still needs more details, for example, the Abstract
says to give remote contributors eligible to serve but how many
remote, it is not-reasonable/not-practical to have most remote, and it
is not fare/diverse to have all not remote. Furthermore, you did not
mention diversity in the draft related to members selected.

AB> I prefer if you refer me, or the discussion list chair can refer
me to somewhere we can discuss this new draft. Please note that I was
told not to post more discuss messages on this list, so the chair or
you are required to respond on this issue related to discussing the
draft, because this may be my last post regarding this I-D.

AB> the update may need an informational draft (or better
introduction) like what [1] is doing, so if we know the information on
process challenges we will know the best practice. I like the [1]
draft I think it needs to be renewed including remote members
possibilities.
[1]  http://tools.ietf.org/id/draft-crocker-nomcom-process-00.txt

AB> you need to define *remote contributor* in the draft. When the
authors define it then I can amend or edit. You need to mention that
most of meeting of IETF per year are in one region which makes some
from other regions to contribute remotely.

Section 2> The section is not reasonable because you changed with no
strong reasons. Why you want to change totally, I recommend to add
idea not change. As to give opportunity to additional memebrs that are
remote. These additional memebrs will have a special condition. This
way you don't change the conditions for the current procedure of
selecting f2f memebrs, and you may limit the number of remote
contributors maybe 10 % of the total memebrs.

AB> suggest in Section 2> I suggest not to update the text of the RFC
but to add new rule for selecting few remote participants.

AB> you need to add what are the remote memebrs responsibilities,
because they may be similar or different than the other memebrs.

my answers to your questions below,

On Fri, Jun 28, 2013 at 1:50 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
>
> Hi Abdussalam,
>
>
> Thanks for explaining why you support the draft.  I am going to list some questions.  Please read them as points to consider.  There isn't any obligation to provide comments.

You mean the draft should consider,

>
>  - What is your opinion about helping the "pie get larger"?


No we don't want things to get larger for others to eat, we want
things to get smarter for others to use, share, and develop equally.

>
>
>  - What would be an acceptable way of determining whether someone
>    has been contributing to the IETF over a period of five meetings?

Where are the five meetings (is it a f2f meeting?)and what kind of
contributing you are asking?

>  - Dave Cridland suggested that working groups provide a smallish set of
>    volunteers each for the selection process.  Is it okay to leave it
>    to the working group chair to make the decision?

<I will send you discusses/answers offline>
I really want to focus questions related to the new draft not other
issues. Therefore, I think the draft needs to involve what was
discussed on the list (feedback). Updating this RFC procedure may need
more reasons than what was presented in the draft, I think it is nice
if you add more and change info to renew this draft for more further
discusses. Thanks.

AB

From adrian@olddog.co.uk  Sat Jun 29 01:21:32 2013
Return-Path: <adrian@olddog.co.uk>
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 A9C5F21F9E83 for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 01:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.455
X-Spam-Level: 
X-Spam-Status: No, score=-2.455 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599]
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 WX-fMORNH8aG for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 01:21:28 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id B4E8221F9E89 for <ietf@ietf.org>; Sat, 29 Jun 2013 01:21:27 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5T8LOPh011739;  Sat, 29 Jun 2013 09:21:24 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5T8LLWN011694 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 29 Jun 2013 09:21:21 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>
Subject: RE: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re: The Nominating Committee Process: Eligibility)
Date: Sat, 29 Jun 2013 09:21:16 +0100
Message-ID: <019101ce74a1$a1beb630$e53c2290$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac50oZcS1/+aCDEoTSaO7J1W9Hw0Gw==
Content-Language: en-gb
Cc: 'ietf' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Sat, 29 Jun 2013 08:21:32 -0000

> This message is reply to an author of a new draft under ietf discussion.
> If this list is not the correct place to discuss such matter, then the
> list's responsible Chair is required to give details of where to
> discuss such new work.

I have no idea what a "list's responsible chair" is, but there is an ITEF list
dedicated for the discussion of issues related to NomCom.

https://www.ietf.org/mailman/listinfo/ietf-nomcom

"This mailing list is a relocation of the mailing list used by the
(now-concluded)NomCom working group, and reopened for discussion of the cureent
proposals for revision of the Nomcom process."

> Please note that I was told not to post more discuss messages
> on this list

That is an interesting statement, IMHO. Had you said "requested", I would have
understood. Had you said "warned of the consequences if you continued to post in
a particular way", I would have known what was going on. But "told not to post"
is, AFAIK only achievable through a posting ban, which you don't seem to have
received.

Adrian


From jnc@mercury.lcs.mit.edu  Sat Jun 29 05:24:46 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
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 CBDAB11E80E7 for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 05:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 WGmjt6Gksnf9 for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 05:24:41 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id C0E3F11E80E6 for <ietf@ietf.org>; Sat, 29 Jun 2013 05:24:41 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id ADFD218C0D8; Sat, 29 Jun 2013 08:24:38 -0400 (EDT)
To: ietf@ietf.org
Subject: RE: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re: The Nominating Committee Process: Eligibility)
Message-Id: <20130629122438.ADFD218C0D8@mercury.lcs.mit.edu>
Date: Sat, 29 Jun 2013 08:24:38 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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: Sat, 29 Jun 2013 12:24:46 -0000

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

    > "told not to post" is, AFAIK only achievable through a posting ban,
    > which you don't seem to have received.

Yet.

	Noel

From jnc@mercury.lcs.mit.edu  Sat Jun 29 05:28:57 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
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 0367E21F9A31 for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 05:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 cU6VSutLG3xf for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 05:28:52 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id EC16421F99EE for <ietf@ietf.org>; Sat, 29 Jun 2013 05:28:51 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id A685A18C0D8; Sat, 29 Jun 2013 08:28:51 -0400 (EDT)
To: ietf@ietf.org
Subject: RE: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re: The Nominating Committee Process: Eligibility)
Message-Id: <20130629122851.A685A18C0D8@mercury.lcs.mit.edu>
Date: Sat, 29 Jun 2013 08:28:51 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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: Sat, 29 Jun 2013 12:28:57 -0000

    > From: jnc@mercury.lcs.mit.edu (Noel Chiappa)

    > Yet.

PS: I probably should have added a ":-)" to that. Sorry, it's early, the
brain's not firing on all cylinders yet, and I was so entranced by the chance
to set the record for the shortest ever IETF list e-mail... :-)

	Noel

From dougb@dougbarton.us  Sat Jun 29 12:43:44 2013
Return-Path: <dougb@dougbarton.us>
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 B6C2621F9F48 for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 12:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[AWL=0.620,  BAYES_00=-2.599, 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 aj421RcDiTqj for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 12:43:44 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 45E3021F9B1B for <ietf@ietf.org>; Sat, 29 Jun 2013 12:43:44 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 8CDDE22B13 for <ietf@ietf.org>; Sat, 29 Jun 2013 19:43:39 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1372535019; bh=fPCXgXOVd1eA+SAkX0YNPLpjU+HrTNI1p4UvwnlLNi4=; h=Date:From:To:Subject:References:In-Reply-To; b=LrdXQyF57l4H2FUQSPE7/ryVZX08WFqKzTT2gUC48qGLtG1HSeWUkTvODyvk/nzgi 4dZGLSjiZ1OdU/bW57LJy8rbIBvfq5UzgWWbwZxjWKUIhJb8qNzY0F/bRIvLbO65pY CzYthGT2FBQArzbffdpOJq3a00CyLNYtc+niOogc=
Message-ID: <51CF38EB.3080409@dougbarton.us>
Date: Sat, 29 Jun 2013 12:43:39 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re: The Nominating Committee Process: Eligibility)
References: <20130629122851.A685A18C0D8@mercury.lcs.mit.edu>
In-Reply-To: <20130629122851.A685A18C0D8@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 29 Jun 2013 19:43:44 -0000

On 06/29/2013 05:28 AM, Noel Chiappa wrote:
>      > From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
>
>      > Yet.
>
> PS: I probably should have added a ":-)" to that. Sorry, it's early, the
> brain's not firing on all cylinders yet, and I was so entranced by the chance
> to set the record for the shortest ever IETF list e-mail... :-)

No.


From johnl@iecc.com  Sat Jun 29 13:02:15 2013
Return-Path: <johnl@iecc.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 8A0A121F9F84 for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 13:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.479
X-Spam-Level: 
X-Spam-Status: No, score=-109.479 tagged_above=-999 required=5 tests=[AWL=1.720, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 UsYx+1tLkcSc for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 13:02:11 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 261D621F9F7F for <ietf@ietf.org>; Sat, 29 Jun 2013 13:02:10 -0700 (PDT)
Received: (qmail 7061 invoked from network); 29 Jun 2013 20:02:10 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 29 Jun 2013 20:02:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51cf3d41.xn--btvx9d.k1306; i=johnl@user.iecc.com; bh=Qdm7rtuTDEsBDWJjtMLYhyNecJpki6tloYwyHnu8jL8=; b=c+wELkb46L2L6fxmiTHYt/W3xWk2iStjLUjX0b7UCNRA4AkeipS98daRdf9lk+Y/BKDn3gM1uLL71Mr6MMHYg/nlIIYhibU/xn4JOPonXXb+z5FhWc9MUCle1pU+GBk6YVdY8rzhX5DRBZvaWIvvgsrGMLW01OUxnX+KHK5yqH9ipP7DMZBW2BE8Ayh0elMI272dKsSEK6AI7NbQ4RfTAxuS2JSwDMvXpa8Pdxx7DjagOHLVONyWo28HU/a4TWAn
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51cf3d41.xn--btvx9d.k1306; olt=johnl@user.iecc.com; bh=Qdm7rtuTDEsBDWJjtMLYhyNecJpki6tloYwyHnu8jL8=; b=mB0TUVCqocP5E7/Onu/oRLXUDJrLc9t2GZFrfV9h5MK4tdn4qJVWbom5DLXWgk1IlgKkrc0quFKz5DS3Nx37qAO0SZU4X3o+m782Vii/f2Dj5k8nzQsEm1tMOsYTs43GHVbvKkARXSFS7rXtmEkr5v/NxoXbsZceTrqBs9flIb09sq8phDRJ52aPTx6AZgL7UBoDco7/HNwSUQMpKtIszoIa+gROTqwOFfMfFb+P+azk3a0WdbJME+2JxYcNKPme
Date: 29 Jun 2013 20:01:47 -0000
Message-ID: <20130629200147.98286.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re: The Nominating Committee Process: Eligibility)
In-Reply-To: <51CF38EB.3080409@dougbarton.us>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
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: Sat, 29 Jun 2013 20:02:15 -0000

In article <51CF38EB.3080409@dougbarton.us> you write:
>On 06/29/2013 05:28 AM, Noel Chiappa wrote:
>>      > From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
>>
>>      > Yet.
>>
>> PS: I probably should have added a ":-)" to that. Sorry, it's early, the
>> brain's not firing on all cylinders yet, and I was so entranced by the chance
>> to set the record for the shortest ever IETF list e-mail... :-)
>
>No.

?





From mstjohns@comcast.net  Sat Jun 29 13:30:42 2013
Return-Path: <mstjohns@comcast.net>
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 A076E21F9F2B for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 13:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.959
X-Spam-Level: 
X-Spam-Status: No, score=0.959 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  MIME_QP_LONG_LINE=1.396, RDNS_NONE=0.1]
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 0yTFS-w7NunQ for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 13:30:36 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id A43C821F9E42 for <ietf@ietf.org>; Sat, 29 Jun 2013 13:30:36 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta12.westchester.pa.mail.comcast.net with comcast id uLAJ1l0021ei1Bg5CLWblq; Sat, 29 Jun 2013 20:30:35 +0000
Received: from [192.168.1.13] ([68.188.153.34]) by omta24.westchester.pa.mail.comcast.net with comcast id uLW91l00i0knW983kLWEYV; Sat, 29 Jun 2013 20:30:30 +0000
References: <20130629122851.A685A18C0D8@mercury.lcs.mit.edu> <51CF38EB.3080409@dougbarton.us>
Mime-Version: 1.0 (1.0)
In-Reply-To: <51CF38EB.3080409@dougbarton.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <01635EAC-B3A1-41BD-B0B1-33A4C5749A78@comcast.net>
X-Mailer: iPad Mail (10B329)
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re: The Nominating Committee Process: Eligibility)
Date: Sat, 29 Jun 2013 16:30:11 -0400
To: Doug Barton <dougb@dougbarton.us>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1372537835; bh=5tySVFHSjyjHx4MgWAmSi8J+By54yrKY2wEwQKpA8P8=; h=Received:Received:Mime-Version:Content-Type:Message-Id:From: Subject:Date:To; b=eFWhCbheYTQ2R17fchY1n+MxTP4AtBJUxNLu4UeLNMsNyhWM9ZXTzm7K2LRQKBcxc a2ivXxcVKOxuGMx9b+IczWML7qiQQcieIijjOHrMfbeOcHpx2B2GJSuSZRhkixKFHU 7pymlsUe5wE7bdWJ6CJTbO5uENIyYHUrozlyu6wkpLdlsL+/ieh8kbMpz/j//KllAP BCmb/ku/3BVIMH4UaX2xValuWjtb1Pl9ZVTCa1DCkf0hKDmNn9q3ijsx6m5w+zxXrt 8xJo29bWpvvetWXJ5kL8CsikxZThDi/dpRjjFhZKqSnTSrZSRt/xHvcNwFLhDSokQ1 5BhIhOEkfmsLQ==
Cc: "ietf@ietf.org" <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: Sat, 29 Jun 2013 20:30:42 -0000

The shortest ietf email was sent at least 20 years ago, consisted of a singl=
e "!" as the body.  Of course the subject went on for two lines.   I forget w=
hat the subject was.  Mike

Sent from my iPad

On Jun 29, 2013, at 15:43, Doug Barton <dougb@dougbarton.us> wrote:

> On 06/29/2013 05:28 AM, Noel Chiappa wrote:
>>     > From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
>>=20
>>     > Yet.
>>=20
>> PS: I probably should have added a ":-)" to that. Sorry, it's early, the
>> brain's not firing on all cylinders yet, and I was so entranced by the ch=
ance
>> to set the record for the shortest ever IETF list e-mail... :-)
>=20
> No.
>=20

From brian.e.carpenter@gmail.com  Sat Jun 29 13:48:24 2013
Return-Path: <brian.e.carpenter@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 0ECAC21F8BCE for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 13:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level: 
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 acv3K2GIawgF for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 13:48:23 -0700 (PDT)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 46F2821F8BC0 for <ietf@ietf.org>; Sat, 29 Jun 2013 13:48:23 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id ma3so3426568pbc.7 for <ietf@ietf.org>; Sat, 29 Jun 2013 13:48:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MpTgb3eE5Ixa9LmOsqEuwCkjklcLPXA9WtxKIpyIsE0=; b=TJNP4B8DDZKDBuf7Iu8YXRyz+P7Fj7+sLac8ZdfL5MIpIBGU2le9WYP9K/IZN1ZD09 0gFW9OEQIeZYfdJqwgtEwN/4gfblP4NQ6Jn30cZrHJr2vbdjLsBU06dnUdf8opLDJ3kH fAI3Jwgr6is24JTOvG95diqNDIZpE9fnBjY4Cwx/fRCtTvdawvu/RikeD3luewvlXCyP aPWMP4aADwVftT657r8gHICSVcww6+4XgrxKmEzblnI5gENCOZY1a6AII1wlzNatXEKZ G4D2Exq9b4X6+pcXKvO+kiAqtNctq+jMEm6M6fC/ao6KOlaoTSFAKDS+EMbys4U8A/q2 fU+w==
X-Received: by 10.68.232.225 with SMTP id tr1mr16971842pbc.143.1372538903039;  Sat, 29 Jun 2013 13:48:23 -0700 (PDT)
Received: from [192.168.178.22] (163.197.69.111.dynamic.snap.net.nz. [111.69.197.163]) by mx.google.com with ESMTPSA id ve3sm14286018pbc.14.2013.06.29.13.48.21 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 29 Jun 2013 13:48:22 -0700 (PDT)
Message-ID: <51CF4813.6060101@gmail.com>
Date: Sun, 30 Jun 2013 08:48:19 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Evi Nemeth
References: <51CCC9B3.70606@gmail.com>
In-Reply-To: <51CCC9B3.70606@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Sat, 29 Jun 2013 20:48:24 -0000

Further bad news: no sighting and no debris after considerable searching.

http://www.bbc.co.uk/news/world-asia-23110736

Regards
   Brian Carpenter

On 28/06/2013 11:24, Brian E Carpenter wrote:
> Evi used to be an IETF regular. There is rather ominous news - she is
> lost at sea between New Zealand and Australia:
> 
> http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=10893482
> 
> http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=10893503
> 
> Regards
>    Brian Carpenter
> 
> 
> 

From john-ietf@jck.com  Sat Jun 29 14:25:23 2013
Return-Path: <john-ietf@jck.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 F2D3521F9F2B for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 14:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 R0S-k0VJa2ha for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 14:25:17 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 17BD421F9F1E for <ietf@ietf.org>; Sat, 29 Jun 2013 14:25:17 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ut2dt-000H4Y-Uo; Sat, 29 Jun 2013 17:25:13 -0400
Date: Sat, 29 Jun 2013 17:25:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joe Abley <jabley@hopcount.ca>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: RFC 6234 code
Message-ID: <438EE98A40654DA8CE169232@JcK-HP8200.jck.com>
In-Reply-To: <DB3A3E49-13C6-4CE3-87D5-8F86B37DFC57@hopcount.ca>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net> <51CD9987.8010401@att.com> <BEFC413A958E9B25913F2FE9@JcK-HP8200.jck.com> <D3A3A63A-0CB1-4254-A087-655F9BDA6CEC@vpnc.org> <DB3A3E49-13C6-4CE3-87D5-8F86B37DFC57@hopcount.ca>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: RFC Interest <rfc-interest@rfc-editor.org>, "ietf@ietf.org 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: Sat, 29 Jun 2013 21:25:23 -0000

--On Friday, June 28, 2013 16:41 -0400 Joe Abley
<jabley@hopcount.ca> wrote:

>> If you really think you see a legal difference in doing the
>> second, fine; I propose that you are just searching for
>> problems that do not exist.
> 
> Quite possibly they don't, and I'm not presuming to talk for
> John. But the vague thoughts that crossed my mine were the
> issues that allowed Phil Zimmerman to publish PGP source code
> in book form and avoid conviction for munitions export without
> a licence.

That was one of the examples I had in mind, along with a few
others.  

However, given Paul's extensive legal experience and knowledge
of the details and applicability of export regulations and
associated case law, I apologize for wasting the time of people
on the list by raising this obviously spurious issue.  I am
delighted that, on the basis of that knowledge and experience,
Paul was willing to step in on this issue and assure us that
there is nothing to worry about.

   john

From l.wood@surrey.ac.uk  Sat Jun 29 14:26:25 2013
Return-Path: <l.wood@surrey.ac.uk>
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 BBE1A21F9F5D for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 14:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=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 ia72VEXkkGGe for <ietf@ietfa.amsl.com>; Sat, 29 Jun 2013 14:26:21 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.174]) by ietfa.amsl.com (Postfix) with ESMTP id BE60421F9F5C for <ietf@ietf.org>; Sat, 29 Jun 2013 14:26:20 -0700 (PDT)
Received: from [195.245.230.131:58916] by server-14.bemta-3.messagelabs.com id E0/E8-12881-AF05FC15; Sat, 29 Jun 2013 21:26:18 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-78.messagelabs.com!1372541178!30074480!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11217 invoked from network); 29 Jun 2013 21:26:18 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-5.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 29 Jun 2013 21:26:18 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Sat, 29 Jun 2013 22:26:17 +0100
From: <l.wood@surrey.ac.uk>
To: <jnc@mercury.lcs.mit.edu>, <ietf@ietf.org>
Date: Sat, 29 Jun 2013 22:25:52 +0100
Subject: RE: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re:	The Nominating Committee Process: Eligibility)
Thread-Topic: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re:	The Nominating Committee Process: Eligibility)
Thread-Index: Ac50xEyF8U2u5wUtRTyszGr16JByqAASu7ZC
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EC8@EXMB01CMS.surrey.ac.uk>
References: <20130629122851.A685A18C0D8@mercury.lcs.mit.edu>
In-Reply-To: <20130629122851.A685A18C0D8@mercury.lcs.mit.edu>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Sat, 29 Jun 2013 21:26:25 -0000

-1

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Noel Chiap=
pa [jnc@mercury.lcs.mit.edu]
Sent: 29 June 2013 13:28
To: ietf@ietf.org
Cc: jnc@mercury.lcs.mit.edu
Subject: RE: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was R=
e:   The Nominating Committee Process: Eligibility)

    > From: jnc@mercury.lcs.mit.edu (Noel Chiappa)

    > Yet.

PS: I probably should have added a ":-)" to that. Sorry, it's early, the
brain's not firing on all cylinders yet, and I was so entranced by the chan=
ce
to set the record for the shortest ever IETF list e-mail... :-)

        Noel

From ron.even.tlv@gmail.com  Sat Jun 29 23:46:17 2013
Return-Path: <ron.even.tlv@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 C7D4521F9E0E; Sat, 29 Jun 2013 23:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.865
X-Spam-Level: 
X-Spam-Status: No, score=-1.865 tagged_above=-999 required=5 tests=[AWL=0.733,  BAYES_00=-2.599, HTML_MESSAGE=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 kkzT7OprMUdM; Sat, 29 Jun 2013 23:46:16 -0700 (PDT)
Received: from mail-ea0-x234.google.com (mail-ea0-x234.google.com [IPv6:2a00:1450:4013:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 8406121F9E2D; Sat, 29 Jun 2013 23:46:14 -0700 (PDT)
Received: by mail-ea0-f180.google.com with SMTP id k10so1474675eaj.39 for <multiple recipients>; Sat, 29 Jun 2013 23:46:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=a5AKKqHA8lQoKMEDEWHsncQlifonfwm77je6HtSQxnM=; b=HV+LsGLBWhiFa/uplePeE5TrNm9An7fNun8eTukZA4L5EqoPt6AH2iNEVlAj++EcJ6 FgtYK72Z7ExK+8ufpuJ/wDUCoBsWBgcmQRXxDLoWExKi8xQp3rmqv/EW32m6osfzB4iZ AvvW5tU0zA23fJsbw60SWlM67RXL3FYDLHynbJDYt4N7Cd7XRgNfzbMLXQO7XyAviZAP W4gf3hrT4XnBwts+Fbox1y8i7rRRg0cshR5M5HsE2WbytKl9H44GDkFrUJzJ+z11w1e8 Su++GobPuIo4QEUqrsI5qqlIX6PJcx8NTqINHCs82NMPDwFifYlmcazF37imIgF/AlDA z1ZQ==
X-Received: by 10.14.178.134 with SMTP id f6mr16079448eem.91.1372574773201; Sat, 29 Jun 2013 23:46:13 -0700 (PDT)
Received: from RoniE ([109.67.165.48]) by mx.google.com with ESMTPSA id i2sm21448812eeu.4.2013.06.29.23.46.10 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 29 Jun 2013 23:46:12 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-merkle-tls-brainpool.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-merkle-tls-brainpool-02
Date: Sun, 30 Jun 2013 09:44:45 +0300
Message-ID: <048001ce755d$505996e0$f10cc4a0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0481_01CE7576.75A76B20"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac51XUZ2uR+caSBhSvyQOZR9tzTtoA==
Content-Language: en-us
Cc: gen-art@ietf.org, 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: Sun, 30 Jun 2013 06:46:17 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0481_01CE7576.75A76B20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-merkle-tls-brainpool-02

Reviewer: Roni Even

Review Date:2013-6-30

IETF LC End Date: 2013-7-23

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as Standard track RFC.

 

 

Major issues:

 

Minor issues:

 

In section 1 you reference TLS 1.0 and 1.1 usage based on RFC 4492. What
about TLS 1.2 usage specified in RFC5246 A.7

 

 

 

Nits/editorial comments:

1.	In section 3 the  registry name is EC Named Curve
2.	In section 3 change "suitability" to "suitable"

 


------=_NextPart_000_0481_01CE7576.75A76B20
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:510795705;
	mso-list-type:hybrid;
	mso-list-template-ids:1559919828 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span>draft-merkle-tls-brainpool-02<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;6&#8211;30<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-7&#8211;23<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as Standard track =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
1 you reference TLS 1.0 and 1.1 usage based on RFC 4492. </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>What about =
TLS 1.2 usage specified in RFC5246 A.7<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>In =
section 3 the&nbsp; registry name is EC Named Curve<o:p></o:p></li><li =
class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>In section 3 change =
&#8220;suitability&#8221; to =
&#8220;suitable&#8221;<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0481_01CE7576.75A76B20--


From mike5guo@gmail.com  Sun Jun 30 01:37:17 2013
Return-Path: <mike5guo@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 61E4521F9DF7 for <ietf@ietfa.amsl.com>; Sun, 30 Jun 2013 01:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.246
X-Spam-Level: **
X-Spam-Status: No, score=2.246 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001, SARE_SUB_ENC_GB2312=1.345]
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 077Zjhg6G1K0 for <ietf@ietfa.amsl.com>; Sun, 30 Jun 2013 01:37:17 -0700 (PDT)
Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E97D621F9DC7 for <ietf@ietf.org>; Sun, 30 Jun 2013 01:37:16 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id j6so3796314oag.1 for <ietf@ietf.org>; Sun, 30 Jun 2013 01:37:16 -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 :content-type; bh=A48TKZYyOUAMsP4w1Yn0Oy7ASLl8iASDu4GNGRv7cGo=; b=fDAs52TwmYo0iOF8tyCtLCwiuKzzN0t9V31t/k51P4vWEUn2LnP8kv/oq3FyKJjnp5 aLJzMaHnXDE3b47ktoptmEEMtkRe3o+MnnvlHwYJECSEC3BkC9egdW/BQ7fZGGhwOxAH pUwyNxhsp6/OBbN65OI7iL+Kheg0Y51b60Rr+DaiNHD2k7NfoIP+5SX7nnRcvrHLjDxe 5M9EaqWrolXhEdYdmffdqcesV4Y+260HC/KjARJw77lnFv3VtFnG2ENCb4nYxz9ckyEp csrocudCQEoXpoK7vgrhadSyTeSoUvbwZjD/hCWC/64s5kbG7kGApVWMY9V7d+HB+Dd/ ImWQ==
MIME-Version: 1.0
X-Received: by 10.60.146.230 with SMTP id tf6mr7911370oeb.94.1372581436494; Sun, 30 Jun 2013 01:37:16 -0700 (PDT)
Received: by 10.182.250.130 with HTTP; Sun, 30 Jun 2013 01:37:16 -0700 (PDT)
In-Reply-To: <CAMFEDe5Zk3hGBLMikZRkQxL_fp2SMZhVCEy49_nnW9=93T-qvQ@mail.gmail.com>
References: <CAMFEDe5Zk3hGBLMikZRkQxL_fp2SMZhVCEy49_nnW9=93T-qvQ@mail.gmail.com>
Date: Sun, 30 Jun 2013 16:37:16 +0800
Message-ID: <CAMFEDe4ZOdab1cQYuOAsr5=DRNxOOEM6NgNEiPysGu9gSYRamw@mail.gmail.com>
Subject: =?GB2312?Q?Fwd=3A_Who_use_online_office_software_=2Csuch_as_Google_?= =?GB2312?Q?drive_=2CMicrosoft_office_365=2C_Do_you_think_it_need_break_the_?= =?GB2312?Q?information_island=A3=BF?=
From: Zhun Guo <mike5guo@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=047d7b5d301af2985a04e05b040b
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: Sun, 30 Jun 2013 08:37:17 -0000

--047d7b5d301af2985a04e05b040b
Content-Type: text/plain; charset=ISO-8859-1

Dear all,
Who use online office software ,such as Google drive ,Microsoft office 365,
Do you think it need break the information island (information silo)? I
have subitted a Internet-drafts about this topic :
The Interconnection and Interoperability of Different Cloud-office
Applications (IDCOA) with the HTML File Format ,
https://datatracker.ietf.org/doc/draft-guo-idoca-with-the-html-file-format/
 . Please give me more suggestion!
Best regards!

Zhun Guo

--047d7b5d301af2985a04e05b040b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_quote"><div dir=3D"ltr">Dear all,=
=A0<div>Who use online office software ,such as Google drive ,Microsoft off=
ice 365, Do you think it need break the information island (information sil=
o)? I have subitted a Internet-drafts about this topic :<br>

</div><h1 style=3D"font-size:22px;font-family:arial,helvetica,clean,sans-se=
rif;margin:0px 0px 0.5em">The Interconnection and Interoperability of Diffe=
rent Cloud-office Applications (IDCOA) with the HTML File Format ,<a href=
=3D"https://datatracker.ietf.org/doc/draft-guo-idoca-with-the-html-file-for=
mat/" style=3D"font-family:arial;font-size:small;font-weight:normal" target=
=3D"_blank">https://datatracker.ietf.org/doc/draft-guo-idoca-with-the-html-=
file-format/</a>=A0.<span style=3D"font-family:arial;font-size:small;font-w=
eight:normal;color:rgb(34,34,34)">=A0Please give me more suggestion!</span>=
</h1>

<div><span style=3D"font-family:arial;font-size:small;font-weight:normal;co=
lor:rgb(34,34,34)">Best regards!</span></div><span class=3D"HOEnZb"><font c=
olor=3D"#888888"><div><span style=3D"font-family:arial;font-size:small;font=
-weight:normal;color:rgb(34,34,34)"><br>

</span></div><div><span style=3D"font-family:arial;font-size:small;font-wei=
ght:normal;color:rgb(34,34,34)">Zhun Guo</span></div></font></span></div>
</div><br></div>

--047d7b5d301af2985a04e05b040b--

From scott.brim@gmail.com  Sun Jun 30 07:30:38 2013
Return-Path: <scott.brim@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 29AF021F9B35 for <ietf@ietfa.amsl.com>; Sun, 30 Jun 2013 07:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 S+Dz9Z5s7RnI for <ietf@ietfa.amsl.com>; Sun, 30 Jun 2013 07:30:37 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id B329521F9AAC for <ietf@ietf.org>; Sun, 30 Jun 2013 07:30:37 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id k7so3907207oag.37 for <ietf@ietf.org>; Sun, 30 Jun 2013 07:30:34 -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=5tQh8ByVmiwvHDgk3pjUh4gIA0AdiFLW8qmllXLMEY8=; b=JkIl3p/Krz3JM0CDM21xID9Y0IijeRbPj6ctM5f4NbAkzv3qWqXiSNXj9U5R9faDn5 Zzxh54td66BhF0GJXNw290NIqCPDfi8rJMarg8qo2CLl5HUpVCnUk9anmxmcU5GDNEDd z+S/TXkVUhCfqbe6GHDUN0hVFFVMt2+RAGSyAfGgR74VOx+vJPBmM85NQWTSTILujNr5 d/txlZVSoWESzCrq35C0kLSYRgSiwnbg3OKOMc1oCKzPs6CwiEaVdFomakKv3OM38j90 BKfUdAPEv1z7P05NCVpIxW7YVFXMM9GMQFJSD/bfF6iL5Rg2ZCNKTFkAlmOSBizlNHzw creg==
MIME-Version: 1.0
X-Received: by 10.60.135.167 with SMTP id pt7mr8270011oeb.59.1372602634435; Sun, 30 Jun 2013 07:30:34 -0700 (PDT)
Received: by 10.182.97.37 with HTTP; Sun, 30 Jun 2013 07:30:34 -0700 (PDT)
In-Reply-To: <51CF38EB.3080409@dougbarton.us>
References: <20130629122851.A685A18C0D8@mercury.lcs.mit.edu> <51CF38EB.3080409@dougbarton.us>
Date: Sun, 30 Jun 2013 10:30:34 -0400
Message-ID: <CAPv4CP_VzcNowyDOe=MDF6vKYX44G=znPuYAy+HVfN3TVb_r9w@mail.gmail.com>
Subject: Re: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re: The Nominating Committee Process: Eligibility)
From: Scott Brim <scott.brim@gmail.com>
To: Doug Barton <dougb@dougbarton.us>
Content-Type: multipart/alternative; boundary=047d7b3a849c71865c04e05ff4ee
Cc: "ietf@ietf.org" <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: Sun, 30 Jun 2013 14:30:38 -0000

--047d7b3a849c71865c04e05ff4ee
Content-Type: text/plain; charset=ISO-8859-1

Please someone find and share the UUCP message where the body said "I don't
understand the concern about too many message headers."

--047d7b3a849c71865c04e05ff4ee
Content-Type: text/html; charset=ISO-8859-1

Please someone find and share the UUCP message where the body said &quot;I don&#39;t understand the concern about too many message headers.&quot;

--047d7b3a849c71865c04e05ff4ee--

From jnc@mercury.lcs.mit.edu  Sun Jun 30 07:35:20 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
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 98FCC21F9B81 for <ietf@ietfa.amsl.com>; Sun, 30 Jun 2013 07:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 6y8haqSyRV3o for <ietf@ietfa.amsl.com>; Sun, 30 Jun 2013 07:35:16 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD2A21F9B5B for <ietf@ietf.org>; Sun, 30 Jun 2013 07:35:16 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 926C018C0BF; Sun, 30 Jun 2013 10:35:13 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re: The Nominating Committee Process: Eligibility)
Message-Id: <20130630143513.926C018C0BF@mercury.lcs.mit.edu>
Date: Sun, 30 Jun 2013 10:35:13 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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: Sun, 30 Jun 2013 14:35:20 -0000

    > From: Scott Brim <scott.brim@gmail.com>

    > Please someone find and share the UUCP message where the body said "I
    > don't understand the concern about too many message headers."

I don't know about there being a UUCP one, but here:

  http://www.chiappa.net/~jnc/humour/net.header

is the ARPANET one.

	Noel

From scott.brim@gmail.com  Sun Jun 30 08:09:08 2013
Return-Path: <scott.brim@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 F104B21F9638 for <ietf@ietfa.amsl.com>; Sun, 30 Jun 2013 08:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 DTJpmQbUIHQh for <ietf@ietfa.amsl.com>; Sun, 30 Jun 2013 08:09:08 -0700 (PDT)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 590AB21F962D for <ietf@ietf.org>; Sun, 30 Jun 2013 08:09:08 -0700 (PDT)
Received: by mail-ob0-f177.google.com with SMTP id ta17so3404670obb.22 for <ietf@ietf.org>; Sun, 30 Jun 2013 08:09:06 -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=OzSK3/0LrzpgR8VgnexvrGzWyiS/CBIepQzChAMnMw0=; b=J3E3j0NjEe5LQhnbDcU/9+Dv9H9J/Xz4yIhler1dhCrIa7rJoG2TbyyQHWldS1l0SH Xkqj/KcXLdOV2g+0/AT6Jpjki8lCISe0HvaJvJTlVXUSj5nIvT3rTPFZnjdh4CB/+zwc CjFVmNg/b+uWk3pxfGBXhleFjL/3bleJeKxd8LHJQiG9bWXkszfQOYdPtkK80o+LbqQx 5yKuAj2F1hcql/gppvfyXNIRcIorULUV90QpFQ7MVGl1alfAIj3NsQQT7Vl8uWW23n1t 1sU0jsv0AucyFd5XFLk4J3XYYtiIY4c0pccXwYpobAud3CnXWqZsJqm1ptd/s0CiGmM9 /giA==
MIME-Version: 1.0
X-Received: by 10.182.73.228 with SMTP id o4mr8082472obv.104.1372604946097; Sun, 30 Jun 2013 08:09:06 -0700 (PDT)
Received: by 10.182.97.37 with HTTP; Sun, 30 Jun 2013 08:09:06 -0700 (PDT)
In-Reply-To: <20130630143513.926C018C0BF@mercury.lcs.mit.edu>
References: <20130630143513.926C018C0BF@mercury.lcs.mit.edu>
Date: Sun, 30 Jun 2013 11:09:06 -0400
Message-ID: <CAPv4CP9w4rdRp9d0yTwhcgUVEjkh+rD2BiHTWnUv0YOew=sUTA@mail.gmail.com>
Subject: Re: Comments For I-D: draft-moonesamy-nomcom-eligibility-00 (was Re: The Nominating Committee Process: Eligibility)
From: Scott Brim <scott.brim@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary=089e011830603aaf1204e0607e5e
Cc: "ietf@ietf.org" <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: Sun, 30 Jun 2013 15:09:09 -0000

--089e011830603aaf1204e0607e5e
Content-Type: text/plain; charset=ISO-8859-1

On Sunday, June 30, 2013, Noel Chiappa wrote:

>     > From: Scott Brim <scott.brim@gmail.com <javascript:;>>
>
>     > Please someone find and share the UUCP message where the body said "I
>     > don't understand the concern about too many message headers."
>
> I don't know about there being a UUCP one, but here:
>
>   http://www.chiappa.net/~jnc/humour/net.header
>
> is the ARPANET one.
>
>         Noel
>

That was it, thanks!  I hope it's in the archives.

--089e011830603aaf1204e0607e5e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sunday, June 30, 2013, Noel Chiappa  wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">=A0 =A0 &gt; From: Scott Brim &lt;<a href=3D"javascript:;" onclick=3D=
"_e(event, &#39;cvml&#39;, &#39;scott.brim@gmail.com&#39;)">scott.brim@gmai=
l.com</a>&gt;<br>

<br>
=A0 =A0 &gt; Please someone find and share the UUCP message where the body =
said &quot;I<br>
=A0 =A0 &gt; don&#39;t understand the concern about too many message header=
s.&quot;<br>
<br>
I don&#39;t know about there being a UUCP one, but here:<br>
<br>
=A0 <a href=3D"http://www.chiappa.net/~jnc/humour/net.header" target=3D"_bl=
ank">http://www.chiappa.net/~jnc/humour/net.header</a><br>
<br>
is the ARPANET one.<br>
<br>
=A0 =A0 =A0 =A0 Noel<br></blockquote><div><br></div><div>That was it, thank=
s! =A0I hope it&#39;s in the archives.=A0</div>

--089e011830603aaf1204e0607e5e--
